SPIM writes with address offset

RE: SPIM writes with address offset

obbe — Mon, 15 Oct 2018 14:38:41 GMT

Good idea! I'll poke around in the examples and drivers and see what I can find.

Edit: Somehow, this seems to magically have resolved itself. Suddenly, it started spitting out garbage data again, and when I troubleshoot it, lo and behold, the data was now stored correctly in the buffer. I could swear I cleaned the build several times, but I'm going to blame bad build for now.

RE: SPIM writes with address offset

Kenneth — Mon, 15 Oct 2018 14:33:46 GMT

My suggestion here is to take the \nRF5_SDK_15.2.0_9412b96\examples\peripheral\spi and use that as reference. The NRF_SPIM_TASK_START is called in spim_xfer() for example, you may set a breakpoint prior to this to check all spim configuration.

RE: SPIM writes with address offset

obbe — Mon, 15 Oct 2018 11:48:47 GMT

Yes, here is a screenshot from the oscilloscope. In this case we're also outputting a command, but its not relevant for this case. What I expected to receive from this was a RX buffer of 0x0C 0xC4 0x75 0xFF, but instead it contained 0x?? 0x0C 0xC4 0x75.

Yes, I'm aware of the parallel byte. This is (in my opinion) a slightly odd IC in that it doesn't receive a command prior to outputting the data.

RE: SPIM writes with address offset

Kenneth — Mon, 15 Oct 2018 11:40:42 GMT

Hi,

Do you have a screenshot of CSN, SCK, MISO, and MOSI when this occurs? Are you sure you are taking into account that there will be a byte in parallel on MISO when for instance the command byte is sent on MOSI.

Best regards,
Kenneth