SPI dependent on softdevice?

RE: SPI dependent on softdevice?

Susheel Nuguru — Tue, 17 Nov 2015 10:27:19 GMT

Explicitly enabling them means that you need to explicitly power them down. So Yes

RE: SPI dependent on softdevice?

Emil — Tue, 17 Nov 2015 10:17:23 GMT

Now both SPI and ESB work, when I initialized both HF and LF clock. My question then is should I power them down when powering off?

NRF_CLOCK->LFCLKSRC = (CLOCK_LFCLKSRC_SRC_Xtal << CLOCK_LFCLKSRC_SRC_Pos);

NRF_CLOCK->EVENTS_HFCLKSTARTED = 0;
NRF_CLOCK->TASKS_HFCLKSTART = 1;
while (NRF_CLOCK->EVENTS_HFCLKSTARTED == 0);

NRF_CLOCK->EVENTS_LFCLKSTARTED = 0;
NRF_CLOCK->TASKS_LFCLKSTART = 1;
while (NRF_CLOCK->EVENTS_LFCLKSTARTED == 0);

RE: SPI dependent on softdevice?

Emil — Fri, 13 Nov 2015 10:54:30 GMT

I did not initialize sd, that is the whole point. Because I don't want softdevice involved when working with microESB, because then I would need timeslot API.

I upgraded to SDK 10, and now SPI works without softdevice, but microESB does not.

sd_ functions cannot be called if the softdevice is not initialize, and you can't use NRF_ stuff directly when the softdevice is enabled.

RE: SPI dependent on softdevice?

Susheel Nuguru — Fri, 13 Nov 2015 07:40:36 GMT

SPI and softdevice are not doing anything with each other. SPI slave will not work along with softdevice, because softdevice will interrupt SPI slave handling which Master will not know and hence there will be loss of data.

SPI Master with softdevice should work OK, because it is master that is driving the clock, so it should be ok even if softdevice interrupts its handling.

You code cannot configure LFCLK while using softdevice, because that clock is will be owned by SD.

Seems like APP_ERROR_CHECK(sd_nvic_ClearPendingIRQ(p_spi_instance->irq_type)); is the one in spi_master.c

What is the error code? did you initialize SD before that? did it return without errors?