u37

Forum Replies Created

Log In Register Lost Password
Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
    Posts
  • December 8, 2023 at 03:51 in reply to: Kconfig menu in esp32 #35110
    u37
    Participant

    Thank you.

    August 26, 2016 at 17:46 in reply to: Not running debugging (Live Variables) through J-Link #8930
    u37
    Participant

    Thank you to fix everything!
    1. in the debug window displays the correct value readable variables:
    Read 4 bytes @ address 0x20000590 (Data = 0x0000047B)
    Read 4 bytes @ address 0x20000594 (Data = 0x00000006)
    Read 4 bytes @ address 0x20000598 (Data = 0x00000248)
    2. In the window are displayed correctly LiveVariables counters
    3. The speed of the debugger has become a “normal” (50 s/sec)
    Thanks, it works! ))

    I hope someday to LiveVariablese appears is the same management “registers” CPU/periphery.

    Thanks again.

    August 19, 2016 at 18:08 in reply to: Not running debugging (Live Variables) through J-Link #8891
    u37
    Participant

    Hello.

    Is there any news on the issue?

    August 3, 2016 at 18:50 in reply to: Not running debugging (Live Variables) through J-Link #8737
    u37
    Participant

    Hello.

    Is there any news on the issue?

    July 14, 2016 at 01:43 in reply to: Not running debugging (Live Variables) through J-Link #8553
    u37
    Participant

    Information from Segger:

     

    Visual GDB uses two instances of the J-Link DLL to connect to the target:
    One for debugging (Go / halt / readmem for watch window/ etc….) and a 2nd one for the live watch.

    The 2nd one does not know that the first one started the core again(e.g. after a breakpoint or after reset and halt), therefore it assumes that the content of the RAM did not change.

    Solution:
    Sysprog needs to alter Visual GDB in a way that it uses only one instance of the DLL.
    If Sysprog wants to do this and is facing issues, we would be happy to get in touch with them.

     

    June 27, 2016 at 12:01 in reply to: Not running debugging (Live Variables) through J-Link #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 23, 2016 at 18:56 in reply to: Not running debugging (Live Variables) through J-Link #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 23, 2016 at 18:49 in reply to: Not running debugging (Live Variables) through J-Link #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:44 in reply to: Not running debugging (Live Variables) through J-Link #8479
    u37
    Participant

    VisualGDB v5.2 b882: No changes. ((

    June 23, 2016 at 15:35 in reply to: Not running debugging (Live Variables) through J-Link #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 21, 2016 at 20:45 in reply to: Not running debugging (Live Variables) through J-Link #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 21, 2016 at 19:47 in reply to: Not running debugging (Live Variables) through J-Link #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 16:51 in reply to: Not running debugging (Live Variables) through J-Link #8469
    u37
    Participant

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

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

  • Author
    Posts
Log In Register Lost Password
Viewing 13 posts - 1 through 13 (of 13 total)