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

[Bug Report] Enabling GPS or GPS+Telemetry in Configurator sandbags flight controller requiring reflash of firmware. #655

Closed
BeauBrewski opened this issue Jul 26, 2021 · 8 comments · Fixed by #850
Assignees
Labels
bug Something isn't working hacktoberfest

Comments

@BeauBrewski
Copy link
Collaborator

BeauBrewski commented Jul 26, 2021

Describe the bug

  1. Fresh configure of MatekF405SE works until GPS is enabled in configurator and saved. Then cannot reconnect to fc unless booted in DFU mode and reflashed. Confirmed works in BF. Tried on 0.3.3 and 0.3.4.
  2. Fresh configure of KakuteF7 HD works until GPS and Telemetry are both enabled in configurator and saved. One or the other on is fine. Then cannot reconnect to fc unless booted in DFU mode and reflashed.

To Reproduce

  1. On MatekF405SE, enable GPS in configurator, save/exit, unplug, and try to reconnect.
  2. On KakuteF7 HD, enable GPS and Telemetry in configurator, save/exit, unplug, and try to reconnect.

Expected behavior
Enabling of the GPS or GPS+Telemetry to save without sand bagging the flight controller, and being able to use features to fly long range with GPS and/or Telemetry.

Flight controller configuration
Need diff's from pilots reporting issue.

Setup / Versions

  1. FC: MatekF405SE
    GPS: Flywoo GM8 Mini V2
    Soldered to UART5
  2. FC: KakuteF7 HD
    Pilot speaks French.

Additional context

  1. MatekF405SE works in BF with no hardware changes. Emu was fresh install with no copying of BF diff or dump.
@nerdCopter nerdCopter added the bug Something isn't working label Jul 26, 2021
@nerdCopter
Copy link
Member

nerdCopter commented Jul 26, 2021

so many targets to confuse.
is kakute pilot using the proper target?
we have

KAKUTEF7
KAKUTEF7HDV
KAKUTEF7V15  (V2 in BF)
KAKUTEF7MINIV1
KAKUTEF7MINIV2
KAKUTEF7MINIV3

@BeauBrewski
Copy link
Collaborator Author

BeauBrewski commented Jul 26, 2021

Attempting to verify. Should be the KAKUTEF7HDV.
Edit: Verified to be the KAKUTEF7HDV, correct firmware.

@nonoreb
Copy link

nonoreb commented Jan 23, 2022

Hello,
Did you find any solution to this ? I have the same problem with KAKUTEF7V15, I have to reflash (0.4.0) because I can't acces fc anymore after enabling GPS.

@nerdCopter
Copy link
Member

Hello, Did you find any solution to this ? I have the same problem with KAKUTEF7V15, I have to reflash (0.4.0) because I can't acces fc anymore after enabling GPS.

try KAKUTEF7HDV & let us know.
if still fails, we need to investigate target resources and we request cli dumps of BF vs Emu.

@Kaiowarez
Copy link
Member

Kaiowarez commented Jan 25, 2022 via email

@nerdCopter
Copy link
Member

nerdCopter commented Aug 8, 2022

Needs testing: #850 (MATEKF405SE)

EmuFlight_0.4.1_MATEKF405SE_Build_6cc68df4e.hex.zip

@loutwice
Copy link
Contributor

@nerdCopter @Kaiowarez

hi buddieeees, @Kaiowarez did you get time to add gps driver for the kakute?

@nerdCopter
Copy link
Member

nerdCopter commented Oct 20, 2022

@loutwice , which target do you need. i suppose i can look. I have the MATEKF405SE .zip above, that was never tested by anyone. (we need feedback/validation)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working hacktoberfest
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants