Hey David, Thanks for the reply. Let me back up a bit and say that currently my only knowledge of OpenOCD, GDB, and GDBserver is from a user's perspective, and a GDB GUI user perspective at that. I run OpenOCD, connect to the GDB port from my GDB client launched by my debugger GUI (Eclipse or DDD). My end goal is to have peripheral registers show up automatically in the GUI register window without any client side modifications. Just like the CPU registers show up for the different cores without the client side knowing much about the target, initially.
I am vaguely aware of the web port connection as me and a colleague read it about once when initially building and using OpenOCD. It sounds like the method you and Oyvind are describing would give access to peripheral registers via some command prompt, but not in an already existing window in the various GDB GUI's that exist. Is that correct? If so, it may be just as easy to run some script on the GDB client side and let it just pass the memory read/write commands to the GDBserver? Disclaimer: Please excuse my OpenOCD ignorance! Thanks, Rob Date: Thu, 8 Jul 2010 09:09:18 -0700 From: [email protected] Subject: Re: [Openocd-development] Requesting Help: How to add memory mapped I/O registers? To: [email protected]; [email protected] CC: [email protected] I'm guessing that if I wanted to try to contribute to OpenOCD to add this support, there would be a very steep learning curve. Maybe. The TCL bits, plus whatever display technique is used -- ideally, through the web server. The TCL stuff is easy and you'll want to know that if you work much at all with OpenOCD. If anyone could point me to a good starting point to learn the system well enough to add this support, I could try looking into it. The basic TCL access is easy; you could look for one example at the davinci clock setup logic for how to read and write such registers, and tthere are also some utils somewhere in the tcl library. What I've done sometimes is just print the values via TCL, when debugging setup code, lots of one-off logic to get at modules that I need.
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
