On Tue, Jul 03, 2007 at 01:09:36PM -0500, Rune Torgersen wrote:
-----Original Message----- From: Grant Likely
Do we really need console output before U-Boot has
initialised SDRAM?
For debugging some simple PUTC() and PUTHEX() macros would be sufficient. Of course they have to be disabled on systems
designed to
have a quiet console.
I think it is a good idea to at least default to spitting out *something* on boot. Just in case RAM is hooped.
Console output before RAM is initialized is EXTREMELY important. I thin on our boards, 90% of the output on boot is before RAM is initalized. And when you try to bring up a new board, you definetly need it.
Perhaps because the comment before board_init_f() does not tell the truth:
* * The main purpose is to provide a (serial) console interface as * soon as possible (so we can see any error messages), and to * initialize the RAM so that we can relocate the monitor code to * RAM.
In fact 90% of the init process happen here. This function does not even exist in my approach.
Regards Sascha