Hi there,
I'm currently using SDK 17.1.0 with the NRF52832 Development Board. This is pretty new to me, but the examples helped me get an application going pretty quickly. I am now at the point where I'd like to start testing with a bootloader. I've built the micro-ecc library and generated keys. That seems to all be working fine. After programming the secure_bootloader/pca10040_s132_ble example, I try to use the nRF connect app and I don't see anything. I've confirmed there is a softdevice using the Programmer v3.0.0 tool. If I hold the IF BOOT/RESET button on power up, it pulls up the bootloader file system. I get stuck in this state and need to drop a working binary in for it to restart and launch said binary. However, if I program the ble_peripheral\ble_app_blinky example, I can use the nRF Blinky app and it seems to work just fine. I just started using the Nordic board a little over a week ago so forgive me if I'm missing something. I mainly have a couple of questions here:
1. How do I get the secure_bootloader/pca10040_s132_ble example working so I can perform DFU over BLE.
2. At minimum, I'd like to use the bootloader file system to drop my own binary image for booting. Does this need to be signed? I programmed the bootloader example with my own generated key, then reset with the button pressed and dropped this j-link-ob-sam3u128-v2-nordicsemi-170724.bin I found on the internet. It seemed to boot into the application without requiring a signature.
3. If my current application doesn't require BLE, but I plan to add it down the line, should I be using the softdevice and update app later to use the BLE stack or can I just merge the softdevice with my app later and load that?
Thank you,
Kenny
