[support]

Hi,

No problem and thanks for letting us know. We have fixed the issue in this build: VisualGDB-5.6.5.4230.msi

[support]

No problem and thanks for your pull request with adding proper timeout handling to the telnet target.

We have added a new ITargetWithRawPipes interface to VisualGDBExtensibility.dll that should be implemented by the telnet target:

public interface ITargetWithRawPipes : ICustomRemoteTarget
{
    Stream OpenPipeForReading(string path);
}

VisualGDB will call the OpenPipeForReading() method, supplying it the full path of the pipe on the Linux machine (e.g. /tmp/pipe). The target should open it and return a readable stream that VisualGDB will read from a background thread.

Note that the pipe output can contain arbitrary bytes and not just printable characters, so the target may need special handling to escape/unescape them properly. We highly advise testing it by reading a test file containing all possible 256 byte values.

[support]

Thanks for emailing us the detailed repro instructions. We have double-checked everything and confirmed that NRFConnect SDK 1.6.0 was indeed not working out-of-the-box. It turned out, we could not reproduced it initially due to an old value cached in our test environment.

The problem was caused by this commit, removing the deprecated gccarmemb toolchain variant that VisualGDB used due to backward compatibility.

We have updated VisualGDB to use the correct gnuarmemb name: VisualGDB-5.6.5.4230.msi

If you need to build older NRFConnect versions using the old gccarmemb name, you can edit the NRFConnect/GCCToolchainName tag in the %VISUALGDB_DIR%\Rules\RegularExpressions.xml file and simply restart Visual Studio.

[support]

Hi,

No problem. We have added panning support for the following build: VisualGDB-5.6.5.4229.msi. You can now hold Shift and drag it with the mouse to move the viewport around.

We could not reproduce the problem with disappearing graphs, although we have found a glitch that could have been causing it. If the problem persists in the new build, please make sure you can reproduce it from scratch and share the repro steps we could follow on our side, so that we could reproduce and fix it.

[support]

Thanks for sharing this. VisualGDB 5.6 Beta 4 should set HWREGISTER_LIST_FILE automatically. If you are using an older Beta, it might indeed fail to do so under some circumstances.

[support]

Hi,

Thanks very much for sharing this!

[support]

Hi,

VisualGDB can display many different windows, depending on what you are doing. You can find detailed description of most of them in our documentation, tutorials and the list of settings.

If VisualGDB is not working as expected, please provide a complete description how to reproduce the issue from scratch per our problem reporting guidelines and we will try to point you to the relevant setting. Please make sure you include the relevant screenshots, as they often contain important information required to pinpoint the issue.

[support]

The build with the new Live Watch improvements is ready: VisualGDB-5.6.5.4228.msi. Feel free to try it out and let us know your feedback.

[support]

Hi,

In our quick experiments, the breakpoints didn’t work in QSPI. This could be specific to a particular chip we used and could work differently on your one. You can try manually using the hbreak command in gdb to set a hardware breakpoint at a specific function in QSPI. If it doesn’t work, please consider checking it with ST – it might be completely unsupported, or might require some extra setup (e.g. disabling cache).

[support]

Thanks, this indeed looks like a debug symbol problem. Please see the following tutorial for detailed instructions troubleshooting it: https://visualgdb.com/tutorials/linux/symbols/

[support]

Hi,

Programming external memories with OpenOCD indeed requires building and using a special FLASH programming plugin. You can find more information in this tutorial.

[support]

A custom source path mapping should take care of that. If it doesn’t work, please attach a screenshot of your path mapping settings, the full path of the file on Windows where you are trying to set a breakpoint, and a gdb log showing the command that VisualGDB used to set the breakpoint.

[support]

The -mfloat-abi setting should make it to both compiler and linker settings. The easiest way to ensure it would be to use the Configuration Properties -> ARM Settings -> Floating-point ABI setting.

The “frame not in module” error would typically mean that the CPU stopped outside any code that has symbols. You can double-check it by hardcoding a breakpoint (e.g. asm(“bkpt 255”) followed by asm(“nop”) in main()).  Once it hits, try checking the disassembly view. If it displays the “bkpt 255” and “nop” instructions but doesn’t map them to the main source file, there is a problem with symbols. If the code is stopped on a completely different instruction, the problem is not related to the debugger.

[support]

For mbed projects the list of memories (e.g. m_ivt) is computed by parsing the linker script, since there is no other source for this information. For MSBuild projects it’s taken from the device definition shipped with the BSP.

[support]

Hi,

No problem. We are planning to add a few minor improvements to Live Watch in the next couple of weeks, so we will address this issue as well.

We will post an update here once we get a preview build with the new behavior.

[Author]

Posts