Selecting boot medium
The boot medium can be selected by DIP switch on the board. DIOT board can boot from QSPI, eMMC or microSD card.
NOTE: In most cases there is no need to change the boot source/medium.
NOTE: On the first bach of the boards, the DIP switches were not working as described on the board. For details see issue #211 (closed).
U-boot
Booting form network
By default DI/OT board will try to obtain from the DHCP server the IP address of the tftp server and the filename of an image. U-boot will try to retrieve the pointed image via TFTP. After the successful transfer the u-boot will try to run the retreived image as a script. If it fails, it will run as regular image.
Create script to be used by network booting
Create text file with valid uboot commands to be executed. E.g.:
echo "echo hello!" > boot_script.txt
Make a uboot image out of that file:
mkimage -A arm -O linux -C none -T script -n 'boot script' -d boot_script.txt boot_script.img
Updating boot images
BOOT.BIN
Updating To ease the update of u-boot image (boot.bin
) or kernel image (image.ub
) on different mediums there are several scripts available in the u-boot. For u-boot image:
update_boot_qspi_from_net
update_boot_mmc_from_net
update_boot_sd_from_net
update_boot_mmc_from_sd
update_boot_qspi_from_sd
Names are self-explanatory. To run these scipts type:
run <script_name>
E.g. run update_boot_qspi_from_net
updates the boot.bin
in QSPI memory.
image.bin
Updating Similar scripts are available to update image.ub
:
update_image_qspi_from_net
update_image_mmc_from_net
update_image_sd_from_net
update_image_qspi_from_sd
update_image_mmc_from_sd