I am currently working on a custom product that uses module BMD-300 from u-blox, which has nrf52382 chip in it. My application works fine and now I want to integrate the Secure DFU function into it. I programmed the board with the DFU test image sd_s132_bootloader_buttonless_with_setting_page_dfu_secure_ble_debug_without_bonds.hex but I could not see it advertising when I scan for devices on nrf Connect. Does anyone know what problem could cause it to not advertising? I am using sdk v15.0.0.
Thank you in advance.
The BMD-300 lacks the 32768 Hz RTC (LFXO) quarz crystal that most Nordic examples require. You need to change the LF clock configuration in the source code and recompile - or populate the quarz circuit on XTAL1/XTAL2.
I tried your suggestion but the problem still exists. I followed the instruction on this link Add Nordic DFU to SDK Example from u-blox, and then changed the clock configuration afterward, but I still could not see it on the nRF Connect Scanner.
Now I think the custom board may behave different than the eval board, so I go straight into modify my firmware, which I know is working, and the scanner can see the device. After following the instruction on the link above, I can connect to it through nRF Connect and see the DFU service, but the device is frozen after a few seconds. Same thing happened when I use nRF Connect on Android. The nRF Connect on iOS, on the other hand, can connect to the device without any problem, but it doesn't see the DFU service.
I know these maybe 2 different problems, but I just want to put it here in case you (or anybody) know the answer for the problems.
The p_new_conn_params is:
When I connect with iPhone the send_update_request() is never called as it never reached my breakpoint there.
sd_ble_gap_conn_param_update() does not return as the hardfault is at 0x2dd76:
I want to clarify again that this has nothing with the bootloader project, the custom board only contains my own application and the soft device. The only file I change in SDK for my application project is the bsp.c in sdk\component subfolder.
Oh, I am sorry. I thought the HardFault was in when the bootloader was running, but I see, it is in the application. I didn't see the comment that you took out the bootloader.
Can you try to turn off optimization and check what function call that is the last one that is called? Are you sure sd_ble_gap_conn_param_update() is called? Because the address that it refers to looks like it is outside the softdevice. You are using s132v6.0.0, right? Can you confirm that sd_ble_gap_conn_param() is called? If not, what is the last call that is called before the hardfault?
I can't say that I have seen this message before:
"The processor has escalated a configurable-priority exception to HardFault. Exception occured at ..." Where does this message come from?
Are there any functions that returns something other than NRF_SUCCESS? Have you removed any of the APP_ERROR_CHECK(); calls that are softdevice related? Does the log say anything other that suggests that something is wrong? Can you send a copy of the log?
Is there any way for me to reproduce this?
Can I send you my project? I will take out everything except the BLE part. It's for module BMD-300 from u-blox, but I guess you can try it with any Nordic nrf52382 kit.
Sure. Make sure that it compiles in an unmodified SDK. Just zip the project folder (pca_10040_ble_debug).
Here is my project. I include the sdk and the softdevice for the sake of completeness. They are both unmodified though.
I got my hand on another Nordic DK so I can use a sniffer now. Here is the capture of it.Debug_sniffer.pcapng