nRF Connect for Mac (3.3.0) Failure

[jcvandegrift]

My target platform is nRF5_SDK_14.2.0_17b948a but I suspect that nRF Connect has independent bin/hex files with which to program the nRF52.

I was trying to get the PPK working with nRF52 DK (all three switches = DK) after a few months of non-use (so it used to work). When that failed I decided to just try to work with the DK...

No application in nRF Connect modifies the FW on my nRF52 DK board, that board just keeps doing the blinky example that I'd previously programmed, I was expecting nRF Connect to recognize the FW doesn't match my request, ask my permission to overwrite it, and then program it. However it appears that Connect thinks that the FW is already loaded. But I still see blinky's LEDs doing their non-RSSI (for example) thing.

Here's the log incorrectly validating the programmed firmware:

2019-12-13T18:32:01.032Z INFO Validating firmware for device with s/n 000682513086
2019-12-13T18:32:01.039Z INFO Opening device with s/n 000682513086
2019-12-13T18:32:01.045Z INFO Serial port is closed
2019-12-13T18:32:01.066Z INFO /dev/tty.usbmodem0006825130861 is open

I'll try this on a Win10 desktop this weekend but the Mac is my only portable and at work platform.

[jcvandegrift]

I have two DK's:

• Cut SB9 which is paired with the PPK, and
• Intact SB9 which I'm using standalone

Both DKs work fine with several of the examples using make erase, make flash_softdevice, make flash sequence.

[Vidar Berg]

Hi, I haven't looked at the implementation of the FW validation mechanism, so not sure what parameters it uses for validation, but have experienced false positives as you described here. Could you try to erase the chip first before you open the Bluetooth Low Energy app and see if you get the same result?