Can't flash NRF52810 using last version of Zephyr SDK

RE: Can't flash NRF52810 using last version of Zephyr SDK

Radical Redemption — Wed, 16 Aug 2023 14:22:33 GMT

I believe the issue is that the J-Link I have does not have a valid VTref pin, but instead it has a 3v3 supply voltage on that pin, it is not an input, so the J-Link is not properly detecting the correct logic level from the board.

RE: Can't flash NRF52810 using last version of Zephyr SDK

Einar Thorsrud — Wed, 16 Aug 2023 13:58:18 GMT

I see. I am not able to explain that explicitly, but generally, if you have logic levels on 1.8V in one end and 3.3 V in the other end, it is not unexpected that you could get data corruption (and other issues as the absolute maximum GPIO voltage is VDD + 0.3V).

(Is the corruption always on the same word 0x000002E5, or also elsewhere? If you dump the memory perhaps you would see more issues as well, as validation stops at the first mismatch?)

RE: Can't flash NRF52810 using last version of Zephyr SDK

Radical Redemption — Wed, 16 Aug 2023 13:20:48 GMT

But it worked on another PC with older SDK version.

RE: Can't flash NRF52810 using last version of Zephyr SDK

Einar Thorsrud — Wed, 16 Aug 2023 13:18:51 GMT

I see, that makes sense. Thanks for letting us know!

RE: Can't flash NRF52810 using last version of Zephyr SDK

Radical Redemption — Wed, 16 Aug 2023 12:56:05 GMT

I kind of figured out what the problem is. The board operates at 1.8V and the J-Link I have does not behave properly on that voltage level. I flashed another board that operates at 3.3V and everything went well.

RE: Can't flash NRF52810 using last version of Zephyr SDK

Einar Thorsrud — Wed, 16 Aug 2023 12:20:36 GMT

Hi,

That seems odd. There is one bit flipped 0x000002E5 should be 0xF0 when reading it back but is 0xE0. Do you have another nRF52810 device you can test with to see if it behaves the same if you program it with the exact same tools (same computer etc) and the exact same hex files?

Also, on the failing device, if you first do a nrfjprog --recover and then read back using nrfjprog --memrd 0x000002E4, what do you read then?