nRF5340 DK and PPK2 not working

[langestefann]

Hi,

I am using the PPK2 to evaluate the nRF5340. Neither of these devices is currently working properly, I think the underlying cause has something to do with USB that's why I created only one issue. 

• PPK2

It works the first time after restarting my computer. If I then close Power Profiler and select the device again it hangs at 'Opening device with s/n EAA9B4F32C15'. After that it will not be usable. I have tried unplugging/replugging the USB, using with a powered USB hub, without a USB hub, nothing works except restarting my PC. It's identical to this issue but it never got a solution unfortunately: https://devzone.nordicsemi.com/f/nordic-q-a/76900/cant-open-power-profiler-kit-2-on-windows-pc

• nRF5340 DK

It can connect fine. When I press the 'read' button to read the memory I get:

15:04:19.393 Failed to get device memory map: async task failure for id: 1865463227 msg: JLINKARM_DLL_TIME_OUT_ERROR (Origin: "Error when running fw program.")
15:04:19.393 Error when reading device

I tried the same with nrfjprog command line utility and it gave the same result. I have attached the log here for reference:

 

Furthermore I have tried:

• Using a personal laptop. Both devices work fine on this machine, no issues whatsoever. This makes me sure that it's something with my installation. 
• Reinstalling. I just did a clean install of all software involved, including windows drivers. Unfortunately it made no difference. 

[Simonr]

Hi

I'm not able to download or open the log you have provided. First, please turn on Verbose logging when by going to ABOUT and enable it, then restart the app, so we can get more information from the log as well:

Then add it as a file using the insert image/video/file option here so we can review it.

 

One more thing you can try to do is uninstall the Power Profiler app, the nRF Connect app entirely, and then (assuming you're on Windows) go to C:\Users\<your username>\AppData\Roaming\nrfconnect in your file explorer and make sure this folder is empty or non-existent before reinstalling nRF Connect for Desktop and the Power Profiler app. If that also fails, can you tell me more about your computer? Is it a Windows machine, Linux or Mac OS, and what version? Is the USB cable next to another USB 3.0 device?

Best regards,

Simon

[langestefann]

Fullscreen 2023-01-24T12_29_44.582Z-log.txt Download

2023-01-24T12:29:45.068Z DEBUG Application data folder: C:\Users\lange\AppData\Roaming\nrfconnect\pc-nrfconnect-ppk
2023-01-24T12:29:45.095Z INFO Using nrf-device-lib-js version: 0.4.13
2023-01-24T12:29:45.095Z INFO Using nrf-device-lib version: 0.12.8
2023-01-24T12:29:45.095Z INFO Using nrfjprog DLL version: 10.16.0
2023-01-24T12:29:45.095Z INFO Using JLink version: JLink_V7.80c
2023-01-24T12:29:45.136Z DEBUG App pc-nrfconnect-ppk v3.5.3 official
2023-01-24T12:29:45.137Z DEBUG App path: C:\Users\lange\.nrfconnect-apps\node_modules\pc-nrfconnect-ppk
2023-01-24T12:29:45.137Z DEBUG nRFConnect 3.12.0, required by the app is (^3.12.0)
2023-01-24T12:29:45.137Z DEBUG nRFConnect path: C:\Users\lange\AppData\Local\Programs\nrfconnect\resources\app.asar
2023-01-24T12:29:45.137Z DEBUG HomeDir: C:\Users\lange
2023-01-24T12:29:45.137Z DEBUG TmpDir: C:\Users\lange\AppData\Local\Temp
2023-01-24T12:29:45.137Z INFO Installed JLink version does not match the provided version (V7.66a)
2023-01-24T12:29:49.395Z INFO Validating firmware for device with s/n EAA9B4F32C15
2023-01-24T12:29:49.398Z DEBUG Device has DFU trigger interface, the device is in Application mode
2023-01-24T12:29:49.398Z DEBUG Will wait for device EAA9B4F32C15
2023-01-24T12:29:49.400Z INFO Opening device with s/n EAA9B4F32C15
2023-01-24T12:29:52.400Z DEBUG Timeout when waiting for attachment of device with serial number EAA9B4F32C15
2023-01-24T12:29:52.400Z DEBUG Device did not show up after 3 seconds
2023-01-24T12:30:55.292Z INFO Validating firmware for device with s/n EAA9B4F32C15
2023-01-24T12:30:55.299Z INFO PPK closed
2023-01-24T12:30:55.301Z DEBUG Device has DFU trigger interface, the device is in Application mode
2023-01-24T12:30:55.301Z DEBUG Will wait for device EAA9B4F32C15
2023-01-24T12:30:55.305Z INFO Opening device with s/n EAA9B4F32C15
2023-01-24T12:30:58.303Z DEBUG Timeout when waiting for attachment of device with serial number EAA9B4F32C15
2023-01-24T12:30:58.303Z DEBUG Device did not show up after 3 seconds

Your suggested solution fixed the situation for the nRF5340 DK, I can now use it

Unfortunately the PPK2 still hangs as before, so I have added it's log file as requested. (This is the log file of the PPK2 in Power Profiler.)

I am using a windows 11 machine. The USB cable isn't next to any device, the whole USB 3.0 hub is empty. I also tried a USB 3.0 port which is on the motherboard and a USB 2.0 port on the front of the PC but it made no difference. I tried a short and a long USB cable (which both worked on my laptop with the PPK2) and it also made no difference.

I was previously using WSL2 with usbipd, but because of the issues I switched back to basic windows 11. 

Thanks!

[Simonr]

Hi again

Glad we were able to partly solve the problem at least. From the log it just seems like the PPK2 isn't responding at all, and the connection times out when trying to open it. Is anything strange happening that you're able to observe when waiting for it to connect/open? What color is the PPK2 lighting up as for example? I'll ask the developers of the application if they've seen anything similar as well. I also tested on a Windows 11 (and Windows 10) machine for good measure, but they're both working as expected.

I'll let you know what the developers have to say about this!

Best regards,

Simon

[langestefann]

Nothing weird happens. The PPK2 continues blinking it's green LED, but it never turns blue. 

The PPK2 is recognized as normal btw:

Thanks again, I will await the response

[Simonr]

Hi Stefan

We're not able to reproduce this on our end, so can you try recovering your PPK2 as follows (even though it works as is on another computer I think it's worth the try):

• Disconnect all other nordic devices from the computer, turn off the kit and remove it from the plastic by removing the four screws.
• Insert USB to J2 (USB DATA/POWER).
• Short a connection between GND (e.g on the four pin power output header) to TP34 on the PPK2.
• While holding the jumper cable, turn the kit on and remove the jumper. Now the PPK2 should be in bootloader again.
• Open the PPK app, and select the device which is now just a serial number.
• When selecting it, the user will be prompted to program the application and it should now be working again.

Best regards,

Simon