[Bug] Dronecan Firmware Updating is Broken on Main #23727
Assignees
Labels
Comments
|
This is updating via the PX4 SD card? I wasn't aware of that method and always used the gui tool with a USB to CAN tool. |
|
The main way I've always been updating firmware over CAN has been from the PX4 SD card. Most customers use this method as well since not many people have USB to CAN adapters. |
|
Makes sense. I will have to test this and fix it. |
|
This issue has been mentioned on Discussion Forum for PX4, Pixhawk, QGroundControl, MAVSDK, MAVLink. There might be relevant details there: |
dagar
added a commit
that referenced
this issue
Oct 16, 2024
…ory) - upstream libuavcan was broken and then marked deprecated, this fully absorbs the submodule (renamed libdronecan to deconflict) up to our last good working commit and all commit history is kept - fixes #23727 (regression introduced in #23113) - this puts us in a much better position to evolve the library as needed now that we have full control
dagar
added a commit
that referenced
this issue
Oct 16, 2024
…ory) - upstream libuavcan was broken and then marked deprecated, this fully absorbs the submodule (renamed libdronecan to deconflict) up to our last good working commit and all commit history is kept - fixes #23727 (regression introduced in #23113) - this puts us in a much better position to evolve the library as needed now that we have full control
dagar
added a commit
that referenced
this issue
Oct 17, 2024
…ory) (#23819) - fully absorb the libuavcan submodule (renamed libdronecan to deconflict) up to our last good working commit and preserve all history (upstream libuavcan was broken and then marked deprecated) - fixes #23727 - this puts us in a much better position to be able to evolve the library going forward ow that we have full control in tree
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Firmware updating on 1.15 works but is broken on main after the Dronecan submodule update. Nodes fail the update then the update restarts and fails again indefinitely.
To Reproduce
No response
Expected behavior
No response
Screenshot / Media
No response
Flight Log
No response
Software Version
No response
Flight controller
No response
Vehicle type
None
How are the different components wired up (including port information)
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: