ARM Debugger fails

Sysprogs forums Forums VisualGDB ARM Debugger fails

This topic contains 4 replies, has 2 voices, and was last updated by  support 3 months, 1 week ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #21631

    DonMilne
    Participant

    I’m developing using the STM32F103xx processor. I have 2 VisualGDB custom support licenses last renewed in March this year.

    A new version of OpenOCD was pushed to me today. Since then I am unable to program the flash, or run the debugger. Attempting to run the debugger causes the following exception:

    1 action, String title, String caption, to1 exceptionHandler, Int32 noFormTimeout, String[] stages)
    at uz1.i3.u2-1.c()
    at l11.i1-1.c()
    — End of inner exception stack trace —
    at l11.p[_Type](f1-1 a)
    at uz1.i3.s_2[_ResultType](wg2-1 b, String d, Int32 a, String[] c)
    at uz1.LaunchGDBProjectWithoutDebugging.ExecuteForProject(uz1 instance, Project prj)
    `
    (I have changed some quote characters that seemed to cause format problems with this forum software) If I go to VisualGDB project properties Debug tab then it refuses to show me any details of the current debug method, instead it gives me a very similar error.

    The STM32 ST-Link flash programmer utility has no problem flashing my board, so I’m quite certain that it isn’t some coincidental hardware problem.

    • This topic was modified 3 months, 1 week ago by  DonMilne.
    • This topic was modified 3 months, 1 week ago by  DonMilne.
    #21634

    DonMilne
    Participant

    I still can’t get the formatting to work, and now I seem to be blocked from editing it too.

    #21636

    support
    Keymaster

    Hi,

    Sorry, it looks like an incompatibility between the different Preview builds. Please update VisualGDB to 5.4 Preview 4 and install the latest versions of the debug packages.

    #21637

    DonMilne
    Participant

    Yes, that seems to have fixed it. Thanks for the quick reponse.

    #21638

    support
    Keymaster

    Hi,

    No problem and sorry for the inconvenience. We will consider making a specific check for this type of issue that will automatically suggest updating the necessary components.

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

You must be logged in to reply to this topic.