mirror of
https://github.com/iNavFlight/inav.git
synced 2025-07-25 17:25:18 +03:00
Output more information in MSP_BOARD_INFO
- Report wether the board has OSD support - Report wether the board uses VCP - Include the full target name in the response
This commit is contained in:
parent
2bcdc23752
commit
947bb3df77
1 changed files with 19 additions and 0 deletions
|
@ -310,6 +310,25 @@ static bool mspFcProcessOutCommand(uint16_t cmdMSP, sbuf_t *dst, mspPostProcessF
|
|||
#else
|
||||
sbufWriteU16(dst, 0); // No other build targets currently have hardware revision detection.
|
||||
#endif
|
||||
// OSD support (for BF compatibility):
|
||||
// 0 = no OSD
|
||||
// 1 = OSD slave (not supported in INAV)
|
||||
// 2 = OSD chip on board
|
||||
#if defined(USE_OSD) && defined(USE_MAX7456)
|
||||
sbufWriteU8(dst, 2);
|
||||
#else
|
||||
sbufWriteU8(dst, 0);
|
||||
#endif
|
||||
// 1 = USE_VCP, 0 = no VCP
|
||||
// This way the configurator can find wether a board
|
||||
// uses VCP without relying on a board list.
|
||||
#ifdef USE_VCP
|
||||
sbufWriteU8(dst, 1);
|
||||
#else
|
||||
sbufWriteU8(dst, 0);
|
||||
#endif
|
||||
sbufWriteU8(dst, strlen(targetName));
|
||||
sbufWriteData(dst, targetName, strlen(targetName));
|
||||
break;
|
||||
|
||||
case MSP_BUILD_INFO:
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue