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
For <512k targets, ESC passthrough for non-BL Heli ESCs ESCs fails #11484
Comments
Removed due to firmware size |
@daleckystepan @SteveCEvans I think this is important for the use case. How much memory did this save? Do we have room to get it back? |
Enabling |
Yeah this really shows the end of 512K targets. Do we have still have some space left to support this method a little longer otherwise we can close it as |
Current master
and
It will probably fit but it is very tough - we will not be able to add something more (and maybe more important). On the other hand it's regression. GCC11 will help us slightly. |
🤞 it might be important for manufacturers and esc firmware development |
If we were to include this again, we would only have to remove something else. I'm sure manufacturers and firmware developers can include it and compile on their own |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week. |
Issue closed automatically as inactive. |
Describe the bug
Connection to passthrough ESCs using BF4.3+ fails with non-BL Heli ESCs due to a change in connection string format. The issue appears within RC1 of 4.3, appears to be a compile-time define (USE_SERIAL_4WAY_SK_BOOTLOADER) which affects the connection string format is now guarded by a flash_size check. Imagine below shows the changes.
https://github.com/betaflight/betaflight/commit/82b5e386f39465905c6dbdecbe2e1ee744efe000
Is it possible to reverse this change, or is there a reason for this protocol change?
Thanks!
To Reproduce
Install BF4.3 onto FC, attempt ESC passthrough configurator connection to non BLHeli, non-SK ESC. No issues with prior versions of BF (4.2x).
Expected behavior
USE_SERIAL_4WAY_SK_BOOTLOADER macro remains defined as per previous versions of BF releases.
Flight controller configuration
Flight controller
FC Invariant (reproduced on multiple)
Other components
No response
How are the different components wired up
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: