How to extend the official firmware from a custom ROS package? #545
Replies: 2 comments 1 reply
-
Could you clarify what you mean by "link our custom firmware C code [...] to the official firmware" and "without any modifications on the official firmware code"? If you have custom C code, this automatically changes the firmware image. Please also clarify if the problem is in the building firmware step or the firmware flashing step. |
Beta Was this translation helpful? Give feedback.
-
You can simply keep the firmware external and compile it using make. If you want to flash it with chooser.py, you can specify the path to your firmware images, see crazyswarm/ros_ws/src/crazyswarm/scripts/chooser.py Lines 20 to 30 in 4d6ca47 The firmware in crazyswarm/crazyflie-firmware is only used to build Python bindings for the SIL simulation. These bindings will be part of the official firmware repository soon (see e.g., bitcraze/crazyflie-firmware#886). |
Beta Was this translation helpful? Give feedback.
-
We have created a custom ROS package based on the crazyswarm documentation, and it works successfully for our launch files and Python scripts. However, we can not find out how to link our custom firmware C code from the custom ROS package to the official firmware, build them together and upload to the Crazyflie. We would like to manage this without any modifications on the official firmware code.
Could you please help us?
Thanks in advance,
Peter
Beta Was this translation helpful? Give feedback.
All reactions