[support]

@hikingDev

Thanks, the assemblies on your machine do match our test setup, however, it looks like you are using a couple of extra VS extensions that could be interfering with the WPF.

Please try disabling all other extensions via the Extensions->Manage Extensions command in Visual Studio. If it solves the problem, please try checking if enabling a particular extension triggers the problem, so that we could try installing it on our side and reproducing this.

Edit: for what it’s worth, you can try this build: VisualGDB-6.0.3.4994.msi. It has RemoteHostSelector.Mode renamed to RemoteHostSelector.HostSelectorMode, so if the old name was triggering some strange name collision, it should not happen anymore.

[support]

Thanks for confirming this. It looks like a rather strange assembly load issue. Please try this build: VisualGDB-6.0.3.4993.msi

If the problem persists, please click Help->About VisualGDB while holding the Shift key. The About window will show one extra button called “Troubleshoot Assembly Errors”.

Once you click on it, VisualGDB will generate a detailed report showing possible conflicts. Please attach the report together with the updated call stack from the error message, and we will look further into it.

[support]

Hi,

Based on a quick look, the CCOUNT is indeed not mapped to memory, so reading it would involve patching the ESP32 OpenOCD to allow reading it via special command.

If you would like to get it working, we can offer 2 options:

1. You can try convincing Espressif to add an OpenOCD monitor command for reading CCOUNT (it should be runnable via gdb), or implementing it yourself. If you can get it working, we can help you configure VisualGDB to use it, as long as you have an active VisualGDB license.
2. If we see sufficient interest in this feature from other paid users, or if someone orders it as a custom feature, we can do the OpenOCD patching on our side. If you would like to get a quote for this as a custom feature, feel free to contact us via the support form.

 

[support]

Hi,

Sorry, had a typo in the path. The correct path to DWT.xml would be C:\Program Files (x86)\Sysprogs\VisualGDB\TimestampProviders\DWT.xml.

[support]

Hi,

Sorry, it’s hard to suggest anything definitive based on the description you provided. Please try attaching screenshots of the entire uncropped Visual Studio window showing the project you created, the menus you are using to add files, and the folder that is shown in the “Open file” dialog, and we can try to suggest how to alter it.

[support]

Hi,

This is correct. The chronometer relies on the DWT_CYCCNT register, that is only available on ARM Cortex cores.

The Xtensa cores have a similar register called CYCCNT, so you can try copying the %VISUALGDB_DIR%\DWT.xml file under a new name and changing it to use the Xtensa CYCCNT address, but we have not tested it on our side and cannot guarantee that it will work.

[support]

Hi,

A reasonable strategy would be to get it working outside VisualGDB first (e.g. with PuTTY), make sure it works the way you expect it, and then describe your setup so that we could help you replicate something similar in VisualGDB.

[support]

Thanks for verifying your license. This problem would normally be caused by a bug in the .Net image rendering logic that is triggered by some color profiles, although we have fixed it in the latest 6.0 branch.

You can try reverting to the default color profile via Windows Color Management -> Advanced -> Device Profile = System Default.

If it doesn’t help, please try creating a new project selecting the “full-custom” debug mode in the wizard. Does it show the Debug Settings page correctly? If yes, does switching to OpenOCD immediately show an exception?

[support]

Strange. Could you please share a screenshot of the Help->About VisualGDB window?

[support]

Thanks, we have fixed it on our side and will include the fix in the upcoming VisualGDB 6.0 Beta 3.

If you do not want to wait, you can patch it on your side in the %VISUALGDB_DIR%\MSBuild\PropertyPages\armclang\compiler.xml file.

[support]

Hi,

This behavior was added because the recent versions of the ARMClang toolchain have deprecated the armasm executable, recommending to build them with armclang instead.

You can always restore the old behavior via VS Project Properties -> Configuration Properties -> Keil Settings -> General => Build assembly files with the C compiler = false.

[support]

Hi,

These options should not affect the compiled program. The exact -MD -MP -MF <dep file> combination tells the compiler to produce a dependency file (.dep) for tracking the headers used by this source file (so that VisualGDB would know which files to rebuild if a header changes). If you omit the -MF option, the compiler will try to automatically derive the dependency file name from the object name (which could be different between different compiler types/versions), so VisualGDB uses it to explicitly tell where the dependency file should be created.

The -MP option adds extra Make targets for the header files themselves. They are not directly used by VisualGDB, but they won’t affect the code produced by the compiler either.

You can read more about these options in the GCC documentation. Clang/ARMClang reuses the same syntax.

That said, if you can confirm that changing these options does change the actual code produced by ARMClang, we can gladly investigate it further.

[support]

Hi,

Based on what you described, including a specific header file from your project into a CPPUtest project results in a build error. VisualGDB doesn’t crash or do anything unexpected – it reports the build error as it is supposed to.

In general, VisualGDB cannot automatically fix errors in the code, or automatically make different libraries compatible. It’s up to the user to make sure the code they are trying to build does not contain errors, and that different pieces they are trying to put together are compatible.

You can try exporting the build command line used by VisualGDB into a batch file as shown here and building it manually. Once you reproduce the same build error, you can troubleshoot it just as if it was a regular CMake C++ project not involving VisualGDB.

[support]

Hi,

It’s a part of the project template mechanism, so the GUI for managing it is indeed only available starting from the Custom edition.

That said, the add_bsp_executable() and related commands work with all editions, are fully documented and are expected to remain fully backward-compatible in the future VisualGDB releases. So you can still rely on the VisualGDB’s CMake framework as long as you define the frameworks manually.

[support]

Hi,

It’s hard to say why exactly the command would not be visible. Perhaps, you selected a different project type, or are not using the Custom edition.

If you could attach a screenshot of the entire uncropped Visual Studio window and the context menu with the missing command, we might be able to suggest something.

[Author]

Posts