Not running debugging (Live Variables) through J-Link

Sysprogs forums › Forums › VisualGDB › Not running debugging (Live Variables) through J-Link

Log In Register Lost Password
Viewing 15 posts - 1 through 15 (of 24 total)
1 2
  • Author
    Posts
  • June 21, 2016 at 12:36 #8466
    u37
    Participant

    Segger provided an opportunity to rework the official ST-Link in your J-Link (https://www.segger.com/jlink-st-link.html).This debugger works well in Keil and other programs, but VisualGDB gives errors. In the derivation of “Live Variables” information is incorrect, the rate of output incorrect (too fast), the normal rate of 200-900 samples / sec.

    If you put a normal (original) debugger – ST-Link, J-Link – the information is displayed correctly.

    How can I fix the work VisualGDB?

    [URL=http://saveimg.ru/show-image.php?id=7631099d756c984b8e758ffbc7328179] [IMG]http://saveimg.ru/thumbnails/21-06-16/034cb122544fa33a0492cfbf5f1c8ed2.png[/IMG][/URL]

    June 21, 2016 at 16:04 #8468
    support
    Keymaster

    Hi,

    Please update your J-Link EDP to v3.2 via Tools->Embedded Tools Manager. This should fix the problem.

    June 21, 2016 at 16:51 #8469
    u37
    Participant

    Unfortunately, version 3.2 has been installed. But, I bet again:

    http://saveimg.ru/show-image.php?id=a1c095381a788e6ce36dd47a84bab722

    June 21, 2016 at 19:04 #8471
    support
    Keymaster

    Hi,

    Thanks for checking this. Could you please try this diagnostic build: http://sysprogs.com/files/tmp/VisualGDB-5.2.4.880.msi

    Then replace the %LOCALAPPDATA%\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.segger-dmsp\SeggerEDP.dll file with this one: http://sysprogs.com/files/tmp/SeggerEDP.dll

    Finally start your debug session and open the View->Other Windows->VisualGDB Diagnostics Console window. It should show what exactly the Segger memory reading API returns. Please let us know what is shown there so that we could fix this.

    June 21, 2016 at 19:47 #8472
    u37
    Participant

    No changes. ((

    Additional Information.

    If you stop the program, take the variable Live Variables (eg Tst0) and write 0 to it (any value), then ALL other variables will be the =correct= value. These values correspond to what is in the memory (window = memory, region 0x20…58C / 590 / …)

    After continuing execution Live Variables do not change.

     

     

    JLINKARM_ReadMemEx(0x20000590, 4) returned 4
    JLINKARM_ReadMemEx(0x20000594, 4) returned 4
    JLINKARM_ReadMemEx(0x20000598, 4) returned 4
    JLINKARM_ReadMemEx(0x2000058c, 4) returned 4
    JLINKARM_ReadMemEx(0x20000590, 4) returned 4
    JLINKARM_ReadMemEx(0x20000594, 4) returned 4
    JLINKARM_ReadMemEx(0x20000598, 4) returned 4
    JLINKARM_ReadMemEx(0x2000058c, 4) returned 4
    JLINKARM_ReadMemEx(0x20000590, 4) returned 4
    JLINKARM_ReadMemEx(0x20000594, 4) returned 4
    JLINKARM_ReadMemEx(0x20000598, 4) returned 4
    JLINKARM_ReadMemEx(0x2000058c, 4) returned 4
    JLINKARM_ReadMemEx(0x20000590, 4) returned 4
    JLINKARM_ReadMemEx(0x20000594, 4) returned 4
    JLINKARM_ReadMemEx(0x20000598, 4) returned 4
    JLINKARM_ReadMemEx(0x2000058c, 4) returned 4
    JLINKARM_ReadMemEx(0x20000590, 4) returned 4
    JLINKARM_ReadMemEx(0x20000594, 4) returned 4
    JLINKARM_ReadMemEx(0x20000598, 4) returned 4
    JLINKARM_ReadMemEx(0x2000058c, 4) returned 4
    JLINKARM_ReadMemEx(0x20000590, 4) returned 4
    JLINKARM_ReadMemEx(0x20000594, 4) returned 4
    JLINKARM_ReadMemEx(0x20000598, 4) returned 4
    JLINKARM_ReadMemEx(0x2000058c, 4) returned 4
    JLINKARM_ReadMemEx(0x20000590, 4) returned 4
    JLINKARM_ReadMemEx(0x20000594, 4) returned 4
    JLINKARM_ReadMemEx(0x20000598, 4) returned 4
    JLINKARM_ReadMemEx(0x2000058c, 4) returned 4
    JLINKARM_ReadMemEx(0x20000590, 4) returned 4
    JLINKARM_ReadMemEx(0x20000594, 4) returned 4
    JLINKARM_ReadMemEx(0x20000598, 4) returned 4
    JLINKARM_ReadMemEx(0x2000058c, 4) returned 4
    JLINKARM_ReadMemEx(0x20000590, 4) returned 4
    JLINKARM_ReadMemEx(0x20000594, 4) returned 4
    JLINKARM_ReadMemEx(0x20000598, 4) returned 4
    JLINKARM_ReadMemEx(0x2000058c, 4) returned 4
    JLINKARM_ReadMemEx(0x20000590, 4) returned 4
    JLINKARM_ReadMemEx(0x20000594, 4) returned 4
    JLINKARM_ReadMemEx(0x20000598, 4) returned 4
    JLINKARM_ReadMemEx(0x2000058c, 4) returned 4
    JLINKARM_ReadMemEx(0x20000590, 4) returned 4
    JLINKARM_ReadMemEx(0x20000594, 4) returned 4
    JLINKARM_ReadMemEx(0x20000598, 4) returned 4
    JLINKARM_ReadMemEx(0x2000058c, 4) returned 4
    JLINKARM_ReadMemEx(0x20000590, 4) returned 4
    JLINKARM_ReadMemEx(0x20000594, 4) returned 4
    JLINKARM_ReadMemEx(0x20000598, 4) returned 4
    JLINKARM_ReadMemEx(0x2000058c, 4) returned 4
    JLINKARM_ReadMemEx(0x20000590, 4) returned 4
    JLINKARM_ReadMemEx(0x20000594, 4) returned 4
    JLINKARM_ReadMemEx(0x20000598, 4) returned 4
    JLINKARM_ReadMemEx(0x2000058c, 4) returned 4
    JLINKARM_ReadMemEx(0x20000590, 4) returned 4
    JLINKARM_ReadMemEx(0x20000594, 4) returned 4
    JLINKARM_ReadMemEx(0x20000598, 4) returned 4
    JLINKARM_ReadMemEx(0x2000058c, 4) returned 4
    JLINKARM_ReadMemEx(0x20000590, 4) returned 4
    JLINKARM_ReadMemEx(0x20000594, 4) returned 4
    JLINKARM_ReadMemEx(0x20000598, 4) returned 4
    JLINKARM_ReadMemEx(0x2000058c, 4) returned 4
    JLINKARM_ReadMemEx(0x20000590, 4) returned 4
    JLINKARM_ReadMemEx(0x20000594, 4) returned 4
    JLINKARM_ReadMemEx(0x20000598, 4) returned 4
    JLINKARM_ReadMemEx(0x2000058c, 4) returned 4
    JLINKARM_ReadMemEx(0x20000590, 4) returned 4
    JLINKARM_ReadMemEx(0x20000594, 4) returned 4
    JLINKARM_ReadMemEx(0x20000598, 4) returned 4
    JLINKARM_ReadMemEx(0x2000058c, 4) returned 4
    JLINKARM_ReadMemEx(0x20000590, 4) returned 4
    JLINKARM_ReadMemEx(0x20000594, 4) returned 4
    JLINKARM_ReadMemEx(0x20000598, 4) returned 4
    JLINKARM_ReadMemEx(0x2000058c, 4) returned 4
    JLINKARM_ReadMemEx(0x20000590, 4) returned 4
    JLINKARM_ReadMemEx(0x20000594, 4) returned 4
    JLINKARM_ReadMemEx(0x20000598, 4) returned 4
    JLINKARM_ReadMemEx(0x2000058c, 4) returned 4
    JLINKARM_ReadMemEx(0x20000590, 4) returned 4
    JLINKARM_ReadMemEx(0x20000594, 4) returned 4
    JLINKARM_ReadMemEx(0x20000598, 4) returned 4
    JLINKARM_ReadMemEx(0x2000058c, 4) returned 4

     

    June 21, 2016 at 20:19 #8473
    support
    Keymaster

    OK, please try this version http://sysprogs.com/files/tmp/SeggerEDP.dll

    It will also show the data received from JLINKARM_ReadMemEx().

    June 21, 2016 at 20:45 #8474
    u37
    Participant

    1. All missing variables in the “Live variables”

    2. These variables can be added to the “Visual Watch”

    3. These variables can not be added to the “Live variables”

    http://saveimg.ru/show-image.php?id=fa40bd0c86146aa8a0fa98906ee228b4

    Translation error text: “The index is outside the bounds of the array.”

     

    June 23, 2016 at 04:16 #8477
    support
    Keymaster

    Sorry, does the latest build cause this when adding the same variable as before, or are you trying something completely different?

    June 23, 2016 at 15:35 #8478
    u37
    Participant

    Step 1: Replace SeggerEDP.dll

    Step 2: When the project is opened there is a lack of variables in the “Live Variables”

    Step 3: my variables (are the same that were before) can not be added to the section “Live Variables”. In principle, it is impossible – the error window appears.

    June 23, 2016 at 18:44 #8479
    u37
    Participant

    VisualGDB v5.2 b882: No changes. ((

    June 23, 2016 at 18:49 #8480
    u37
    Participant

    Switch debuger to “STLink” mode:

    0x20000598: 00003cb1
    0x20000590: 00007965
    0x2000058c: 00000001
    0x20000594: 0000009c
    0x20000598: 00003cca
    0x20000590: 00007997
    0x2000058c: 00000001
    0x20000594: 0000009c
    0x20000598: 00003ce4
    0x20000590: 000079c9
    0x2000058c: 00000001
    0x20000594: 0000009d
    0x20000598: 00003cfd
    0x20000590: 000079fd
    0x2000058c: 00000001
    0x20000594: 0000009d
    0x20000598: 00003d17
    0x20000590: 00007a33
    0x2000058c: 00000001
    0x20000594: 0000009d
    0x20000598: 00003d30
    0x20000590: 00007a67
    0x2000058c: 00000001
    0x20000594: 0000009d
    0x20000598: 00003d4a
    0x20000590: 00007a9d
    0x2000058c: 00000001
    0x20000594: 0000009e
    0x20000598: 00003d63
    0x20000590: 00007acf
    0x2000058c: 00000001
    0x20000594: 0000009e

    June 23, 2016 at 18:56 #8481
    u37
    Participant

    Without leaving the Visual Studio project to alter debugger “JLink” mode and run debugging:
    – The window “Live variables” disappear my variables, add impossible (an error occurs).

    (Problem described previously.)

    June 24, 2016 at 19:23 #8485
    support
    Keymaster

    Sorry, looks like a bug in the debug build. Please try this one: http://sysprogs.com/files/tmp/SeggerEDP.dll

    June 27, 2016 at 12:01 #8487
    u37
    Participant

    Add the entire program RAM recording counter in the left’s capacity 0x55aa cells.
    In “Live Variables” read the same garbage (0x55AA).
    http://saveimg.ru/show-image.php?id=9059867313736ca9c679c49aeb472190

    June 27, 2016 at 15:57 #8488
    support
    Keymaster

    Hi,
    OK, this means that the incorrect values are coming from the J-Link software. Please try installing the latest version of it, installing the latest firmware to your J-Link and reducing the JTAG frequency.
    If this does not help, please try contacting Segger support with the log showing what JLINKARM_ReadMemEx() returns, perhaps they have a better idea why it is returning incorrect data.

  • Author
    Posts
Log In Register Lost Password
Viewing 15 posts - 1 through 15 (of 24 total)
1 2
  • You must be logged in to reply to this topic.