[support]

Hi,

This feature is very new and requires installing the latest development build. You can download and install it here: VisualGDB-5.5.7.3682.msi

[support]

Hi,

It’s hard to say why printf() would not work on a specific device. If you could reproduce the problem with the latest VisualGDB (v5.5), toolchain and the SDK on one of the officially supported Nordic development boards, we should be able to fix it. Otherwise, please consider contacting the device vendor for further help.

[support]

Thanks for the update. Looks like the file has the write permissions, but might be inaccessible due to other issues (e.g. bug in the shared folder driver).

Please try editing the same file using the:

1. The nano editor via SSH.
2. SmarTTY’s editor in the smart terminal mode (File->Open Remote File).

Please let us know whether each of these options works.

[support]

It looks like you are testing the entire folder rather than the file shown in the error message.

Please try using a text editor (e.g. nano) to edit exactly the same file that VisualGDB could not access. If it can be saved successfully, it could be a VisualGDB-level issue and we should be able to fix it. If not, it has something to do with the way the folder is mounted and is outside of VisualGDB’s control.

If you want to keep the code base on Windows, please consider selecting it on the “Source code access” page of the wizard. It allows explicitly choosing between keeping the files on Windows and uploading them during build vs. accessing them via SSH vs. other methods.

[support]

You can find our the latest version compatible with your key, and also manage renewal an upgrade options on the following page: https://sysprogs.com/splm/mykey

[support]

Hi,

Version 5.3R8 is very old and indeed may not work with the latest Python versions. Please try updating to VisualGDB 5.5 Preview 7.

[support]

Hi,

It looks like the location where you have the project (that is redacted on the screenshot) is not writable to your Linux user account.

Please double-check the mount point permissions and make sure the Linux user can access it. You can quickly check whether a file is writable by running the following command via SSH:

test -w <file path> && echo "Writable"

If you are not sure how to configure mount points, please try placing the project directly inside the home directory on Linux. It should normally be always writable.

[support]

Hi,

Generally, Cortex-R devices are somewhat niche, so we are not planning to support them directly unless we see more traction. As a workaround, you can always create a project manually as shown in this tutorial.

We have also developed a tool for converting the projects generated by TI’s HalCoGen into VisualGDB BSPs. However, it was created as a part of a custom paid BSP requested by one of our customers, so we cannot guarantee that it will work with all device families. It could be a good starting point, but it may require some tweaking before you get a fully usable BSP out of it.

[support]

Hi,

No problem, we can help you get it working, however we would first kindly ask you to renew your technical support here as it has recently expired.

[support]

This actually comes from the new ESP-IDF toolchain that does not include the MinGW shell anymore. Please try this VisualGDB build: VisualGDB-5.5.7.3679.msi. We have added a context command to Solution Explorer for launching the “monitor” command. Note that if the monitor settings are inconsistent or missing, the command will exit without printing anything. You can find out its output by dumping the “monitor” command to a batch file (see this page) and running it manually from a Command Prompt window.

[support]

Thanks, we have updated VisualGDB to handle it correctly: VisualGDB-5.5.7.3679.msi

[support]

Hi,

Looks like Espressif has changed the internal structure of the config definitions again. We have updated VisualGDB to handle the new structure in this build [VisualGDB-5.5.7.3679.msi].

That said, ESP-IDF 4.1 is still a pre-release, so it may change again. If you would like to avoid disruptions to your workflow, please consider waiting until it becomes a stable release use the version that we will ship with our toolchain (it will be tested for compatibility and should work out-of-the-box).

[support]

Sorry, we do not have any special GUI for comparing two external projects.

Regarding the differences, it’s hard to say why the numbers would not add up. The difference could be coming from other source files, or library functions that are not associated with any particular source file.

[support]

Hi,

Thanks for reporting this. We have just released an updated version of the STM32 BSP that defines the FPU for all the devices correctly. You can install it via Tools->VisualGDB->Manage VisualGDB Packages.

If you still need help overriding the settings, please let us know.

[support]

Thanks for the detailed repro example. We have reproduced the problem and fixed it in the following build: VisualGDB-5.5.7.3678.msi

[Author]

Posts