Wire not connected on Q9080-DX LinkServer

[rickdickerson]

I have a new Q9080-DX development board that I am trying to debug through the LinkServer CMSIS-DAP interface on a Windows 10 machine using MCUXpresso 10.1.1. I have successfully pushed two example projects to the board and was able to debug them, but I can't connect to the board anymore (the error message is below) for either of those projects. It stopped working while I was developing, so the IDE and development board were in the same state as the previous successful debugging session. No changes were made to the debug configuration between the last successful debugging session and the beginning of the failures. The last application I pushed into the QN9080 is still working, so that chip appears to be alive.

I think the LPC hardware is still working and configured properly because I still see the virtual comm port in the Windows Device Manager and the probe can be discovered by the debugger. However, when I try to debug the application I get an error stating that the wire is not connected. I have tried restarting MCUXpresso, rebooting the PC, starting a new workspace and deleting and recreating the debug configuration to no avail. The LPC driver version is 2.0.0.0, which I think is up to date.

After the failure, the MCUXpresso IDE status bar says that it killed redlinkserv.exe, but I can see the process is still running in the task manager. I tried manually killing that process but it didn't help.

I would appreciate any help someone can provide in getting this board back up and running. 

 

[jlee642]

So if we are developing an Bluetooth application for qn908x, would we always have to reset the board by jumping JP15?

[lpcxpresso_supp]

One other minor aside - I notice that your board appears to have old LPC-Link2 probe firmware pre-programmed into it (v5.173). I would suggest that you either remove the header on JP5 (DFUlink) to allow the IDE to softload the current version (v5.18x) or use LPCScrypt to program the current version into flash (seeLPC-Link2 Debug Probe firmware programming for more details).

Regards,

MCUXpresso IDE Support

[rickdickerson]

Thanks for the tip. I upgraded my probe.

[neoxiong]

Hi, Rick

Heart rate project has enabled low power feature by define cPWR_UsePowerDownMode 1. So the chip will go to Power down state and you can't get connected to an external debugger. 

[rickdickerson]

The chip was still advertising BLE and I was able to connect to it with the IoT Toolbox app when I couldn't connect with a debugger. Wouldn't that indicate that the chip wasn't in a low power state?

[neoxiong]

Hi, Rick

Between advertising event and connection event, the chip goes to Power Down 0. No clock to support debugger

[rickdickerson]

That makes perfect sense. Thanks.

[lpcxpresso_supp]

I do see a problem with MCUXpresso terminating the debug session when attempting a Restart. We'll investigate a fix for a future release.

Thanks and regards,

MCUXpresso Support

[lpcxpresso_supp · Accepted solution]

I'm  not certain. Place a jumper on JP15, and reset the board, or power it on/off. This will boot the part into the ISP and will not allow the flashed image to execute. Then, erase flash using the flash utility and flash another example. I've located a QN9080 v1.1 board to test with, but I'd prefer to use the same revision as yourself.

Thanks and regards,

MCUXpresso Support

[rickdickerson]

That fixed it!! After following your instructions I have been able to load several example programs into the development board. Thanks!!

[lpcxpresso_supp]

Hi Rick,

What version board(s) do you have?

Thanks and regards,

MCUXpresso Support

[rickdickerson]

Both boards are marked as

QN9080 DK-V1.2

R20161129

[rickdickerson]

Is it possible that the heart rate example could be the culprit? On my first board, I successfully downloaded the ble relay proxy example and then the heart rate example. I could not download anything else after that. The heart rate example was the first thing I downloaded to the second development board and I haven't been able to download anything else.

My SDK version is 2.2.0.

[lpcxpresso_supp]

Please include The Debug Log in your response. You stated there were no debug configuration changes to blame, but the  first question I'll ask is whether your launch configuration uses the qn908xreset.scp reset script?

Thanks and regards,

LPCXpresso Support

[rickdickerson]

Can you provide any insight into this issue? I suspected the development board may be defective so I purchased another one. I got the Windows message about installing new drivers when I plugged in the new board. I let that process finish and was able to successfully install the heart rate example into the new board. I plugged in the old board to see if the driver update had any effect, but still had the same problems. I then went back to the new development board and could no longer connect to it. 

A coworker downloaded the QN9080 SDK and has tried both boards with the same failures that I have been seeing. 

Is it possible to get the LPC4322 hung up so it won't communicate with the PC? Cycling power on the development board and/or the PC doesn't do any good.

[rickdickerson]

I used the default configuration settings and it appears that I am using the qn908xresect.scp script. Nothing is selected in the Reset Handling field though. Should I have something selected there?

The qn908cdk_wireless_examples_bluetooth_heart_rate_sensor_bm Debug messages console is empty.

Here is the RedlinkServer log:

[Started server]
[Connected on port 3025]
redlink>ProbeList
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.173
Serial Number = BTAVCQEQ
VID:PID = 1FC9:0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&618ad55&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
redlink>ProbeStatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.173
Serial Number = BTAVCQEQ
VID:PID = 1FC9:0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&618ad55&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = FALSE
WireInitialized = FALSE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 1024
Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = CMSIS-DAP
Probe Reference Count = 0
redlink>ProbeIsOpen 1
FALSE
redlink>ProbeOpenByIndex 1
Probe Handle 1 Open
redlink>WireIsConnected 1
FALSE
redlink>WireSwdConnect 1
Wire Ack Fault - target connected?
redlink>CoresConfigured 1
FALSE
redlink>CoreConfig 1
Wire not connected
[Closed]
[Started server]
[Connected on port 3025]
redlink>ProbeStatus
redlink>quit
[Closed]

This is the arm-none-eabi-gdb console log

GNU gdb (GNU Tools for ARM Embedded Processors 6-2017-q2-update) 7.12.1.20170417-git
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-w64-mingw32 --target=arm-none-eabi".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".

This is the gdb traces console log

862,535 2-list-thread-groups
862,551 2^done,groups=[{id="i1",type="process"}]
862,551 (gdb)
865,160 3-gdb-version
865,175 ~"GNU gdb (GNU Tools for ARM Embedded Processors 6-2017-q2-update) 7.12.1.20170417-git\n"
865,175 ~"Copyright (C) 2017 Free Software Foundation, Inc.\n"
865,175 ~"License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>\nThis is fre\
e software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitt\
ed by law. Type \"show copying\"\nand \"show warranty\" for details.\n"
865,175 ~"This GDB was configured as \"--host=i686-w64-mingw32 --target=arm-none-eabi\".\nType \"sho\
w configuration\" for configuration details."
865,175 ~"\nFor bug reporting instructions, please see:\n"
865,175 ~"<http://www.gnu.org/software/gdb/bugs/>.\n"
865,175 ~"Find the GDB manual and other documentation resources online at:\n<http://www.gnu.org/soft\
ware/gdb/documentation/>.\n"
865,175 ~"For help, type \"help\".\n"
865,175 ~"Type \"apropos word\" to search for commands related to \"word\".\n"
865,175 3^done
865,175 (gdb)
865,191 4-environment-cd C:/Users/rdickerson/mcuxpresso/01/SDKPackages/SDK_2.2_QN908XCDK/boards/qn90\
8xcdk/wireless_examples/bluetooth/ble_relay_proxy_rickd/qn908xcdk_wireless_examples_bluetooth_heart_\
rate_sensor_bm
865,239 4^done
865,239 (gdb)
865,239 5-gdb-set breakpoint pending on
865,254 5^done
865,254 (gdb)
865,254 6-enable-pretty-printing
865,270 6^done
865,270 (gdb)
865,270 7-gdb-set python print-stack none
865,271 7^done
865,271 (gdb)
865,271 8-gdb-set print object on
865,286 8^done
865,286 (gdb)
865,302 9-gdb-set print sevenbit-strings on
865,318 9^done
865,318 (gdb)
865,318 10-gdb-set charset ISO-8859-1
865,333 10^done
865,333 (gdb)
865,333 11-gdb-set auto-solib-add on
865,349 11^done
865,349 (gdb)
865,349 12-file-exec-and-symbols --thread-group i1 C:/Users/rdickerson/mcuxpresso/01/SDKPackages/SDK\
_2.2_QN908XCDK/boards/qn908xcdk/wireless_examples/bluetooth/ble_relay_proxy_rickd/qn908xcdk_wireless\
_examples_bluetooth_heart_rate_sensor_bm/Debug/qn908xcdk_wireless_examples_bluetooth_heart_rate_sens\
or_bm.axf
865,380 12^done
865,380 (gdb)
865,380 13-interpreter-exec console "set remotetimeout 60000"
865,396 =cmd-param-changed,param="remotetimeout",value="60000"
865,396 13^done
865,396 (gdb)
867,060 14-target-disconnect
867,060 15-gdb-exit
867,075 14^error,msg="You can't do that when your target is `exec'"
867,075 (gdb)
867,075 15^exit