Hello Spen, I very briefly just skimmed over your code. I didn't see any direct provisions for memory mapped register access but it does seem like you are replacing the default register info with something else that you've defined (Please correct me or clarify where needed). If no method exists to add registers to the CPU core defaults then being able to replace the default register definitions with one that included both the core and memory mapped registers might be an option.
Using an xml file to define define the memory mapped registers is exactly what I had in mind. Do you think its possible to add memory mapped register access to your project? I'd be willing to spend time working on this. Unfortunately, I'm a bit slow coming up to speed on things so if I were to work on this task, I'd probably be bugging you or someone alot in the process. Thanks, Rob > Date: Thu, 8 Jul 2010 19:25:27 +0100 > From: [email protected] > To: [email protected] > CC: [email protected] > Subject: Re: [Openocd-development] Requesting Help: How to add memory mapped > I/O registers? > > On 08/07/2010 15:53, Robert Lee wrote: > > 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! > > > > It is possible using the xml to describe any new registers to gdb. > > I have started a test branch a while back but progress is slow: > http://repo.or.cz/w/openocd/ntfreak.git/shortlog/refs/heads/gdbxml > http://repo.or.cz/w/openocd/ntfreak.git/commitdiff/78697a57d839861b9b62839266d931cfa74d88a3 > > This method is used heavily by codesourcery and a few other embedded tools. > > Cheers > Spen
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
