Programming custom board vs Arduino bluefeather nrf52852

RE: Programming custom board vs Arduino bluefeather nrf52852

Simonr — Fri, 07 Aug 2020 07:18:24 GMT

Okay, thank you for the update. We generally ship our chips from factories clean, but there might, of course, be discrepancies to this. In general, if you're not sure whether a device is ready to flash or not, you should erase its flash memory to make sure programming the chip will succeed.

In order to check whether the flash memory is empty or not, you can use the nRFConnect for Desktop Programmer application, where you'll get a detailed block diagram of the flash memory layout.

Best regards,

Simon

RE: Programming custom board vs Arduino bluefeather nrf52852

MCB — Thu, 06 Aug 2020 17:47:34 GMT

I am flashing my device by Jlink swio interface.

The reason that i confused , when i got my device from factory , i didnt erased it all and flashed it directly and it didnt work. I am not using dfu , but since p0.17 is blinking . I think there is some software loaded from factory.

RE: Programming custom board vs Arduino bluefeather nrf52852

Simonr — Mon, 03 Aug 2020 12:15:57 GMT

You should always do an "erase all" when flashing an application onto your nRF in order to make sure it is a "clean" device. Otherwise, you risk that the new firmware tries to overwrite the old one, which is likely what's causing this failure. Just to confirm. You are flashing your devices using DFU, correct? Is this DFU happening "over-the-air" (OTA) or over UART/something else?

Best regards,

Simon