Is this an issue with new SDK?
Running into the same issue here.
What's considered new? I'm running 2.4.1 - I know there may be a 3.0.0 (even 3.0.1) somewhere, but I have a hard time finding it.
I've sent invites.
Unfortunately, still an issue for 3.1.0; steps to reproduce is the same as OP
What system/OS are you running on?
Is this issue 100% reproducible?
When the hang happens - can you go to the appropriate task manager and see if the fdti openocd application is still running or not?
We cannot reproduce this at this moment. So need more information from people who can.
osx 10.9.5 running on a early 2011, 13" mbp
The process 'openocd-all-bcrm-libftdi_run' starts when running debug in eclipse, and stops when terminating the debug session.
I will try this on a different machine running osx and report back.
Were you able to reproduce this issue using their instructions?
Here were my steps:
- Change jdk to 1.6 and run WICED debug on our application; hangs on terminate
- Open a new hello world project, debug according to their instructions using gdb (/usr/local/bin/gdb); debugs and terminates correctly
- Run WICED debug on our application; hangs on terminate
- Run WICED debug on snippets; hangs on terminate
GDB traces output:
WICED IDE (Helios)
601,197 31-interpreter-exec --thread-group i1 console kill
601,198 ~"Kill the program being debugged? (y or n) [answered Y; input not from terminal]\n"
601,247 33-break-delete --thread-group i1 2
601,247 34-break-delete --thread-group i1 3
601,247 35-break-delete --thread-group i1 1
601,247 36-break-delete --thread-group i1 4
I can detach the gdb process by issuing 'detach' from the gdb console. Quitting gdb from the console seems to produce the same results.
It feels like Helios isn't aware when gdb quits, and hangs from there. Perhaps Eclipse has fixed this at some point.
Side note, the IDE bundled with WICED 2.4.1 OSX install has a couple of local references under
Eclipse preferences --> Install/Update --> Available Software Sites
Found a temporary workaround that's much better than force closing
At any point you'd like to terminate, do the following:
- Bring up the gdb console in WICED IDE (you may need to switch console tabs)
- Disconnect the remove device by entering 'disconnect' followed by an 'enter'
- Terminate last_built.elf first (right click --> terminate, or left click to select, then click terminate)
- Terminate gdb afterwards (right click --> terminate, or left click to select, then click terminate)
- must be done in this order
Selecting and terminating last_built.elf also seems to work.
I am finding exactly the same issue (Yosemite, SDK 2.4.1 - as I am using an STM32F1xx in an SN8200x).
The work-around seems to work but a fix would be appreciated.