FDS not working after SD initialize

[Maidu]

HI, I have nrf52832 and I am using latest SDK 14.2.0. 

I am using FDS and the problem is that before setting up BLE fds_record_write works fine but after setting up BLE all data using fds_record_write goes to dirty records. My ble part is just simple central what scanns advertisements and creates connectioin. Here is my main code.

ret_code_t ret;

ret = NRF_LOG_INIT(NULL);
APP_ERROR_CHECK(ret);

NRF_LOG_DEFAULT_BACKENDS_INIT();

ret = app_timer_init();
APP_ERROR_CHECK(ret);

NRF_LOG_INFO("RUN\r\n");

//INIT FLASH
fds_register(fds_evt_handler);

NRF_LOG_INFO("Initializing fds...");

ret = fds_init();
APP_ERROR_CHECK(ret);

wait_for_fds_ready();

fds_stat_t stat = {0};

ret = fds_stat(&stat);
APP_ERROR_CHECK(ret);

NRF_LOG_INFO("Found %d valid records.", stat.valid_records);
NRF_LOG_INFO("Found %d dirty records (ready to be garbage collected).", stat.dirty_records);

fds_gc();

//When I call here fds_record_write it works fine

ble_init();

//When I call here fds_record_write it goes to dirty records

[Edvin]

Do you check all the returns from the FDS functions?

Attached is an example using the FDS from the ble_app_uart example. Check the UART log to see if it works. At least from here, I can start the FDS module after ble_stack_init();

 

ble_app_uart_FDS.zip

 

Best regards,

Edvin

[Maidu]

Hi, that looks working. I can take it as reference to my project. Thanks.

<warning> nrf_sdh_ble: RAM starts at 0x20002A68, can be adjusted to 0x20002760.

<warning> nrf_sdh_ble: RAM size can be adjusted to 0xD8A0.

<info> app: UART Start!

<info> app: fds_test_write()

<info> app: read from record: 

<info> app: DEADBEEF

<info> app: DEADBEEF

<info> app: DEADBEEF

<info> app: DEADBEEF

<info> app: DEADBEEF

<info> app: DEADBEEF

<info> app: 

<info> app: Found 6 valid records.

<info> app: Found 0 dirty records (ready to be garbage collected).

[Maidu]

Hi, I tested it with one of my custom boards what don't have second crystal and it does not run. 

I use this config

// </h>
//==========================================================

// <h> Clock - SoftDevice clock configuration

//==========================================================
// <o> NRF_SDH_CLOCK_LF_SRC  - SoftDevice clock source.

// <0=> NRF_CLOCK_LF_SRC_RC
// <1=> NRF_CLOCK_LF_SRC_XTAL
// <2=> NRF_CLOCK_LF_SRC_SYNTH

#ifndef NRF_SDH_CLOCK_LF_SRC
#define NRF_SDH_CLOCK_LF_SRC 0
#endif

// <o> NRF_SDH_CLOCK_LF_RC_CTIV - SoftDevice calibration timer interval.
#ifndef NRF_SDH_CLOCK_LF_RC_CTIV
#define NRF_SDH_CLOCK_LF_RC_CTIV 16
#endif

// <o> NRF_SDH_CLOCK_LF_RC_TEMP_CTIV - SoftDevice calibration timer interval under constant temperature.
// <i> How often (in number of calibration intervals) the RC oscillator shall be calibrated
// <i>  if the temperature has not changed.

#ifndef NRF_SDH_CLOCK_LF_RC_TEMP_CTIV
#define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV 2
#endif

// <o> NRF_SDH_CLOCK_LF_XTAL_ACCURACY  - External crystal clock accuracy used in the LL to compute timing windows.

// <0=> NRF_CLOCK_LF_XTAL_ACCURACY_250_PPM
// <1=> NRF_CLOCK_LF_XTAL_ACCURACY_500_PPM
// <2=> NRF_CLOCK_LF_XTAL_ACCURACY_150_PPM
// <3=> NRF_CLOCK_LF_XTAL_ACCURACY_100_PPM
// <4=> NRF_CLOCK_LF_XTAL_ACCURACY_75_PPM
// <5=> NRF_CLOCK_LF_XTAL_ACCURACY_50_PPM
// <6=> NRF_CLOCK_LF_XTAL_ACCURACY_30_PPM
// <7=> NRF_CLOCK_LF_XTAL_ACCURACY_20_PPM

#ifndef NRF_SDH_CLOCK_LF_XTAL_ACCURACY
#define NRF_SDH_CLOCK_LF_XTAL_ACCURACY 0
#endif

[Spirit]

Nordic guys, 

I discovered the exact same problem that Maidu is talking about.
With the 32k crystal all is working fine, but without it the FDS_EVT_INIT (or any other FDS handler event) is not trigger. Never.

That is a huge problem for me. Now I'm with 25 not working (custom) PCBs.
And I repeat. The previous version of that mainly same PCB, had a 32k crystal and there the (FDS) code is working without any problem.

Any solution for that? (SDK 14.2)

[Edvin]

For both:

Have you tested this setup on an nRF52DK?

I just did a test with the same settings as described above on the DK, using the same example that I sent in a previous reply in this post, and it seems to work fine.

Is it the FDS that does not work when you try the PCBs without the Xtal, or is it the entire application (advertising etc.) that is not working?

 

BR,

Edvin

[Maidu]

Hi, it is only FDS what is not working. I run BLE in central role and works fine.