Error JLINKARM_DLL_ERROR when using Power Profiler

RE: Error JLINKARM_DLL_ERROR when using Power Profiler

Jim — Wed, 08 Mar 2017 09:58:50 GMT

This now works if you use the Nordic Development board NOT the Rigado BDM-300.

RE: Error JLINKARM_DLL_ERROR when using Power Profiler

wlgrd — Wed, 01 Mar 2017 09:45:09 GMT

Good to hear :)

RE: Error JLINKARM_DLL_ERROR when using Power Profiler

Ed Kuzemchak — Tue, 28 Feb 2017 21:55:36 GMT

Yes, I was trying to run the PPK board mounted on a BMD-300 DK, not the Nordic DK. I switched to running the PPK board standalone as described in Section 5.6 in the User Guide and that worked. And I just received the correct Nordic DK board, and the DK+PPK solution works as well. Thanks!

RE: Error JLINKARM_DLL_ERROR when using Power Profiler

wlgrd — Mon, 27 Feb 2017 11:43:02 GMT

Oh... Yeh, it only supports the original DK's. But you are saying "running on the dk". The PPK firmware should never run on the DK, but only be flashed to the PPK. If the software finds an RTT session on another board, it may hook onto it, but never give you any valid data. Please make absolutely sure that you are flashing the PPK. With a non-Nordic DK, I assume you have never had contact with the actual PPK.

RE: Error JLINKARM_DLL_ERROR when using Power Profiler

Ed Kuzemchak — Fri, 24 Feb 2017 16:54:16 GMT

Update - I am able to run the PPK board and the Power Profiler software if I run without the DK as described in Section 5.6 of the User Guide. That led me to realize my dev board isn't a Nordic DK, but rather a Rigado BMD-300 dev board for the nRF52. Soooo, I'm ordering the right Nordic DK board and I'm sure that will work great when it gets here - many thanks!

RE: Error JLINKARM_DLL_ERROR when using Power Profiler

Ed Kuzemchak — Fri, 24 Feb 2017 16:17:55 GMT

After trying 2 things, it appears more like the PPK firmware is not executing on the DK:

I cleared the Flash on the DK, and the above Python snipped behaves the same (is willing to rtt_start, but never finds a control block). So with no program on the DK, rtt_start() succeeds but no control block is ever found.
I added a simple SEGGER_RTT_printf() to Blinky, and the above Python program runs OK with that. I can print the result of the rtt_read to see my message

So, now, why would the PPK firmware not run on my DK? My DK is marked "BMD-300 Series Evaluation Board 320-00050 vB" My PPK board is "PCA63511 Rev 1.0.0 2016.27".

For the PPK firmware, I have tried loading it with "flash_ppy.py" and also loading ppk_v1_0_0.hex using nRFgo Studio.

RE: Error JLINKARM_DLL_ERROR when using Power Profiler

Ed Kuzemchak — Fri, 24 Feb 2017 15:30:49 GMT

Updated my question above. I tried spinning until rtt_is_control_block_found() is True and it is always False.

RE: Error JLINKARM_DLL_ERROR when using Power Profiler

Ed Kuzemchak — Fri, 24 Feb 2017 13:53:54 GMT

On a clean machine, I started over and made sure I used the versions specified in the PPK user guide:

Python 2.7.12 (32 bit Windows)
nRF5x Command Line Tools 9.0.0 (which installs Segger JLink 5.12g)

The Segger JLinkconfig.exe connects to the DK board OK.

I will try your suggestion above of spinning on rtt_is_control_block_found.

RE: Error JLINKARM_DLL_ERROR when using Power Profiler

wlgrd — Fri, 24 Feb 2017 13:09:52 GMT

This block has always worked for me

    self.nrfjprog.sys_reset()
    self.nrfjprog.go()
    self.nrfjprog.rtt_start()
    time.sleep(1)

    data = self.nrfjprog.rtt_read(0, 100, encoding=None)

But quite a few people have the ppk software and haven't stumbled into this issue, so it makes me wonder if you have an outdated or failing Segger Jlink installation(?).

RE: Error JLINKARM_DLL_ERROR when using Power Profiler

wlgrd — Fri, 24 Feb 2017 13:03:23 GMT

Try adding a import time at the top, and time.sleep(1) after nrfjprog.rtt_start(). I don't remember why but, but it usually fixes this issue (unless it was the -2, INVALID_OPERATION it fixed).

You can also try to spool on rtt_is_control_block_found before proceeding