
31 Aug
2015
31 Aug
'15
5:31 p.m.
i found the problem..
The first stage bootloader has initialized the mmu unit and since the second stage is running on an already initialized RAM, the RAM test still sees data outside physical address and hence thinks it to be 1GB.
When it tries to relocate itself into this address range, it fails and resets.
I dont see a problem if i hardcode my RAM size to 256 << 20 for the 2nd stage u-boot.bin. But I will try to read the value of the RAM from the chip itself..
-Harsha
-- View this message in context: http://u-boot.10912.n7.nabble.com/valid-RAM-region-on-a-256MB-fails-occasion... Sent from the U-Boot mailing list archive at Nabble.com.