Forum Replies Created
-
AuthorPosts
-
support
KeymasterHi,
We looked into the new CC3220S SDK and unfortunately its internal structure is completely different from the SDK we used for CC3200.
Given that currently the popularity of CC3220S is a fraction of the CC3200 popularity, we do not have any short-term plans for fully wrapping the new SDK.
We could help you resolve any issues you discover while following the legacy device tutorial or we could also build an updated BSP for a small fee as a part of our consulting services if you don’t want to wait until CC3220S gets enough popularity for us to support it officially.
Another option would be to create a project with Code Composer and import it into VisualGDB (or debug the ELF file produced by it via Quick Debug).
support
KeymasterHi,
VisualGDB already allows showing the local variables on top of other suggestions via a corresponding button:
However it does not distinguish all the possible scopes (only local variables vs. everything else).
-
This reply was modified 8 years, 2 months ago by
support.
Attachments:
You must be logged in to view attached files.support
KeymasterHi,
Sorry, this is a bit too specific and non-trivial to add. We would recommend using name filtering (typing a part of the method or a class) and type filters (buttons in the suggestion window) instead.
support
KeymasterHi,
This is a separate issue. Generally ESP32 IDF does not work when built with the disabled optimization (-O0) and requires changing the optimization level to at least -Og. This also fixes the inline functions.
support
KeymasterHi,
You can increase the delay via Tools->Options->VisualGDB->General->SSH->Minimal delay between PTY requests.
Alternatively please try updating your SSH package on the Linux side (see this thread for the related package versions).
support
KeymasterHi,
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.
July 27, 2017 at 16:15 in reply to: Seeing the actual command line used for compiling with MSBuild #11850support
KeymasterHi,
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.
July 27, 2017 at 00:18 in reply to: Seeing the actual command line used for compiling with MSBuild #11844support
KeymasterHi,
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.
July 27, 2017 at 00:13 in reply to: How do you enable the 64-bit version of CppEngineHost.exe in Preview 2? #11843support
KeymasterOK, 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.
support
KeymasterHi,
OK, thanks, we will reinvestigate this within the next 5-10 business days after releasing Preview 5.
support
KeymasterHi,
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.
support
KeymasterHi,
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
support
KeymasterHi,
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.
support
KeymasterHi,
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.
July 25, 2017 at 05:39 in reply to: Seeing the actual command line used for compiling with MSBuild #11824support
KeymasterHi,
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.
-
This reply was modified 8 years, 2 months ago by
-
AuthorPosts