The exact situation:
console_init_f() executes properly. Execution stops at printf() inside display_options().
hang() kept _after_ display_options() is never reached. Even if hang() is removed, the problem remains.
Execution stops (as expected) at hang() if it is placed before display_options().
Hope that explained the problem.
Regards, Nishant.
Ps. SDRAM is not yet initialized at this point. Could that be the cause? Is it necessary to see any statements on the serial console?
-----Original Message----- From: Wolfgang Denk wd@denx.de To: "Nishant Galange" nishant.subs@myrealbox.com Date: Thu, 06 Jan 2005 18:15:41 +0100 Subject: Re: [U-Boot-Users] How to pause u-boot after serial init
In message 1105027245.41d677cnishant.subs@myrealbox.com you wrote:
I have a query regarding my custom board (8266 based PMC card, 512K boot fl ash, Himem (top boot), 32 MB main flash, 128 MB SDRAM, u-boot 1.1.1).
Will you please use a shorter linelength, say 70 characters or so as suggested by the netiquette? Thanks.
When trying to bring up the serial port, I want to stop execution after ser ial initialization. So, I inserted an infinite loop ('hang') in init_sequ ence[] in lib_ppc/board.c.
I don't understand what this would be good for, but if you really want to do this...
The problem is that a 'hang' placed just after console_init_f works but I c an't see any display on Hype Terrminal, because no prints have happened y et.
That's what you asked for...
And a 'hang' placed after 'display options' dosen't even load! The data lin es (seen on a Logic Analyzer) show all 0s
What do you mean by "does not load"? And which data lines are you talking about, and when do you sample these data lines?
Can anybody please shed some light on this problem? Any help / hints will b e greatly appreciated.
I have no idea what you're trying to do, but attaching a BDI2000 and running the code under GDB is probably the fastest way to find out what's going on on your system.
Best regards,
Wolfgang Denk