AnsweredAssumed Answered

could not connect to target(Jlink, MCUXpresso)

Question asked by liang chen on Mar 13, 2019
Latest reply on Apr 11, 2019 by Hui_Ma

MCU:KL17Z64VFM4 , connect to Jlink via SWD.

very strange, only happen on new chip, error info below:

 

Could not connect to target.
  SEGGER J-Link GDB Server V6.40 Command Line Version
  JLinkARM.dll V6.40 (DLL compiled Oct 26 2018 15:06:02)
  Command line: -nosilent -swoport 2332 -select USB=59402905 -telnetport 2333 -singlerun -endian little -noir -speed auto -port 2331 -vd -device MKL17Z64xxx4 -if SWD -halt -reportuseraction
  -----GDB Server start settings-----
  GDBInit file:                  none
  GDB Server Listening port:     2331
  SWO raw output listening port: 2332
  Terminal I/O port:             2333
  Accept remote connection:      localhost only
  Generate logfile:              off
  Verify download:               on
  Init regs on start:            off
  Silent mode:                   off
  Single run mode:               on
  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:                 MKL17Z64xxx4
  Target interface:              SWD
  Target interface speed:        auto
  Target endian:                 little
  Connecting to J-Link...
  J-Link is connected.
  Device "MKL17Z64XXX4" selected.
  Firmware: J-Link V9 compiled Oct 25 2018 11:46:07
  Hardware: V9.40
  S/N: 59402905
  Feature(s): RDI, GDB, FlashDL, FlashBP, JFlash
  Checking target voltage...
  Target voltage: 2.67 V
  Listening on TCP/IP port 2331
  Connecting to target...InitTarget()
  Found SW-DP with ID 0x0BC11477
  Scanning AP map to find all available APs
  AP[2]: Stopped AP scan as end of AP map has been reached
  AP[0]: AHB-AP (IDR: 0x04770031)
  AP[1]: JTAG-AP (IDR: 0x001C0020)
  Iterating through AP map to find AHB-AP to use
  AP[0]: Core found
  AP[0]: AHB-AP ROM base: 0xF0002000
  CPUID register: 0x410CC601. Implementer code: 0x41 (ARM)
  Found Cortex-M0 r0p1, Little endian.
  FPUnit: 0 code (BP) slots and 0 literal slots
  CoreSight components:
  ROMTbl[0] @ F0002000
  InitTarget()
  Found SW-DP with ID 0x0BC11477
  AP map detection skipped. Manually configured AP map found.
  AP[0]: AHB-AP (IDR: Not set)
  AP[0]: Core found
  AP[0]: AHB-AP ROM base: 0xF0002000
  CPUID register: 0x410CC601. Implementer code: 0x41 (ARM)
  Found Cortex-M0 r0p1, Little endian.
  FPUnit: 0 code (BP) slots and 0 literal slots
  CoreSight components:
  ROMTbl[0] @ F0002000
  ERROR: Could not connect to target.
  Target connection failed. GDBServer will be closed...Restoring target state and closing J-Link connection...
  Shutting down...
  Could not connect to target.
  Please check power, connection and settings.

 

from the error message,  Jlink could find MCU but fail on later step. then  I try my PCB with IAR 8.2, I can debug under IAR, then I switch to MCUXpresso, it works fine too

I try another new soldered PCB, the same phenomenon,

very strange, sames MCUXpresso can not handle new KL17 chip? but MCUXpresso could debug KL17s which has been download program before(IAR did some config to KL17 that MCUXpresso need?)

 

I also tried MCUXpresso v10.2.1 , also the same phenomenon.

 

could someone help on this, thanks very very

Outcomes