IMXRT105x hardware register defs

Sysprogs forums Forums VisualGDB IMXRT105x hardware register defs

This topic contains 6 replies, has 2 voices, and was last updated by  mmilo 1 month ago.

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #25627

    mmilo
    Participant

    NXP already provides a .xml with the hardware register definitions with their BSP. The format is not the same as required by VisualGDB (http://visualgdb.com/documentation/hwregs).

    Is there any chance that I could get some help converting the file? Maybe you already have some in-house tools that could ease the process?
    I’m guessing it’s the same for all NXP products? It would really be awesome if we could use those hardware register definitions, just like you already added support for their BSP’s.

    Snippet of the NXP .xml file:

    • This topic was modified 1 month, 1 week ago by  support. Reason: formatting
    #25629

    support
    Keymaster

    Hi,

    This looks like a regular SVD file that should be already supported by VisualGDB. Simply select it when clicking on the “Locate SVD file” link in the Hardware Registers window and VisualGDB will automatically convert it to its format.

    Alternatively, you can use the converter from our BSPTools repository that is equivalent to the converter used by VisualGDB.

    #25642

    mmilo
    Participant

    Unfortunately visualGDB fails when I try to import the .xml with the hardware definitions from NXP.

    #25646

    support
    Keymaster

    Thanks for letting us know, however unfortunately it’s hard to suggest anything specific without knowing more details. If you could describe exactly how you were importing them and what you observed (and ideally, share the entire file you tried importing), we should be able to suggest a workaround or release a hotfix for it.

    #25647

    mmilo
    Participant

    I’ve attached the hardware definition file generated by the newest version of the NXP SDK for the IMXRT1052 (zipped because it’s 8MB).

    I get the following error when I open the Hardware Registers windows and try to “Import register from an SVD file or a VisualGDB resiger definition file”

    VisualGDB version: 5.4.112.3242
    —————— System.InvalidOperationException ——————
    System.InvalidOperationException: There is an error in XML document (2, 2). —> System.InvalidOperationException: <device xmlns=”> was not expected.
    at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderMCUDefinition.Read8_MCUDefinition()
    — End of inner exception stack trace —
    at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
    at System.Xml.Serialization.XmlSerializer.Deserialize(Stream stream)
    at BSPEngine.XmlTools.LoadObject[_Ty](String xmlFile, Type[] extraTypes)
    at q3.b4(Boolean a)
    —————— Inner exception ——————
    —————— System.InvalidOperationException ——————
    System.InvalidOperationException: <device xmlns=”> was not expected.
    at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderMCUDefinition.Read8_MCUDefinition()

    When I try to add the file in the VisualGDB project properties -> Embedded Project -> Peripheral register definitions, then the Hardware registers windows says they are still missing when trying to open it while debugging.

    I assume that the registers definitions .xml generated by NXP is just too different from the VisualGDB standard for it to work. Hopefully you guys can make a fix, as I guess it would make it work for all NXP devices, not just the IMXRT1052.

    Attachments:
    You must be logged in to view attached files.
    #25650

    support
    Keymaster

    Thanks for the update. Looks like VisualGDB tries to load it as a VisualGDB-specific XML file instead of using the SVD loading logic.

    Please try changing the file extension to .svd and importing it again.

    #25651

    mmilo
    Participant

    Works perfectly, thanks a lot!

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.