[support]

Hi,

According to our records, your support period has expired. In order to continue receiving support, please renew your key here: https://sysprogs.com/splm/mykey

[support]

No problem, we have investigated this and released another update. Please update your OpenOCD package via the VisualGDB Package Manager.

[support]

Hi,

No problem, looks like the upstream OpenOCD has renamed some JTAG-related commands and some of the scripts shipped with our OpenOCD build were not updated.

We have fixed the issue. Please try reinstalling the OpenOCD release via Tools->VisualGDB->Manage VisualGDB Packages.

[support]

Hi,

Please see the following page for a detailed explanation: https://visualgdb.com/support/idfcheckout/

Edit: VisualGDB 5.5 Preview 5 now fully supports ESP-IDF 4.1. Simply install it over any other VisualGDB version and get our latest ESP32 toolchain and you will be able to install ESP-IDF 4.1 into it:

• This reply was modified 5 years, 4 months ago by support. Reason: Mentioned new ESP-IDF 4.1 support

Attachments:

You must be logged in to view attached files.

[support]

Hi,

This is already supported via VisualGDB Project Properties -> Debug Settings -> Full-Custom Mode.

Simply specify “–interpreter mi $(TargetPath)” in the gdb arguments and use the “target remote <host>:<port>” as the target selection command. This will connect gdb to a remote target.

You can also automate running the remote OpenOCD instance via the Custom Debug Steps page of VisualGDB Project Properties.

[support]

Sorry, it is not possible for us to provide the exact configuration steps for 3rd-party frameworks and tools, unless it is something extremely common (i.e. relevant to a huge amount of users) and worth supporting out-of-the-box and having a separate tutorial.

We can do the necessary research and publish a detailed tutorial as a part of our paid consulting program (please contact our sales for pricing). Alternatively, we can help you understand the VisualGDB side of the setup. E.g. if you manage to setup the project manually and find the correct compiler command lines and file layout, we can help you setup VisualGDB to replicate the manual setup results.

[support]

This sounds very similar to what is already supported with the VisualGDB project templates.
We actually have a huge collection of tutorials showing various VisualGDB features here: https://visualgdb.com/tutorials/

You can find the one showing the project templates by searching for “templates” on the tutorial list page.

Please also feel free to look through other tutorials for ideas on further improving your productivity with VisualGDB.

[support]

No problem. Please share a screenshot of the entire VS window showing your solution and also a screenshot of the Help->About VisualGDB window and we will help you find the right setting.

[support]

Hi,

Please use the following page to search through all VisualGDB settings: https://visualgdb.com/settings/

You can find the up-to-date setting name by searching for “deploy”. Please also make sure you are using this build, as the Preview 4 might apply the setting incorrectly in some cases: VisualGDB-5.5.4.3549.msi

[support]

Update: to make it less confusing while we are working on supporting the new JSON API, we have released VisualKernel 3.1R3 that will detect the cases when the VIX API is missing and will prompt to suspend and then resume the VM manually. It will still edit the configuration files automatically, minimizing the amount of extra steps.

[support]

Hi,

Just wanted to let you know that we have added support for test resources (files on the Windows machine that can be accessed from the embedded code) to the following VisualGDB build: VisualGDB-5.5.4.3548.msi

You can find a reference of the test resource manager API here: https://visualgdb.com/documentation/semihosting/_t_r_m_a_p_i.html

Please make sure you install the latest semihosting/profiler framework and enable test resources via VisualGDB Project Properties -> Unit Tests. The new functionality, along with detailed tutorials, will be included in the upcoming Preview 5.

[support]

Please note that VisualKernel can only install a symbol package if it has been released by your Linux distribution (e.g. Ubuntu). The released symbol package must exactly match the running kernel, have the same version, build number, etc. Trying to use a mismatching symbol package (e.g. having the same kernel version, but a different build number) will not work, since it will not match the running kernel.

If you are not sure what is going on, please try installing the latest Ubuntu 19.10 from scratch and make sure you use the stock kernel (i.e. don’t install any unofficial kernels). This Ubuntu version is fully supported by VisualKernel 3.1 and should work out-of-the-box.

[support]

Sorry, this is not covered by our technical support. Please refer to the STM32 documentation for further details.

[support]

Unfortunately, VMWare 15 no longer contains the VIX API used by VisualKernel to restart the virtual machine in order to modify its configuration. As a workaround, please follow the steps below to enable debugging of a VMWare 15 machine:

1. Suspend or stop the VM. Make sure it is no longer running.
2. Add the following lines to the vmx file (replace guest64 with guest32 if you are running a 32-bit kernel):

   debugStub.listen.guest64 = 1
   debugStub.listen.guest64.remote = "TRUE"
   debugStub.hideBreakpoints = "FALSE"

3. Start the VM. Make sure the VM log file contains the following lines:

   2020-01-28T10:25:40.627-08:00| vmx| W115: Debug stub: VMware Workstation is listening for debug connection on port 8864.
   2020-01-28T10:25:40.627-08:00| vmx| W115: Debug stub:     (gdb) target remote <host running VM>:8864
   2020-01-28T10:25:40.627-08:00| vmx| W115: Debug stub:     (lldb) gdb-remote <host running VM>:8864

As long as the “target remote” line is present in the log file, VisualKernel will be able to automatically connect to the virtual machine.

We are working on supporting the new JSON-based VMWare API and will make sure that the upcoming VisualKernel 3.2 will handle this automatically and won’t require any manual configuration editing.

[support]

Looks like you did not follow our instructions about creating a project and removing the libraries via VisualGDB Project Properties -> Embedded Frameworks and instead created a project without a linker script and other compiler/linker-level settings. Please make sure you follow those instructions.

[Author]

Posts