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.
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
We cannot explain this, do you have any ideas?