Community news, upcoming events and general discussions
Threads: 36 Posts: 88
Get technical support from the community
Threads: 1427 Posts: 7608
Threads: 18 Posts: 64
Tell us how to make XDK better!
Threads: 36 Posts: 119
Share and discuss community member projects
Threads: 81 Posts: 350
I wrote some code and wanted to debug it. Its possible to build the project without any errors and warnings, but when trying to debug it the following message appears:
Failed to execute MI command: -exec-run Error message from debugger back end: Error creating process E:/Tools/XDK-Workbench/workspace/XDK_CollectAndSend/XDK_Application/debug/XDK_Application.out, (error 193). Error creating process E:/Tools/XDK-Workbench/workspace/XDK_CollectAndSend/XDK_Application/debug/XDK_Application.out, (error 193).
..a shorter workspace path - it doesn`t work
..to check my workspace path for spaces - there`re none
For more informations take a look at the attached images.
Thank you very much in advance!
Hi Michael, how are you?
The debug is actually possible on XDK but not in the regular way as a desktop C code, you need to use a special debug tool, for XDK, is called JLINK, with this you only need to attach it on the XDK´s 10 pin header, connect to USB, then just use the button Debug on XDK perspective of the workbench, it will create a JLINK launcher, the correct debug interface for XDK C code.
The problem here is, JLINK is actually a little expense tool, but you can find the EDU version to use in non commercial projects with a more affordable price check it out: https://www.adafruit.com/product/3571 Let me know your further questions. Best Felipe
as Felipe already mentioned, debugging on the XDK is possible via the mentioned JLINK adapter.
I am not quite sure, if you are already using a JLINK or not. Would you be so kind and tell us if this is the case?
We did not tried the mentioned EDU version yet. We internally use the J-link lite version.
If you are already using a JLINK, I would like to know which kind of debugger you are currently using.
Please note that without the J-Link adapter you can only debug via printfs, which I can not recommend, because there are several limitation like you can not step through the application while it is running.
In addition, I compared your screenshots with the settings in the XDK-Workbench 2.0.1 and observed that there are some differences. Therefore I assume you are not using the latest XDK-Workbench 2.0.1.
To be able to reproduce your issue and to propose a suitable solution, I would like to know which version of the XDK-Workbench and operating system are you currently using?
Kind regards, Franjo
unfortunately I`m not using a JLINK adapter, because my contacts from Bosch
said debugging on the XDK should be possible without. Thank you for your answers!
Now I`ve to get one of them.
For your information - im using Workbench 2.0.1 on a Windows 7 (x64) system.
Unfortunately, you are not able to debug the XDK without a JLINK adapter. The only other method I know of would be with printf-statements, since you cannot peek into the state of the XDK otherwise.
If you need any help with the JLINK adapter, feel free to ask questions in this forum.
which one would you prefer of the segger J-Links - BASE, PLUS or the ULTRA one?
I would buy the PLUS edition because of the unlimited flash breakpoints propertie.
a cheaper alternative, compared to the J-Links BASE/PLUS/ULTRA would be the J-Link Lite. It is mentioned in the General Information Guide. Here's the quote:
If you do not have a suitable debug probe and feel the need to access the debug port, you can buy a “J-link LITE CortexM-9” debug probe from SEGGER (https://www.segger.com/products/debug-probes/j-link/models/j-link-lite/j-link-lite-cortex-m/) by contacting the SEGGER sales team. Please mention that you will use the debug probe for the XDK, as J-link LITE is not sold separately.
We use this one as well, but if you want to buy one of the J-Link debug probes you mentioned, I cannot specifically recommend one of the three. They are all powerful tools, and more than what you would need for the XDK only. I recommend the J-Link Lite if you only use it for the XDK, and one of the others if you also want to use it for other MCUs. If you buy one of them, keep in mind that the XDK only has 10 pins, so you will need a Data Cable with 10 pins instead of 20.
Please tell me if this was helpful, and do not hesitate to ask further questions.