NRF52832 Booloader Problem

RE: NRF52832 Booloader Problem

Simonr — Fri, 29 Nov 2019 10:30:33 GMT

It seems like the BUTTON_PULL call isn't defined in SDK 13. Please try defining it as NRF_GPIO_PIN_PULLUP and see if that helps. It seems like a bug in that particular SDK version as it is fixed in newer versions.

Best regards,

Simon

RE: NRF52832 Booloader Problem

cool__looc — Thu, 28 Nov 2019 07:08:47 GMT

Hi Simon,

Thanks for your reply. It turns out after flash the bootloader to the device then the nRst pin is low. After pull-up this pin the device can access again. But what could be the reason for this? I assume the bootloader will not configure this pin, is that right?

Thanks,

RE: NRF52832 Booloader Problem

Simonr — Wed, 27 Nov 2019 13:44:27 GMT

First off, your schematics look good, so I think it's safe to say that this isn't a hardware issue. Can you show me the procedure of how you're flashing the bootloader onto your device? It might be that the device goes straight to bootloader mode when you flash it onto the chip. In that case, it should be advertising over BLE with the device name DfuTarg. Can you check if you're able to find it advertising? When the bootloader starts it will determine if it has a valid app based on the state of the settings page and a CRC check verifying the integrity of the application, so you'll need to perform a DFU to get the app into the system.

Best regards,

Simon