OpenOCD, Cortex-M3 and threads - any success?

OpenOCD, Cortex-M3 and threads - any success?

[Stanislav Meduna]

Hi,

anyone has any success with the eCos thread support in OpenOCD?

I am using the current snapshot of OpenOCD with -rtos auto,
a TI Stellaris Cortex-M3 processor and a gdb 7.4.
This combination is able to successfully detect the eCos
but then probably tries to access invalid memory
and is not able to show the threads.

Setting CYGDBG_HAL/KERNEL_DEBUG_GDB_THREAD_SUPPORT
has no effect.


The OpenOCD shows

Open On-Chip Debugger 0.6.0-dev-00571-g0644754 (2012-05-18-10:41)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.sourceforge.net/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
3000 kHz
Info : clock speed 3000 kHz
Info : JTAG tap: lm3s9b9x.cpu tap/device found: 0x4ba00477 (mfg: 0x23b,
part: 0xba00, ver: 0x4)
Info : lm3s9b9x.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : accepting 'gdb' connection from 3333
Warn : acknowledgment received, but no packet pending
undefined debug reason 6 - target needs reset
Auto-detected RTOS: eCos
Error: JTAG-DP STICKY ERROR
Error: MEM_AP_CSW 0x23000050, MEM_AP_TAR 0x4000f4f0


The debugged application is a simple RAM one running on top
of the RedBoot. eCos is current trunk.


Thanks
-- 
                                         Stano

Re: OpenOCD, Cortex-M3 and threads - any success?

[Stanislav Meduna]

On 18.05.2012 23:15, Stanislav Meduna wrote:

> anyone has any success with the eCos thread support in OpenOCD?

OK.. this can't work. OpenOCD uses fixed offsets in the
Cyg_Thread structure for its magic. With eCos the exact
offsets of course depend on configuration offsets used.

I'll report the issue to the OpenOCD list - this approach
is plain wrong.

Regards
-- 
                                  Stano