This guide is designed to provide a step-by-step walkthrough on in-system programming (ISP) for flash devices on the SP7350 platform. Covering a range of devices including eMMC, SPI-NOR flashes, SPI-NAND flashes, and 8-bit NAND flashes, the document aims to simplify the ISP process. Follow the outlined steps to seamlessly download, compile, and write images to flash devices, ultimately enabling you to boot the system from these devices.
...
Choose the board you want to build the image for. For instance, press 1 to select "SP7350 Ev Board."
Choose the device from which the system will boot. For example, press 1 to specify booting from the eMMC device. SP7350 supports booting from eMMC, SPI-NAND, SPI-NOR and 8-bit NAND flashes.
Choose the size of the flash device. For example, press 4 to select an 8 GiB eMMC device.
Choose the root file-system for Linux. For example, press 5 7 to opt for “Ubuntu MATE MATE 2224.04.04” 1” as the root file-system.
Decide whether to use the overlay file system. For example, press 1 to choose not to use an overlay file-system.
Choose boot modes. Press 1 to select building “Normal boot” images.
Once you have completed the configuration selections in the menu, the system will start configuring the building environment. This process may take tens seconds or even a few minutes, depending on your computer's performance. Please wait patiently for the configuration process to conclude.
Please note that the system takes additional time to complete its initial run during the configuration process, as it requires the download of the toolchain.
Build Code
After completing all configurations, you are ready to initiate the code build. Execute the following command to commence the build process:
...
| Code Block |
|---|
wellslu@scdiu3:~/Q654$ ll out total 915672 drwxr-xr-x 2 wellslu sp 4096 Jan 1 14:59 ./ drwxr-xr-x 11 wellslu sp 4096 Jan 1 14:47 ../ -rw-r--r-- 1 wellslu sp 134144 Jan 1 14:47 down_32M.exe -rw-r--r-- 1 wellslu sp 53248 Jan 1 14:58 dtb -rw-r--r-- 1 wellslu sp 408526 Jan 1 14:58 fip.img -rw-r--r-- 1 wellslu sp 577901568 Jan 1 14:59 ISPBOOOT.BIN lrwxrwxrwx 1 wellslu sp 36 Jan 1 14:47 isp.sh -> /home/wellslu/q654/Q654/build/isp.sh* lrwxrwxrwx 1 wellslu sp 40 Jan 1 14:47 nor_isp.sh -> /home/wellslu/q654/Q654/build/nor_isp.sh* lrwxrwxrwx 1 wellslu sp 37 Jan 1 14:47 part.sh -> /home/wellslu/q654/Q654/build/part.sh* -rw-r--r-- 1 wellslu sp 564031488 Jan 1 14:58 rootfs.img -rw-r--r-- 1 wellslu sp 834528 Jan 2 14:58 u-boot.img -rw-r--r-- 1 wellslu sp 9846045 Jan 2 14:58 uImage -rw-r--r-- 1 wellslu sp 135516 Jan 2 14:58 xboot.img wellslu@scdiu3:~/Q654$ |
xboot.img: Image file of X-Boot, the first-stage boot-loader responsible for DDR SDRAM initialization and training, loading images of TF-A, OP-TEE, U-Boot, and initiating the execution of TF-A.
u-boot.img: Image file of U-boot, the second-stage boot-loader responsible for loading and running the Linux kernel image.
uImage: Image file of the compressed Linux kernel with a U-Boot header.
rootfs.img: Image file of the root file-system of Linux.
dtb: Device-tree blob file. Note: dtb has been merged into the U-Boot image. This copy is provided for your reference; U-Boot will load the dtb inside it.
fip.img: Image file comprising images of Trusted Firmware-A (TF-A) and Open Portable Trusted Execution Environment (OP-TEE).
ISPBOOOT.BIN: Binary file containing X-boot, U-boot, and all other images. It is for in-system programming.
...