NCS zephyr SPI on nRF52832

RE: NCS zephyr SPI on nRF52832

Jeff4BLE — Tue, 03 May 2022 12:30:45 GMT

Hi Marius,

Sorry I had confused CONFIG_SPI with a different SPI macro that has been modified earlier. CONFIG_SPI is the correct macro for NCS v1.9.1.

I had started to draft a response to the post referencing the hci_spi project. Since that reference has been removed, I assume that you now understand the hci_spi is used for communicating HCI API between the BLE Host and BLE controller over an SPI transport.

An SPIS device can not transmit data without the outside world providing an SPI Clock. This is typically provided by a SPIM device.

You could use the hci_spi example to piece an SPI example together. However, the Adding a Peripheral to an NCS Zephyr project blog is a complete SPIS and SPIM example. For NCS 1.9.X, use the NCS 1.7 updates and move the nf52dk_nrf52840.overlay to the project's root directory.

Cheers

RE: NCS zephyr SPI on nRF52832

Marius_U — Tue, 03 May 2022 10:47:39 GMT

I am using nRF Connect version 1.9.1. I honestly thought that what I was using is the latest thing. I guess now the question is what is the latest thing? Because I took this line "CONFIG_SPI" from sample code provided in the NCS sample which is called hci_spi.

RE: NCS zephyr SPI on nRF52832

Jeff4BLE — Mon, 02 May 2022 16:24:52 GMT

Hi Marius,

It would be helpful if you would include what version of NCS is being used. The use of CONFIG_SPI, suggests you may not be using the latest version.

The implementation is that of an SPI Slave. Therefore, an SPI Clock must be present before data will be clocked out of the slave.

Unless you are creating your own dts file for customer hardware, using an overlay is recommended over editing a dts file.

The SPI is the peripheral used in the blog Adding a Peripheral to an NCS Zephyr project. It's a bit dated, but it should help resolve any potential binding issues.

Cheers,

Jeff