Still using OpenOCD in Workbench?

Developer Tools
1

Is Particle still using OpenOCD (auto-installed) via the Workbench plugin to VS Code?

Seems when I installed Workbench on a new PC a dir went away; specifically -
*used to look like this (could run bin\openocd.exe from this 'adhoc' ) -
image

*but now looks like this (no 'adhoc' folder, else 'particle' still present but bin\openocd.exe doesn't work from here) -
image

To reiterate, both 'adhoc' and 'particle' have "bin\openocd.exe" nested under them, but the 'new setup' (thru 'particle' folder) doesn't seem to work -

image
image833Ă—272 17.6 KB

Even when trying to use the tried and true routine from this great post (noting it still works on the old PC) -

Bonus,
Do you suppose this is also related to why the debugger isn't working, as noted here? (Means the openocd script issue is the root cause?)

2

Added to our issue tracker. Not sure of the answer. @Support can you bring to Triage?

2 Likes
3

Hi @emcdee

To clarify: does the openocd work well on a fresh installation (new computer in your case) but it is not working when updating from a previously installed version on your old computer?

4

Ah, so the openocd

  • works on the 'old' PC (thru the 'adhoc' folder, installed sometime back still running Win10),
  • but NOT on the 'new' PC (w/ just the 'particle' folder, installed recently running Win11)
5

Thanks!

I'm passing all this information to the team to take a look. I will be back to you soon.

1 Like