Issue with Softdevice in nRF52832 QFAA E1 series chips.

RE: Issue with Softdevice in nRF52832 QFAA E1 series chips.

Xeon — Thu, 30 Sep 2021 14:40:33 GMT

Hi Amanda,

https://github.com/aninda-ghosh/nRF52-Series-DFU
Here I have showcased the memory stack being used for the nRF.

DFU firmware works independent of the Application firmware. I am utilising the

NRF_POWER->GPREGRET = BOOTLOADER_DFU_START;

For forcing the boot loader to start in the next reboot.

Regards,

Aninda

RE: Issue with Softdevice in nRF52832 QFAA E1 series chips.

Xeon — Thu, 30 Sep 2021 14:35:12 GMT

Hi,

Just wanted to update. it was a very silly bug in the hardware. Generally the DFU example in SDK 15 incorporates BSP leds to show statuses and the exact pin was connected to a transistor which in turn is used to reset the device. Hence the device was continuously restarting while in DFU mode.

Anyway thanks for the reply.

Regards,

Aninda

RE: Issue with Softdevice in nRF52832 QFAA E1 series chips.

Amanda Hsieh — Wed, 29 Sep 2021 12:49:22 GMT

Hi,

[quote user=""]after Changing the chip revision to nRF52832QFAA E1. I can't find the device in nRFconnect anymore. [/quote]

Not pretty sure the situation. Can the device be scanned by nRF Connect before DFU updating?

Did you try SDK example? Can it make the device be scanned by nRF Connect?

What did you do then the device cannot be scanned by nRF Connect?

What image did you flash to the image?

[quote user=""]The application code work as expected only the DFU firmware is showing this weird issue. [/quote]

What do you mean "the DFU firmware is showing"? Is it the device get into DFU mode and update application, then the application can work as expect?
Not sure what is your application. If it's like Buttonless DFU Template Application, it would need bootloader to work.

Regards,
Amanda