Forum Replies Created
-
Posts
-
Hi,
VisualGDB currently only supports kernel event tracing for FreeRTOS: https://visualgdb.com/tutorials/profiler/realtime/freertos/
We are planning to support other OSes in the next releases, although we would not name specific deadlines currently. The only workaround until we support it officially would be to look into our FreeRTOS tracing implementation that is automatically added to the projects when the tracing is enabled (it provides hooks for FreeRTOS functions and sends structured events to VisualGDB using our semihosting API) and making a quick-and-dirty equivalent of this for your configuration.
Hi,
As a quick test, could you confirm that the same problem exists with v5.3 Preview 4? If yes, please try creating a “hello, world” project demonstrating the issue and attach it here (or send it to us via the support form). We should be able to investigate this and suggest a workaround or fix it.
Hi,
If this is a locally built project, the regular VS verbosity setting (Tools->Options->Projects and Solutions->Build and Run->MSBuild project build output verbosity) should get VisualGDB to show the command lines. Alternatively you could simply check the .rsp files (they contain saved command lines). The regular Visual Studio Command Line page won’t show the custom options.
Please also ensure you are using the latest VisualGDB 5.2r9.
OK, we would need to run a few tests of this on our side.
Would you be able to detach the problem from any confidential code and send it to us? E.g. preprocess the file to a single source file, confirm that the problem still happens when opening it and then start removing the parts of the file until you pinpoint the exact declaration that causes this. Using binary search, this should take only a few iterations.
Hi,
OK, thanks, we will reinvestigate this within the next 5-10 business days after releasing Preview 5.
Hi,
VisualGDB actually allows running unit tests directly on embedded devices with no special scripting required: https://visualgdb.com/tutorials/tests/arm/
We would recommend using this functionality instead of scripting it manually. If this does not work, we would be happy to hear feedback and suggestions on improving our unit testing framework to support your case.
Hi,
The ” jtag status contains invalid mode value” usually indicates a wiring problem and could be a result of a damaged board (or the new OpenOCD might be using a higher SWD frequency).
Either way, you can download the older versions of OpenOCD package here:
- http://sysprogs.com/files/visualgdb/hwsupport/EDP/com.sysprogs.arm.openocd/openocd-20161025.vgdbxedp
- http://sysprogs.com/files/visualgdb/hwsupport/EDP/com.sysprogs.arm.openocd/openocd-20161014.vgdbxedp
- http://sysprogs.com/files/visualgdb/hwsupport/EDP/com.sysprogs.arm.openocd/openocd090r11.vgdbxedp
Hi,
This is supported starting from the Custom edition and requires installing VisualGDB 5.3 (currently in the Preview stage). Once installed, toolchains will use multi-version mode automatically and the BSPs can be switched between single-version and multi-version mode via Tools->VisualGDB->Manage VisualGDB Packages.
Hi,
Thanks, we will support VS2017 in the next VisualKernel release scheduled for this Fall. It is planned after the VisualGDB release so we can support the new technology for editing files on a Linux machine directly over SSH, greatly increasing the overall performance.
Hi,
Normally you can just enter “-Ofast” in the corresponding field even if it’s not listed. VisualGDB will understand that you meant an out-of-list option and will handle it correctly.
Hi,
Thanks for the repro. It looks like VisualGDB is getting confused by an unexpected combination of tabs and spaces in your code.
Please try resetting the indentations (by selecting all text and holding Shift-Tab) and then reformatting the document. This should set the indentations properly.
Alternatively you can switch from the Clang-based IntelliSense engine to the regular VS IntelliSense engine via VisualGDB Project Properties to get the regular VS behavior (please note that the VS IntelliSense engine often gets confused by GCC-specific constructs in the embedded code and hence may produce less accurate results).
The comment collapsing is not supported yet, sorry.
Hi,
The message refers to the X11 – mechanism used to show GUI on Linux systems. Normally SSH should forward those connections to your Windows computer and you would see the GUI locally. This could be broken due to several reasons:
- Missing X11 packages server on the Raspberry Pi
- X11 forwarding disabled by the SSH server
- X11 forwarding disabled in the per-host VisualGDB settings
- X11 permissions not configured properly
A quick workaround would be to select “Show X11 windows on the remote computer” on the Debug Settings page of VisualGDB Project Properties.
Hi,
You can enable the global verbose mode via Tools->Options->VisualGDB->Common->Output->Verbose Mode.
Hi,
The answer depends on what exactly you are trying to do. Normally the OpenCV_LIBS variable is exported by the OpenCV library itself and you would need to study its CMakeLists.txt structure to locate the statement that exports it. If you define this variable manually in some of your projects, you could use VisualGDB GUI to edit it, but the exact location would depend on the way the variable is defined.
Hi,
We would recommend importing a Gradle-based project into VisualGDB (e.g. see this tutorial). Projects created with the VisualGDB project wizard are based on Ant and won’t support Gradle dependencies (we will be switching Android projects to the new advanced CMake project subsystem in the next release and will fully support the latest Gradle).
