J-Link issue with nRF21540-DK

RE: J-Link issue with nRF21540-DK

pixbroker — Tue, 19 Mar 2024 15:24:36 GMT

Ok, my nRF21540DK now works on macOS. Im not sure what happened to my windows machine, but after the downgrade it is no longer recognizing the DK at all :) but it works now on macOS and the constant eject message is also gone.

Thanks for the help everyone.

Just to clarify, the following JLink OB FW works:

Firmware: J-Link OB-nRF5340-NordicSemi compiled Nov 7 2022 16:22:01

RE: J-Link issue with nRF21540-DK

pixbroker — Tue, 19 Mar 2024 14:37:30 GMT

Thank you koos

I can't find 7.88j on the Segger download page. The last of the 7.88 versions was "n" and i tried that and my nRF21540DK still does not show up properly in VSCode. (I did this on Windows btw). Where did you get 88j from?

FWIW, the Segger Release notes do mention some change to the macOS "System Tray" (i guess they mean Finder) in version 88h.

I downgraded my nRF Command Line Tools to 10.23.5.

RE: J-Link issue with nRF21540-DK

koos — Tue, 19 Mar 2024 13:11:56 GMT

I think I'm encountering the same issue.

I connected an nRF52DK (which was working fine on my 2019 Intel Macbook) to my new Macbook Pro M3 and continuously got notifications about "Disk Not Ejected Properly", and the DK was unusable.
So I guess it has to do with the combination of the Apple M3 and Oct 30 2023 J-Link firmware. Other boards with an older J-Link version, and a regular J-Link device have no issues.

As an intermediate solution you could try to remove Segger J-Link 7.94e and downgrade nRF Command Line Tools to 10.23.5 (I was using the latest 10.24.0).
Then open JLinkConfig (note that it should now be J-Link version 7.88j when using nRF Command Line Tools 10.23.5), right-click on the listed device, and click "Replace firmware".
Following these steps I got it to work again.

RE: J-Link issue with nRF21540-DK

PaKa — Tue, 19 Mar 2024 09:14:32 GMT

The BIN file is for the older NXP based OBD (JLINKs) so won't work with your board. The new boards don't have the push button to DFU solution, they only update from the SEGGER tools. Can you test the board on a Windows computer and see it it pops up there as normal and updat the code there? The SW version you have should be the latest for that board.