On 08/25/2011 02:17 PM, Øyvind Harboe wrote:
On Thu, Aug 25, 2011 at 2:16 PM, j. m. norrisu17...@att.net wrote:
Would it make sense for someone to collect a 'wish list' of
'architectures
and registers'
and then prioritize it?
Ultimately we need patches :-) It doesn't matter if we want
I investigated a bit, and openocd needs to provide an XML target description
(qXfer:features:read) to GDB that supports it (qSupported:xmlRegisters).
I'd prefer a patch that just fixes it once and for all, but in lieu of that and
as a start perhaps a patch w/the .xml file and openocd.texi
After updating to GDB 7.3 from 7.2, I can no longer connect to openocd
(git version from couple of days ago). The target is a Cortex-M3
STM32F207, and I start openocd using:
openocd -f interface/jlink.cfg -f target/stm32f2x.cfg
The output from GDB looks like this:
arm-none-eabi-gdb
We need more support in OpenOCD to handle variations on the ARM
architecture and registers. Spencer wrote about this a while ago.
Patches anyone?
--
Øyvind Harboe - Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / International +47 51 87 40 27
http://www.zylin.com/
We need more support in OpenOCD to handle variations on the ARM
architecture and registers. Spencer wrote about this a while ago.
Patches anyone?
Would it make sense for someone to collect a 'wish list' of
'architectures and registers'
and then prioritize it?
Would it make sense for someone to collect a 'wish list' of 'architectures
and registers'
and then prioritize it?
Ultimately we need patches :-) It doesn't matter if we want something but nobody
can work on it, but perhaps it could be good as a starting point for a
discussion?
--
Øyvind
On Thu, Aug 25, 2011 at 2:16 PM, j. m. norris u17...@att.net wrote:
Would it make sense for someone to collect a 'wish list' of
'architectures
and registers'
and then prioritize it?
Ultimately we need patches :-) It doesn't matter if we want something but
nobody
can work on it, but perhaps
