This is what I do to build the arducopter binary before loading it to the BBBlue.
git clone https://github.com/silver2row/ardupilot
git checkout Copter-4.2
git submodule update --init --recursive
git submodule update --init --recursuve, I perform these steps to directly load the building of the files to the BBBlue.
# This command is done in the /ardupilot/ directory.
python3 waf configure --board=blue --rsync-dest firstname.lastname@example.org:/home/debian
# This command is done in the /ardupilot/build/blue/ directory.
python3 ../../waf --target bin/arducopter --upload
I think this is how it is supposed to be done, i.e. after installing all the required building tools.
If you see what steps I am taking that may be incorrect, please let me know. I have been working on this project off and on for about three to four years and I have come up empty so far.
P.S. Oh! My .service file is like this idea:
Conflicts=arduplane.service ardurover.service antennatracker.service
ExecStart=/home/debian/more/bin/arducopter $TELEM1 $TELEM2 $GPS
and…the file I am using for making the build known to the service file for working on boot is this idea:
This .dtbo is not to be used, AM335X-PRU-UIO-00A0.dtbo, I think. I think the .dtb in /boot/uEnv.txt is already done and completed. So, one might not even need to call the .dtb for am335x-boneblue.dtb in /boot/uEnv.txt.
dtb=am335x-boneblue.dtb # Here is where I was using the .dtb at first.
###Overide capes with eeprom
uboot_overlay_addr0=AM335X-PRU-UIO-00A0.dtbo # This probably does not need to be in the file either.
and…Cape_Universal commented out like so:
#enable_uboot_cape_universal=1 # I am not sure if this file needs a comment or not.
If you are an avid ArduPilot, esp. around ArduCopter, user and have notes, please describe to me what exactly I am doing incorrectly…