Hi,
is anyone out there working on something that they would like
to see in the next release?
I know Tomek has been working on SWD. Here we need resources
to review, give feedback and look into what it would take to bring
this to a state where the community is happy to take responsibility
for
Hi
Yesterday I posted a patch that enhances cortex_A hardware breakpoint
functions(hybrid breakpoint), I will be glad if it's merged for next release.
By the way I was surprised, my email does not appear on the mailing list.
Best regards
-Original Message-
From:
On Fri, Aug 19, 2011 at 9:03 PM, Antonio Borneo
borneo.anto...@gmail.com wrote:
On Fri, Aug 19, 2011 at 6:36 PM, Xiaofan Chen xiaof...@gmail.com wrote:
[...]
Thanks a lot for the updates. Yes I can confirm that V4.33h beta firmware
fixed the issue with OpenOCD for V8 version of J-Link. Thanks
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
On 08:12 Thu 25 Aug , Øyvind Harboe wrote:
Hi,
is anyone out there working on something that they would like
to see in the next release?
I know Tomek has been working on SWD. Here we need resources
to review, give feedback and look into what it would take to bring
this to a state
On 16:52 Thu 25 Aug , Xiaofan Chen wrote:
On Fri, Aug 19, 2011 at 9:03 PM, Antonio Borneo
borneo.anto...@gmail.com wrote:
On Fri, Aug 19, 2011 at 6:36 PM, Xiaofan Chen xiaof...@gmail.com wrote:
[...]
Thanks a lot for the updates. Yes I can confirm that V4.33h beta firmware
fixed the
On Thu, Aug 25, 2011 at 2:12 AM, Øyvind Harboe oyvind.har...@zylin.com wrote:
Hi,
is anyone out there working on something that they would like
to see in the next release?
I know Tomek has been working on SWD. Here we need resources
to review, give feedback and look into what it would take
Hi Evan,
GDB manual says about qP:
Don't use this packet; use the `qThreadExtraInfo' query instead (see below).
Since qThreadExtraInfo is already supported in rtos.c, why qP is
still needed?
Regards,
Jie
___
Openocd-development mailing list
Hi Evan,
I'm wondering why threadid_t is int64_t. Is there any known RTOS needs
int64_t for its thread id? Can it be long?
Regards,
Jie
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
Hi,
There are a lot of coding style mismatch in the current OpenOCD code.
I'd like suggest setting a rule that asks fixing all coding style
issues before a patch is merged.
And there are still something missing on
http://openocd.berlios.de/doc/doxygen/html/stylec.html , like
* how to deal with
I used int64_t for threadid because in the implementations I wrote for
FreeRTOS and ThreadX, the threadid is actually the address of the
thread control block. Hence if it is running on a 64 bit processor
(currently unlikely) it would need a 64 bit address.
Regards,
Evan
Quoting Jie
Backward compatibility is the reason -
When I was testing with GDB+eclipse I found that OpenOCD received qP
packets sometimes, and I think I implemented it first, before reading
that same quotation you mentioned. Then when I implemented
qThreadExtraInfo, I figured it was nicer to keep qP
16 matches
Mail list logo
