SPI Slave problem with buffers (nRF51, SDK v10) - Bug in nrf_drv_spis_event_t structure?

RE: SPI Slave problem with buffers (nRF51, SDK v10) - Bug in nrf_drv_spis_event_t structure?

Susheel Nuguru — Fri, 02 Sep 2016 07:06:02 GMT

fixed in SDK12, look here

RE: SPI Slave problem with buffers (nRF51, SDK v10) - Bug in nrf_drv_spis_event_t structure?

utrank00 — Wed, 11 May 2016 04:00:27 GMT

If I set the tx buffer to 0, I expect the AMOUNTTX to be 0 when the transfer complete. But instead, the AMOUNTTX always equal the the AMOUNTRX when the transfer complete. This is why this issue did not became obvious. I think this is a bug.

RE: SPI Slave problem with buffers (nRF51, SDK v10) - Bug in nrf_drv_spis_event_t structure?

Susheel Nuguru — Mon, 11 Apr 2016 07:37:14 GMT

yes, unfortunately, and hence i reflected this in this thread.

RE: SPI Slave problem with buffers (nRF51, SDK v10) - Bug in nrf_drv_spis_event_t structure?

puz_md — Fri, 01 Apr 2016 11:35:42 GMT

Uhm... the bug is still present in SDK11 official release :(

Also, there seems to be no info about this bug in the relase notes...

RE: SPI Slave problem with buffers (nRF51, SDK v10) - Bug in nrf_drv_spis_event_t structure?

Susheel Nuguru — Wed, 10 Feb 2016 15:09:33 GMT

I agree ..

RE: SPI Slave problem with buffers (nRF51, SDK v10) - Bug in nrf_drv_spis_event_t structure?

puz_md — Wed, 10 Feb 2016 14:37:32 GMT

Currently I am using SDK10 as SDK11 is still in alpha state. I can't remember if I actually compiled my code with SDK11, but I definitely took a look at the release notes and there was no information about a fixed SPIS bugs. So I assumed the bug would still be present in SDK11 ;)

Maybe not so many people use the SPI Slave interface (with a complex protocol), as this would suggest that there is another microcotroller which uses probably more power than the nRF5x. So this would not be a classic low power application. We are using the nRF5x in different scenarios where sometimes low energy consumption is crucial. In other cases, there is enough power available and the nRF5x just provides Bluetooth (Smartphone) support and sometimes sensor access for a device. Having the same software and hardware architecture makes development much easier :)

RE: SPI Slave problem with buffers (nRF51, SDK v10) - Bug in nrf_drv_spis_event_t structure?

Susheel Nuguru — Wed, 10 Feb 2016 14:20:38 GMT

Thanks for fixing my typo puz :)

RE: SPI Slave problem with buffers (nRF51, SDK v10) - Bug in nrf_drv_spis_event_t structure?

Susheel Nuguru — Wed, 10 Feb 2016 14:19:28 GMT

I thought you were using SDK10 .. i am so surprised now that no one were bitten by this before. So all of them (before you) used same TX and RX buffer length. That is good to know info :)

RE: SPI Slave problem with buffers (nRF51, SDK v10) - Bug in nrf_drv_spis_event_t structure?

puz_md — Wed, 10 Feb 2016 14:09:43 GMT

I know (sorry for not mentioning SDK11). This is why I reported it ;)

RE: SPI Slave problem with buffers (nRF51, SDK v10) - Bug in nrf_drv_spis_event_t structure?

Susheel Nuguru — Wed, 10 Feb 2016 14:08:25 GMT

My my......this is also a bug in SDK11_aplha ... :(

RE: SPI Slave problem with buffers (nRF51, SDK v10) - Bug in nrf_drv_spis_event_t structure?

Susheel Nuguru — Wed, 10 Feb 2016 14:06:04 GMT

puz_md,

Thanks for this report,

I did some debug and found that this is a bug in the driver in file nrf_spis.h

__STATIC_INLINE uint8_t nrf_spis_tx_amount_get(NRF_SPIS_Type const * p_spis)
{
    return (uint8_t) p_spis->AMOUNTRX;
}

__STATIC_INLINE uint8_t nrf_spis_rx_amount_get(NRF_SPIS_Type const * p_spis)
{
    return (uint8_t) p_spis->AMOUNTTX;
}

Here you can see clearly that wrong registers are fetched. Correct them to the below.

__STATIC_INLINE uint8_t nrf_spis_tx_amount_get(NRF_SPIS_Type const * p_spis)
{
    return (uint8_t) p_spis->AMOUNTTX;
}

__STATIC_INLINE uint8_t nrf_spis_rx_amount_get(NRF_SPIS_Type const * p_spis)
{
    return (uint8_t) p_spis->AMOUNTRX;
}

I will add this in known bugs in here and register an internal ticket for the team to know about it

RE: SPI Slave problem with buffers (nRF51, SDK v10) - Bug in nrf_drv_spis_event_t structure?

Susheel Nuguru — Wed, 10 Feb 2016 10:33:50 GMT

Thanks puz, I deleted the comment with the image .. i will update this thread when I have new info.

RE: SPI Slave problem with buffers (nRF51, SDK v10) - Bug in nrf_drv_spis_event_t structure?

puz_md — Wed, 10 Feb 2016 09:39:10 GMT

I'm not in a hurry as there is an easy workaroung (switching values). I just thought that you might want to fix this bug before the next SDK is released.

Can you please remove the image from your previous comment? Please see my private message for details. Thanks a lot!

RE: SPI Slave problem with buffers (nRF51, SDK v10) - Bug in nrf_drv_spis_event_t structure?

Susheel Nuguru — Wed, 10 Feb 2016 07:50:07 GMT

You are right, the output from the hex you mentioned seems wrong, i will try to look into it, cannot promise that it will be today ..

RE: SPI Slave problem with buffers (nRF51, SDK v10) - Bug in nrf_drv_spis_event_t structure?

puz_md — Tue, 09 Feb 2016 14:08:50 GMT

Accidentially, my .zip file contained old binaries in the output folder (which you used - they switched the variables for the software to work correctly). The correct binary from the test code should be called "SPIS_Test.hex". Can you please try again with this one?

RE: SPI Slave problem with buffers (nRF51, SDK v10) - Bug in nrf_drv_spis_event_t structure?

Susheel Nuguru — Tue, 09 Feb 2016 12:19:11 GMT

ill take a look at it today.

RE: SPI Slave problem with buffers (nRF51, SDK v10) - Bug in nrf_drv_spis_event_t structure?

puz_md — Mon, 08 Feb 2016 10:58:06 GMT

Hi Aryan, I appended some test code and a short description to my initial post.

RE: SPI Slave problem with buffers (nRF51, SDK v10) - Bug in nrf_drv_spis_event_t structure?

Susheel Nuguru — Mon, 08 Feb 2016 08:01:48 GMT

can you help me reproduce this problem? please send me your project.