We had an issue with the FDS such that if the device lost power in the ~50ms window after bonding was carried out, the FDS would take longer to initialise when power was restored due to incomplete/erroneous data, this is perfectly understandable.
What is puzzling is that when you reboot the bootloader fails to see the application for a few attempts, and then suddenly it sees it and is happy to boot correctly.
0.175 <info> app: Inside main (gateway wireless bl653 bootloader)
0.176 <info> app: Bootloader Version: 2
0.178 <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
0.179 <info> app: No firmware to activate.
0.708 <warning> nrf_dfu_settings: No additional data erased
0.709 <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
5.716 ÿ<info> app: Inside main (gateway wireless bl653 bootloader)
5.719 <info> app: Bootloader Version: 2
5.720 <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
5.723 <info> app: No firmware to activate.
6.253 <warning> nrf_dfu_settings: No additional data erased
6.255 <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
11.262 ÿ<info> app: Inside main (gateway wireless bl653 bootloader)
11.265 <info> app: Bootloader Version: 2
11.266 <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
11.268 <info> app: No firmware to activate.
11.799 <warning> nrf_dfu_settings: No additional data erased
11.800 <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
12.189 <info> app: Starting application.
12.190 <info> app: Reset Status 00000002
12.190 <info> app: dbDiscoveryInit
12.191 <info> app: bleStackInit start
12.192 <info> app: Configuring BLE stack.
The number on the left is a timestamp (ms since power on) - we have a relay in series such that we can cut the power easily in the 50ms window (trigger on peer event debug) to make it fail 100% of the time and also put a timestamp in the debug data as above.
This is normal startup when we have not cut the power in a FDS operation
The number on the left is a timestamp (ms since power on) - we have a relay in series such that we can cut the power easily in the 50ms window (trigger on peer event debug) to make it fail 100% of the time and also put a timestamp in the debug data as above.
This is normal startup when we have not cut the power in a FDS operation
0.156 <info> app: Inside main (gateway wireless bl653 bootloader)
0.157 <info> app: Bootloader Version: 2
0.159 <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
0.160 <info> app: No firmware to activate.
0.690 <warning> nrf_dfu_settings: No additional data erased
0.692 <info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
1.168 <info> app: Starting application.
1.169 <info> app: Reset Status 00000001
1.170 <info> app: dbDiscoveryInit
We cannot explain this, do you have any ideas?
We cannot explain this, do you have any ideas?
