register definitions load failed

[s.voulaz]

Hello,
it happens that register definition file for MIMXRT1061 (up to SDK 2.11) cannot be loaded, even after changing the extension to .svd. The file can be downloaded from here as part of the SDK and it is located under devices\MIMXRT1061. Error details follow.

Best regards,
Stefano Voulaz

VisualGDB version: 5.6.103.4531
—————— System.ArgumentNullException ——————
System.ArgumentNullException: Value cannot be null.
Parameter name: path1
at System.IO.Path.Combine(String path1, String path2)
at VisualGDB.Add_In.Tool_Windows.WPF.HardwareRegisters.HardwareRegistersToolControl.ControllerImpl.ImportRegisterDefinition(Boolean isAuxiliary)
trace=[System.IO.Path.Combine:26, VisualGDB.Add_In.Tool_Windows.WPF.HardwareRegisters.HardwareRegistersToolControl+ControllerImpl.ImportRegisterDefinition:209]

 

• This topic was modified 3 years ago by support.
• This topic was modified 3 years ago by support. Reason: split the issue into a separate topic

[support]

Hi,

It looks like an issue triggered by the project layout, and not specific to a particular SVD file.

We can gladly investigate it further if you could provide the steps we could follow on our side to reproduce the problem from scratch (including any steps necessary to create the project).

We would also kindly ask you to renew your support period here, as it has expired a while ago.

[s.voulaz]

Hi,

it’s a “Quick Debug with GDB” session, so no actual GDB project layout. It’s a cmake project we use across different hosts (Win/Mac) and development environments, so we can’t set up a VisualGDB/VisualStudio project. Any chance to use SVD files in such a context?

[support]

Hi,

No problem, please renew your license via this page, and we will gladly investigate and fix it.

[s.voulaz]

Just renewed…

 

[s.voulaz]

Btw, trying to load the file as XML (i.e., not changing the extension) still produces the error mentioned earlier in another post. FYI.

Regards,
Stefano

 

[support]

Thanks for renewing your license. The error was triggered by the settings updating logic in VisualGDB: it expected a non-empty project directory in order to save the converted register definition file there.

We have updated VisualGDB to save the converted register definition files to the directory of the original files when using Quick Debug presets. Please feel free to try this build: VisualGDB-5.6.104.4533.msi

[s.voulaz]

Thanks, register definition file is now correctly loaded. However, using the new version the plugin does not initialize correctly: when Visual Studio 2022 starts and the CMake project is opened,  in the Debug menu there’s only “Quick Debug Cmake Scripts” (no “Quick Debug With GDB” entry).

Note that the Clang IntelliSense dialog is not shown at startup (although “Show this dialog when Visual Studio starts” is checked).

“Quick Debug With GDB” is shown only after I somehow “force” the plugin to start (I suppose), i.e., by clicking on any menu entry under Tools->Visual GDB (and at this point the Clang IntelliSense dialog is shown before the dialog related to the selected command).

Best regards,
Stefano

[support]

Hi,

This is by design. The Quick Debug feature is supported starting from the Custom edition of VisualGDB (see the feature matrix), and will indeed not work with the Linux and Embedded editions.

[Author]

Posts