Hard fault when spi msg receive during ble scanning.

RE: Hard fault when spi msg receive during ble scanning.

utrank00 — Thu, 10 Mar 2016 03:33:27 GMT

It's my fault. I have a logging break point at the spi interupts. That's enough to throw sd out of sync.

RE: Hard fault when spi msg receive during ble scanning.

utrank00 — Wed, 09 Mar 2016 20:55:06 GMT

No, I'm try to receive spi msg while ble event coming in from another MCU.

RE: Hard fault when spi msg receive during ble scanning.

Susheel Nuguru — Wed, 09 Mar 2016 20:49:23 GMT

So you are trying to send SPI message from BLE event handler?

RE: Hard fault when spi msg receive during ble scanning.

utrank00 — Wed, 09 Mar 2016 20:27:24 GMT

I use the api function spi_slave_init() to set up my spi bus. This function set IRQ priority to APP_IRQ_PRIORITY_LOW.

My spi interupt handle is very simple, it just call spi_slave_buffers_set() when I got SPI_SLAVE_XFER_DONE.

In my code, if scanning not running, then everything is ok. After scan start, and ble events start coming in from the sd, when I try to sent the spi msg from the Cortex, the hard fault occurs.

RE: Hard fault when spi msg receive during ble scanning.

Susheel Nuguru — Wed, 09 Mar 2016 19:44:57 GMT

Did you set any priority of your SPI interrupt? if not then it is set to default highest priority and that most probably will cause an assert in the softdevice because softdevice does not like anything else at the priority in which it will work.

If you have SPI priority to APP_PRIORITY_HIGH, then it is OK to the softdevice but as soon as you make any SVC calls (calls to sd_xxxx functions) then it will hardfault. This seems to be more probable for me that your SPI interrupt priority is high and somewhere it makes sd_call (most probably enter critical section using softdevice API)