Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Custom_table_size_100 |
---|
Introduction
Expand | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
the industry standard "distro boot" boot flow for U-boot has been implemented as default by Xilinx. (see xilinx-wiki.atlassian "Using Distro Boot With Xilinx U-Boot") The distro boot functionality is implemented as an extension of the existing U-Boot bootcmd functionality in U-Boot. It extends its functionality by redirecting the call to bootcmd to a call to the distro_bootcmd variable.
Distro_bootcmd and Boot_targetsThe distro_bootcmd variable typically contains a sequence of commands that scans a pre-defined list of potential boot targets in search of boot collateral as shown below .in an snippet of the printenv
The boot_targets list is defined in the platform definition in the U-Boot source tree. Depending on the specifics of the target platform, the distro boot infrastructure can either use the boot_targets list to explicitly find specific boot collateral (eg. hard-coded loading once a valid boot target is located) or it can be used to locate some kind of decoupled configuration information. Boot Method Precedence The order of precedence for searching for boot components is as follows
Boot Method PrecedenceThe order of precedence for searching for boot components is as follows
In absence of a valid extlinux.conf file, U-Boot will scan the boot_targets list looking for a file named boot.scr.uimg or boot.scr (in that order) and run any commands located in the script file. If your environment requires a different sequence of commands or behaviour, you can edit the boot.scr file to suit your needs. |
Using the boot.src method
Install u-boot-tools on Linux OS
Before using the mkimage function, the u-boot-tools needs to be installed.
Code Block | ||||
---|---|---|---|---|
| ||||
sudo apt-get update sudo apt install u-boot-tools |
Generate boot.script file from boot.scr file
For the modification of the boot.scr file convert the existing boot.scr file into an boot.script file:
Code Block | ||||
---|---|---|---|---|
| ||||
dd if=boot.scr of=boot.script bs=72 skip=1 |
Modifying boot.script file
Modify the boot.script file based on your needs. For example, when booting image.ub from SD card, USB or QSPI flash, the following boot.script file should work after conversion into an boot.scr file. The boot.scr file could be located on all working boot_targets.
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
# This is a boot script for U-Boot # Generate boot.scr: # mkimage -c none -A arm -T script -d boot.script boot.scr # # Generate boot.script (for modifications in boot.scr): # dd if=boot.scr of=boot.script bs=72 skip=1 # ################ imageub_addr=0x10000000 # imageub_flash_addr=0x200000 imageub_flash_size=0xD90000 echofor [TE_BOOT-01] Trenz Boot-file version 1.0 (development); echo [TE_BOOT-10] Found boot.scr in device: ${target} echo [TE_BOOT-11] Chosen Bootmode is ${modeboot} from boot_targets=${boot_targets}; echo [TE_BOOT-11] Use RAM Address boot_target in ${boot_targets}; do # Boot target is mmc0 or usb0: image.ub on mmc0 or usb0 if test "${boot_target}" = "${devtype}0"; then if test -e ${devtype} 0:${distro_bootpart} /image.ub; then fatload ${devtype} 0:${distro_bootpart} ${imageub_addr} for linux image.ub; for boot_target in ${boot_targets bootm ${imageub_addr}; do fi fi #echo [TE_BOOT-11] currently trying to load from ${target}; #echo [TE_BOOT-12] boot_target = ${boot_target}; #echo [TE_BOOT-13] devtype = ${devtype}; #echo [TE_BOOT-14] devnum = ${devnum}; #echo [TE_BOOT-15] distro_bootpart = ${distro_bootpart}; #echo [TE_BOOT-16] boot_prefixes = ${boot_prefixes}; #echo [TE_BOOT-17] source = ${prefix}${script}; # Boot target is mmc0 or usb0: image.ub on mmc0 or usb0# Boot target is mmc1 or usb1: image.ub on mmc1 or usb1 if test "${boot_target}" = "${devtype}1"; then if test -e ${devtype} 1:${distro_bootpart} /image.ub; then fatload ${devtype} 1:${distro_bootpart} ${imageub_addr} image.ub; bootm ${imageub_addr}; fi fi # Boot target is qspi: image.ub on qspi; image.ub is included in BOOT.bin if test "${boot_target}" = "${devtype}0qspi"; then if || test -e "${devtypeboot_target} 0:${distro_bootpart} /image.ub" = "qspi0"; then echo [TE_BOOT-20] boot_target issf probe 0 0 0; sf read ${bootimageub_targetaddr}. Found image.ub on ${devtype}0:${distro_bootpart} ; fatload ${devtype} 0:${distro_bootpart} ${imageub_addr} image.ubimageub_flash_addr} ${imageub_flash_size}; bootm ${imageub_addr}; fi done fi # Boot target is mmc1 or usb1: image.ub on mmc1 or usb1 if test "${boot_target}" = "${devtype}1"; then if test -e ${devtype} 1:${distro_bootpart} /image.ub; then echo [TE_BOOT-21] boot_target is ${boot_target}. Found image.ub on ${devtype}1:${distro_bootpart}; fatload ${devtype} 1:${distro_bootpart} ${imageub_addr} image.ub; bootm ${imageub_addr}; fi fi # Boot target is qspi: image.ub on qspi; image.ub is included in BOOT.bin if test "${boot_target}" = "qspi"; then echo [TE_BOOT-30] Try to use image.ub from ${boot_target}, load image.ub from qspi-flash address ${imageub_flash_addr}; echo [TE_BOOT-30] max. image.ub size is ${imageub_flash_size} ; sf probe 0 0 0; sf read ${imageub_addr} ${imageub_flash_addr} ${imageub_flash_size}; bootm ${imageub_addr}; fi done |
Info | ||
---|---|---|
| ||
The alias name ${devnum}, used in Xilinx default files, does not work in all variants tested, therefore the ${devtype} boot_targets were split up |
Generate boot.scr file from boot.script file
Please remember that the boot.script file needs to be converted back into the boot.scr file after the edits are complete
Code Block | ||||
---|---|---|---|---|
| ||||
mkimage -c none -A arm -T script -d boot.script boot.scr
|
Distro Boot in SD-Boot mode
|
Info | ||
---|---|---|
| ||
The alias name ${devnum}, used in Xilinx default files, does not work in all variants tested, therefore the ${devtype} boot_targets were split up |
Generate boot.scr file from boot.script file
Please remember that the boot.script file needs to be converted back into the boot.scr file after the edits are complete
Code Block | ||||
---|---|---|---|---|
| ||||
mkimage -c none -A arm -T script -d boot.script boot.scr
|
Distro Boot for Zynq-7000 series
SD-Boot mode
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The following table provides an overview of the possible boot combinations for the devices SD card, USB and QSPI in SD Boot mode. The table is not complete, but gives an impression of the possibilities of the Distro Boot.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Variant 1 (Boot.bin, image.ub and boot.scr on SD card):
Variant 2 (Boot.bin on SD card, image.ub and boot.scr on USB):
Variant 1 (Boot.bin, image.ub and boot.scr on SD card):
|
Distro Boot in QSPI-Boot mode
Variant 2 (Boot.bin on SD card; image.ub and boot.scr on USB):
|
QSPI-Boot mode
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The following table provides an overview of the possible boot combinations for the devices SD card, USB and QSPI in QSPI Boot mode. The table is not complete, but gives an impression of the possibilities of the Distro Boot.
Variant 1 (Boot.bin on QSPI Flash; image.ub and boot.scr on SD card):
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Scroll Title | | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Boot Variants | SD-Card (mmc0) | USB-Stick (usb0) | QSPI-Flash | Comments | Variant 1 | -- | BOOT.bin2 zynq_fsbl_flash | Boot only from QSPI flash | Variant 2 | image.ub boot.scr | BOOT.bin1 zynq_fsbl_flash | used boot.scr and image.ub from SD card | Variant 3 | BOOT.bin1 image.ub | BOOT.bin3 zynq_fsbl_flash | used boot.scr from QSPI-Flash and image.ub from SD card | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Scroll Title | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
File name | BOOT.bin1 | BOOT.bin2 | BOOT.bin3 | QSPI Flash Offset Address | RAM Load Address | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
fsbl.elf | x | x | x | -- | NA | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
test_board.bit | x | x | x | -- | NA | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
u-boot.elf | x | x | x | -- | NA | image.ub | x | 0x200000 | 0x10000000 | boot.scr | x | x | 0xfc0000 | 0x3000000 |
Info | ||
---|---|---|
| ||
When booting from a QSPI device, care must be taken to maintain a very specific scheme for where files are located both in the nonvolatile flash device as well as where they are loaded into DDR prior to hand-off to the robust operating system. |
Variant 1 (Boot.bin on QSPI Flash and image.ub and boot.scr on SD):
- Connect JTAG and power on carrier with module (boot mode set to SD boot and no SD card is inserted)
- Open Vivado Project with "vivado_open_existing_project_guimode.cmd" or if not created, create with "vivado_create_project_guimode.cmd"
- Type on Vivado TCL Console: TE::pr_program_flash -swapp u-boot
Note: To program with SDK/Vivado GUI, use special FSBL (zynq_fsbl_flash) on setup
optional "TE::pr_program_flash -swapp hello_te0715" possible - Copy boot.scr and image.ub on SD-Card
- use files from (<project folder>/_binaries_<Article Name>)/boot_linux from generated binary folder,see: Get prebuilt boot binaries or use prebuilt file location, see <design_name>/prebuilt/readme_file_location.txt
- Set boot mode to QSPI-Boot mode and , insert SD card and start the board.
- Depends on Carrier, see carrier TRM.
Variant 2 (Boot.bin, image.ub and boot.scr on QSPI Flash):
- Connect JTAG and power on carrier with module (boot mode set to SD boot and no SD card is inserted) SD boot and no SD card is inserted)
- Open Vivado Project and program QSPI flash
- Set boot mode to QSPI-Boot mode and start the board.
Variant 3 (Boot.bin on QSPI Flash; image.ub and boot.scr on USB):
- Connect JTAG and power on carrier with module (boot mode set to SD boot and no SD card is inserted)
- Open Vivado Project and program QSPI flash
- Copy boot.scr and image.ub on SD card.
- Open Vivado Project with "vivado_open_existing_project_guimode.cmd" or if not created, create with "vivado_create_project_guimode.cmd"
- Type on Vivado TCL Console: TE::pr_program_flash -swapp u-boot
Note: To program with SDK/Vivado GUI, use special FSBL (zynq_fsbl_flash) on setup
optional "TE::pr_program_flash -swapp hello_te0715" possible - Set boot mode to QSPI-Boot mode, insert USB and start the board.Depends on Carrier, see carrier TRM.
Code Snippets for Boot.scr file
Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|
Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|
Expand | |||||||||
---|---|---|---|---|---|---|---|---|---|
| |||||||||
|
Expand | |||||||||
---|---|---|---|---|---|---|---|---|---|
| |||||||||
|
References
https://wiki.ubuntu.com/ARM/EditBootscr
Scroll Only | ||
---|---|---|
|
Scroll pdf ignore | ||||||
---|---|---|---|---|---|---|
|