Repository navigation
Noble NB4+: internal RF module is on USART6 (PC6/PC7), not USART3 - findings from the stock firmware #7912
Replies: 4 comments 2 replies
|
cc @richardclli – you wrote the NB4+ hardware mod guide and mentioned that you were still working on usable TX modules for the NB4+. The findings above (internal RF on USART6 / PC6-PC7, power via PD11/PI8) might be relevant for that. |
|
Seems you are working on something interesting. Did you managed to make the original internal module working properly? As I know the internal module did not have compatible firmware for EdgeTX. |
|
NB4+ status update + an open CE/FCC question ApexTX ( I did a static trace of the stock FlySky firmware (1.0.22 EU FCC app + its NOR package) to find how the radio sets the regional RF standard, hoping ApexTX could offer a CE/FCC selector. Findings:
Net: on the NB4 internal path, nothing transmitter-side sets CE/FCC; the region looks module/hardware/runtime-governed. EdgeTX/ApexTX already carries Open question — can anyone help? Does the NB4 internal RF module honour an |
|
I don't think you can put the internal module for any use. Flysky told me that the firmware in the internal module is a RF command passthrough design, and the AFHDS3 protocol is implemented in the main stock firmware but not in the TX MCU. And I have checked with Flysky if they can port the EL18 internal module firmware to the STM32F030 chip, and the fact is it did not fit, the firmware too big to fit in a STM32F030, it need a STM32FF072 to run. And STM32F030 and STM32F072 is not pin compatible, so you cannot change the mcu and make it works. |
Uh oh!
There was an error while loading. Please reload this page.
The NB4P target currently maps the internal module to USART3 (PB10/PB11) with
PI8 as power, and the NB4+ internal RF is listed as unsupported. I compared the
stock FlySky firmware of the NB4+ (1.0.22) and the original NB4 (2.0.116) and
found the following, which may help get the internal RF working:
USART6, PC6/PC7, 1.5 Mbaud, 8N1. USART3 on PB10/PB11 is configured as
well but only selected for one special per-model mode.
and PI8 high (same on NB4 and NB4+).
ApexTX (GPL fork of EdgeTX for the NB4) already implements it for the NB4:
https://github.com/GastonGelhorn/apextx
sequence and default receiver configuration blocks.
More details, including the board comparison (ADC map, keys, battery,
charging, display) and how the analysis was done:
https://github.com/Semtexmagix/apextx/blob/nb4plus-hw/docs/nb4plus/README.md
Tests and results:
https://github.com/Semtexmagix/apextx/blob/nb4plus-hw/docs/nb4plus/TEST_RESULTS.md
None of this has been tested on hardware yet; I am sharing it so that someone
with an NB4+ and the right setup can verify it.
All reactions