[support]

Thanks, the steps you described should normally work, so most likely the problem is caused by some project-specific setting.

Normally, SysprogsInstrumentingProfiler_QueryAndResetPerformanceCounter would be defined in the InstrumentingProfiler.cpp file inside the profiler framework (unless you are using Nordic nRF5x devices that do not have a DWT register and require a timer-based implementation in ProfilerDriver_Nrf5x.cpp).

Searching all files included in the project for SysprogsInstrumentingProfiler_QueryAndResetPerformanceCounter  should explain why it’s not being linked properly.

[support]

Hi,

Yes, please try using the “Add Configuration” button in VisualGDB Project Properties instead. It will make sure all VisualGDB-specific files and settings are properly created.

[support]

Normally it should be added automatically. It’s hard to say why it wasn’t, but if you can reproduce the problem reliably and share the steps with us, we will be happy to fix it.

[support]

Hi,

Sorry, we do not have any USB examples for the EFM32 chips. Please consider asking on StackOverflow or EFM32 forums to get further pointers.

[support]

No problem and thanks for the update. Just a quick clarification from our side: normally the ID/Version variables would be set inside the project file and the _ROOT and _DIR variables would be computed inside the %LOCALAPPDATA%\VisualGDB\FindXXX.props files that are managed by VisualGDB. So deploying these files to the build machine should get the variables working automatically.

You can find more details on this in our TFS tutorials here: https://visualgdb.com/w/tutorials/tag/tfs/

[support]

Hi,

Normally, the function would be defined in the InstrumentingProfiler.cpp file. Please try locating it in Solution Explorer to see why the function is not properly built.

If you have enable the “use custom performance counter” setting, you would need to provide your own implementation of the function (see this tutorial for details).

[support]

Hi,

It looks like your support period has expired a while ago. Please kindly renew it here and we will be happy to point out the relevant settings.

[support]

Thanks, restarting the target between synchronizations indeed reproduced the problem. We have fixed it in the following build: VisualGDB-5.5.7.3704.msi

[support]

Thanks for renewing your license.

We have updated our CC3220 BSP based on the latest SDK from TI (v4.20.00.07). You can install it via Tools->VisualGDB->Manage VisualGDB Packages. Please also ensure you use the latest VisualGDB 5.5 Preview 7.

We have retested it with CC3220 Launchpad using the latest OpenOCD (0.10.0 2020-07-01) and it did work as expected, aside from the “most device registers are zero” error that can be safely ignored for CC3220. If it doesn’t work on your side, please share a screenshot of the error you get and we will help you resolve it.

[support]

No problem, we can help you.

This error happens when you build a FreeRTOS-based project without referencing the semihosting/profiler framework, or without defining that USE_FREERTOS macro.

If the framework is referenced and the macro is defined, please double-check that the ProfilerFreeRTOSHooks.h file is added to the project as a forced include (referencing the profiler framework should do it manually).

[support]

Hi,

Please try double-checking the exact breakpoints set by gdb by running “info breakpoints”. You might have set additional breakpoints that are not shown in the regular Visual Studio GUI.

Also please note that stepping over/out of functions requires creating a temporary breakpoint, that counts toward the overall limit.

You can also obtain a full gdb log of the debug session as shown here and search for breakpoint-related command to understand what contributes to the breakpoint amount the most.

Please also consider using Segger J-Link instead of your current debug probe, since it supports seamless software breakpoints in the FLASH memory.

[support]

Hi,

Please refer to the following pages for information on troubleshooting VisualGDB installation and loading:

• https://visualgdb.com/documentation/troubleshooting/install/
• https://visualgdb.com/support/loadfail/

 

[support]

Hi,

Please let us know the email associated with your license key so that we could check your support status.

[support]

Hi,

The CC3220 devices have a considerably smaller user based compared to mainstream device families, such as STM32, hence we indeed don’t update the CC3220 BSP as often.

We should be able to update our CC3220 BSP based on the latest SDK from TI (and also help you resolve any OpenOCD issues you get), however we would kindly ask you to renew your license first.

[support]

Hi,

Yes, Visual Studio Professional is fully supported.

[Author]

Posts