Both the enqueue operation in the ESB queue buffer (esb_write_payload) and the dequeue operation (esb_pop_tx) use ++tx_fifo.back.https://devzone.nordicsemi.com/f/nordic-q-a/127608/both-the-enqueue-operation-in-the-esb-queue-buffer-esb_write_payload-and-the-dequeue-operation-esb_pop_tx-use-tx_fifo-backIn the enqueue function esb_write_payload , the enqueue implementation uses ++tx_fifo.back . In the dequeue function esb_pop_tx , the dequeue processing also uses ++tx_fifo.back . Is this reasonable?en-USTelligent Community 13Fri, 27 Mar 2026 15:22:18 GMTRE: Both the enqueue operation in the ESB queue buffer (esb_write_payload) and the dequeue operation (esb_pop_tx) use ++tx_fifo.back.https://devzone.nordicsemi.com/thread/564210?ContentTypeID=1Fri, 27 Mar 2026 15:22:18 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f2bafd3e-a3e9-4fb4-b979-61194b44cb2aKenneth<p>Hello,</p> <p></p> <p>I believe the implementation is correct.</p> <p>Enqueue: Adds items at the back (tail) pointer<br />Dequeue: Removes items from the front (head) pointer</p> <p>Both pointers wrap around to 0 when they reach CONFIG_ESB_TX_FIFO_SIZE</p> <p>The dequeue operation modifies the front pointer, not the back pointer, which is the expected behavior.</p> <p>Hope that helps,<br />Kenneth</p><div style="clear:both;"></div>