surahman

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 16 total)
  • Author
    Posts
  • in reply to: STM32 connection issues #24719
    surahman
    Participant

    If I set Debug using under debug methods to SEGGER J-Link with USB-Auto I get the following:

    SEGGER\JLink_V644g\JLinkGDBServerCL.exe -select USB -device STM32F412ZG -speed auto -if SWD -port 2028
    SEGGER J-Link GDB Server V6.44g Command Line Version
    
    JLinkARM.dll V6.44g (DLL compiled Apr 18 2019 17:12:10)
    
    Command line: -select USB -device STM32F412ZG -speed auto -if SWD -port 2028
    -----GDB Server start settings-----
    GDBInit file:                  none
    GDB Server Listening port:     2028
    SWO raw output listening port: 2332
    Terminal I/O port:             2333
    Accept remote connection:      localhost only
    Generate logfile:              off
    Verify download:               off
    Init regs on start:            off
    Silent mode:                   off
    Single run mode:               off
    Target connection timeout:     0 ms
    ------J-Link related settings------
    J-Link Host interface:         USB
    J-Link script:                 none
    J-Link settings file:          none
    ------Target related settings------
    Target device:                 STM32F412ZG
    Target interface:              SWD
    Target interface speed:        auto
    Target endian:                 little
    
    Connecting to J-Link...
    Connecting to J-Link failed. Connected correctly?
    GDBServer will be closed...
    Shutting down...
    Could not connect to J-Link.
    Please check power, connection and settings.

    If I manually supply the USB serial number, which I’ve double checked is correct, I get the following:

    SEGGER\JLink_V644g\JLinkGDBServerCL.exe -select USB=066EFF333036434B43015523 -device STM32F412ZG -speed auto -if SWD -port 2021
    SEGGER J-Link GDB Server V6.44g Command Line Version
    
    JLinkARM.dll V6.44g (DLL compiled Apr 18 2019 17:12:10)
    
    Command line: -select USB=066EFF333036434B43015523 -device STM32F412ZG -speed auto -if SWD -port 2021
    -----GDB Server start settings-----
    GDBInit file:                  none
    GDB Server Listening port:     2021
    SWO raw output listening port: 2332
    Terminal I/O port:             2333
    Accept remote connection:      localhost only
    Generate logfile:              off
    Verify download:               off
    Init regs on start:            off
    Silent mode:                   off
    Single run mode:               off
    Target connection timeout:     0 ms
    ------J-Link related settings------
    J-Link Host interface:         USB
    J-Link script:                 none
    J-Link settings file:          none
    ------Target related settings------
    Target device:                 STM32F412ZG
    Target interface:              SWD
    Target interface speed:        auto
    Target endian:                 little
    
    Could not select J-Link with specified S/N (66).
    GDBServer will be closed...
    Shutting down...
    Could not connect to J-Link.
    Please check power, connection and settings.

    If I use the USB Devices I only see ST-Link v2.1, I have installed SEGGER J-Link as well as installed the

    Digitally signed USB driver for ST-Link/V2, ST-Link/V2-1 and STLINK-V3 on Windows7, Windows8 and Windows10, 32 and 64 bits.
    [stsw-link009]

    The error persists. It works fine out of the box on my laptop.

    • This reply was modified 5 years, 7 months ago by surahman.
    in reply to: STM32 connection issues #24716
    surahman
    Participant

    I can connect to the device using the STM32 ST-LINK Utility just fine, so I think that OpenOCD should be able to connect to the device. I can also see ST-Link Debug in the Device Manager under Universal Serial Bus devices.

    • This reply was modified 5 years, 7 months ago by surahman.
    in reply to: STM32 connection issues #24713
    surahman
    Participant

    The issue has resurfaced now that I’ve switched to VS2019 with VGDB5.4-R5.

    AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.openocd\bin\openocd.exe -c "gdb_port 30455" -c "telnet_port 30456" -f interface/stlink-v2-1.cfg -f target/stm32f4x.cfg -c init -c "reset init" -c "echo VisualGDB_OpenOCD_Ready"
    Open On-Chip Debugger 0.10.0 (2019-02-10) [https://github.com/sysprogs/openocd]
    Licensed under GNU GPL v2
    For bug reports, read
    http://openocd.org/doc/doxygen/bugs.html
    WARNING: interface/stlink-v2-1.cfg is deprecated, please switch to interface/stlink.cfg
    Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'.
    Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
    adapter speed: 2000 kHz
    adapter_nsrst_delay: 100
    none separate
    Info : clock speed 2000 kHz
    Error: open failed

    If I use the old executable provided above I get the following error:

    AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.openocd\bin\openocd.exe -c "gdb_port 30440" -c "telnet_port 30441" -f interface/stlink-v2-1.cfg -f target/stm32f4x.cfg -c init -c "reset init" -c "echo VisualGDB_OpenOCD_Ready"
    Open On-Chip Debugger 0.10.0 (2019-02-25) [https://github.com/sysprogs/openocd]
    
    Licensed under GNU GPL v2
    For bug reports, read
    	http://openocd.org/doc/doxygen/bugs.html
    WARNING: interface/stlink-v2-1.cfg is deprecated, please switch to interface/stlink.cfg
    Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'.
    Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
    adapter speed: 2000 kHz
    adapter_nsrst_delay: 100
    none separate
    Info : clock speed 2000 kHz
    Info : libusb reported 6 devices
    Info : USB descriptor mismatch for device #0 (046d/c318)
    Info : USB descriptor mismatch for device #1 (1b21/1242)
    Info : USB descriptor mismatch for device #2 (8086/a12f)
    Info : USB descriptor mismatch for device #3 (046d/c52b)
    Info : USB descriptor mismatch for device #4 (05ac/12a8)
    Info : USB descriptor mismatch for device #5 (13fd/1340)
    Error: open failed: jtag_libusb_open() returned error -4
    • This reply was modified 5 years, 7 months ago by surahman.
    in reply to: STM32 connection issues #23989
    surahman
    Participant

    No worries, here is the updated run:

    AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.openocd\bin\openocd.exe -c "gdb_port 43497" -c "telnet_port 43498" -f interface/stlink-v2-1.cfg -c "transport select hla_swd" -f target/stm32f4x.cfg -c init -c "reset init" -c "echo VisualGDB_OpenOCD_Ready"
    Open On-Chip Debugger 0.10.0 (2019-02-25) [https://github.com/sysprogs/openocd]
    Licensed under GNU GPL v2
    For bug reports, read
    http://openocd.org/doc/doxygen/bugs.html
    WARNING: interface/stlink-v2-1.cfg is deprecated, please switch to interface/stlink.cfg
    hla_swd
    Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
    adapter speed: 2000 kHz
    adapter_nsrst_delay: 100
    none separate
    Info : clock speed 2000 kHz
    Info : libusb reported 7 devices
    Info : USB descriptor mismatch for device #1 (1b21/1242)
    Info : USB descriptor mismatch for device #2 (8086/a12f)
    Info : USB descriptor mismatch for device #3 (0a12/1004)
    Info : USB descriptor mismatch for device #4 (046d/c52b)
    Info : USB descriptor mismatch for device #5 (05ac/12a8)
    Info : USB descriptor mismatch for device #6 (13fd/1340)
    Info : STLINK V2J33M25 (API v2) VID:PID 0483:374B
    Info : Target voltage: 3.259843
    Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints
    Info : Listening on port 43497 for gdb connections
    Info : Unable to match requested speed 2000 kHz, using 1800 kHz
    Info : Unable to match requested speed 2000 kHz, using 1800 kHz
    adapter speed: 1800 kHz
    target halted due to debug-request, current mode: Thread 
    xPSR: 0x01000000 pc: 0x0805cb6c msp: 0x20002d68
    Info : Unable to match requested speed 8000 kHz, using 4000 kHz
    Info : Unable to match requested speed 8000 kHz, using 4000 kHz
    adapter speed: 4000 kHz
    VisualGDB_OpenOCD_Ready
    Info : Listening on port 6666 for tcl connections
    Info : Listening on port 43498 for telnet connections
    Info : accepting 'gdb' connection on tcp/43497
    Info : device id = 0x30006441
    Info : flash size = 1024kbytes
    Info : dropped 'gdb' connection (error -400)
    shutdown command invoked

    At the end of the test, the result indicated success but the 2nd last line in the output seems to indicate failure.

    • This reply was modified 5 years, 9 months ago by surahman.
    • This reply was modified 5 years, 9 months ago by surahman.
    in reply to: STM32 connection issues #23985
    surahman
    Participant

    Hi,

    I updated the OpenOCD executable and I’m now getting this error:

    AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.openocd\bin\openocd.exe -c "gdb_port 41975" -c "telnet_port 41976" -f interface/stlink-v2-1.cfg -c "transport select hla_swd" -f target/stm32f4x.cfg -c init -c "reset init" -c "echo VisualGDB_OpenOCD_Ready"
    Open On-Chip Debugger 0.10.0 (2019-02-25) [https://github.com/sysprogs/openocd]
    Licensed under GNU GPL v2
    For bug reports, read
    http://openocd.org/doc/doxygen/bugs.html
    WARNING: interface/stlink-v2-1.cfg is deprecated, please switch to interface/stlink.cfg
    hla_swd
    Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
    adapter speed: 2000 kHz
    adapter_nsrst_delay: 100
    none separate
    Info : clock speed 2000 kHz
    Error: open failed: jtag_libusb_open() returned error -4

     

    Thanks,

    in reply to: Intellisense and CPPUTest issues #21675
    surahman
    Participant

    You are awesome, thanks, that fixed the issue. If anyone else runs into this issue in future make sure to delete the old template project and start with a fresh one using the new build because the old project will have issues.

    On the windows display scaling side of things all the windows in the VGDB properties pane now scale properly except the Debug Properties page.

    Thanks,
    /Saad

    • This reply was modified 6 years, 3 months ago by surahman.
    Attachments:
    You must be logged in to view attached files.
    in reply to: 32bit link on a 64bit machine #20931
    surahman
    Participant

    That fixed it, thanks!

    in reply to: Instrumentation: Sanitizers #20283
    surahman
    Participant

    Hi,

    Sorry, I guess I should’ve been a little more precise with my question and given a little more information on the Linux system. Deploying and testing on WSL with g++6, which might be the primary cause of the issue, and I can’t really find where in the VGDB UI I should be passing/setting these arguments. I’m still finding my way around all the settings.

    Thanks.

    in reply to: Stray character in program. #20142
    surahman
    Participant

    I think the issue might be that the project I’m trying to convert is one that was built using the VS Cross-platform wizard.

    in reply to: Stray character in program. #20140
    surahman
    Participant

    I can confirm that the MSBuild Project wizard works, but I can’t convert a ready-made project.

    in reply to: Stray character in program. #20132
    surahman
    Participant

    I can confirm that VGDB is installed in said directory and that the registry key is as specified. I ran a repair of VS2017 and a clean install of VGDB, but the problem still persists. Not sure what to try next.

    in reply to: Stray character in program. #20129
    surahman
    Participant

    I uninstalled VisualGDB and that didn’t help. Repairing VS2017 Enterprise now…

    Installation directory is the default one: C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE

    • This reply was modified 6 years, 9 months ago by surahman.
    in reply to: Stray character in program. #20126
    surahman
    Participant

    The problem persists, unfortunately.

    in reply to: Stray character in program. #20119
    surahman
    Participant

    I’m now getting the following error when I try to “convert” an already built project to use VisualGDB:

    VisualGDB version: 5.3.18.1973
    —————— System.InvalidOperationException ——————
    System.InvalidOperationException: Platform ‘VisualGDB’ referenced in the project file ‘Server’ cannot be found.
    at Microsoft.Verify.FailOperation(String message, Object[] args)
    at Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.VCProjectShim.<AddPlatformNoEventsAsync>d__336.MoveNext()
    — End of stack trace from previous location where exception was thrown —
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.VCProjectShim.<>c__DisplayClass61_0.<<AddPlatform>b__0>d.MoveNext()
    — End of stack trace from previous location where exception was thrown —
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.ApartmentMarshaler.<>c__DisplayClass7_0.<<Invoke>b__0>d.MoveNext()
    — End of stack trace from previous location where exception was thrown —
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at Microsoft.VisualStudio.Threading.JoinableTask.CompleteOnCurrentThread()
    at Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.ApartmentMarshaler.Invoke(Func`1 method)
    at Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.VCProjectShim.AddPlatform(String platformName)
    at mw.AddNewPlatformAndEnsureConfigurations(String b, String[] a)
    at w9.b(qp1 f, IProjectEditContext e, t b, hj1 d, l g, Boolean c, a[] a)
    at d61.c_2(v1 a, IProjectEditContext c, qp1 b, String d)
    at jb1.NewLinuxConfiguration.Execute()

    in reply to: Stray character in program. #20113
    surahman
    Participant

    I forgot to add this is the tutorial I am working with: https://visualgdb.com/tutorials/porting/lxss/

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