Skip to content
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

feat: Flysky Noble 4 Plus (NB4+) support #5095

Merged
merged 36 commits into from
Jan 24, 2025
Merged

feat: Flysky Noble 4 Plus (NB4+) support #5095

merged 36 commits into from
Jan 24, 2025

Conversation

richardclli
Copy link
Collaborator

@richardclli richardclli commented Jun 1, 2024

Flysky Noble 4 Plus (NB4+) Support

Development progress:

  • LCD drver
  • touch driver
  • ST, TH
  • pots
  • switches
  • trims
  • encoder (the hardware has 2 encoders, once mapped one currently, need some input to how to make use 2nd encoder)
  • audio
  • battery charging
  • internal module (STM32F030 MCU nothing good can be supported)
  • external module (Bluetooth USART3 port, mapped as internal module that can support MULTI/AFHDS3/CRSF)
  • modding documentation https://github.com/EdgeTX/edgetx/wiki/Flysky-NB4--Hardware-Mod-for-Complete-EdgeTX-Support

Known hardware limitations:

  1. No on board RTC support, missing battery and a few cap, diode, crystal components. (PL18 is a lot simpler, just need to add a battery)
  2. NOR flash is small (Only 8MB on board, can change the chip to maximum 128MB, same as PL18 mod)
  3. DAC sound output work out of the box without modding ^.^

@richardclli richardclli added this to the 2.11 milestone Jun 1, 2024
@richardclli richardclli changed the title feat(nb4p): Flysky Noble 4 Plus Support feat(nb4p): Flysky Noble 4 Plus (NB4+) Support Jun 1, 2024
@richardclli richardclli self-assigned this Jun 1, 2024
@pfeerick pfeerick changed the title feat(nb4p): Flysky Noble 4 Plus (NB4+) Support feat: Flysky Noble 4 Plus (NB4+) support Jun 1, 2024
@richardclli richardclli force-pushed the fs_nb4plus branch 2 times, most recently from c007856 to d307b41 Compare June 8, 2024 20:48
@richardclli richardclli force-pushed the fs_nb4plus branch 2 times, most recently from d5b505a to 6779428 Compare June 16, 2024 02:47
@richardclli richardclli force-pushed the fs_nb4plus branch 2 times, most recently from c966618 to c952b8b Compare June 28, 2024 04:36
@richardclli richardclli force-pushed the fs_nb4plus branch 4 times, most recently from 330b500 to 7ae769f Compare July 7, 2024 09:58
@richardclli richardclli force-pushed the fs_nb4plus branch 8 times, most recently from 8bfe593 to 0096da0 Compare July 19, 2024 02:01
@richardclli richardclli force-pushed the fs_nb4plus branch 6 times, most recently from 6f96397 to e1bbc88 Compare July 29, 2024 03:51
Copy link
Member

@pfeerick pfeerick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Functionally everything is looking good for the first round for this handset.

Obviously a few more details to figure out, such as using the second rotary encoder, trying to do something more with the build in internal module (i.e. PPM so it does something rather than nothing).

Two very minor cosmetic issues - bootloader green tick drew over text and Radio Settings -> Hardware -> Pots is not portrait friendly.

@pfeerick
Copy link
Member

Does this radio have a trainer port? As trainer thinks it can show master/slave jack settings.

Do the trim hats have anything more than the up/down outputs (electrically) - one axis does something, does the other do anything, and what about pressing on them - i.e. any TODOs there?

@gagarinlg
Copy link
Member

Some trims are not working
I get "missing or bad radio data" at every boot
I was not able to enter the bootloader
TR1 and TR2 have only one axis working
TR3 and TR4 do not work
I think the steering wheel should be reversed

@pfeerick
Copy link
Member

pfeerick commented Jan 24, 2025

  • Bootloader - you use the two buttons on each side the centre grip - SW1/SW2
  • bad or missing data - is the SPI flash formatted?
  • T3 should work - it is the main input rotary encoder - you can use it + SW1 and SW2 for UI input - scroll, enter, exit
  • T4 is the unused rotary encoder I referenced above

@gagarinlg
Copy link
Member

I did not format the flash, did it now, works better than before

@gagarinlg
Copy link
Member

  • Bootloader - you use the two buttons on each side the centre grip - SW1/SW2

    • bad or missing data - is the SPI flash formatted?

    • T3 should work - it is the main input rotary encoder - you can use it + SW1 and SW2 for UI input - scroll, enter, exit

    • T4 is the unused rotary encoder I referenced above

ok, then I think we should merge this,

@gagarinlg gagarinlg merged commit 81a469a into main Jan 24, 2025
51 checks passed
@gagarinlg gagarinlg deleted the fs_nb4plus branch January 24, 2025 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants