[support]

Hi,

It looks like VisualGDB is trying to add some file to the project and this triggers an internal exception in VS. Please try updating to VisualGDB 5.3 Preview 8 and check if the problem persists. If yes, please attach an updated stack trace so that we could help you pinpoint this.

[support]

Hi,

The easiest way to do it would be to close VS and remove the old toolchain directory. The latest VisualGDB 5.3 Preview and the latest ESP32 toolchain include a fix that prevents VisualGDB from keeping any files in the toolchain directory open, so it should not be a problem next time you update.

[support]

Hi,

OK, we have investigated this and unfortunately it looks like the debug popup handling for ‘(‘ is hardcoded inside the Visual Studio logic with no reliable way to work around it without negative side effects. So unfortunately we won’t be adding this functionality to the final v5.3, sorry.

[support]

Hi,

Thanks, we have retested this and could only measure a 12% slowdown compared to regular VS IntelliSense. Please ensure that you are deleting the same amount of files with the same layout in both cases. If yes, can you reproduce it on a test project with 1000 generated files? If yes, please send it to us and we will investigate.

[support]

Hi,

This could happen if the sampling is happening too often and the CPU is busy processing the sampling data most of the time. Please try modifying the sampling frequency to something like 100 hz and check if this fixes the problem. If yes, please try experimenting with the sampling frequencies to see the frequency that works.

[support]

Hi,

Thanks, this looks like a known gcc-ar bug.

Please try this build, we have added a workaround to it: http://sysprogs.com/files/tmp/VisualGDB-5.3.8.1800.msi

[support]

Hi,

Please double-check the initialization function you are calling. For instrumentation profiler please call InitializeInstrumentingProfiler() as shown in the instrumentation tutorial, for sampling profiler please call InitializeSamplingProfiler().

Calling InitializeSamplingProfiler() for instrumentation-based profiling won’t work, sorry.

[support]

Hi,

You could try using VisualGDB project templates: https://visualgdb.com/tutorials/arm/templates/

[support]

Hi,

We are not aware of any parameters related to that, however we have observed similar issues with some client devices. We would advise double-checking this with Espressif as they should have a better understanding of what is going on inside the low-level Wi-Fi logic.

[support]

Hi,

Yes, please try setting __attribute__((packed(number)) on the specific structures that need to be packed.

You can also try this build [http://sysprogs.com/files/tmp/VisualGDB-5.3.8.1797.msi]. Once you click ‘details’ in the embedded memory explorer, it will show struct sizes and field offsets directly in the code.

[support]

Hi,

Looks like you are trying to use instrumentation-based profiler without calling the InitializeInstrumentingProfiler() function. Please ensure you call this function if you are using the instrumenting profiler (if not, please double-check your profiling settings, the error would only appear if the instrumenting profiler was selected).

[support]

Hi,

Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.3.8.1797.msi

We have added an option on the “Librarian” page to select between ar and gcc-ar.

[support]

Hi,

We have checked the ST examples for the F429I-Discovery board and they indeed don’t include a COM port example. Please try creating a project based on the FatFS_USBDisk example and then copy the system file and the HAL configuration file from it to the regular USB CDC project. This should combine the F429iDiscovery-specific initialization code with the generic USB CDC logic.

[support]

Hi,

The exact flags would depend on the toolchain you are using. We currently don’t ship any toolchains for Alwinner H5, so we cannot provide a 100% working walkthrough. However if you could share the errors you get here, we might be able to point you in the right direction if we have encountered similar errors before.

[support]

Hi,

Unfortunately we don’t have any specific tutorial for STM32 IAP, so we would recommend checking the STM32 documentation for an example of the memory offsets compatible with the bootloader. If you know the memory offsets, normally applying them should be as easy as just editing the linker script. If this doesn’t work, let us know the memory layout you are trying to get, your current linker script and the behavior you observe and we will help you get it to work.

[Author]

Posts