GPDSC import error

Sysprogs forums Forums VisualGDB GPDSC import error

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #28037
    ExtSol
    Participant

    Hy All,

     

    I generated a project with STM32CubeMx and cant’t import it.

    Here is my error message:

    VisualGDB version: 5.4.112.3309
    ------------------ System.Xml.XmlException ------------------
    System.Xml.XmlException: Invalid character in the given encoding. Line 12, position 27.
    at System.Xml.XmlTextReaderImpl.Throw(Exception e)
    at System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
    at System.Xml.XmlTextReaderImpl.InvalidCharRecovery(Int32& bytesCount, Int32& charsCount)
    at System.Xml.XmlTextReaderImpl.GetChars(Int32 maxCharsCount)
    at System.Xml.XmlTextReaderImpl.ReadData()
    at System.Xml.XmlTextReaderImpl.ParseText(Int32& startPos, Int32& endPos, Int32& outOrChars)
    at System.Xml.XmlTextReaderImpl.ParseText()
    at System.Xml.XmlTextReaderImpl.ParseElementContent()
    at System.Xml.XmlTextReaderImpl.Read()
    at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
    at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
    at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
    at System.Xml.XmlDocument.Load(XmlReader reader)
    at System.Xml.XmlDocument.Load(String filename)
    at STM32CubeMXImporter.STM32CubeMXProjectImporter.ImportProject(ProjectImportParameters parameters, IProjectImportService service)
    at VisualGDB.WPF.Wizards.Embedded.EmbeddedProjectTypePage.ControllerImpl.CommitPage(m commitMode)
    at VisualGDB.WPF.Wizards.WPFWizardWindow.ControllerImpl.TryPrepareAndCommitPagesUntil(Int32 pageIndex)

     

    Any idea for resolve it?

     

    Best Regards:

    ExtSol

    #28038
    support
    Keymaster

    Hi,

    This is a known bug in the STM32CubeMX generator. It doesn’t properly escape the “&” symbol in the generated XML files (i.e. produces “value1&value2” instead of “value1&value2”). The easiest workaround would be to patch the file manually before importing it into VisualGDB.

    Please also consider reporting this to ST, as the issue is on their side.

    #28039
    ExtSol
    Participant

    Thank you very much!

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.