Hi,
I'm working on getting the DFU bootloader working and I'm following this blog post.
- I'm successfully compiling and loading the bootloader to our custom hardware (we only have one dev-kit at the moment)
- nRF Connect (Mac + nRF52-DK) successfully discovers the device, as does LightBlue and nRF Connect on iPhone.
- Connection is initially started, but nRF Connect on Mac says it disconnects.
From the log:
Disconnected from device FD:60:D5:02:62:44, reason: BLE_HCI_CONNECTION_TIMEOUT
I'm trying to start a debug session with the bootloader, but haven't been successful yet. I can see that it starts though, and then enters app_sched_execute. (If I have deciphered the call stack correctly)
Using the same procedure (erase device, flash S132 3.0.0, flash bootloader, reset) but change hardware to the nRF52-DK I can successfully connect to the bootloader. I figured with no other application, the bootloader would always enter DFU mode?
What are likely sources for this behaviour?
Thanks in advance,
Edit: Got more from the stack trace. The bootloader is compiled with -O0 and the addresses in the linker script has been modified accordingly.
app_sched_queue_empty@0x0007b03a (Unknown Source:0)
app_sched_execute@0x0007b2a8 (/app_sched_execute.cdasm:52)
wait_for_event@0x00070164 (Unknown Source:0)
nrf_dfu_init@0x000701da (/nrf_dfu_init.cdasm:44)
nrf_bootloader_init@0x000709a6 (/nrf_bootloader_init.cdasm:7)
main@0x00074a10 (/main.cdasm:7)
