AnsweredAssumed Answered

Kinetis MCU "KV10Z-32" - With power up, Reset pin will always with low voltage.

Question asked by Harpreet Singh Employee on Apr 26, 2018
Latest reply on Apr 26, 2018 by Hui_Ma

Hi,

I am using KV10Z32 MCU and while debugging following error occurs:

 

1. With 'download and debug' option, below is the error logs

Error in final launch sequence
Error: Unable to connect wire for probe index 2.
Hardware interface transfer error

LinkServer has been terminated and will be restarted.
Please restart your debug session.
If the problem recurs, please power cycle your debug probe and restart MCUXpresso IDE.
Error: Unable to connect wire for probe index 2.
Hardware interface transfer error

LinkServer has been terminated and will be restarted.
Please restart your debug session.
If the problem recurs, please power cycle your debug probe and restart MCUXpresso IDE.

 

2. With 'Resurrect locked kinetis device' option, below is the error logs

crt_emu_cm_redlink --connect -g --debug 2 --vendor NXP -p MKV10Z32xxx7 -ProbeHandle=2 -CoreIndex=0 --ConnectScript kinetismasserase.scp --reset vectreset -x C:
/Users/XXXX/mcuxpresso/01/.mcuxpressoide_packages_support/MKV10Z32xxx7_support --flash-dir C:/Users/XXXX/mcuxpresso/01/.mcuxpressoide_packages_support/MKV10Z32xxx7_support/Flash


Ns: MCUXpresso RedlinkMulti Driver v10.1 (Dec 19 2017 16:58:35 - crt_emu_cm_redlink.exe build 390)
Pc: ( 0) Reading remote configuration
Wc(03). No cache support.
Pc: ( 5) Remote configuration complete
Nc: Reconnected to existing redlink server (PID 4294967295)
Nc: Connecting to probe 2 core 0 (server PID unknown) gave 'Ee(36). Could not connect to core.'
Nc: Connecting to probe 2 core 0 (server PID unknown) gave 'Ee(36). Could not connect to core.'
Nc: Connecting to probe 2 core 0 (server PID unknown) gave 'Ee(36). Could not connect to core.'
Nc: Server OK but no connection to probe 2 core 0 (after 3 attempts) - Ee(36). Could not connect to core.
Ed:02: Failed on connect: Ee(36). Could not connect to core.
Et:31: No connection to chip's debug port
Pc: (100) Target Connection Failed
Nc: error closing down debug session - Em(02). MEM-AP is not selected.

 

"With power up, Reset pin will always with low voltage, or output oscillated signals (different with blanked chip), for example, KL chip without programmed, the reset pin output normal signal period is 36us and low voltage about 30us"

(Maybe)Best on the above comment, its looks that MCU got locked because the RESET LED always glow RED after power-up.

 

Please help me to figure out whats going wrong and how to solve this.

 

Thanks, 

Ashutosh#

Outcomes