This page covers the daughterboard configuration for a demo flight. First, make sure you upload the flight computer
Follow instructions written here
Follow the instructions from here.
A few notes about the uploading. For debugging it is possible to set up ftp on the GCS and dhcp file transfer on the TK1/uboot. This is a bit of a pain to set up on the host side (hence we don’t provide specific instructions), but works fine once going.
For the actual flight we use USB loading. That means we put a USB stick into the TK1 (into the blue usb port!). The USB has a file called sel4.img which contains the TK1 image. Then we have uboot configured to do a USB boot.
The uboot sequence is:
usb start load usb 0:1 0x81000000 sel4.img bootelf 0x81000000
NOTE: if your image has different name than sel4.img make sure to modify the command accordingly.
If that works you can save it as the default boot command with
setenv bootcmd "usb start; load usb 0:1 0x81000000 sel4.img; bootelf 0x81000000" saveenv
The sequence for booting the actual copter is:
Download the linux filesystem image from Dropbox here and unzip it.
Go into uboot and do:
ums mmc 0
This makes the EMMC available as a USB mass storage device. Then plug into the mini-USB port on the TK1. If you connect this to your computer you should see
/dev/sdb1 (or similar) which you can mount and read/write. You can wipe out what’s there already and replace it with the proper filesystem. Just use the
-r flag to cp to preserve permissions. Run
sync afterwatds to make sure all files got properly copied.
The files relevant for the demo flight are under
Follow the instructions from here