Issue with Softdevice in nRF52832 QFAA E1 series chips.

[Xeon]

Greetings,

I am using nRF52832 QFAA E0 in my development stages and found no issues regarding the architecture I have been using. 

Architecture:

DFU is built separately with SDK 15.0.0 and S132 Softdevice. 

Application is built separately with SDK 15.0.0, MBED OS 5.18. 

I have used nrfUtil to fuse the bootloader and the softdevice which is used while creating the DFU package. 

Resources
https://devzone.nordicsemi.com/nordic/short-range-guides/b/software-development-kit/posts/getting-started-with-nordics-secure-dfu-bootloader
https://github.com/aninda-ghosh/nRF52-Series-DFU

Till the point I was using nRF52832 QFAA E0/B0 series chip DFU was completely fine and I could scan and push the dfu file from nRF connect but after Changing the chip revision to nRF52832QFAA E1. I can't find the device in nRFconnect anymore. (Note: using a custom board).  The application code work as expected only the DFU firmware is showing this weird issue. 

Need some guidance in fault finding. Please let me know if any additional information is needed.

I am new to the forum, advanced apologies for any relevant concerns. 

[Amanda Hsieh]

Hi,

after Changing the chip revision to nRF52832QFAA E1. I can't find the device in nRFconnect anymore.

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?

 

The application code work as expected only the DFU firmware is showing this weird issue. 

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

[Xeon]

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

[Xeon]

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