A detailed description of Linux platform chip writing process

The details will be updated continuously!

Connect the Development Board, reboot, enter the U-boot interface and do the following:

First, configure the network

# pri
# setenv IPAddr 192.168.64.11 (Note: IPADDR for Development Board IP)
# setenv ServerIP 192.168.64.12(Note: ServerIP is a Windows host IP)
# setenv Gatewayip 192.168.64.1 (Note: Gatewayip is a gateway)
# saveenv

# ping 192.168.64.12 (If you can, continue to do)

Second, burn and write system files (TFTP is downloaded to DDR first, and then written to Nandflash by DDR)

First, start the TFTP service, select the path to the destination file to download, and perform the following actions:

Note: You can tftp to memory first, then use "Bootm address" to start the test, do not have to erase Nandflash

1) Burn and write kernel

Download kernel image to memory
# TFTP 0x40000000 uimage

This command can be used to verify that the kernel can start normally, so that the current problem and the original normal wipe
# BOOTM 0x40000000

Erase Nandflash Space 0x500000 byte size starting from address 0x600000
# NAND Erase 0x600000 0x500000

Burn the kernel image in memory to Nandflash
# NAND Write 0x40000000 0x600000 0x500000

2) Burn-write FS
# TFTP 0x40000000 rootfs.img
# NAND Erase 0xe00000 0xf200000
# NAND write.yaffs 0x40000000 0xe00000 0xxxxx (0xXXXX determined based on the size of the TFTP 0x40000000 rootfs.img download performed)

3) Burn and write U-boot

# TFTP 0x40000000 U-boot.bin
# NAND Erase 0x0 0x600000
# NAND Write 0x40000000 0x0 0x600000

Third, restart into the U-boot interface, configure the Uboot startup parameters

Test 1 (Boot kernel):

Set the start command: Read the memory from the Nandflash and boot the kernel from the memory
# setenv Bootcmd NAND read 0x40000000 0x600000 0x500000\; Bootm 0x40000000

Save the above setting parameters
# saveenv

Restart, observe the effect.

Test 2 (set machine code):

# setenv Machid 0xXXX (depending on your situation)
# saveenv

Restart, observe the effect.

Test 3 (Start the local file system):
# setenv Bootargs root=/dev/mtdblock4 init=/sbin/init console=ttysac0,115200 rootfstype=yaffs RW
# saveenv

Restart, observe the effect.

Iv. to implement the NFS Mount file system, do the following:

1, ensure that the network card in the virtual machine VirtualBox is a wired network card (because it is mounted via a network cable)

2. Set the IP address
# setenv ServerIP 192.168.64.13

# setenv IPAddr 192.168.64.11
# setenv Gatewayip 192.168.64.1
# saveenv

Note: ServerIP is the IP of Ubuntu in Windows VirtualBox

Test 4 (Mount the root file system in Ubuntu):
# setenv Bootargs root=/dev/nfs nfsroot=192.168.64.13:/mini_rootfs ip=192.168.64.11:192.168.64.1::255.255.255.0:: Eth0:off INIT=/LINUXRC

console=ttysac0,115200
# saveenv

Restart, observe the effect.

A detailed description of Linux platform chip writing process