AnsweredAssumed Answered

QN9080 - Devkit stoped working

Question asked by Shai Berman on Mar 26, 2020
Latest reply on Mar 31, 2020 by Shai Berman

Hello team,

I have been working with QN9080 a few weeks back and everything was working properly, but when I have tried to work with the devkit once again and I got the following error: 'Wire Ack Fault'.

Could you please advise how to overcome this issue, please find below the errors log.

 

02: Failed on connect

  02: Failed on connect

  Could not connect to core.

  31: No connection to chip's debug port

  Debugging context: qn908xcdk_wireless_examples_bluetooth_glucose_sensor_freertos LinkServer Debug

 

Error in final launch sequence:

 

Failed to execute MI command:

-target-select extended-remote | crt_emu_cm_redlink -msg-port=55307 -g -mi -2 -pQN908XC -vendor=NXP --connectscript=RunBootRomConnect.scp --resetscript=qn908xreset.scp --reset= -ProbeHandle=1 -CoreIndex=0 -cache=disable --flash-driver= -x C:/Users/User/Documents/MCUXpressoIDE_11.0.1_2563/workspace_QN9080_2/.mcuxpressoide_packages_support/QN908XC_support --flash-dir C:/NXP/MCUXpressoIDE_11.0.1_2563/ide/plugins/com.nxp.mcuxpresso.tools.bin.win32_11.0.1.201908271452/binaries/Flash --flash-dir C:/Users/User/Documents/MCUXpressoIDE_11.0.1_2563/workspace_QN9080_2/.mcuxpressoide_packages_support/QN908XC_support/Flash --telnet 3330

Error message from debugger back end:

Remote communication error.  Target disconnected.: Success.

Failed to execute MI command:

-target-select extended-remote | crt_emu_cm_redlink -msg-port=55307 -g -mi -2 -pQN908XC -vendor=NXP --connectscript=RunBootRomConnect.scp --resetscript=qn908xreset.scp --reset= -ProbeHandle=1 -CoreIndex=0 -cache=disable --flash-driver= -x C:/Users/User/Documents/MCUXpressoIDE_11.0.1_2563/workspace_QN9080_2/.mcuxpressoide_packages_support/QN908XC_support --flash-dir C:/NXP/MCUXpressoIDE_11.0.1_2563/ide/plugins/com.nxp.mcuxpresso.tools.bin.win32_11.0.1.201908271452/binaries/Flash --flash-dir C:/Users/User/Documents/MCUXpressoIDE_11.0.1_2563/workspace_QN9080_2/.mcuxpressoide_packages_support/QN908XC_support/Flash --telnet 3330

Error message from debugger back end:

Remote communication error.  Target disconnected.: Success.

 

Console log below

 

MCUXpresso IDE RedlinkMulti Driver v11.0 (Aug 27 2019 16:46:33 - crt_emu_cm_redlink build 22)

Found part description in XML file QN908XC_internal.xml

Reconnected to existing LinkServer process.

Connecting to probe 1 core 0 (using server started externally) reports:

'Ee(42). Could not connect to core.'

Retrying...

Reconnected to existing LinkServer process.

Server OK but no connection to probe 1 core 0 (after 3 attempts) - Ee(42). Could not connect to core.

============= SCRIPT: RunBootRomConnect.scp =============

Error: Wire Ack Fault - target connected?

Error: Wire not connected

Error: Wire not connected

Error: Wire not connected

Error: Wire not connected

Halt on reset vector catch

Error: Wire not connected

Error: Wire not connected

Error: Wire not connected

Halt on watchpoint read of vector table

Error: Wire not connected

============= END SCRIPT ================================

Failed on connect: Ee(42). Could not connect to core.

No connection to chip's debug port

 

Please advise back, thanks in advance and keep safe.

Kind regards,

Shai

Outcomes