NAND: Special NAND id table Version 1.35
Nand ID: 0 x2c xda x90 x06 x95 0 0 0 0 0 x00 0 x00 0 x00
Nand (Hardware) : Block: 128 KB Page: 2 KB Chip: 256 MB * 1 OOB: 64 b ECC: 1 bit/512 byte
256 MiB
Check the spi flash controller v300. Found
Can 't find a valid spi flash chip.
Can 't find a valid spi flash chip.
In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
NAND read: device zero offset 0 x100000, size 0 x500000
5242880 bytes read: OK
# # Booting the kernel from Legacy Image at 82000000...
Image Name: Linux - 3.0.8
Image Type: ARM Linux Kernel Image (uncompressed)
The Data Size: 3001532 Bytes=2.9 MiB
The Load Address: 80008000
Entry Point: 80008000
Loading the Kernel Image... OK
OK
Starting the kernel...
Uncompressing Linux...
This is the log information, only these information,
Ask how to solve this problem,
Via TFTP can write the firmware is successful, after the start, the result is like this,
CodePudding user response:
How much is the address of the TFTP?CodePudding user response:
Looking for table can be run machines, try with your image, estimation is image do you have any questionCodePudding user response:
Haisi official will not go wrong, unless it is changed the kernel yourself! Pay attention to modify!CodePudding user response:
You burn write memory size is larger than your kernel's small, so don't run, you go to take a closer look at your environment parameter and file size is more than,CodePudding user response:
You burn write memory size is larger than your kernel's small, so don't run, you go to take a closer look at your environment parameter and file size is more than,CodePudding user response:
The landlord to provide the information, the size of the file read no problem, the mirror is only 3 m, read more than 5 m,But here:
# # Booting the kernel from Legacy Image at 82000000...//here should be the original poster to read image memory address
Image Name: Linux - 3.0.8
Image Type: ARM Linux Kernel Image (uncompressed)
The Data Size: 3001532 Bytes=2.9 MiB
The Load Address: 80008000//here may have a problem, some solutions must be in this Address can be normal boot, Suggestions on the building Lord read mirror x80008000 Address 0 start try
Entry Point: 80008000
CodePudding user response:
Uboot startup CTRL + c configure yourThe setenv bootcmd nand read x100000 x8100000 0 0 0 x500000 \; Bootm 0 x8100000
Sav
Reset
0 x82000000 this address Legacy to load the Image when the address is 81008000, after changing the bootm to 0 x8100000 loading address is 0 x80008000 can