This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Cannot use Power Profiler Kit with nRF52 DK and nRF Connect Desktop on Mac or Linux

Hi, I need to do some power analysis of an application I am working on. I have a Power Profiler Kit, but it will not work with nRF Connect currently.

I have two machines, both with nRF Connect installed - a Mac and a Manjaro Linux PC. On Mac, I get the error "Error when validating firmware: Error occured when read. Errorcode: CouldNotOpenDLL (0x7) Lowlevel error: INVALID_OPERATION" and the Log reads "Failed to read PPK metadata" and "Failed to start the PPK". On Manjaro, I get "Error while probing devices: Error occured when get serial numbers. Errorcode: CouldNotOpenDLL (0x7) Lowlevel error: JLINKARM_DLL_NOT_FOUND (ffffff9c)".

I would really like a solution for either my Mac or Manjaro Linux PC, does not matter which one. My MAC can run the RSSI Viewer just fine, but Manjaro gives the same error when attempting to use the RSSI Viewer. I have nRF Connect V2.6.2 on Mac and V3.2.0 on Manjaro. I've disconnected SB9 on the DK and have not altered it in any way. On Manjaro, I've downloaded V6.22 of JLink software and documentation, but currently just have the folder containing binaries in my Downloads folder. Should I move these somewhere else, like into the Segger folder? Not really sure what to do, have spent several hours looking for a solution online with no luck.

Parents
  • Here is the log report on Manjaro:

    2019-11-15T03:07:18.022Z INFO Application data folder: /home/noah/.config/nrfconnect/pc-nrfconnect-ppk
    2019-11-15T03:07:18.025Z INFO App initialized
    2019-11-15T03:07:18.121Z DEBUG App pc-nrfconnect-ppk v2.2.0 official
    2019-11-15T03:07:18.121Z DEBUG App path: /home/noah/.nrfconnect-apps/node_modules/pc-nrfconnect-ppk
    2019-11-15T03:07:18.121Z DEBUG nRFConnect 3.2.0 is supported by the app (^3.0.0)
    2019-11-15T03:07:18.122Z DEBUG nRFConnect path: /tmp/.mount_nrfcon2wGt7e/resources/app.asar
    2019-11-15T03:07:18.122Z DEBUG HomeDir: /home/noah
    2019-11-15T03:07:18.122Z DEBUG TmpDir: /tmp
    2019-11-15T03:07:18.163Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS0
    2019-11-15T03:07:18.163Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS1
    2019-11-15T03:07:18.163Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS2
    2019-11-15T03:07:18.163Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS3
    2019-11-15T03:07:18.163Z ERROR Error while probing devices: Error occured when get serial numbers. Errorcode: CouldNotOpenDLL (0x7)
    Lowlevel error: JLINKARM_DLL_NOT_FOUND (ffffff9c)

    2019-11-15T03:16:29.480Z INFO Validating firmware for device with s/n 000682383579
    2019-11-15T03:16:29.483Z INFO PPK closed
    2019-11-15T03:16:29.489Z INFO Opening device with s/n 000682383579
    2019-11-15T03:16:29.491Z INFO PPK opened
    2019-11-15T03:16:29.505Z INFO PPK started
    2019-11-15T03:16:40.200Z INFO Generating system report...
    2019-11-15T03:16:40.575Z INFO System report: /home/noah/.config/nrfconnect/pc-nrfconnect-ppk/nrfconnect-system-report-2019-11-15T03-16-40.200Z.txt

    I already placed the Linux udev rules in the appropriate place as well, but maybe there is still something strange going on? This morning when I connect the PPK, I get the same error but am able to start the power profiler. However, nothing appears on the screen, it just runs but nothing shows up on either graph. I imagine this error needs to be solved before anything works. I will install most recent command line tools as well as update nRF Connect and let you know how it goes.

  • None of the listed serial ports are what I'm connecting to, my DK/PPK show up on /dev/tty/ACM1

Reply Children
Related