nRF52832: SPIM1/2 don't generate SCKs

RE: nRF52832: SPIM1/2 don't generate SCKs

Bruce McKenney — Thu, 06 Dec 2018 17:54:29 GMT

My mistake. Some "dead" code came alive and adopted my pins for something else. (Double-assignment.)

Sorry for wasting everyone's time.

RE: nRF52832: SPIM1/2 don't generate SCKs

Jørgen Holmefjord — Thu, 06 Dec 2018 12:29:31 GMT

Hi,

Have you been able to reproduce this behavior on nRF52-DK?
Which pins are you using for the SPI interface?
Can you post the code you used for testing this?

Best regards,
Jørgen

RE: nRF52832: SPIM1/2 don't generate SCKs

Nguyen Hoan Hoang — Wed, 05 Dec 2018 21:37:29 GMT

It supports both actually. Have a look at use cases in sensor drivers from the root of the project. This example shows how to use it in SPI Master/Slave mode full duplex

RE: nRF52832: SPIM1/2 don't generate SCKs

Bruce McKenney — Wed, 05 Dec 2018 21:23:03 GMT

Thank you for the suggestion. It appears (?) that this driver works only half-duplex, i.e. a transaction is broken up into Tx-only and Rx-only segments. I might be able to do that with mine, but I didn't expect that was a restriction -- SPIM0 doesn't appear to have it.

The only other difference I could see was the interrupt enablement, which I'm not doing. I threw in a ClearPendingIRQ just as an experiment, but it made no difference.

RE: nRF52832: SPIM1/2 don't generate SCKs

Nguyen Hoan Hoang — Wed, 05 Dec 2018 20:22:34 GMT

This SPI driver works well with all 3 SPI. The code is very simple. It supports both master & slave mode. Have a look, you may find the missing link to your SPI issue.