S130 v1.0 assert encountered: rem.c line 1376

RE: S130 v1.0 assert encountered: rem.c line 1376

Hung Bui — Fri, 15 Apr 2016 12:16:23 GMT

Hi Roberto, Could you read the laser mark on top of the chip (will be QFAA-XX not QFAA-R7) , just want to check if the chip revision support S130 v1.0.0.

If you only test with the stock example with no modification do you have the same issue ? Could you provide us the project so we can test here ?

I assume that this only occurs when the peripheral got connected and exchange the battery level by a read from the central or notification ?

RE: S130 v1.0 assert encountered: rem.c line 1376

Roberto Saltini — Thu, 14 Apr 2016 23:52:35 GMT

Hi Hang,

I have tried your suggestions to use NRF_CLOCK_LFCLKSRC_RC_250_PPM_4000MS_CALIBRATION and verify that all of the code regarding hrs is commented out, but I continue to get the same assert.

RE: S130 v1.0 assert encountered: rem.c line 1376

Hung Bui — Thu, 14 Apr 2016 11:22:07 GMT

Hi Roberto,

The error line telling that there is some issue with the timer used by the softdevice. I'm not sure why that happened, but could be because of the clock source you used. NRF_CLOCK_LFCLKSRC_SYNTH_250_PPM is not supported by the softdevice. You should use NRF_CLOCK_LFCLKSRC_RC_250_PPM_4000MS_CALIBRATION instead if you don't have external 32kHz crystal.

Also 0xFF00 is not a 16 bits UUID defined by Bluetooth sig, it's not a good idea to use. Have you made sure you removed all the code related to hrs client ? (because you removed hrs_c_init();)