Maix Doc Debug with Segger JLink

Sysprogs forums Forums VisualGDB Maix Doc Debug with Segger JLink

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #30880
    marcusob
    Participant

    Hi,.

    I am trying to follow this page to debug the Maix Doc I with a Segger J-Link V8, on Windows 10 with Visual Studio Community 2019.

    Debugging Kendryte K210 Projects with Visual Studio – VisualGDB Tutorials

    Creating a new project using New embedded project wizard I get the following exception thrown

    System.Exception: Missing C:\Users\marcu\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.arm.segger-dmsp\SeggerEDP.dll
    at VisualGDB.Common_GUI.WPF.DebugMethodSettingsControl.Controller.BoundDebugMethod.ProvideConfiguratorOrThrow(IBSPConfiguratorHost host)
    at VisualGDB.Common_GUI.WPF.DebugMethodSettingsControl.Controller.UpdateSelectedConfigurator(Boolean suppressPropertyChangeHandlers, MethodOrDeviceItemBase value, MethodOrDeviceItemBase prevValue)

     

    When I ignore the error and go into VS, it tells me I need to have the JLink as a WINUSB driver. I’ve been messing around with Zadig before this trying to debug the Maix Longan-Nano – which required me to install drivers via Zadig etc.

    To see how JLink is currently listed – see image for device driver

    When I click debug it says “J-Link does not appear to have “WinUSB” driver installed. The debugger may have problems finding your device. Try installing it now ?”

    I say yes and it says Failed signing the driver, do I want to install manual, I say yes and I get another exception

    VisualGDB version: 5.5.105.4124
    —————— System.Exception ——————
    System.Exception: Don’t know how to load settings type: com.visualgdb.edp.openocd.settings.risc-v
    at BSPEngine.LoadedBSP.LoadedDebugMethod.LoadConfigurationObject(XmlElement node)
    at rb2.q1(ConfiguredDebugMethod a)
    at om1.s_2(DebugCustomizationSettings b, Boolean a)
    at ef.k3()
    at kt.f1_2()
    at VisualGDB.GDBDebugEngine.q(d23 b, w1 a)
    trace=[BSPEngine.LoadedBSP+LoadedDebugMethod.LoadConfigurationObject:164, rb2.q1:102, om1.s_2:0, ef.k3:484, kt.f1_2:22, VisualGDB.GDBDebugEngine.q:58]

    Any ideas on how to proceed with this ?

    Thanks

    Attachments:
    You must be logged in to view attached files.
    #30888
    support
    Keymaster

    Hi,

    It looks like you have manually edited some files in the VisualGDB debug packages.

    Please try deleting the entire %LOCALAPPDATA%\VisualGDB\EmbeddedDebugPackages folder and creating another project from scratch, letting VisualGDB download all the packages.

    #30892
    marcusob
    Participant

    Thanks for the quick reply ! I did what you suggested, and it certainly looks healthier, I can test the connection with the Test Button in the new project wizard when I select k210, and OpenOCD not the Jlink software and it works. But I still can’t debug, I get this message

    I can see the Jlink under Universal Serial Bus (and I applied the WinUSB like VisualGDB asked me to), and under Ports (COKM ^ LPT) I can see USB-SERIAL CH340 (COM9)

    “JTAG scan chain interrogation failed : al zeroes

    This error typically indicates JTAG/SWD wiring problems

    Please double check”

    This is the GDB log

     

    C:\Users\marcu\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.riscv.openocd-kendryte\bin\openocd.exe -c “gdb_port 62446” -c “telnet_port 62447” -f interface/jlink.cfg -c “adapter_khz 3000” -f target/kendryte.cfg -c “echo VisualGDB_OpenOCD_Ready”
    _ __ _ _
    | |/ /___ _ __ __| |_ __ _ _| |_ ___
    | ‘ // _ \ ‘_ \ / _` | ‘__| | | | __/ _ \
    | . \ __/ | | | (_| | | | |_| | || __/
    |_|\_\___|_| |_|\__,_|_| \__, |\__\___|
    |___/
    Kendryte Open On-Chip Debugger For RISC-V v0.2.3 (2019-02-21)
    Licensed under GNU GPL v2
    adapter speed: 3000 kHz
    Info : auto-selecting first available session transport “jtag”. To override use ‘transport select <transport>’.
    srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst
    VisualGDB_OpenOCD_Ready
    Info : Listening on port 6666 for tcl connections
    Info : Listening on port 62447 for telnet connections
    Info : J-Link ARM V8 compiled May 27 2009 17:31:22
    Info : Hardware version: 8.00
    Info : VTarget = 3.332 V
    Info : clock speed 3000 kHz
    Error: JTAG scan chain interrogation failed: all zeroes
    Error: Check JTAG interface, timings, target power, etc.
    Error: Trying to use configured scan chain anyway…
    Error: riscv.cpu: IR capture error; saw 0x00 not 0x01
    Warn : Bypassing JTAG setup events due to errors
    Error: dtmcontrol is 0. Check JTAG connectivity/board power.
    Info : Listening on port 62446 for gdb connections
    Info : accepting ‘gdb’ connection on tcp/62446
    Error: slot_offset called with xlen=-1, slot=0
    Info : Got data from 0x0 but expected it from 0x4
    Error: slot_offset called with xlen=-1, slot=0
    Error: Unexpected HART read back from DMCONTROL: 0 instead of 0

    Error: slot_offset called with xlen=-1, slot=0
    Info : Got data from 0x0 but expected it from 0x4
    Error: slot_offset called with xlen=-1, slot=0
    Error: Target not initialized. Return ERROR_FAIL.
    Error: get register list failed
    Info : Failed detecting Target Description Support, disabling
    undefined debug reason 7 – target needs reset
    Error: slot_offset called with xlen=-1, slot=0
    Info : Got data from 0x0 but expected it from 0x4
    Error: slot_offset called with xlen=-1, slot=0
    Error: Unexpected HART read back from DMCONTROL: 0 instead of 0

    Error: slot_offset called with xlen=-1, slot=0
    Info : Got data from 0x0 but expected it from 0x4
    Error: slot_offset called with xlen=-1, slot=0
    Error: Target not initialized. Return ERROR_FAIL.
    Info : dropped ‘gdb’ connection

     

    #30896
    support
    Keymaster

    Hi,

    This looks like a wiring problem. Please double-check your wiring, clocks and power. If nothing works, please contact Kendryte for assistance, as hardware problems are outside of VisualGDB’s control.

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.