This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

BLE Secure Bootloader works fine on Dev board, does not work on custom board

We have developed many solutions starting from example and modifying them to fit our needs, this one in particular has me stumped.  We already have working BLE and USB CDC ADM comms in our application, our bootloader though we originally released with just the USB DFU which works great.  I'm trying to add BLE DFU and for some reason I cannot get the BLE transport to be included and initiate when DFU mode is triggered.  I've resorted to going back to the basics and starting from an example and flash it to our board to attempt to get it working.

I'm compiling the examples/dfu/secure_bootloader/pca10056_s140_ble_debug/ operates great on the nRF52840-DK, but as soon as I flash the same thing to our custom board it will not activate the transport (NRF_DFU_EVT_TRANSPORT_ACTIVATED event is never firing) but I am receiving the event of NRF_DFU_EVT_DFU_INITIALIZED.  How is changing the board causing the transport to not be included and not fire on the exact same binary/hex?  I've even gone as far as reading the DK board and then flashing the custom board with the read and it does not initiate the BLE transport.

Our custom board is pretty much a copy of pca10056 with the LED's moved around and less buttons, utilizing SDK 16.0.0.

EDIT: and just to follow up I'm ensuring the softdevice is on the board before doing any of this testing, as I stated earlier our main app utilizes normal BLE comms without issue.

Related