-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
USE_MSP_UART does not activate MSP on UART1 #13642
Comments
When passing a value for a macro through EXTRA_FLAGS we need to use single quotes, e.g. to set USART1 we could use
When using the configurator to start a cloud build the value can be placed in the "Custom Defines" text box as
|
I see. |
betaflight/src/main/io/serial.c Lines 211 to 216 in 9d4ebda
Have not tested this application. Maybe this combination works: EXTRA_FLAGS="-DUSE_MSP_UART -D'MSP_UART=SERIAL_PORT_USART1'" |
No need to overcomplicate things: make [TARGET] EXTRA_FLAGS="-DMSP_UART=SERIAL_PORT_USART1" Works like a charme, I have just tested. Configurator cloud build also work with |
Thanks for testing. Did not think about this application while adding as now we can use other ports for MSP. Also found the change |
I came across this because I found out that all FCs can also be flashed with the STM32CubeProgrammer and a simple USB/TTL Converter via UART1 and 3 without further requirements, keyword broken USB port. |
Describe the bug
If compiled with the extra flag "USE_MSP_UART", MSP is not activated on UART1.
/src/main/io/serial.c, Line 211
The Argumet for
serialFindPortConfigurationMutable
should beSERIAL_PORT_USART1
, if i'am right?To Reproduce
Compile with
EXTRA_FLAG=-DUSE_MSP_UART
Expected behavior
MSP is activted on UART1
Support ID
Flight controller
ALL
Other components
No response
How are the different components wired up (including port information)
No response
Add any other context about the problem that you think might be relevant here
No response
The text was updated successfully, but these errors were encountered: