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
  • Some additional information: due to the soft device's presence, in Keil I change the memory map from:

    Start 0x0 Size 0x14000 Start 0x20000000 Size 0x2000

    to:

    Start 0x2000 (this one is from memory, may not be correct) Size 0x2B000 Start 0x20002000 Size 0x2000

    Could there be a memory mapping conflict of the soft device with the SPI peripheral? Are there any APIs for the SPI that I should be aware of (I cannot find this in the docs)?

    Thanks, Jamie

Reply
  • Some additional information: due to the soft device's presence, in Keil I change the memory map from:

    Start 0x0 Size 0x14000 Start 0x20000000 Size 0x2000

    to:

    Start 0x2000 (this one is from memory, may not be correct) Size 0x2B000 Start 0x20002000 Size 0x2000

    Could there be a memory mapping conflict of the soft device with the SPI peripheral? Are there any APIs for the SPI that I should be aware of (I cannot find this in the docs)?

    Thanks, Jamie

Children
No Data
Related