Guennadi Liakhovetski wrote:
On Wed, 7 Feb 2007, Gary Thomas wrote:
To debug RedBoot, you'll need to use your BDI.
Simply connect GDB to the BDI instead of the serial port.
Something like this:
(gdb) tar rem bdi:2001
Aha, ok, this makes sense, but, unfortunately, bdi doesn't work with
this board. It worked somehow with pxa255 (not very reliably) and I
haven't been able to use it with pxa270. Yes, I do have the necessary
register description etc. files, just it wouldn't work. So, I guess,
it's not an option for me. I could disable bootp, but the point was not
to somehow get it to build and run, but to find the reason of the
mis-compilation and (preferrably) fix redboot. Besides, every
non-booting redboot means about 20 minutes jtag flashing...
In that case, what I would do is install a working RedBoot
(built with 3.3.2) and then experiment with a RAM version
built with the new tools. Put in some diag_printf() to
trace the code. You might even be able to debug this
using the serial connection and GDB (since that does
seem to be alive in your ROM/ROMRAM version)
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
