Re: issue with FCB reboot logs

Hi Chris, On 28 February 2017 at 16:59, Christopher Collins 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

Re: issue with FCB reboot logs

This comes up a lot Ive noticed, at least with nrf51. I was thinking that the bsp could expose an erase for newtmgr for the cases when it does On Tue, Feb 28, 2017 at 12:24 PM, marko kiiskila wrote: > > > On Feb 28, 2017, at 7:59 AM, Christopher Collins >

Re: issue with FCB reboot logs

> On Feb 28, 2017, at 7:59 AM, Christopher Collins 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

Re: issue with FCB reboot logs

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

issue with FCB reboot logs

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