This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

BLE Soft Device + SPI

Hi,

I've noticed that when using SPI without a Soft Device or BLE function calls, the SPI peripheral is easy to control and operates correctly.

This nice operation stops when we try to put in the Soft Device + BLE API calls. I have cut+pasted code from a non-BLE project--for which SPI works--to one with BLE, and SPI no longer works. In fact, I wind up in the hardfault handler.

Any advice on any conflicts to be aware of, or how to treat SPI with BLE added in, would be much appreciated.

Thanks, Jamie

Parents
  • Hi Hailang,

    THanks for your reply and suggestion. After further testing, it seems SPI might not be the issue at all. The part I am configuring with SPI is in fact being configured properly to generate an interrupt signal, but as soon as the interrupt comes in, the NRF51822 goes to the HardFault handler. This does not happen when the softdevice is not present. I have tried configuring the interrupt in two ways, using the default CMSIS NVIC functions, as well as the sd_nvic_* functions, with no success found with either one.

    Any suggestions or further readings for me to try?

    Thanks much, Jamie

Reply
  • Hi Hailang,

    THanks for your reply and suggestion. After further testing, it seems SPI might not be the issue at all. The part I am configuring with SPI is in fact being configured properly to generate an interrupt signal, but as soon as the interrupt comes in, the NRF51822 goes to the HardFault handler. This does not happen when the softdevice is not present. I have tried configuring the interrupt in two ways, using the default CMSIS NVIC functions, as well as the sd_nvic_* functions, with no success found with either one.

    Any suggestions or further readings for me to try?

    Thanks much, Jamie

Children
No Data
Related