Quote:
Originally Posted by eureka
MMU is disabled before Linux kernel loading on ARM. It's a strict requirement. And bootm command (which has been used by ixtab) is designated for loading Linux kernel, so it's reasonable to not consider any value of TLB registers as sign of problems.
|
You are getting ahead of the work described in this thread.
ixtab described data written to DRAM before loading u-boot as not being able to be found at the same address as after loading u-boot.
So yes, looking at the TLB entries would give us some information with which to replace the guesses with.
And ixtab is correct, we don't need U-boot to do the DRAM initialization - sending i.ROM a CSF list of address, data, data size will get all of that I/O done before it executes the downloaded application.
For instance, the "RAM kernel" (that's en_Freescale for client command processor). It that case the off-chip resources are started by the files sent prior to downloading the "RAM kernel" itself.
And we got into this long thread because this suggested alternative code passes "null" for the DCD and then blindly uses some binary objects borrowed from Freescale utiliites.