Forum Replies Created
-
Posts
-
Hi,
This is a known limitation. OpenOCD requires the WinUSB-based driver, while Segger J-Link software uses their own proprietary driver.
This can be fixed permanently if Segger either shares their driver specification with the OpenOCD community (and someone adds support for this to OpenOCD), or J-Link software itself is modified to recognize the WinUSB driver. Both options are fairly complex, so we would not expect either of them to become available in the near future.
That said, you can switch the driver back very easily. Simply run UsbDriverTool by clicking the corresponding link in OpenOCD Settings -> Manual mode, right-click on Segger J-Link and select “restore default driver”.
Hi,
This could be an indication of a wiring problem, so errors can occur intermittently and it may appear that one IDE works, while a different IDE with slightly different timings does not. Please double-check your board connections.
Another reason for this could be that your firmware is disabling the JTAG unit. Please try modifying the OpenOCD scripts as shown in this tutorial to enable the “connect under reset” mode.
In order to understand what is going on, please use the Call Stack window to locate the code that calls the syscall function.
If the syscall is used to report a critical error, please try tracking back what causes the error.
Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.15.1406.msi
We have added an option under Tools->Options->VisualGDB->Embedded->Other that controls whether VisualGDB stops on unsupported syscalls.
Hi,
Yes, spaces in toolchain paths can cause strange problems, so we generally recommend avoiding them.
Hi,
Thanks, looks like our bug. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.2.15.1403.msi
Hi,
The Makefile-based projects are designed to be built outside VisualGDB as well, so they don’t support using VisualGDB variables in settings that are stored in Makefiles. Please use relative paths (e.g. ../MathLibrary/Debug) instead.
Hi,
The Keil toolchain output should not bypass the regex filters, but it could use some special unicode characters that could interfere with the regexes.
Please try running “make > build.log” from the command line and then double-check using a hex editor that the lines generated by Keil look exactly the same as the lines printed from the Makefile. You can also send the log file to our support email so that we could check it for you (please attach it instead of pasting to avoid automatic character transformation).
We have not tested it with Keil as we don’t officially support it out-of-the-box yet, sorry.
Hi,
Thanks for letting us know. We will consider making the button state more explicit for the dark theme.
Hi,
This could indicate a corruption of the Clang IntelliSense database files. Please try closing the project and removing the CodeDB folders under the the project directory.
Hi,
This looks like an unhandled semihosting call (mechanism used by the firmware to send printf() output to the debugger). Please ensure that you have semihosting enabled via VisualGDB Project Properties -> Debug. Either way, this message can be just ignored as well as it does not indicate an error.
Hi,
JAYLINK_ERR_DEV might indicate a driver issue. Are you able to use J-Link with OpenOCD (not Segger gdb stub) to debug normal ARM devices? If yes, it could be wiring problem instead.
Hi,
Thanks, we are aware of this. As those warning don’t really have any side effects and don’t appear unless the extra warnings are enabled, we recommend simply suppressing them via per-file settings.
If you don’t want to do that, you can send us the patch adding the necessary attributes and we will include it in our release branch, but we don’t have any plans of addressing them on our side, as we prioritize other features over it. Sorry.
Hi,
In order to keep VisualGDB price competitive, we only directly support the most popular devices and offer various customization mechanisms to allow our customers to easily add support for the devices that are not directly supported.
The easiest way to create a project for an unsupported device is to follow our legacy device tutorial.
Our BSP generators on github have a very basic Wiki page that outlines the basic concepts, but generating a full-blown BSP would much harder than just setting up a manual project (and exporting it to a template).
We also provide a service for creating BSPs for rare devices on demand, so if you don’t want to go through this process yourself, feel free to contact our sales to get a quote for a custom BSP.
