I fired up GDB against an ARM1136 with current git code and
observed the "breakpoints work in Tcl, fail in GDB" problem.
So I committed a fix that makes GDB work too, at least on
an omap2420 core.
It'd be worth verifying this works on other ARM1136 targets.
- Dave
___
On Thursday 21 January 2010, Øyvind Harboe wrote:
> Sometimes we saw two strange blank spaces at the beginning
> of the telnet lines.
>
> progress
> ogress
> >
>
I've not happened across that one myself.
That looks like a spelling correction, IMO. Goes along
properly with the ELF file format
On Friday 22 January 2010, simon qian wrote:
> Hi,
> I plan to add trace support for Cortex-M3 to Versaloon.
> Hardware is ready, first trace port is SWO configured in UART mode.
Do you have a CM3 where that doesn't require SWD support to
be working? The chips I've looked at so far use the option
Hi,
I plan to add trace support for Cortex-M3 to Versaloon.
Hardware is ready, first trace port is SWO configured in UART mode.
Is there codes in OpenOCD available to configure the TPIU and ITM module for
SWO trace output?
Or implement it by add the configuration operations into config file of
STM
On Friday 22 January 2010, Florian Echtler wrote:
> - is it acceptable to handle XSDRB and XSDRC identically? AFAICT the TAP
> should be in Shift-DR state anyway at that point?
If it were, there wouldn't be two distinct opcodes. :)
Xilinx XAPP503 (defining XSVF) says in Appendix B:
XSDRB
On Friday 22 January 2010, Edgar Grimberg wrote:
> OK, can you provide me with the revision and the range I have to skip
> (parameters for git bisect skip)?
I think it would suffice to just make sure that both
ARM11: partial support for standard ARM register interfaces.
ARM11: rem
Hello again,
> I have to replay an XSVF file using openocd which uses the XSDRB, XSDRC
> and XSDRE commands. I'm definitely not a JTAG expert, but I've hacked
> together a patch to support these three commands. It seems to work on my
> Spartan3A device, though I haven't done a lot of testing yet.
On Fri, Jan 22, 2010 at 7:40 AM, David Brownell wrote:
> On Thursday 21 January 2010, Edgar Grimberg wrote:
>> >> and want to see what a bisection that skips known-incomplete stuff
>> >> will turn up.
>>
>> 5eb893ec41c8c6cf6499558b6fed826b65e18a16 is first bad commit
>>
>> Does this make more sens
