From: Stanislav Meduna <stano@meduna.org>
To: ecos-devel@ecos.sourceware.org
Subject: OpenOCD, Cortex-M3 and threads - any success?
Date: Fri, 18 May 2012 21:16:00 -0000 [thread overview]
Message-ID: <4FB6BC02.8040600@meduna.org> (raw)
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
next reply other threads:[~2012-05-18 21:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 21:16 Stanislav Meduna [this message]
2012-05-19 12:26 ` Stanislav Meduna
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FB6BC02.8040600@meduna.org \
--to=stano@meduna.org \
--cc=ecos-devel@ecos.sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).