Power Profiler Kit Error - Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a)

RE: Power Profiler Kit Error - Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a)

Simonr — Thu, 22 Aug 2019 06:52:31 GMT

Hi Shodney

The set up you're using now should be the best way to measure current using the PPK, since you won't experience any leak current what so ever from the DK to the PPK. However, at the moment I've had a similar setup running for 22 minutes, and not experienced a single corrupt data error. Either your USB that's powering the PPK or the 10-pin cable is experiencing some disconnection issues it seems. If possible you should try with another USB cable and/or another debug cable to see if this issue still occurs.

Best regards,

Simon

RE: Power Profiler Kit Error - Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a)

Shodney — Wed, 21 Aug 2019 17:13:02 GMT

Hi Simon,

Sorry for the delay in getting back to you.

I've just tried with a 10 pin cable and that seems to connect with no errors, but how do I measure the DK current by connecting it in this way?

I can set it up to measure an external device by connecting debug out on DK to debug in on PPK, DUT select set to external, power set to USB reg, and COM switch set to EXT, - essentially the same set up as https://infocenter.nordicsemi.com/topic/ug_ppk/UG/ppk/PPK_user_guide_PPK_on_customHW_standalone.html - but with the DK as the J-Link.

This seems to work for the most part but i'm then getting an error "Corrupt data detected, please check connection to PPK." every 5 minutes or so and have to reconnect a few times to get it to kick back in.

Thanks.

RE: Power Profiler Kit Error - Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a)

Simonr — Wed, 14 Aug 2019 05:45:30 GMT

Hi Shodney

Do you have a 10-pin debugger cable? Could you try connecting one to the debug out on the DK and debug in on the PPK to see if that makes a difference? There have been issues in the past where the other header pins from the nRF52840DK have been interfering with the PPK. What are you using as a power source? Can you tell me what positions the switches on the PPK is set to?

Best regards,

Simon

RE: Power Profiler Kit Error - Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a)

Florian Zierer — Wed, 14 Aug 2019 05:12:03 GMT

I still see the error from time to time.

I realized, that there are some issues if you are running two or more dev kits on the same computer. E.g one for the ppk and another for debugging your firmware.

The ppk uses RTT for data transmission, so check if there are some conflicts.

RE: Power Profiler Kit Error - Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a)

Shodney — Tue, 13 Aug 2019 15:31:55 GMT

Hi,

I've tried that, but no difference I'm afraid. Thanks though.

Also tried plugging into different USB sockets but still the same error.

RE: Power Profiler Kit Error - Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a)

Florian Zierer — Mon, 12 Aug 2019 05:09:43 GMT

I have/had the same problem. In another thread someone suggested to change the USB cable and I think it helped also in my case.

Would be cheaper than buying another DK :-)

RE: Power Profiler Kit Error - Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a)

Shodney — Sat, 10 Aug 2019 17:34:24 GMT

Thanks for getting back to me.

I was initially running custom code, but I've ran the recover command and getting the same error with just the blinky example from the SDK. I'm getting the error even with no code on the DK at all, straight after a recover command.

I don't have another DK unfortunately - I did consider buying one to test, but didn't really want to drop £40 on another one if I was missing something obvious and can make this one work!

RE: Power Profiler Kit Error - Lowlevel error: JLINKARM_DLL_ERROR (ffffff9a)

Simonr — Thu, 08 Aug 2019 10:54:53 GMT

First of all, could you try downloading and installing the nRF Command Line Tools, and try running the nrfjprog --recover command to recover your DK, to see if that changes anything. What code is your DK flashed with when you're trying this. Does the same behavior occur if you use one of our SDK examples? Do you have any other DKs to try it with to see if it is the one DK that is the problem?

Best regards,

Simon