[ECOS] Debugging Redboot..

Bart Veer bartv@ecoscentric.com
Wed Oct 7 16:20:00 GMT 2009


>>>>> "Jim" == Jim Bradleigh <jim.bradleigh1@btinternet.com> writes:

    Jim> Hi,
    Jim> Is there a guide to how to debug "into" redboot?

    Jim> I`ve managed to get redboot loaded via GDB (using redboot
    Jim> itself) and I can get the application to run, and certain
    Jim> breakpoints to function during easrly startup.

    Jim> However when the redboot prompt appears I cannot Ctrl+C and
    Jim> any breakpoints don`t seem to trigger (i.e. when debugging
    Jim> redboot commands)

    Jim> Are there special options required to allow me to gain full
    Jim> access to debug redboot?

In general you cannot use a ROM RedBoot to debug a RAM RedBoot, or
anything along those lines. The problem is that RedBoot always takes
over certain bits of hardware, including the h/w exception vector(s)
used for debugging and the uart for communicating with the host. Hence
shortly after the RAM RedBoot start running the ROM RedBoot will
become disconnected from the rest of the world, and can no longer
interact with gdb. Changing this behaviour is non-trivial.

Hence debugging RedBoot itself generally involves jtag or similar h/w
debug support. If that is not available then you may have to resort to
debugging via diag_printf()'s.

Bart

-- 
Bart Veer                                   eCos Configuration Architect
eCosCentric Limited    The eCos experts      http://www.ecoscentric.com/
Barnwell House, Barnwell Drive, Cambridge, UK.      Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
       >>>> Visit us at ESC-UK  http://www.embedded.co.uk <<<<
       >>>> Oct 7-8 on Stand 433 at FIVE ISC, Farnborough <<<<

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss



More information about the Ecos-discuss mailing list