RE: Fstorage - fs_erase causes connection failure

Petter Myhre — Mon, 25 Sep 2017 12:45:11 GMT

I see :) Thanks for the update!

RE: Fstorage - fs_erase causes connection failure

John — Mon, 25 Sep 2017 12:17:18 GMT

Hi Petter,

Yep, I was sure that I was not getting a reset. The board kept executing normally as my CLI did not show a reset and that's pretty obvious since the welcome banner prints and you get a prompt of "00:00:00>".

That said, I worked with this over the weekend. I was forced to conclude on Saturday after trying many things that perhaps the connection interval timings were too tight. So on Sunday I loosened them up and that forced a connection parameters negotiation near the start of the connection. Once the negotiation completed, I observed a similar behavior. No response to connection events until after the connection supervisor popped.

This of course was a bit puzzling because I've seen plenty of successful parameter negotiations with this software, and never seen this before. Plus these were very vanilla connection settings. This got me to be very suspicious of the development board I was trying to bring up. So, it was off to the lab and the magnifiers. It became pretty clear quickly what was likely wrong. The entire top of the 32KHz Oscillator was missing! No idea why, perhaps some crazy experiment by the HW guys, who knows. Replaced with another development board, and the connection settings did seem to fix the flash erase problem. Further experimentation with the parameters will go on this week to make sure that with the original connection settings that we aren't on the edge of having flash operations issue. I know you guys have a table about that in the manual, but I'll be a lot more comfortable after some testing to go with that.

RE: Fstorage - fs_erase causes connection failure

Petter Myhre — Mon, 25 Sep 2017 09:00:56 GMT

Very strange indeed. Are you sure you are not calling APP_ERROR_CHECK() with an error code somewhere and you get a reset? What happens after you get NRF_EVT_FLASH_OPERATION_SUCCESS? Are you getting further in your program?