Hi Chris, On 28 February 2017 at 16:59, Christopher Collins <[email protected]> wrote: > Hi Szymon, > > On Tue, Feb 28, 2017 at 03:51:51PM +0100, Szymon Janc wrote: >> Hi, >> >> I noticed that some applications (eg bleprhp) enable FCB logging in >> syscfg.yml by default. >> When flashing such sample on nRF52DK I get assertion [1] before even >> main() is reached. >> And if I reset a board I get loop of assert and unhandled interrupt >> exception [2]. >> >> Disabling FCB makes sample works fine. Do I need to do any magic to >> get it working >> with FCB enabled? > > My guess is that there is something else written to the reboot log area. > I believe the reboot log package asserts that it initializes > successfully. Do you know what code is at the indicated address > (0x1a393)? > > This would be the case if it has been a long time since you erased your > device's flash. The flash map changed in an non-backwards-compatible > way between 0.9.0 and 1.0.0-b1.
Yes, that was this. Although it wasn't due to 0.9.0->1.0.0 but rather flashing Zephyr. Doing 'nrfjprog --eraseall -f nrf52 before flashing Mynewt did the trick. That said, I find asserting and leaving system in unbootable state a bit odd. -- pozdrawiam Szymon K. Janc
