Overview for Axxia 5600 and Axxia 6700

Size: px

Start display at page:

Download "Overview for Axxia 5600 and Axxia 6700"

Antony O’Brien’
5 years ago
Views:

1 Overview for Axxia 5600 and Axxia 6700 Axxia Systems use a 3 stage boot process to initialize the system and allow an operating system to be loaded. 1. The first stage is part of the asic and loads the Secondary Program Loader (SPL) into the asic s local memory. If the secure boot feature is enabled, it will verify and optionally decrypt the SPL before transferring control to it. If the redundant boot feature is enabled, the SPL image to load will be selected based on the sequence number of the available images and the cause of the last reset. As the first stage is not based on U-Boot, and cannnot be modified, it is not discussed here. In the 5600 or 6700 simulation environment, a binary of the bootrom will be provided. 2. After control is transferred to the SPL, system memory is initialized and U-Boot is loaded into system memory. 3. Once control is transferred to U-Boot, a prompt is available on uart0. Local Builds and Modifications Build Environment It is assumed that a Linux host is used to build and that tools are avilable to target aarch64. The cross compilation tools, mentioned above, should be in the PATH and CROSS_COMPILE should contain the proper prefix. SYSROOT should point to the tools sysroot for arm if required by the tools. ARCH should be set to arm64. The secure moniotor from the Axxia ARM trusted firmware repository ( is required. To build it, see the wiki for that repository. A Clone of the Axxia U-Boot Repository To get a local copy of the Axxia U-Boot source tree, do the following. Use the axxia-dev branch. $ git clone $ cd axxia_u-boot $ git checkout --track -b axxia-dev origin/axxia-dev When updates or available, 1

2 $ git checkout axxia-dev $ git pull Specific Releases [Optional] If you want a previously released version of Axxia U-Boot, based on a commit or a tag, do the following. Determine the Tag Name or Commit Number To list the available tags, $ git tag egrep 'axxia' To list commits. $ git log Create the Branch To create a branch based on a tag or commit, do the following. $ git checkout axxia-dev Then, $ git checkout -b <name of the new branch> <tag name OR commit number> Build $ make <board type>_defconfig Where is one of the following. * axm5600_sim * axm5600_emu * axm5600 * axc6700_sim * axc6700_emu * axc6700 Copy bl31.o (as described above, see the Readme section of the Axxia ATF wiki at to the spl directory. Note that you may have to create the spl directory. $ make $./tools/mkimage -A arm64 -T firmware -C none -a 0 -e 0 -n XLOADER \ -d spl/u-boot-spl.bin spl/u-boot-spl.img $./tools/mkimage -A arm64 -T firmware -C none -a 0 -e 0 -n XLOADER \ 2

3 -d u-boot.bin u-boot.img To use the SSP DMA feature in the boot rom, change the -e 0 option above when creating u-boot-spl.img as follows. Do not change any options when creating u-boot.img. For emulation, -e 0x For simulation or the hardware, -e 0x u-boot.img is U-Boot. spl/u-boot-spl.img is the SPL. Updating the SPL and U-Boot Simulation Copy u-boot-spl.img and u-boot.img to the simulation directory. Emulation or Hardware Using the External Host to Update Serial Flash The SPL and U-Boot can be written to serial flash from the external host. First load the RTE on the external host, then do the following. $ ncpbootmem -a write -r prom -o 0 <u-boot-spl.img> $ ncpbootmem -a write -r prom -o 0x80000 <binary parameter file> $ ncpbootmem -a write -r prom -o 0x <u-boot.img> Using U-Boot If you can get to the U-Boot prompt, update the SPL, parameters, and U-Boot as follows. Note that getting images into memory could be accomplished using the network interface (dhcp, tftp), an external host, or a JTAG debugger. => sf probe 0 => sf erase <copy the SPL image into memory at $(loadaddr)> => sf write $(loadaddr) => sf erase <copy the binary parameter file into memory at $(loadaddr)> => sf write $(loadaddr) => sf erase <copy the U-Boot image into memory at $(loadaddr)> => sf write $(loadaddr)

4 Using a Debugger A script for DS-5 is avaialable to boot a system with no external host and nothing written to flash. To use it, clone the Axxia errata repository at and use the associated wiki, to do the following. Add configuration databases to DS-5 for Import the script at /ds5/scripts/axm56xx_bringup.ds. Follow the comments in the script to boot U-Boot on the target. Use U-Boot, as described above and in the script comments, to write the SPL, parameters, and U-Boot to serial flash. Booting a Linux Image Use the build instructions at [ Put linux.fit, from the above, in memory at the load address. In simulation, linux.fit should only contain the Linux kernel. For emulation or hardware, linux.fit should contain the Linux kernel and the device tree. In simulation, copy the device tree binary to the simulation directory. In emulation or hardware, this can be accomplished using the network, a copy from serial flash, usb, etc. Once linux.fit is in memory, bootm $(loadaddr) will start Linux. Appendices Parameters and the U-Boot Environment Unless mentioned here, there are no changes to the meaning of U-Boot environment variables. U-Boot documentation is avaible at Boot/Documentation. Not all compile time options are enabled, and the list of enabled options varies by target, board, and instance. Some input is required by the SPL to, for example, set the voltage, clocks, initialize system memory, etc. All such input is stored in a parameter file. The parameter file is generated by the ASE. It is stored in serial flash. In some cases, baud rate for example, there are compile time settings, a parameter, and an environment setting. When that is the case, the following sequence and precedence holds. Until the parameter file is available, the compile time setting is used. Once the parameter file is available, the value in it us used. Finally, if the environment contains a setting, that is used. 4

5 Baud Rate In the header file for each target, CONFIG_BAUDRATE sets the initial baud rate used by the SPL. If there are errors reading the parameter file, they will be sent to the console at this speed. If the baud rate parameter value is 0x , indicating that there should be no change, nothing will change, otherwise, the baud rate will be changed to the value indicated. Since it is possible to start the boot process with U-Boot, skipping the SPL, U-Boot will follow the same sequence. It will begin with CONFIG_BAUDRATE, read the parameter file and switch to it. Finally, there is the U-Boot environment. Note that once baudrate is set, it cannot be deleted. If baudrate is set, U-Boot will use that value once the environment is available. QoS Control Settings (6700 Only) On 6700, the QoS control registers for the A53 clusters can be controlled by setting the following environment variables. cluster_0_qos, cluster_1_qos, etc. The valid bits are 0xf007f, as described in the register documentation. A Sample U-Boot Environment Following is an example U-Boot environment that is used by LSI to verify U-Boot releases. setenv baudrate 9600 setenv bootargs root=/dev/nfs rw mem=2g console=ttyama0 ip=dhcp setenv bootcmd setenv autoload ; dhcp ; bootm setenv bootdelay 5 setenv ethact NEMAC setenv ethaddr <board's MAC address> fdt_high=0x initrd_high=0x setenv loadaddr stderr=serial stdin=serial stdout=serial 5

6 Using EIOA as a Network Interface U-Boot can use Ethernet ports in EIOA for network connectivity. GMAC 0-4 and can be used as follows. U-boot Environment U-boot environment to setup gmac18 to 1G. setenv ethact LSI_EIOA setenv eioaport gmac4 setenv macspeed 1G setenv phymedia copper Possible Values eioaport gmac[0-4,16-18]. macspeed 1G. phymedia copper phy_address Value of phy address when phymedia is copper. 6

Use U-Boot. U-Boot Main Commands. U-Boot script capability

Use U-Boot. U-Boot Main Commands. U-Boot script capability Use U-Boot U-Boot Main Commands setenv this command is used to set variables saveenv this command saves variables previously set in the environment permanent storage space printenv this command print the