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

Add KAKUTEF7 target #3868

Merged
merged 1 commit into from
Sep 17, 2018
Merged

Conversation

shellixyz
Copy link
Collaborator

@shellixyz shellixyz commented Sep 16, 2018

Closes #3855

Configurator update: iNavFlight/inav-configurator#573

@adamstern2000
Copy link

I have a kakute f7. The configurator 2.0.0 doesn’t have it as an option. How can I install? Thanks in advance.

@shellixyz
Copy link
Collaborator Author

@adamstern2000 You can test this dev build: inav_2.1.0_KAKUTEF7.hex.zip

You will need to run the latest configurator's master branch.

@adamstern2000
Copy link

adamstern2000 commented Dec 17, 2018 via email

@shellixyz
Copy link
Collaborator Author

The first RC for 2.1 should be released very soon

@adamstern2000
Copy link

adamstern2000 commented Jan 3, 2019 via email

@d4nieel d4nieel mentioned this pull request Jan 25, 2019
@PHMT
Copy link

PHMT commented Apr 14, 2019

Kakute F7 target in 2.1 stable does not appear to work for Kakute F7 non-AIO FC. INAV 2.1 flashes (with full erase) just fine to my Kakute F7 non-AIO, but INAV configurator will not connect afterwards (using INAV config 2.1.4). I get "no configuration received within 10 seconds, communication falied". Note that I have no issues flashing/re-flashing Betaflight 4.0 to this FC.

I also downloaded the kakuteF7.hex and tried flashing using Betaflight configurator. Flash went fine, but INAV still would not connect with same error.

If it only works for AIO version, I suggest adding "AIO" to the name (KakuteF7AIO). Or it would be nice if it worked for the non-AIO version too.

Edit: Never mind. It does work for the non-AIO version. My issue looks like it was a driver problem. I went back and re-flashed iNav and now iNav connected just fine after the flash. I spent hours yesterday and iNav would not connect. Now it did. What changed was in between, I had given up on iNav and flashed Arducopter and had downloaded Mission Planner. When Mission Planner installed, I noticed that it installed/re-installed some drivers and one of them was a STM driver. What ever drivers I had previously worked just fine for Betaflight, but apparently not iNav. I suspect that at least one of the drivers installed by Mission Planner was also what iNav needed. So now it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants