erasmus

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 24 total)
  • Author
    Posts
  • in reply to: Debugging w. VS2015 and Segger J-Link #12147
    erasmus
    Participant

    Thanks. I see that in the brand new VisualGDB-5.3-preview6.msi version now. After reimaging the PC that was having problems – the preview 6 version is working.

    in reply to: Debugging w. VS2015 and Segger J-Link #12069
    erasmus
    Participant

    Yep – I’ve looked at the three latest versions of VGDB, debugger settings and advanced debugger settings. And do NOT see the disable stack checking control. If you could post a screen shot of the control you are referring to – perhaps I could locate it.

    in reply to: Debugging w. VS2015 and Segger J-Link #12050
    erasmus
    Participant

    Can you post a picture of the VGDB UX component (validate stack pointer) that you’ve kept referring to ? I don’t seem to find it in any version. Is that a difficult thing for you to do?

    in reply to: Debugging w. VS2015 and Segger J-Link #12047
    erasmus
    Participant

    I’ve included a picture of VisualGDB Project Properties -> Advanced Debug (posting again). Can you point out the “->Validate stack pointer” you are referring to?

    Perhaps you are running a different version of VGDB? Have not seen what you are talking about in any of the versions I’ve installed here. Also, verified the segger dll is loading in process explorer (win internal tools).

    Attachments:
    You must be logged in to view attached files.
    in reply to: Debugging w. VS2015 and Segger J-Link #12044
    erasmus
    Participant

    There are No devices that show up (Even after downloading and installing All the Nordic nRFx devices, legacy and SDK 13).
    This seems to be a bug unique to this new version.

    Also to reiterate the problem. “VGDB debug message says The memory location used for stack is not writable. Please check the selected device type and linker scripts. You can disable the automatic stack checking via VisualGDB Project Properties”.

    So far NONE of your responses have indicated how to “disable automatic stack checking…”. VGDB in any version we’ve seen does not have this setting. Are you seeing it there ? If so can you send a picture?

    Attachments:
    You must be logged in to view attached files.
    in reply to: Debugging w. VS2015 and Segger J-Link #12042
    erasmus
    Participant

    Installed version VGDB (5.3.5.1716) -there is something wrong with the devices (nRFx) after the tool downloads the legacy SDK 12, and new SDK 13 nRFx, they Do NOT show up when the project is created. So whatever extra debug output this version provides – it never gets to a point that it matters.

    So basically we are Unable to use this machine for development now. Uninstalling VGDB, segger tools, arm toolchain does NOT work. There is something from VGDB ‘left over’ that prevents even the basic ‘blinky’ example from working (which we’ve never had issues with). This seems to be common to all VGDB versions.

    in reply to: Debugging w. VS2015 and Segger J-Link #12040
    erasmus
    Participant

    Yes same VGDB 5.3 preview 5. The segger dll exists in all cases whether it is 4.1 or 3.6 or 4.0 . I should add this works on other computers – its just once this bug starts happening it seems to persist on a given computer. Uninstalling everything VGDB, toolchain, devices, segger and reinstalling does not seem to fix. Short of reimaging our computers with VGDB – we would like a work around.

    Is there a way to get telephone support for VGDB?

    in reply to: Debugging w. VS2015 and Segger J-Link #12022
    erasmus
    Participant

    Update to the above. Recall I uninstalled VGDB, deleted all VGDB local app data and reinstalled. Working fine after that -UNTIL we updated to SEGGER 4.1 tools! Here is the error message right after upgrading to 4.1 (worked fine previously).

    As soon as I updated to Segger 4.1 (from 3.6)

    • This reply was modified 7 years, 3 months ago by erasmus.
    Attachments:
    You must be logged in to view attached files.
    in reply to: Debugging w. VS2015 and Segger J-Link #12021
    erasmus
    Participant

    I deleted Everything under %LOCALAPPDATA%\VisualGDB\, reinstalled VGDB and we are back to working now.

    It would be Nice have some sort of fidelity check tool for data VGDB stores in ‘%LOCALAPPDATA%\VisualGDB’.

    Thanks!

    –Bart

    in reply to: Debugging w. VS2015 and Segger J-Link #12011
    erasmus
    Participant

    And complete GDB log for the blinky example

    (gdb begin)
    VisualGDB is licensed to Jimmy Leo
    C:\tools\arm-eabi\bin\arm-eabi-gdb.exe –interpreter mi C:\vsProj\fixGDB2\VisualGDB\Debug\fixGDB2
    -gdb-version
    =thread-group-added,id=”i1″
    ~”GNU gdb (GDB) 7.12\n”
    ~”Copyright (C) 2016 Free Software Foundation, Inc.\n”
    ~”License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html&gt;\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law. Type \”show copying\”\nand \”show warranty\” for details.\n”

    ~”This GDB was configured as \”–host=i686-pc-mingw32 –target=arm-eabi\”.\nType \”show configuration\” for configuration details.”

    ~”\nFor bug reporting instructions, please see:\n”
    ~”<http://www.gnu.org/software/gdb/bugs/&gt;.\n”
    ~”Find the GDB manual and other documentation resources online at:\n<http://www.gnu.org/software/gdb/documentation/&gt;.\n”

    ~”For help, type \”help\”.\n”
    ~”Type \”apropos word\” to search for commands related to \”word\”…\n”
    ~”Reading symbols from C:\\vsProj\\fixGDB2\\VisualGDB\\Debug\\fixGDB2…”
    ~”done.\n”
    ~”GNU gdb (GDB) 7.12\n”
    ~”Copyright (C) 2016 Free Software Foundation, Inc.\n”
    ~”License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html&gt;\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law. Type \”show copying\”\nand \”show warranty\” for details.\n”

    ~”This GDB was configured as \”–host=i686-pc-mingw32 –target=arm-eabi\”.\nType \”show configuration\” for configuration details.”

    ~”\nFor bug reporting instructions, please see:\n”
    ~”<http://www.gnu.org/software/gdb/bugs/&gt;.\n”
    ~”Find the GDB manual and other documentation resources online at:\n<http://www.gnu.org/software/gdb/documentation/&gt;.\n”

    ~”For help, type \”help\”.\n”
    ~”Type \”apropos word\” to search for commands related to \”word\”.\n”
    ^done
    -list-features
    ^done,features=[“frozen-varobjs”,”pending-breakpoints”,”thread-info”,”data-read-memory-bytes”,”breakpoint-notifications”,”ada-task-info”,”language-option”,”info-gdb-mi-command”,”undefined-command-error-code”,”exec-run-start-option”]
    -gdb-set disassembly-flavor intel
    ^error,msg=”No symbol \”disassembly\” in current context.”
    -gdb-set print demangle off
    ^done
    -break-insert -f main
    ^done,bkpt={number=”1″,type=”breakpoint”,disp=”keep”,enabled=”y”,addr=”0x0001b2aa”,func=”main()”,file=”LEDBlink.cpp”,fullname=”c:\\vsProj\\fixGDB2\\LEDBlink.cpp”,line=”20″,thread-groups=[“i1″],times=”0″,original-location=”main”}
    -data-evaluate-expression “sizeof(void *)”
    ^done,value=”4″
    -data-evaluate-expression “sizeof(int)”
    ^done,value=”4″
    -data-evaluate-expression “sizeof(short)”
    ^done,value=”2″
    -data-evaluate-expression “sizeof(long)”
    ^done,value=”4″
    -data-evaluate-expression “sizeof(long long)”
    ^done,value=”8″
    -data-evaluate-expression “sizeof(char)”
    ^done,value=”1″
    -data-evaluate-expression “sizeof(wchar_t)”
    ^error,msg=”No symbol \”wchar_t\” in current context.”
    -data-evaluate-expression “sizeof(float)”
    ^done,value=”4″
    -data-evaluate-expression “sizeof(double)”
    ^done,value=”8″
    -data-evaluate-expression “sizeof(long double)”
    ^done,value=”8″
    info target
    &”info target\n”
    ~”Symbols from \”C:\\vsProj\\fixGDB2\\VisualGDB\\Debug\\fixGDB2\”.\n”
    ~”Local exec file:\n”
    ~”\t`C:\\vsProj\\fixGDB2\\VisualGDB\\Debug\\fixGDB2′, file type elf32-littlearm.\n”
    ~”\tEntry point: 0x1b5ec\n”
    ~”\t0x00000000 – 0x0001b000 is .softdevice\n”
    ~”\t0x20000000 – 0x20001fe8 is .softdevice_sram\n”
    ~”\t0x0001b000 – 0x0001b0c0 is .isr_vector\n”
    ~”\t0x0001b0c0 – 0x0001c408 is .text\n”
    ~”\t0x0001c408 – 0x0001c40c is .init_array\n”
    ~”\t0x0001c40c – 0x0001c410 is .fini_array\n”
    ~”\t0x20001fe8 – 0x20001fec is .data\n”
    ~”\t0x20001fec – 0x20002074 is .bss\n”
    ^done
    -data-evaluate-expression “&_estack”
    ^done,value=”0x20004000 <error: Cannot access memory at address 0x20004000>”
    -var-create – * “*((void **)0x20003ffc)”
    ^done,name=”var1″,numchild=”0″,value=””,type=”void *”,has_more=”0″
    -var-evaluate-expression “var1″
    ^done,value=””
    -exec-continue

    in reply to: Debugging w. VS2015 and Segger J-Link #12009
    erasmus
    Participant

    Here it is…

    Attachments:
    You must be logged in to view attached files.
    in reply to: Debugging w. VS2015 and Segger J-Link #12006
    erasmus
    Participant

    and one more of advanced GDB settings. These are defaults like we always use…

    Attachments:
    You must be logged in to view attached files.
    in reply to: Debugging w. VS2015 and Segger J-Link #12001
    erasmus
    Participant

    Here are some screen shots from recently created blinky(BSP) example. We did this example several times when evaluating VGDB. Has always worked perfectly – until now. This is exactly the same error we see in our real projects now.

    Attachments:
    You must be logged in to view attached files.
    in reply to: Debugging w. VS2015 and Segger J-Link #11999
    erasmus
    Participant

    Creating an example from scratch now (e.g. – blinky) Also fails now in the same way as above. This is After uninstalling and reinstalling toolchain (latest from VGDB), VGDB, segger jlink tools. Also VS2015 and Visual GDB 5.3.5.1707.

    in reply to: Debugging w. VS2015 and Segger J-Link #11997
    erasmus
    Participant

    Looks like All our VGDB Visual Studio projects are exhibiting similar failures now. We have tried completely removing the toolchains, visual GDB, and segger tools. Just to re-iterate these projects were working fine before the latest toolchain update. Now we consistently break all projects now when trying to load into the nRF51822. Here is the VGDB log for the second project that is now broken…..

    C:\tools\arm-eabi\bin\arm-eabi-gdb.exe –interpreter mi C:\srcroot\NordicMain\Dongle_BTLE\VisualGDB\Debug\Dongle_BTLE
    -gdb-version
    =thread-group-added,id=”i1″
    ~”GNU gdb (GDB) 7.12\n”
    ~”Copyright (C) 2016 Free Software Foundation, Inc.\n”
    ~”License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html&gt;\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law. Type \”show copying\”\nand \”show warranty\” for details.\n”

    ~”This GDB was configured as \”–host=i686-pc-mingw32 –target=arm-eabi\”.\nType \”show configuration\” for configuration details.”

    ~”\nFor bug reporting instructions, please see:\n”
    ~”<http://www.gnu.org/software/gdb/bugs/&gt;.\n”
    ~”Find the GDB manual and other documentation resources online at:\n<http://www.gnu.org/software/gdb/documentation/&gt;.\n”

    ~”For help, type \”help\”.\n”
    ~”Type \”apropos word\” to search for commands related to \”word\”…\n”
    ~”Reading symbols from C:\\srcroot\\NordicMain\\Dongle_BTLE\\VisualGDB\\Debug\\Dongle_BTLE…”
    ~”done.\n”
    ~”GNU gdb (GDB) 7.12\n”
    ~”Copyright (C) 2016 Free Software Foundation, Inc.\n”
    ~”License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html&gt;\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law. Type \”show copying\”\nand \”show warranty\” for details.\n”

    ~”This GDB was configured as \”–host=i686-pc-mingw32 –target=arm-eabi\”.\nType \”show configuration\” for configuration details.”

    ~”\nFor bug reporting instructions, please see:\n”
    ~”<http://www.gnu.org/software/gdb/bugs/&gt;.\n”
    ~”Find the GDB manual and other documentation resources online at:\n<http://www.gnu.org/software/gdb/documentation/&gt;.\n”

    ~”For help, type \”help\”.\n”
    ~”Type \”apropos word\” to search for commands related to \”word\”.\n”
    ^done
    -list-features
    ^done,features=[“frozen-varobjs”,”pending-breakpoints”,”thread-info”,”data-read-memory-bytes”,”breakpoint-notifications”,”ada-task-info”,”language-option”,”info-gdb-mi-command”,”undefined-command-error-code”,”exec-run-start-option”]
    -gdb-set disassembly-flavor intel
    ^error,msg=”No symbol \”disassembly\” in current context.”
    -gdb-set print demangle off
    ^done
    -break-insert -f main
    ^done,bkpt={number=”1″,type=”breakpoint”,disp=”keep”,enabled=”y”,addr=”0x0002745c”,func=”main”,file=”C:/srcroot/NordicMain/nRF51_SDK_9.0.0_2e23562/examples/ble_central/ble_connectivity/main.c”,fullname=”C:\\srcroot\\NordicMain\\nRF51_SDK_9.0.0_2e23562\\examples\\ble_central\\ble_connectivity\\main.c”,line=”131″,thread-groups=[“i1″],times=”0″,original-location=”main”}
    -data-evaluate-expression “sizeof(void *)”
    ^done,value=”4″
    -data-evaluate-expression “sizeof(int)”
    ^done,value=”4″
    -data-evaluate-expression “sizeof(short)”
    ^done,value=”2″
    -data-evaluate-expression “sizeof(long)”
    ^done,value=”4″
    -data-evaluate-expression “sizeof(long long)”
    ^done,value=”8″
    -data-evaluate-expression “sizeof(char)”
    ^done,value=”1″
    -data-evaluate-expression “sizeof(wchar_t)”
    ^done,value=”4″
    -data-evaluate-expression “sizeof(float)”
    ^done,value=”4″
    -data-evaluate-expression “sizeof(double)”
    ^done,value=”8″
    -data-evaluate-expression “sizeof(long double)”
    ^done,value=”8″
    info target
    &”info target\n”
    ~”Symbols from \”C:\\srcroot\\NordicMain\\Dongle_BTLE\\VisualGDB\\Debug\\Dongle_BTLE\”.\n”
    ~”Local exec file:\n”
    ~”\t`C:\\srcroot\\NordicMain\\Dongle_BTLE\\VisualGDB\\Debug\\Dongle_BTLE’, file type elf32-littlearm.\n”
    ~”\tEntry point: 0x272dc\n”
    ~”\t0x0001c000 – 0x00028140 is .text\n”
    ~”\t0x00028140 – 0x00028148 is .ARM.exidx\n”
    ~”\t0x20002800 – 0x20002880 is .data\n”
    ~”\t0x20002880 – 0x200037ec is .bss\n”
    ^done
    -data-evaluate-expression “&_estack”
    ^error,msg=”No symbol \”_estack\” in current context.”
    -data-evaluate-expression “&__StackLimit”
    ^done,value=”0x20003800 <error: Cannot access memory at address 0x20003800>”
    -var-create – * “*((void **)0x200037fc)”
    ^done,name=”var1″,numchild=”0″,value=””,type=”void *”,has_more=”0″
    -var-evaluate-expression “var1″
    ^done,value=””
    -exec-continue
    ^error,msg=”The program is not being run.”

Viewing 15 posts - 1 through 15 (of 24 total)