Atomic FIFO bug report - calling nrf_atfifo_alloc_put twice in a row truncates data in atfifo buffer

RE: Atomic FIFO bug report - calling nrf_atfifo_alloc_put twice in a row truncates data in atfifo buffer

Hakon — Tue, 30 Jul 2019 08:46:56 GMT

It's possible. In any case, it has been reported so we just need to wait.

RE: Atomic FIFO bug report - calling nrf_atfifo_alloc_put twice in a row truncates data in atfifo buffer

mk2 — Mon, 29 Jul 2019 09:26:57 GMT

Hi,

How is it going with this issue? Is it perhaps delayed because of summer vacation?

RE: Atomic FIFO bug report - calling nrf_atfifo_alloc_put twice in a row truncates data in atfifo buffer

mk2 — Wed, 17 Jul 2019 07:51:56 GMT

Well that doesn´t surprise me.

I intentionally wrote those two examples because write-read-write and write-write-read should end up in same result if it is a FIFO.

Moreover, if the first element I write to the FIFO is 0x000000A9 4 bytes, then I will and should expect getting same value back when reading 4 bytes from the FIFO.

And I would like to know why this is happening too.

RE: Atomic FIFO bug report - calling nrf_atfifo_alloc_put twice in a row truncates data in atfifo buffer

Hakon — Tue, 16 Jul 2019 16:19:55 GMT

Hello,

I changed the order of nrf_atfifo_alloc_put(m_data_atfifo, data, data_size, NULL) and nrf_atfifo_alloc_put(m_data_atfifo, data, data_size, NULL) at the end, and then got 30201A9 in both cases.

I changed the code to this

    nrf_atfifo_alloc_put(m_data_atfifo, &data_size, sizeof(data_size), NULL);
    nrf_atfifo_alloc_put(m_data_atfifo, data, data_size, NULL);

    uint32_t get_size = 0;
    nrf_atfifo_get_free(m_data_atfifo, &get_size, sizeof(get_size), NULL);
    NRF_LOG_INFO("1. get_size: %x", get_size);

    nrf_atfifo_clear(m_data_atfifo);


    nrf_atfifo_alloc_put(m_data_atfifo, &data_size, sizeof(data_size), NULL);
    nrf_atfifo_alloc_put(m_data_atfifo, data, data_size, NULL);
    nrf_atfifo_get_free(m_data_atfifo, &get_size, sizeof(get_size), NULL);
    NRF_LOG_INFO("2. get_size: %x", get_size);

If you do it in this order get_size will be the same in both cases.