Note: Press ctrl + C at boot to enter the uboot command set
Because I was used to using RK’s burning tool before, in order to be compatible with the ssd202d burning method
So I started to try to use ssd202d to burn.
The method for SSD202D is
Burn uboot
Then use TFTP to burn it, so I started to try
Just burn the first three, and use tftp to burn the following img. Since the workload is too heavy to display, I only do a demonstration of boot.img.
================================================== =======================
1. Clear memory
2. Burn most of the firmware, deliberately not burning boot.img (because it only verifies feasibility)
It is stuck in the uboot instruction set because there is no kernel firmware, which is normal.
Set the IP, 143 is the IP of my window computer; 199 is the IP of the motherboard;
setenv serverip 192.168.1.143 setenv ipaddr 192.168.1.199 saveenv estart
You can see it, and then use the tftp command to burn
md 30000000 40 tftp 30000000 boot.img
The content inside shows edfe0dd0, which is the head of dtb and the head of boot.img.
In this way, tftp has successfully burned the boot.img image, but it has not ended. It is only in the RAM space at this time. We need to write it to the corresponding memory. I use emmc here, and spinand will be used later;
Then it can be seen that the starting address is 0x8000 and the size is 0x10000;
You can also use mmc part
It can be seen that //0x00008000 0x00017fff “boot”
You can also read the contents of boot
mmc read 30000000 8000 100000
write emmc
mmc write 30000000 8000 10000 md 32000000 40 mmc read 32000000 8000 10000
You can see that the read content is different, then reset and restart
Now you have entered the system, which means that our tftp burning boot.img has been successful.
================================================== ===================
refer to:
The burning method of ssd202d, but the nand is replaced by mmc
That’s it after success!
===========================spi nand====================== ==============
Extended a spinand
It turns out that ssd uses nand tool, but rv1126-rv1109 uses mtd.
so
Since the address has offsets here, so: (Set the IP first)
setenv serverip 192.168.1.147 setenv ipaddr 192.168.1.150 saveenv tftp 22000000 boot.img mtd erase spi-nand0 B00000 800000 mtd write.oob spi-nand0 22000000 B00000 800000 mtd read.oob spi-nand0 22000000 B00000 800000
22000000 is the memory space RAM;
First use tftp to put boot.img into 0x22000000;
Then erase erases the specified space;
write.oob is written in; nand must be erased before writing;
Finally, read it out to see if nand is written.
<name>: spi-nand0 <addr>: 22000000 <off>: B00000 <size>: 800000
You can see 0x00004000@0x00005800 (boot), which is the boot.img we want to download.
Then you can see that the actual size in memory is
You can see how 0x800000 corresponds to 0x4000
So calculated in the same way (multiplied by 0x200 in the middle), it is 512
Hidden merit and fame!