[Developer] Debugging questions.

Carl van Schaik carl at ok-labs.com
Sun Apr 29 08:56:45 EST 2007


Hi Seth,

There is a bunch of config options that can be enabled/disabled.
for example, if you look in pistachio/Sconscript:

some options: ENABLE_KDB_CONS, ENABLE_TRACEPOINTS, ENTER_KDB etc

to set these options:

./tools/build.py machine=xxx project=xxx pistachio.ENABLE_KDB_CONS=False

disabling ENABLE_KDB_CONS, will end up disabling a bunch of other 
interactive debugging options as well.

I have not used BDI 2000 myself, but I've used other JTAG programmers 
before. Loading the elf file should be fairly easy. You probably want to 
load  build/image.boot which has physical address entry point etc. Note 
that your debugger may not find symbols for current program address 
either before entering virtual mode (enabling MMU) or after enabling the 
MMU. Please watch out for some debuggers that don't zero the BSS, you 
have to change the build process slightly to fixup the image in that case.

I suggest that you write a serial driver for your board as soon as you 
can, it will aid debugging quite a bit.

with a serial console, then able things like: 
pistachio.VERBOSE_INIT=True pistachio.ENTER_KDB=True

regards,
Carl

seth bollinger wrote:
> Hello all,
>
> Is there a way I can easily disable the in-kernel debugger?  I don't have serial drivers and what not written for my board yet.  I would like to use a bdi 2000 and gdb to debug instead.
>
> This brings me to my second question.  Has anyone used a bdi 2000 and gdb to debug the kernel yet?  With our current OS, we configure the processor and board using a debugger script, then simply generate the elf image and load it directly into ram and run it (we don't really use the mmu).
>
> I'm assuming this is going to be slightly different on l4, being that it makes more extensive use of the mmu.  How is this usually done?  I apologize if this is a noob question.  :)
>
> Thanks,
>
> Seth
>
> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer
>
>   




More information about the Developer mailing list