Well if your board has JTAG debug ability, you can step the entire thing. The start up code isn't really all that much.

There are many things which could be wrong.

What CPU are you using....what board is it close to...variations on a theme tend to be quite easy to port and diagnose errors for...

Regards, Richard W.

-----Original Message----- From: u-boot-users-admin@lists.sourceforge.net [mailto:u-boot-users- admin@lists.sourceforge.net] On Behalf Of Benjamin Collar Sent: Tuesday, August 31, 2004 10:01 AM To: u-boot-users@lists.sourceforge.net Subject: [U-Boot-Users] porting to new board: what to do next?

Greetings

We're porting U-Boot to a new board. We've followed the plan given in the README and have written board.c, flash.c, configs/board.h. We've flashed it and ... well, nothing happens. Nothing at all.

Now, I know you'll need more information from me, but I'm not sure exactly what you'll want to know, so for the moment, we'll leave it

like

that.

What I need to know is, how do I find out what U-Boot is up to? Is

there

a way to debug it from the beginning? I've got it connected serially (unfortunately, our debugger works under windows, so we've got to use HyperTerminal) but nothing shows up at all.

Thanks for any help Ben

-- Benjamin Collar Siemens AG CT SE 2 Embedded Linux 089-636-53711

---

This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users