Quote:
Originally Posted by Merlin09
ok, here it is:
Code:
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2017.02.26 16:08:18 =~=~=~=~=~=~=~=~=~=~=~=
HW
U-Boot 2009.08-lab126 (Jan 16 2017 - 03:44:52)
CPU: Freescale i.MX6 family TO0.0 at 996 MHz
Temperature: 32 C, calibration data 0x5524e15f
mx6sl pll1: 996MHz
mx6sl pll2: 528MHz
mx6sl pll3: 480MHz
mx6sl pll8: 50MHz
ipg clock : 66000000Hz
ipg per clock : 66000000Hz
uart clock : 80000000Hz
cspi clock : 60000000Hz
ahb clock : 132000000Hz
axi clock : 198000000Hz
emi_slow clock: 22000000Hz
ddr clock : 396000000Hz
usdhc1 clock : 198000000Hz
usdhc2 clock : 198000000Hz
usdhc3 clock : 198000000Hz
usdhc4 clock : 198000000Hz
MMC: FSL_ESDHC: 0,FSL_ESDHC: 1,FSL_ESDHC: 2
Board: Unknown
Boot Reason: [ POR ]
Boot Device: NAND
Board Id:
S/N:
I2C: ready
Invalid board id! Can't determine system type for RAM init.. bailing!
DRAM: 0 kB
Using default environment
In: serial
Out: serial
Err: serial
Quick Memory Test 0x80000000, 0xffff0000
POST done in 4 ms
Battery voltage: 3938 mV
Hit any key to stop autoboot: 1 0
uboot >
uboot > bist
then it stays stuck like this doing nothing.
But reading the log, I see Invalid board id! Can't determine system type for RAM init.. bailing!. Could it be a part of my problem? |
Without a correct board id, the u-boot code does not know how to start the dynamic (off SoC) ram.
Just like the message says.
Which is why it reports 0 kbyte of external ram rather than 256 (or 512) mbyte of ram.
bist is too big to run in internal ram, you must have the dynamic ram running so it can be used.
Use the imx_<something> program (which contains the DCD entries to start the dynamic ram).
or
Replace the missing boardid.
You might be able to do that from the minimum (first) sized u-boot.
Post the output of:
?
command (or of the help command, same-same thing)
Read the source code of KindleTool, it contains a fairly complete list of board ids.
= = = = =
How did those device specific values get over-written?
They are stored outside of the partitioned areas of the eMMC.
Did you enter the magic: "Erase All" command to see if it would work?
You almost must have done something like that.
PS:
Yes, "Erase All" does work, and does exactly what you would imagine from its name.