Inav: Anyone willing to test my firmware target for Heli-Nation Talon F7 Fusion?

Created on 26 Dec 2019  路  4Comments  路  Source: iNavFlight/inav

Hi,

I managed to compile and make iNAV configurator recognise my flight controller Heli-Nation Talon F7 Fusion. On iNAV configurator it seems to be working. Here is my branch (the target name is CLRACINGF7 to keep the same name as from Betaflight):
https://github.com/ricardodeazambuja/inav/tree/talonf7fusion

I compiled it using the docker recipe from iNAV:

docker run --rm -v "$(pwd)":/home/src/ inav-build make TARGET=CLRACINGF7

Converted it to raw bin using (from inside the obj directory):

docker run --rm -v "$(pwd)":/home/src inav-build arm-none-eabi-objcopy -I ihex -O binary inav_2.3.0_CLRACINGF7.hex inav_2.3.0_CLRACINGF7.bin

and finally downloaded it to the flight controller using dfu-util (after starting the flight controller holding the DFU enabling button):

dfu-util -a 0 -s 0x08000000:leave -D inav_2.3.0_CLRACINGF7.bin

If you want to backup your original firmware, here is the command:

dfu-util -a 0 -U talonf7fusion_betaflight.bin -s 0x08000000:131072

Any help will be much appreciated ;)

DISCLAIMER: I haven't flown anything using it, so totally untested!

Cheers,

Ricardo

Inactive Support

Most helpful comment

Issue-Label Bot is automatically applying the label Support to this issue, with a confidence of 0.83. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

All 4 comments

Issue-Label Bot is automatically applying the label Support to this issue, with a confidence of 0.83. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

Ok, I learned how to fix the order of the motors and everything seems to work. Tested the motors, armed and disarmed on the bench, that kind of stuff. Now it "only" needs to fly to confirm that it really works :)

BTW, using the inav-configurator that installs as a chrome app (instead of running from the repo using "npm install" and "npm start .") allowed me to download the firmware to the flight controller directly from the generated .hex using inav-configurator firmware flasher and "Load Firmware (Local)", hurray!

I was almost forgetting to mention my Python interface also seems to work with iNav... on this flight controller at least: https://github.com/ricardodeazambuja/YAMSPy
I'm curious if there's a bug on my code because the MSP V2 messages are much much slower to receive than MSP V1.

This issue / pull request has been automatically marked as stale because it has not had any activity in 60 days. The resources of the INAV team are limited, and so we are asking for your help.
This issue / pull request will be closed if no further activity occurs within two weeks.

Automatically closing as inactive.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

PR31D picture PR31D  路  4Comments

seriousrob picture seriousrob  路  3Comments

mrcottonmouth picture mrcottonmouth  路  3Comments

Painless360 picture Painless360  路  4Comments

peteoz picture peteoz  路  3Comments