This layer provides machine configurations and recipes for building the bootable disk image with AndeSight™ Linux packages.
kas-container provides a Yocto development environment based on the Debian docker image. Before you proceed with the build process, make sure Docker is installed on your host machine.
$ mkdir riscv-andes && cd riscv-andes
$ git clone https://github.com/andestech/meta-andes.git -b ast-v5_3_0-branch
$ wget https://raw.github.com/siemens/kas/4.1/kas-container
$ chmod a+x ./kas-container
AndeSight™ v5.3.0 includes OpenSBI, U-Boot and Linux source based on the following versions.
And, its RISC-V GNU toolchain versions are as follows:
- GCC 13.2.0
- Binutils 2.41
To build a Poky reference distribution, take ae350-ax45mp as an example:
$ ./kas-container build meta-andes/kas/ae350-ax45mp.yml
Upon completion of the build process, the build results are located within the directory build/tmp/deploy/images/.
| File | Description |
|---|---|
core-image-base-ae350-ax45mp.rootfs.wic.gz |
A compressed root filesystem image which will be written onto the SD card. |
fitImage |
A Flattened Image Tree (FIT) that contains the Linux kernel and device-tree with their load address. |
ax45mp_c4_d_dsp_ae350.dtb |
Device Tree Blob generated using the ae350-ax45mp YAML file. The naming convention is structured as follows: <cpu>_c<core-count>_<double-float-support>_<andes-dsp-support>_<platform>.dtb. It will be programmed onto flash memory using SPI_burn tool. |
boot.scr.uimg |
U-Boot script image, automating the boot process by attempting various boot scenarios such as loading boot files via TFTP or MMC, and executing the corresponding commands to load and boot the kernel images. |
uEnv.txt |
Contains boot environment variables for U-Boot, specifying parameters like boot arguments, and commands to load and run kernel images (e.g. fitImage). |
u-boot-spl.bin |
The Secondary Program Loader (SPL) of U-Boot which will be programmed onto flash memory using SPI_burn tool. |
u-boot.itb |
An image tree binary of U-Boot, combining OpenSBI (fw_dynamic.bin) which will be loaded by U-Boot SPL. It will be programmed onto flash memory using SPI_burn tool. |
To update the bootloader, use the SPI_burn tool. Ensure you have an ICEman connection set up as follows:
Local Host Local/Remote Host
.----------------. .--------------.
| yocto images | | |
| | ICEman host <IP:PORT>
| .----------. | | .--------. |
| | SPI_burn |<--+--socket--+->| ICEman | |
| '----------' | | '--.-----' |
'----------------' '-----|--------'
|
USB
.--------------. |
| target | .-----v-----.
| board <---JTAG---| ICE |
| | '-----------'
'--------------'
You can download the pre-built SPI_burn for x86 hosts and skip building it locally from source.
Download & extract SPI_burn source code:
$ wget https://github.com/andestech/Andes-Development-Kit/releases/download/ast-v5_3_0-release-windows/flash.zip
$ unzip flash.zip
$ cd ./flash/src-SPI_burn
Build SPI_burn:
$ ./build_SPIburn.sh
Program the U-Boot SPL & ITB and device-tree blob onto flash memory:
$ ICE_HOST=<ICEman host IP>
$ ICE_PORT=<ICEman host burner port>
$ ./SPI_burn --host $ICE_HOST --port $ICE_PORT --addr 0x0 -i u-boot-spl.bin
$ ./SPI_burn --host $ICE_HOST --port $ICE_PORT --addr 0x10000 -i u-boot.itb
$ ./SPI_burn --host $ICE_HOST --port $ICE_PORT --addr 0xf0000 -i ae350.dtb
Use the Linux dd command to flash the image to an SD card.
$ gunzip -c <IMAGE>.wic.gz | sudo dd of=/dev/sdX bs=4M iflag=fullblock oflag=direct conv=fsync status=progress
$ sync
You can also use the belenaEther GUI to flash the image on Windows and macOS.
Upon inserting the SD card, access the serial console (e.g. picocom) with the baud rate settings 38400/8-N-1, and then reset the board, the system should start the boot process.
$ sudo picocom -b 38400 /dev/ttyUSB1
Andes platforms follow the typical RISC-V boot process illustrated below.
.-------------------------.
| (u-boot.itb) |
| |
(1)-----------------+ | (2)-----------------+ |
| U-Boot SPL |--+->| OpenSBI | |
| (u-boot-spl.bin) | | | (fw_dynamic.bin) | |
+------------------+ | +---------.--------+ |
| | |
Machine mode | | |
.......................|............|............|..................
Supervisor mode | | |
| v |
| (3)-------------------+ | (4)-----------+
| | U-Boot |-+--->| Linux |
| | (u-boot-nodtb.bin) | | | (fitImage) |
| +--------------------+ | +------------+
'-------------------------'
The U-Boot sf command provides an alternative method for updating flash memory.
Upon flashing the <IMAGE>.wic.gz file to an SD card, the U-Boot SPL (u-boot-spl.bin), ITB (u-boot.itb), and the device-tree blob are subsequently located in the first partition.
RISC-V # fatload mmc 0:1 0x600000 u-boot-spl.bin
RISC-V # sf probe 0:0 50000000 0
RISC-V # sf erase 0x0 0x10000
RISC-V # sf write 0x600000 0x0 0x10000
RISC-V # fatload mmc 0:1 0x600000 u-boot.itb
RISC-V # sf probe 0:0 50000000 0
RISC-V # sf erase 0x10000 0xa0000
RISC-V # sf write 0x600000 0x10000 0xa0000
RISC-V # fatload mmc 0:1 0x20000000 ae350.dtb
RISC-V # sf probe 0:0 50000000 0
RISC-V # sf erase 0xf0000 0x10000
RISC-V # sf write 0x20000000 0xf0000 0x10000
$ ICE_HOST=<ICEman host IP>
$ ICE_PORT=<ICEman host debug port>
$ $GDB -ex "target remote $ICE_HOST:$ICE_PORT" \
-ex "set confirm off" \
-ex "set pagination off" \
-ex "monitor reset halt" \
-ex "set \$ra=0" \
-ex "set \$sp=0" \
-ex "maintenance flush register-cache" \
-ex "c"