In message c3d0340b0502221121c489be4@mail.gmail.com you wrote:
We're using some emulation box to develop our SoC. Somehow the UART will the last component available for firmware development. Without
What a major mistake of design...
UART, it's very hard to debug UBoot. Can we "easily" drive a car without eyes?
Easily yes, savely no ;-)
But it's not impossible to do that. My first thought about porting UBoot under this circumstance is to disable the serial driver in UBoot and to redirect all printf to a fixed memory area, just as what a circular log buffer does. I'm wondering how much workload this will be. Is this kind of mechasim already existent in UBoot?
There is a log driver, yes.
But U-Boot really assumes that you have a working console port. Anything else is a major pain in the ...
Best regards,
Wolfgang Denk