5.2 FC firmware dev - terrytaylorbonn/auxdrone GitHub Wiki
24.0528 I hate it when this happens, but i am kind of lost on this page... these file. I was going to have FC FW dev in several sections, but moved it all here (new use not want to do firmware dev).
after i get the copters all flying (sbee -- inav, bf, (AP); pix -- px4, (ap)), then come back to this section to clean all this up. i think the idea is all fw dev in one place.
24.0508 TERRY: here focus on modifying PX4 firmware.
24.0505 got my first px4 (px4 = copter firmware) custom module working
see
- (Gdrive) 5.2-1_MODIFY_PX4_UBU_(mine-works_v04_24.0512.docx (added hello sky)
my goal in new few months is to
-
make more px4 mods (small ones) to understand how it works.
-
focus on understanding mavlink/mavsdk, uart interfaces, etc
-
goal is (among other things) stealth mode (control drone over a wire, no wireless xmissions)
-
5.2b_4.4-1_build_fw_(all)_v02_24.0430_0517.docx
this came from 4.4
How to build the firmware
- 4.4-1_BUILD_FW_(overview, notes, theirs, etc)_v01_24.0430.docx
- 4.4-2_BUILD_PX4_UBU_(mine-works)_v04_24.0512.docx
- 4.4-X_px4_firmware_reinstall_24.0328.docx
- Gdrive.
24.0517
all builds (px4, BF, ardu, etc) all in one file now 4.4-1_build_fw_(all)_v02_24.0430_0517.docx
Hello sky, etc... new modules.. this is all in mission platform dev 5.2_ files.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
How to build the firmware
with different modules included First build (this actually includes the "hello sky" custom mod... but just building the firmware would be the same... just leave out the "hello sky" stuff... need to modify this doc later to show just building with specified modules, not creating new modules (not sure if this makes sense :) ) ):
4.4-2_BUILD_PX4_UBU_(mine-works)_v04_24.0512.docx
=== clean this up later ==================================
ardu?
can you do this for
- BF
- INAV
DISTILL THIS >>>>>>>>>>>>>>>>>
For details see the following docs on my Gdrive 8_eth_drone (these docs became part of a new project 8_eth_drone).