• State Suggested Answer
  • Replies 15 replies
  • Answers 1 answer
  • Subscribers 70 subscribers
  • Views 2527 views
  • Users 0 members are here
Attachments (2) Download All
Nordic Case Info
  • Case ID: 301746
Options

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. 
  • 0 in reply to Simonr

    Hi, I was able to follow the steps and put the device into the correct mode (LED slowly flashing red). Unfortunately I am then unable to program the PPK2 on my windows PC. I get the following error:

    Failed to write to the target device: async task failure for id: 3579147264 msg: serialport could not be opened

    I then tried the same on my linux laptop, it programmed the board without any issues. I then reconnected the board to my windows pc, I get the same issues again.

    From the error it seems that something is blocking the COM port. I have also tried opening the COM port using a few other tools and all give more or less the same error message, so something is indeed blocking the COM port. I have no clue what it could be.

  • 0

    Hi

    With "other tools" I assume you're referring to other apps than nRF Connect for Desktop? I think it's related to something on your Windows 11 machine. A quick Google search led me to this Github issue which at first glance at least, seems similar, so why don't you give that thread a read? Other ideas that come to mind is that you're not allowed to use the COM ports for some reason due something like a third party anti virus program or insufficient admin rights.

    Other than that I'm afraid I don't have much more assistance to provide.

    Best regards,

    Simon

  • 0 in reply to Simonr

    Yes correct. I also believe it's something related to the windows 11 machine.

    About the error, it's a bit strange to me that the log file of power profiler shows the client times out while actually the underlying error seems to be an inaccessible COM port. I would expect a COM port error, and not a time out. That would have saved me some debugging and you some time helping because I would blame W11 shenanigans and not power profiler Slight smile

    Anyway I looked at your link and I tried a bunch of things, can't get it to work. I'll just use my trusty linux laptop for now and hope a next windows update fixes this...

    thanks!

  • 0 in reply to langestefann

    I'll update the internal ticket we have ongoing as well and I'll let you know if we find some way to reproduce this on our end or have any more suggestions you can try, but I can't guarantee anything. Glad you have a workaround with using your laptop instead.

    Best regards,

    Simon

Related