[support]

Hi,

Good to know it works. Unfortunately the statistics is currently computed when the report is built (it involves a few advanced cases like multiple sources reporting the same function implemented in a header file), so the filters won’t affect it. We might be able to improve this in the next major release, but we won’t be able to push this into v5.4, sorry.

The entries in the exclusion lists are actually prefixes (e.g. /usr will cover both /usr/local/include and /usr/include). Right-clicking on the files will add the entire directory of this file to the exclusion list, and then you can fine-tune via VisualGDB Project Properties (e.g. exclude the parent directory).

[support]

Hi,

Thanks for the update. Could you please also check if the files/registry values mentioned in steps 7 and 8 are present (replace VisualGDB with VisualKernel in all names)?

[support]

Hi,

Thanks for checking this. Please also check that the .so file is present in the cross-toolchain’s sysroot directory.

If it does, please try adding “-Wl,-verbose” to the linker flags and check the linker output. It will show where exactly the linker is searching for the library.

If nothing helps, please attach a screenshot of the error and the build output with the verbose linker mode turned on.

[support]

Hi,

Sorry for the delay. We originally planned to include an advanced mbed project subsystem into the upcoming Preview 4, that would eliminate the need for a special BSP package, but it got delayed to due a few changes in other external tools. We will investigate the latest mbed release next week and will release an updated BSP.

[support]

Hi,

This doesn’t look like any error that should interfere with attaching. Please check the gdb log for other errors.

[support]

Hi,

Sorry, we are not currently planning direct support for changing the option bytes, as the ST-Link utility from ST already provides a convenient GUI for editing them.

[support]

Hi,

Sorry for the delay. Based on a quick look, we should be able to support one of the TFS-supported formats relatively easily. We should be able to get you a time estimate in the next week. Would that work for you?

[support]

Hi,

Thanks for the very detailed description. It looks like an internal exception in the Visual Studio Automation logic used by VisualGDB to create some project types. It used to get triggered a lot in early preview builds of VS2017, but was fixed after we filed a bug report with Microsoft. This might be another instance of it, or a completely different bug.

We tried quickly reproducing it (creating a new Make-based project in a solution that already has a project), but could not get it to crash. As it might be a glitch in one of the recent VS2017 updates, our advice would be to keep on using the workaround until the next VS update (15.8) rolls out. If the issue persists after the next VS update, please try reproducing it from scratch (i.e. first create a new solution with a new project, then add another project) and share the exact choices you make in the wizard so that we could try reproducing it on our side.

[support]

Hi,

Yes, we are working on that. Due to the large amount of changes (also the integration of the IoT SDK), it’s taking us a bit longer than expected. The current estimate is 2-3 weeks more.

[support]

Hi,

Good to know it works. BTW, you can find out more about the expected project structure for esp-idf-based projects here: http://esp-idf.readthedocs.io/en/latest/api-guides/build-system.html

VisualGDB automatically follows it when creating new projects and cloning samples, but imported 3rd-party project may need adjustment. That said, you can also use the automatic header discovery logic to simply edit the component properties to let it use any include directories you prefer.

[support]

Hi,

Looks like the wiringPi library was either not built/installed successfully, or the toolchain synchronization after it was built did not complete.

Could you confirm that the “build” command for wiringPi succeeded and that the libwiringPi.so file is present in /usr/lib on your Raspberry Pi and in the corresponding directory inside the toolchain’s sysroot.

[support]

Hi,

No problem, please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.3.2335.msi

We have added a context menu command to the coverage report viewer to hide files from a given directory (and a corresponding option to the Code Coverage page of VisualGDB Project Properties).

With gcov files, they are created per translation unit, not per source file, so VisualGDB will automatically locate all the relevant files and build a searchable report from them.

[support]

Hi,

No problem, thanks for reporting this. Please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.3.2334.msi

[support]

Hi,

Stepping through code on Nordic devices could be tricky due to the built-in watchdog that would reset the CPU each time it is stopped for a non-trivial amount of time, although it should not lead to the behavior you are describing.

From a quick look at the log file you attached, it looks that the Segger gdb stub fails to read the CPU registers shortly after the reset command:

Received monitor command: reset
Resetting target
Connected to 127.0.0.1
Read 2 bytes @ address 0x000003B4 (Data = 0xF107)
Read 2 bytes @ address 0x000003E2 (Data = 0x1D3B)
Read 4 bytes @ address 0x2000DFFC (Data = 0x4B642F0A)
Downloading 4 bytes @ address 0x2000DFFC
Reading all registers
ERROR: Can not read register 0 (R0) while CPU is running
ERROR: Can not read register 1 (R1) while CPU is running
ERROR: Can not read register 2 (R2) while CPU is running
ERROR: Can not read register 3 (R3) while CPU is running

This might affect the initial breakpoints or could cause other weird behavior.

Please try updating the Segger J-Link software and/or try adding delays (e.g. mon sleep 1000) before and after the reset command under VisualGDB Project Properties -> Debug Settings -> Advanced Settings.

[support]

Hi,

You can use the /runtests switch of VisualGDB.exe (see this tutorial) to generate an XML file with test results, however we don’t support automatically exporting them to TFS yet. As a temporary workaround, please try converting the output into one of the existing formats (e.g. NUnit) and then using a standard TFS plugin for importing the converted file.

 

[Author]

Posts