W dniu 2012-10-16 17:01, Jonathan Dumaresq pisze:
> Hi Freddie,
>
> Freddie Chopin wrote:
>> You need to use "GDB (DSF) Hardware Debugging Launcher" in GDB
>> Hardware Debugging configuration - not the usual "Standard GDB ...".
>>
> I use GDB Hardware Debugging->GDB (DSF) Hardware Debugging Launcher
>
> This should be the same as your.
>
> In the Debugger pan, I check the Force thread list update on suspend too.
Actually I just managed to get it to work in the "normal" launcher
(Standard...).
I start OpenOCD with theses arguments:
-f interface/ftdi/jtagkey.cfg -f target/lpc1769.cfg -c "adapter_khz 250;
reset_config trst_and_srst; lpc1769.cpu configure -rtos auto"
Then in GDB Hardware Debugging you HAVE to add this line to
initialization commands:
file /your/full/path/to/elf/file.elf
make sure not to use backslashes.
Unfortunatelli with Standard Launcher you don't see thread names... With
DSF Launcher you see thread names and stares, but other pieces are not
working as they should... This mode also works with the fix from above
("file ...") - you may want to check "force thread update on suspend"
too - just as you did.
4\/3!!
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
