File transfer to JLINK DK52 MacOS error

[billsalt]

I'm having an issue that (I think) is related to MacOS Ventura upgrade.  I'm trying to update the firmware on a DK52 Development board by copying the .hex file into the JLINK drive.

I get an error "The operation can't be completed because an unexpected error occurred (error code 100093)", and the update does not occur.

Any clues?  Is this a permissions thing or??  I think it worked fine before the Ventura upgrade.  And it works fine (same board, same hex) with my Win11 system.

Thanks!

[Kenneth]

Hello,

There should be no need to manually update the firmware, the j-link will automatically do this for you if it detect old firmware. If you want you can use the j-link configurator to control&check the firmware used:
https://wiki.segger.com/J-Link_Configurator 

Btw, the latest nRF Command line tools can be downloaded from:
https://www.nordicsemi.com/Products/Development-tools/nrf-command-line-tools/download

In the above I assumed you wanted to update the interface MCU that is used to program/debug the target nRF52 on the DK. If you are trying to program the nRF52, then you should check out the devAcademy on how to:
https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/ 

For instance does programming through nrfjprog and west work? Just want to understand if it's only the drag and drop that seems to fails or not.

Kenneth

[billsalt]

I have installed the latest Segger tools for MacOS M1 and they did not help.  I haven't installed the nRF tools yet and should not need to do so for this basic operation, should I?

I have created a support ticket with Segger as well.

[Kenneth]

I can report this internally, but can you confirm that the normal development using nrfjprog and west (either from command line or using flash through VS code) works?

Kenneth

[billsalt]

Sorry Kenneth, I'm not trying to be difficult, but I'm also not going to waste the time fighting NCS toolset since they are not yet supported on the M1 Mac by Nordic; confirmed through my Case ID 287961.  That's one reason I was trying to use the JLINK drag/drop.

Bill

[mytzyiay]

On my M1 Max I have been using CLI nrfjprog with no major issues for several months.  I haven't tried the drag/drop -- partly because I want to control exactly which operations are performed on the target, and partly because I don't really trust the emulated HDD translation layers.

[billsalt]

I've received feedback from my case logged at Segger -- they acknowledge the issue and will be releasing a fix in the next week.  I'm frankly surprised Nordic isn't aware of this because most of their DK products are affected (if not all), but to get us all in the loop:

Hello Bill,

Thank you for your inquiry.

We have fixed this issue internally already for several J-Link OB models.

With the next version of the J-Link software package, planned to be released this week,

an update for the firmware of the J-Link OB models listed below is available and after applying that update,

drag and drop programming will work on macOS Ventura.

Could you please do the following?

1. Download and install the most recent version of the J-Link software
2. Start J-Link Commander (JLinkExe)
3. Make sure it is connected to your J-Link OB
4. Provide a screenshot of the J-Link Commander output
5. That way I can double-check that the J-Link OB model you are using will be fixed with the aforementioned version

Fixed J-Link OB firmwares:

• J-Link-OB-K22-CortexA
• J-Link-OB-K22-CortexM
• J-Link-OB-K22-RISCV
• J-Link-OB-K22-NordicSemi
• J-Link-OB-K22-Qorvo
• J-Link-OB-K22-SiFive
• J-Link-OB-SAM3U128-V2-NordicSemi
• J-Link-OB-nRF5340-NordicSemi