Zephyr SPI master timeout (-ETIMEOUT)

RE: Zephyr SPI master timeout (-ETIMEOUT)

Vidar Berg — Fri, 30 Jun 2023 12:19:28 GMT

Please try the attached project and see if it works. It includes an overlay for the 'bl652_dvk' board.

devzone.nordicsemi.com/.../3122.spi.zip

RE: Zephyr SPI master timeout (-ETIMEOUT)

Bret Foreman — Thu, 29 Jun 2023 22:12:35 GMT

I put a message up on the Zephyr Discord SPI discussion looking for some SPI code for the nRF52832. No reply yet. I still think the best is to modify the nRF52840 code to work on the 832, but I'm not sure how to do it.

RE: Zephyr SPI master timeout (-ETIMEOUT)

Bret Foreman — Thu, 29 Jun 2023 20:27:08 GMT

I figured out why the device tree provided in the tool chain doesn't work - it's not supposed to. Laird, the manufacturer, hasn't rolled out support for SPI on that module. What's in the provided device tree is just a placeholder.

There _is_ a SPI device tree for the BL654, which uses the nRF52840 chip. This device tree looks a lot like the example you gave, which is also for the nRF52840.

Is it possible that Zephyr SPI for the nRF52832 is simply not supported? Could I create the appropriate overlay to support my board?

RE: Zephyr SPI master timeout (-ETIMEOUT)

Bret Foreman — Thu, 29 Jun 2023 18:36:12 GMT

I copied the example main.c and overlay files into a fresh project based on the Hello_world template and created a build configuration for my blk652 module (based on the nRF52832 chip). When I did the build, I got the following error:

devicetree error: c:/Nordic/VS_Code/SPI_test/bl652_dvk.overlay:39 (column 16): parse error: undefined node label 'spi3'

I also notice that the "low-power" tag does not exist in "nordic,nrf-pinctrl:child:child". And there is no compatible property for spi-dev-a@0.

How should I modify the overlay to fix this?

RE: Zephyr SPI master timeout (-ETIMEOUT)

Vidar Berg — Thu, 29 Jun 2023 15:11:31 GMT

Hello,

Your I2C slave should be defined as a child node to your SPI peripheral because the 'operation' flags are meant to be configured individually for each device on the bus. Same as what my coworker Torbjørn did in his SPI example here: https://github.com/too1/ncs-spi-master-slave-example/blob/master/nrf52840dk_nrf52840.overlay#L46. You can also see how he initializes the spi_dt_spec struct here: https://github.com/too1/ncs-spi-master-slave-example/blob/master/src/main.c#L43C32-L43C39. You can also use the SPI_DT_SPEC_GET(DT_NODELABEL((<spi bus node>)) helper macro.