Hi! As I've already mentioned, I also had trouble with getting rtos support working. I just got around to try it out again. I'm still getting a segfault when after starting the debug session from eclipse.
Attached are the configuration files and the openocd debug_level 3 output. As you can probably see from the configuration files, I am using NXP's lpc1758 device, with FreeRTOS, and a couple of (~4) tasks. The segfault occurs when I start the debug session from eclipse. As I wrote this email, I solved the issue, but I will post this mail to the list nonetheless. The problem was that I started the debug session without uploading the code to the controller, so the code on the controller and the elf file were not in sync. There is not really much to do in such a case, but it should not cause a segfault IMHO Regards, Ákos Vandra On 27 April 2012 06:35, Paul Fertser <fercer...@gmail.com> wrote: > Morning, > > On Thu, Apr 26, 2012 at 11:01:49PM +0200, Freddie Chopin wrote: >> W dniu 2012-04-26 22:07, Paul Fertser pisze: >>> On Thu, Apr 26, 2012 at 09:56:23PM +0200, Freddie Chopin wrote: >>>> 1. I cannot make RTOS support work >>> >>> This's with eclipse i assume and that requires working without Eclipse >>> first. >> >> Well, it still leaves the issue of OpenOCD not detecting anything (not >> reporting FreeRTOS), or maybe you see some underlying condition that >> links these two issues... I don't know (; It just works perfectly >> perfect via Eclipse (not counting the RTOS thing)... > > Since i have no idea how exactly Eclipse interacts with gdb (and i do > not think i was able to find any decent documentation about the topic) > i assume that it passes some questionable unneeded commands that might > prevent RTOS support from working. > > And since i know for sure that my bare gdb config works for the > purpose, i come to the conclusion that Eclipse is doing something > strange and you never hit some RTOS-specific codepath that leads to > OpenOCD's segfault while with the correct config you do. Apparently, > there's still some nasty bug left but to debug it one needs to see the > backtrace. > > If you're going to try copying the unstripped binary and the sources > from your GNU/Linux system you'll most probably need to put the > sources at exactly the same path as they were for gdb to be able to > find them (should be possible with mingw). > > HTH > -- > Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! > mailto:fercer...@gmail.com
Open On-Chip Debugger 0.5.0-dev-g2780cba-dirty (2012-04-13-23:33)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
adapter_nsrst_delay: 200
10 kHz
666 kHz
Info : KT-LINK JTAG-Mode initialization complete...
Info : max TCK change to: 30000 kHz
Info : clock speed 666 kHz
Info : JTAG tap: lpc1768.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part:
0xba00, ver: 0x4)
Info : Selecting JTAG transport command set.
Info : AP INIT COMPLETE
Info : lpc1768.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: FreeRTOS
openocd.cfg
Description: Binary data
iqprogrammer.cfg
Description: Binary data
lpc1768.cfg
Description: Binary data
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
