On Tue, May 17, 2011 at 10:16 PM, Øyvind Harboe wrote:
>
> Good work!
>
> I think your chances of getting help on this one would
> improve if we get this into the official repository first.
>
> If your code is well tested, I'm inclined to commit it as-is as
> a starting point to make improvements
Which chip?
--
Ø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/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
___
Openocd-develop
Are you still comfortable with this patch?
Any objections?
Anyone did any testing on other targets?
--
Ø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/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG deb
Any objections?
--
Ø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/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
___
Openocd-dev
Good work!
I think your chances of getting help on this one would
improve if we get this into the official repository first.
If your code is well tested, I'm inclined to commit it as-is as
a starting point to make improvements and get testing going.
A general comment about error messages. The er
I am attempting to use OpenOCD with a cellular chipset with an ARM11 and an
ARM7+DSP core. I can access it with the Lauterbach debugger, but I find the
interface very difficult to use and would prefer OpenOCD.
It looks like some sort of TAP controller, perhaps like an OMAP3. Has anyone
seen anythi
> current_threadid is neither 0 or 1. I think that the 0 is the case
> where the current thread has not been updated, but I'm not sure why
> the test for 1. Should it instead be a test for -1 (the
> initialisation value for the global variable) to check whether it has
> been updated at all? If s
