RE: nRF52840 SPIM cannot get input data, while oscilloscope signals are right.

SuirenEngineer — Wed, 23 Jun 2021 04:28:09 GMT

Thanks for reply. I have just solved the problem. just look at

NRF_LOG_HEXDUMP_INFO(m_rx_buf, strlen((const char *)m_rx_buf));

When the fisrt byte received by the spim driver is 0x00, strlen((const char *)m_rx_buf)) will return 0. Thus the callback will print nothing for ever. So I tried to print m_rx_buf[1] and finally I got the device ID. Maybe the sdk examples should fix this emmm...bug?

Best regards

RE: nRF52840 SPIM cannot get input data, while oscilloscope signals are right.

Karl Ylvisaker — Tue, 22 Jun 2021 13:05:23 GMT

Hello,

[quote user=""]After some effort, now I managed to get the right signals on a oscilloscope.[/quote]

I am not sure I understand your issue correctly; could you confirm for me whether this means that you are able to see the right output signals by your device (but not receiving a reply from your SPIS device), or if you mean that you are seeing correct outbound and inbound communication on the bus, but it is not showing up in your application?

Are you entering into the callback handler every time a transfer is complete?
Is this part of an application that uses BLE in addition to the SPIM communication (i.e is there a SoftDevice present and enabled)?

Looking forward to resolving this issue together!

Best regards,
Karl