• State Verified Answer
  • Replies 19 replies
  • Subscribers 74 subscribers
  • Views 5192 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 261409
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

NOT_AVAILABLE_BECAUSE_PROTECTION, jlink fails, nRF Connect for desktop fails

brec

I keep seeing NOT_AVAILABLE_BECAUSE_PROTECTION errors on all sub-programs of nRF Connect when attempting to program the associated firmware (RSSI viewer, Bluetooth Low Energy, Programmer, etc). J-Link command line keeps flagging the part as protected every time I connect to it:

nrfjprog gives:

C:\windows\system32>nrfjprog --family nrf52 --recover
Recovering device. This operation might take 30s.
ERROR: Recover failed. Please make sure that the correct device family is given
ERROR: and try again.

C:\windows\system32>nrfjprog -v
nrfjprog version: 10.12.1
JLinkARM.dll version: 6.90

I can only program the part through dropping a hex file on the JLINK drive or through nRF Connect SDK version of SES.

Part = nRF52840

nRF Connect for Desktop v3.6.1

How can I use any of the nRF Connect for Desktop apps?

Thanks,

Bob

Parents
  • 0

    Hi again Bob

    I'm very sorry about the generic "ask U-Blox" comment in my last reply. The fact that this is specific to the CKAA package chips, point towards that these are not added as compatible in nRFConnect for Desktop or nrfjprog for some reason. I have updated the internal ticket I have with the devs to check whether this is the case. 

    Unfortunately, I'm restricted to home office at the moment (COVID is on the uprise again here in Norway) so I don't have any CKAA packages available at the moment to test, but I'll ask my colleagues if they have any and can test this.

    Best regards,

    Simon

  • 0 in reply to Simonr

    Hi Simon,

    No worries -- I meant to put a smiley at the end of that sentence :-)  Even the helpers need help now and again.

    Thanks for updating your internal ticket. I'm headed to our lab today to pick up some supplies. I'll see if we have any boards with just the BMD-380 already mounted, and try them with an external SEGGER J-Link Base.

    Cheers,

    Bob

  • 0 in reply to brec

    Hi Simon,

    For the small board I was thinking of, we don't have any built up, just bare PCBs.

    One other point of reference -- on several attempts throughout the course of debugging this ticket, I pulled P0.18 high to ensure the module was not held in reset for some reason. VDD & VDDH measure approximately 3.1 V on the EVK due to the protection diode for multiple power sources and 3.3V on the small test board.

    I tried one more new EVAL board with only using nRF Connect BLE. When attempting to load the firmware, the debug IC re-enumerated on USB a couple times. After a few seconds wait, I see the same protection error.

    Cheers,

    Bob

Reply
  • 0 in reply to brec

    Hi Simon,

    For the small board I was thinking of, we don't have any built up, just bare PCBs.

    One other point of reference -- on several attempts throughout the course of debugging this ticket, I pulled P0.18 high to ensure the module was not held in reset for some reason. VDD & VDDH measure approximately 3.1 V on the EVK due to the protection diode for multiple power sources and 3.3V on the small test board.

    I tried one more new EVAL board with only using nRF Connect BLE. When attempting to load the firmware, the debug IC re-enumerated on USB a couple times. After a few seconds wait, I see the same protection error.

    Cheers,

    Bob

Children
No Data
Related
Terms of service