How to solve the error FDS_ERR_NO_SPACE_IN_QUEUE using SDK14.0.0

[Amy]

Fullscreen log.log Download

0> !!!!!flash[0]=D64A0C59, hr=59, time=D64A0C
 0> Send Indication Complete.
 0> !!!!!flash[0]=D649D059, hr=59, time=D649D0
 0> WB100_SERVICE_SPO2_CHARACTERISTIC evt CCCD_WRITE. 
 0> Send Indication Complete.
 0> !!!!!flash[0]=D6499459, hr=59, time=D64994
 0> WB100_SERVICE_SDNN_CHARACTERISTIC evt CCCD_WRITE. 
 0> Send Indication Complete.
 0> !!!!!flash[0]=D6495859, hr=59, time=D64958
 0> WB100_SERVICE_FALL_ALARM_CHARACTERISTIC evt CCCD_WRITE. 
 0> Send Indication Complete.
 0> !!!!!flash[0]=D6491C59, hr=59, time=D6491C
 0> WB100_SERVICE_ACTIVEMINUTES_CHARACTERISTIC evt CCCD_WRITE. 
 0> Send Indication Complete.
 0> !!!!!flash[0]=D648E059, hr=59, time=D648E0
 0> WB100_SERVICE_CALORIES_CHARACTERISTIC evt CCCD_WRITE. 
 0> Send Indication Complete.
 0> !!!!!flash[0]=D648A459, hr=59, time=D648A4
 0> fds_gc() error 8
 0> WB100_SERVICE_CURRENTTIME_CHARACTERISTIC evt WRITE. 
 0> Send Indication Complete.
 0> !!!!!flash[0]=D6486859, hr=59, time=D64868
 0> fds_gc() error 8
 0> Send Indication Complete.
 0> !!!!!flash[0]=D6482C58, hr=58, time=D6482C
 0> fds_record_delete() Error! ret=8
 0> Send Indication Complete.
 0> !!!!!flash[0]=D647F058, hr=58, time=D647F0
 0> Send Indication Complete.
 0> !!!!!flash[0]=D647B457, hr=57, time=D647B4
 0> fds_gc() error 8
 0> Send Indication Complete.
 0> !!!!!flash[0]=D6446C4B, hr=4B, time=D6446C
 0> fds_gc() error 8
 0> Send Indication Complete.
 0> !!!!!flash[0]=D644304B, hr=4B, time=D64430
 0> fds_record_delete() Error! ret=8
 0> Send Indication Complete.
 0> !!!!!flash[0]=D643F450, hr=50, time=D643F4
 0> fds_gc() error 8
 0> Send Indication Complete.
 0> !!!!!flash[0]=D643B857, hr=57, time=D643B8
 0> fds_gc() error 8
 0> Send Indication Complete.
 0> !!!!!flash[0]=D6437C57, hr=57, time=D6437C
 0> fds_record_delete() Error! ret=8
 0> Disconnected, reason 19.
 0> @@@@@@@@@fileID=0x1010, item=0
 0> @@@@@@@@@@@@@@@@@flash_record_data==0xF4, 244, savedata=215, length=11
 0>  Update!!!!!
 0> fds_gc() error 8
 0> @@@@@@@@@fileID=0x1010, item=0
 0> @@@@@@@@@@@@@@@@@flash_record_data==0xF4, 244, savedata=215, length=11
 0>  Update!!!!!
 0>  fds_record_update() error!!!!! 8
 0> Update KEY!!!!
 0> !!!!!!!PASSKEY
 0> PassKey@@@@@@@@@@@@tmp=0.97, Calories_sum = 0.97  
 0> ADC:4095 Percent:100 AIN V: 3.00V    Battery V:4.19V
 0> save HR(5min).
 0> @@@@@@@@@@@@tmp=0.97, Calories_sum = 1.94  
 0> ADC:4095 Percent:100 AIN V: 3.00V    Battery V:4.19V

Hi,

We use the FDS to write/update/delete the data that store to the flash.

When operating delete/update the data to the flash for a while, the error FDS_ERR_NO_SPACE_INQUEUE occurred.

We also increase the value FDS_OP_QUEUE_SIZE from 4 to 10, but the error still occurred.

Thanks for help.

[Martin Lesund]

Hi Amy, 

How often and how much do you write to flash?

Do the FDS tasks that are scheduled already get dequeued after receiving FDS_ERR_NO_SPACE_IN_QUEUES?

As you may know, BLE activity does affect the flash performance, please refer to the Flash API chapter in the SDS for more details. This means that you may have to reduce protocol activity (connection interval, etc) if frequent logging to flash is required.