nRF Connect Desktop Programmer fails on Mac (Catalina)

[Robert Colvin]

Hi 

I am experiencing an issue with nRF Connect Desktop Programmer failing on Mac OS Catalina.

I am attempting to program a Thingy:91 via nRF Connect Desktop Programmer (v 3.6.1) - loading the HEX file works and the programming begins, 99% of the time it gets to 10-11% before failing with just a white screen; I can cmd+r to refresh and get the main interface back, but generally I need to close nRF Connect Desktop before I can try flashing again. 

maybe 0.9% of the time, it gets to about 80% before crashing; once in a few hundred attempts has it succeeded - I have screen casts of all three.

Reviewing the developer logs shows no issues at all, no warnings or errors. I have tried multiple USB cables (which are known good quality) to no avail; 

I am able to program the thingy on my Mac via west with a nRF9160 DK, via the same USB ports. Leading me to believe it's an issue with nRF Connect Desktop

Flashing the exact same HEX file on the exact same Thingy using Windows 10 works with no issues.

The Mac is a 2012 Mac Mini; quad core i7 2.3GHz, with 16GB RAM and SSDs, running Catalina 10.15.7 - though I have spoken to a colleague who experienced the same issue on a 2020 Mac Book Pro.

There is a previous ticket (now closed) with the exact same issue - devzone.nordicsemi.com/.../on-mac-os-x-programmer-1-1-0-nrf-connect-for-desktop-2-7-0-crashed

[Robert Colvin]

updating the ticket, as this issue is still apparent on my 2020 MacBook Pro running Monterey and nRF Connect for Desktop v3.9.0 and Programmer v2.0.0

[Joakim Jakobsen]

Hi again.

Sorry there haven't been any update on this.

I'll talk to our developers and ask what the status is.

Sorry about the inconvenience.

Br,
Joakim

[Joakim Jakobsen]

Hi again.

I've been talking to our developers and we can't actually reproduce this issue.

Could you provide detailed steps on how you reproduce this. What HEX-file are you using etc.

Thanks,
Joakim

[Robert Colvin]

Hi!

1. nRF Connect for Desktop, v3.9.1

2. Programmer v2.0.0

3. MacBook Pro (13", 2020, 2GHz Quad-Core Intel Core i5; 16GB 3733 MHz LPDDR4X), Monterey v 12.0.1

4. Thingy:91 1.0.0

5. Hex File: thingy91_at_client_2021-10-20_d29f1dde.hex extracted from thingy91_fw_2021-10-20_d29f1dde

6. Connect Thingy -> MacBook (good quality USB cable)

7. MCU Boot mode

8. Select Device (Thingy:91 UART - PCA20035:x79dc6119413)

8. Add Hex File

9. Write

10. MCUBoot DFU Screen -> "You are now programming via MCUboot...." -> click "Write"

- starting to erase image on device. this will take some time

- uploading image to device

- 28% entire Programmer window goes white

 11. CMD+R to reload, nRF Connect Crashes (this is a new bug!)

Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [19314]

(full crash log available)

11. reopen nRF Desktop and Update Programmer to 2.0.1

12. reload same HEX and try to program

completed successfully!

Try Again to be sure :)

completed successfully

it appears that 2.0.1 has fixed the issue; as initially reported this was confirmed on my 2012 Mac Mini on Catalina and then on my 2020 MacBook Pro on Big Sur and then also Monterey.

my Mac Mini is in the same state as when I had the issue if need be; however maybe if it's fixed and im the only one reporting the issue... 

[Joakim Jakobsen]

Thanks for the detailed explanation.

I'm glad to hear that upgrading to v.2.0.1 fixed the issue. If you encounter any other issues, please let me know. 

I will forward this to our developers, with a note that the issue is resolved by upgrading to v.2.0.1.

Thanks, 
Joakim