Hello Earthlings,
>From a user perspective, part of the magic that the GDB clients and OpenOCD
>GDB server provides is the register info for the CPU core (such as a
>ARM926ej-s) automagically. So it doesn't matter what debug UI I run (Eclipse,
>ddd, etc.) when I bring up a register window, I see all my ARM core registers.
>Super!
But many SoCs contain many more I/O registers that are memory mapped. It is
very painful when debugging to constantly look-up the address and access these
manually, so these need to be easily accessed in the debugger UI window for
registers (using a standard vanilla GDB client), just like the ARM core
registers.
Can OpenOCD do this? Is there some method for users/developers to add memory
mapped register definitions to a config file?
While these addresses usually get re-mapped by an OS to a virtual address,
Since OpenOCD has the ability to read and write to physical addressed, this
shouldn't be a problems. Worst case, if physical address accesses don't work,
you'd just need the right configuration file that corresponds to your OS's
virtual mapping when you start OpenOCD (assuming this functionality and the
necessary config file will exist one day.)
Thanks,
Rob
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
