target/JHEMCUF435: fix UART7 ESC telemetry defaults#11641
Conversation
…zzer-ignore-fix dshot beeper ignore list fix
Release/9.1 to master
Branch Targeting SuggestionYou've targeted the
If This is an automated suggestion to help route contributions to the appropriate branch. |
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
Test firmware build ready — commit Download firmware for PR #11641 1 targets built. Find your board's
|
|
Thank you for this. |
PR Description
Summary
This PR fixes missing ESC telemetry on
JHEMCUF435by correcting the FC target UART configuration and adding target default serial mapping.Root cause
This issue exists on both sides of the telemetry path:
ESC firmware side (AM32)
A related fix is here: f421: honor USE_PA14_TELEMETRY for serial telemetry am32-firmware/AM32#373
That PR addresses the ESC-side (all target that using MCU AT32F421 with telemetry at PA14) telemetry issue.
FC firmware side (this PR)
The
JHEMCUF435target was missing:USE_UART7_PIN_SWAPAs a result,
ESCSERIALcould be configured logically, but UART7 was still routed to the wrong physical pins for this board.What this PR changes
1. Fix UART7 pin routing for
JHEMCUF435Adds:
#define USE_UART7_PIN_SWAPThis ensures UART7 uses the correct physical routing for ESC telemetry on this target.
2. Add default target serial configuration
Adds a target
config.cso this board comes up with sane defaults:RX_SERIAL -> USART2ESCSERIAL -> USART7This avoids requiring manual remapping after flashing and makes the target work correctly out of the box for this wiring layout.
Why both fixes matter
Telemetry was blocked by a combination of:
Fixing only one side is not sufficient for a complete working telemetry path.
Validation
With:
AM32#373ESC telemetry is now received correctly through the FC and is forwarded successfully to the TX.