Home Topics PyOCD not in Debug Configurations in KDS 3.2.0

Overview Forums NXP KDS and KSDK Software Tools PyOCD not in Debug Configurations in KDS 3.2.0

Tagged: , , ,

This topic contains 20 replies, has 7 voices, and was last updated by  hs4n.mzb 2 years ago.

Viewing 6 posts - 16 through 21 (of 21 total)
  • Author
    Posts
  • #1980

    anupam_on
    Participant

    ok. Thank you for the clarification

    #2009

    jayaura
    Participant

    Hi, I’ve fixed the issue. I’ve sent a pull request to pyOCD. Until they accept it, you can get it from my fork. Simply install pyOCD from https://github.com/aurabindo/pyOCD

    #2439

    jaimezorno
    Participant

    Hello!

    Did you manage to solve the initial problem for windows?
    I get the same error as you did initially.

    WARNING:root:Failed to load SVD file MK64F12.svd
    INFO:root:DAP SWD MODE initialised
    Traceback (most recent call last):
    File “pyOCD\tools\gdb_server.py”, line 259, in run
    File “pyOCD\board\mbed_board.py”, line 263, in chooseBoard
    File “pyOCD\board\board.py”, line 50, in init
    File “pyOCD\target\target_kinetis.py”, line 58, in init
    File “pyOCD\target\coresight_target.py”, line 75, in init
    File “pyOCD\coresight\dap.py”, line 112, in init
    File “pyOCD\coresight\dap.py”, line 117, in read_id_code
    File “pyOCD\coresight\dap.py”, line 130, in read_reg
    File “pyOCD\coresight\dap.py”, line 186, in readDP
    File “pyOCD\pyDAPAccess\dap_access_usb.py”, line 534, in read_reg
    File “pyOCD\pyDAPAccess\dap_access_usb.py”, line 726, in _write
    File “pyOCD\pyDAPAccess\dap_access_usb.py”, line 473, in flush
    File “pyOCD\pyDAPAccess\dap_access_usb.py”, line 624, in _read_packet
    File “pyOCD\pyDAPAccess\dap_access_usb.py”, line 329, in decode_data
    File “pyOCD\pyDAPAccess\dap_access_usb.py”, line 275, in _decode_transfer_data
    TransferError
    uncaught exception:

    #2457

    goldscott
    Participant

    Hello,

    I gave up on it. I was advised to install the latest version of KDS. Which version are you using?

    #2968

    hs4n.mzb
    Participant

    Hello.

    I faced with the same problem.
    Is there any progress?

    I call pyocd-gdbserver.exe directly from command line, but it is same.

    OS: Windows7 64bit

    ——
    c:\Freescale\KDS_v3>pyocd-gdbserver.exe
    WARNING:root:Failed to load SVD file MK64F12.svd
    INFO:root:DAP SWD MODE initialised
    uncaught exception:
    Traceback (most recent call last):
    File “pyOCD\tools\gdb_server.py”, line 259, in run
    File “pyOCD\board\mbed_board.py”, line 263, in chooseBoard
    File “pyOCD\board\board.py”, line 50, in init
    File “pyOCD\target\target_kinetis.py”, line 58, in init
    File “pyOCD\target\coresight_target.py”, line 75, in init
    File “pyOCD\coresight\dap.py”, line 112, in init
    File “pyOCD\coresight\dap.py”, line 117, in read_id_code
    File “pyOCD\coresight\dap.py”, line 130, in read_reg
    File “pyOCD\coresight\dap.py”, line 186, in readDP
    File “pyOCD\pyDAPAccess\dap_access_usb.py”, line 534, in read_reg
    File “pyOCD\pyDAPAccess\dap_access_usb.py”, line 726, in _write
    File “pyOCD\pyDAPAccess\dap_access_usb.py”, line 473, in flush
    File “pyOCD\pyDAPAccess\dap_access_usb.py”, line 624, in _read_packet
    File “pyOCD\pyDAPAccess\dap_access_usb.py”, line 329, in decode_data
    File “pyOCD\pyDAPAccess\dap_access_usb.py”, line 275, in _decode_transfer_data

    TransferError

    c:\Freescale\KDS_v3>

    #3013

    hs4n.mzb
    Participant

    Hello,

    After previous my post, I tried to rewrite F/W, it also impossible.
    I tried following 2 way.

    1. OTAP update (using Hexiwear application on android) -> It looks update is succeeded by Android app, but it does not work.
    2. writing FW to DAPLINK drive (with docking station) -> It fails by creating FAIL.TXT, it describe “The transfer timed out.”.

    Also I tried J-link connection, referring following article.
    Flashing and Restoring the Hexiwear Firmware

    But, it is not work. Then, I tried to use J-link commander to connect, but it can’t.

    —-
    SEGGER J-Link Commander V6.16d (Compiled Jun 21 2017 19:08:48)
    DLL version V6.16d, compiled Jun 21 2017 19:08:15

    Connecting to J-Link via USB…O.K.
    Firmware: J-Link ARM Lite V8 compiled Oct 29 2014 09:03:16
    Hardware version: V8.00
    S/N: XXXXXXXX
    License(s): GDB
    VTref = 3.358V

    Type “connect” to establish a target connection, ‘?’ for help
    J-Link>connect
    Please specify device / core. <Default>: MK64FN1M0XXX12
    Type ‘?’ for selection dialog
    Device>
    Please specify target interface:
    J) JTAG (Default)
    S) SWD
    TIF>S
    Specify target interface speed [kHz]. <Default>: 4000 kHz
    Speed>
    Device “MK64FN1M0XXX12” selected.

    Connecting to target via SWD
    Executing InitTarget()
    Connect Under Reset
    Connect Under Reset
    Executing InitTarget()
    Connect Under Reset
    Connect Under Reset

    ****** Error: InitTarget(): PCode returned with error code -1

    Executing InitTarget()
    Connect Under Reset
    Connect Under Reset
    Executing InitTarget()
    Connect Under Reset
    Connect Under Reset

    ****** Error: InitTarget(): PCode returned with error code -1

    Cannot connect to target.
    J-Link>
    —-

    So, I doubt MK64 would be prohibited to attach debugger by secure.
    What could I do anything to attach debugger?

Viewing 6 posts - 16 through 21 (of 21 total)

You must be logged in to reply to this topic.