OTA code killed custom 52840 boards

RE: OTA code killed custom 52840 boards

Menon — Sat, 14 Oct 2023 06:55:05 GMT

Hello,

[quote user="Avadacadabara"] Is there any chance that I could revive the dead chip with --recover?[/quote]

Yes, you could try nrfjprog --recover for recovering, and I don't recommend using nRFgo Studio for flashing the files (for nRF52840) as it is very old and is in a maintenance-only state.

Kind Regards,

Abhijith

RE: OTA code killed custom 52840 boards

Avadacadabara — Thu, 12 Oct 2023 07:00:38 GMT

Hi,

I think the custom board is OK since we've been developing with it for a long time and it works properly.

But the hex files are usaully flashed via nrfgo studio. OTA needs settings page and bootloader so I use command line tool for the first time...

My developement drivers are updated and I'll try it again. Is there any chance that I could revive the dead chip with --recover?

Thanks,

Ava

RE: OTA code killed custom 52840 boards

Menon — Wed, 11 Oct 2023 11:28:46 GMT

Hello,

Do any other samples from the SDK work with your custom board? I recommend programming any BLE sample and seeing if this is working or not (for testing). Thank you for sharing the versions of the tools you use. But I also recommend you update all these to the latest version available.

Have you done any hardware reviews here to make sure this is not a hardware-related issue?

Kind Regards,

Abhijith

RE: OTA code killed custom 52840 boards

Avadacadabara — Wed, 11 Oct 2023 06:39:45 GMT

I'm using SDK 16 ^_^

RE: OTA code killed custom 52840 boards

Avadacadabara — Wed, 11 Oct 2023 06:38:40 GMT

Dear Menon,

Sorry for late reply, I made a complete update on my developement environment recently, the previous version is listed below:

JLinkARM: V6.80a

nrfjprog: 10.9.0

Jlink debugger V8 (which been proved working not so well according to this thread)

Following is my implementation process:

1. generating settings.hex

nrfutil settings generate --family NRF52840 --application app.hex --application-version 1 --bootloader-version 1 --bl-settings-version 2 settings.hex

2. merge app/softdevice/bootloader/settings

mergehex --merge bootloader.hex settings.hex --output bl_temp.hex 

mergehex --merge bl_temp.hex app.hex s140_nrf52_7.0.1_softdevice.hex --output load_me_in.hex

3. downloading hex to board

nrfjprog --eraseall -f NRF52 
nrfjprog --program load_me_in.hex --verify -f NRF52 
nrfjprog --reset -f NRF52

I think the probem lies on Jlink debugger since I use the same command, same driver version, same hex files on both custom board and 52840 DK.

Thanks,

Ava

RE: OTA code killed custom 52840 boards

Menon — Wed, 20 Sep 2023 11:27:17 GMT

Hello,

Could you share some more details, like which nrfjprog command you have used here for flashing? Which SDK version are you using? Have you done a hardware review with us? Just to make it clear whether it's a hardware-related issue or not.

Kind Regards,

Abhijith