SPI blocked by BLE(idle_state_handle())

RE: SPI blocked by BLE(idle_state_handle())

Jared — Thu, 24 Aug 2023 08:15:48 GMT

Hi,

[quote user="Buli"]I'm using only SPI, so I think it shouldn't block something else.[/quote]

The logs processing and the handling of BLE application events will be blocked since you're spinning in a loop until the SPI transaction has been completed:

err_code = nrf_drv_spi_transfer(&spi, SpiTxData, spiTransferSize, Spirxd, spiTransferSize);
while (!spi_xfer_done)
{
__WFE();
}

[quote user="Buli"]A flag will be set in the timer callback handler. The flag will trigger in the main loop the call from getOBDData()[/quote]

And getOBDData() will call DRV_SPI_TransferData()?

[quote user="Buli"]At both modes the SPI is slowed down for an intervall 1,2sec[/quote]

What kind of BLE activity are you running? Is it in a connection or is it advertising?

[quote user="Buli"]

an interrupt to happen,

When I comment out NRF_LOG_PROCESS(), then everything works fine. But why is it so? I couldn't find an answer

[/quote]

NRF_LOG_PROCESS will process any pending logs, the more logs that are in the queue, the longer time it will take for it to process the log data. If you don't need to use the logger, then you can always disable it.

regards
Jared

RE: SPI blocked by BLE(idle_state_handle())

Buli — Wed, 23 Aug 2023 10:53:48 GMT

Hi, I'll try to answer for all

[quote userid="73165" url="~/f/nordic-q-a/103073/spi-blocked-by-ble-idle_state_handle/442726"]Which SPI instance are you using?[/quote]

SPI0

[quote userid="73165" url="~/f/nordic-q-a/103073/spi-blocked-by-ble-idle_state_handle/442726"]I see that you are running the SPI in blocking mode, why? Wouldn't it better to let the program handle the logging in the meantime you wait for the SPI transaction to finish? Or maybe you're only printing data from the SPI transaction?[/quote]

I'm using only SPI, so I think it shouldn't block something else.

[quote userid="73165" url="~/f/nordic-q-a/103073/spi-blocked-by-ble-idle_state_handle/442726"]From where do you call DRV_SPI_TransferData() is it from the main loop in getOBDData()?[/quote]

A flag will be set in the timer callback handler. The flag will trigger in the main loop the call from getOBDData()

static void ndts_service_event_handler(ble_ndts_t * p_ndts, ble_ndts_evt_t * p_evt)
{

	if(p_evt->evt_type == BLE_NDTS_EVT_NOTIFICATION_ENABLED)
	{
		NRF_LOG_INFO("Notifications Enabled event occurred!!");
		data_tx_timer_start();
		NRF_LOG_INFO("DTS Timer started!");
	}

	else if (p_evt->evt_type == BLE_NDTS_EVT_NOTIFICATION_DISABLED)
	{
		NRF_LOG_INFO("Notifications Disabled event occurred!!");
		data_tx_timer_stop();
		NRF_LOG_INFO("DTS Timer stopped!");
	}

	else
	{
	}
}

static void data_trans_timeout_handler(void * p_context)
{
	if(!obd_req_ready)
		obd_req_ready = true;
}

// Enter main loop.
	for (;;)
	{
			if(obd_req_ready)
			{
				getOBDData();
				obd_req_ready = false;
			}
			idle_state_handle();

[quote userid="73165" url="~/f/nordic-q-a/103073/spi-blocked-by-ble-idle_state_handle/442726"]What is the BLE doing, is it in a connection or advertising? If you increase the interval, does it work fine? At what BLE interval is it fine? [/quote]

At both modes the SPI is slowed down for an intervall 1,2sec

[quote userid="73165" url="~/f/nordic-q-a/103073/spi-blocked-by-ble-idle_state_handle/442726"]Which SDK and softdevice version are you using?[/quote]

SDK 17.1

Softdevice is 112

[quote userid="73165" url="~/f/nordic-q-a/103073/spi-blocked-by-ble-idle_state_handle/442726"]It shouldn't really be blocked in that function, what it basically does is to call __WFE() and wait for an interrupt to happen,[/quote]

When I comment out NRF_LOG_PROCESS(), then everything works fine. But why is it so? I couldn't find an answer

static void idle_state_handle(void)
{
	//if(NRF_LOG_PROCESS() == false)
	nrf_pwr_mgmt_run();
}

BR,

Büli

RE: SPI blocked by BLE(idle_state_handle())

Jared — Wed, 23 Aug 2023 10:07:16 GMT

Hi,

I have some questions,

Which SPI instance are you using?
I see that you are running the SPI in blocking mode, why? Wouldn't it better to let the program handle the logging in the meantime you wait for the SPI transaction to finish? Or maybe you're only printing data from the SPI transaction?
From where do you call DRV_SPI_TransferData() is it from the main loop in getOBDData()?
What is the BLE doing, is it in a connection or advertising? If you increase the interval, does it work fine? At what BLE interval is it fine?
Which SDK and softdevice version are you using?

[quote user="Buli"]I don't know why the NRF_LOG_PROCESS() is blocking for 1,2sec. Without to check for logs to transmit it, the data is fired over BLE every 20ms in a notify.[/quote]

It shouldn't really be blocked in that function, what it basically does is to call __WFE() and wait for an interrupt to happen,

regards

Jared

RE: SPI blocked by BLE(idle_state_handle())

Buli — Tue, 22 Aug 2023 20:44:41 GMT

I found where it's blocked

static void idle_state_handle(void)
{
	//if(NRF_LOG_PROCESS() == false)
	nrf_pwr_mgmt_run();
}

I don't know why the NRF_LOG_PROCESS() is blocking for 1,2sec. Without to check for logs to transmit it, the data is fired over BLE every 20ms in a notify.