Gazell FIFO issues

RE: Gazell FIFO issues

Sumanth Murali — Mon, 17 Sep 2018 14:35:36 GMT

why is it a good idea?

RE: Gazell FIFO issues

Kenneth — Mon, 17 Sep 2018 14:18:26 GMT

When changing hopping table I think it is a good idea to disable synchronization until the device and host have successfully exchange a packet and is in synchronization again.

RE: Gazell FIFO issues

Sumanth Murali — Thu, 13 Sep 2018 18:45:12 GMT

How would setting sync lifetime to 0 help in this case?

RE: Gazell FIFO issues

Kenneth — Wed, 09 May 2018 11:29:35 GMT

My suggestion is that before you change channel table call: nrf_gzll_set_sync_lifetime(0);

You can change it after you have successfully sent a new packet with new channel table.

RE: Gazell FIFO issues

Sumanth Murali — Tue, 08 May 2018 21:32:22 GMT

We try to make sure they do change at the same time by timing them using application timers on both sides. Changing channel tables frequently seems to mess up gazell completely. Is there a suggested way to do this?

RE: Gazell FIFO issues

Kenneth — Mon, 07 May 2018 13:43:24 GMT

If the host and device change table at different time, for instance if the device is waiting for an ACK, while host has changed table. Then the device will very likely experience nrf_gzll_ok_to_add_packet_to_tx_fifo() while waiting to synchronize again.

RE: Gazell FIFO issues

Sumanth Murali — Mon, 07 May 2018 13:14:37 GMT

This specifically happens while switching the channel table. Is there something specific that needs to be done while switching the channel table

RE: Gazell FIFO issues

Kenneth — Mon, 07 May 2018 12:56:40 GMT

I would expect that you from time to time experience that nrf_gzll_ok_to_add_packet_to_tx_fifo() return false, for instance if you are out of range or if there is much interference. Typically this means that Gazell is currently trying to transmit a packet already, and there is no available space to buffer more packets. In such case the application must either buffer the packet or discard the packet. There is no need to assert or reset the application.

/**
 * @brief Check if adding a packet to a pipe's TX FIFO should be successful.
 *
 * Checks if there is another space in the pipe's TX and RX FIFOs
 * as well as enough overall space in the packet pool.
 *
 * @param pipe The pip for which to check. This value must be < NRF_GZLL_CONST_PIPE_COUNT.
 *
 * @retval true  If there is another space.
 * @retval false If there is not enough space, or the pipe is invalid.
 */
bool nrf_gzll_ok_to_add_packet_to_tx_fifo(uint32_t pipe);