Loading...
 

Zephyr project on STM32

   Zephyr Workbench, a VSCode extension to manage Zephyr on STM32.
It enables users to easily create, develop, and debug Zephyr applications.
Main features:
  • Install host dependencies.
  • Import toolchain and SDK.
  • Create, configure, build and manage apps.
  • Debug STM32.
You can directly download it from the VSCode marketplace
For more details, visit the Zephyr Workbench

System Workbench for STM32


You are viewing a reply to debugger won't start : again !  

debugger won't start : again !

no, this does not seem to be the same issue. The distro CDT is still at 9,3,2

Eclipse GDB Hardware Debugging

Version: 9.3.2.201709271208
Build id: @build@

I have two systems both running Fedora 26 and essentially in the same state. The above output was from the laptop that I have been using off-site recently.

Returning to the main system I found that it was using CDT 9.4 , this seems to be pulled in by the ac6 installation process and the distro eclipse-CDT was not installed. This does display the TCP/IP error known to affect 9.4 .

To revert this to 9.3, I installed the distro eclipse-CDT package and then restarted eclipse. It now shows CDT 9.3 . However, the TCP/IP error is still occurring.

‘’Error in final launch sequence
Reset command not defined for device ‘Generic TCP/IP’‘’

Time to drop this unreliable mountain of abstraction layers and poorly maintained packages and get back to simple command line debugging, which will probably be ten times faster and more reactive.

No. This whole situation is a mess.

I have one system working but the other one shows this message and is running 9.3.2 which is supposed to be before the update which caused the problem. I was getting a different “invalid context” error before.

I have given up on ac6 closed source, poorly tested and unmaintained debugger and am moving over to using geany editor on linux.

It is possible to get all the arguments to build from command line by looking at the debugging console. I’ve blocked eclipse from updating in case it craps on me again.

I was never happy about relying on blindly installing “unsigned” prorietory software into eclipse. This have just motivated me to do something about ti.