• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 890 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC1310: How big is the buffer for indirect transmissions?

Eugene Peng
Intellectual 620 points
Part Number: CC1310

Hi!

Using the TI 15.5 Co-Processor firmware, how big is the buffer for indirect transmissions (packets to sleepy nodes)? In other words, how many packets can be queued for indirect transmission, waiting for a sleepy node to poll?

Much thanks,

Eugene

  • 0
    TI__Genius 12415 points
    Hi,

    the size of the TX buffer is defined in mac_cfg.c please check the Macros MAC_CFG_TX_MAX and MAC_CFG_TX_DATA_MAX
  • 0 in reply to Hector_r
    Intellectual 620 points

    Hi Hector,

    I am using the co-processor firmware, which I don't have the source code for.

    Do you know what are the macro values for MAC_CFG_TX_MAX and MAC_CFG_TX_DATA_MAX on the coprocessor firmware?

    What kind of messages does MAC_CFG_TX_MAX refer to if not data messages?

    Also, is the TX buffer a FIFO? I.e. if 2 messages are in the queue, they have to go out in the order they were queued, or can either of them go out first depending on which end device polls first?

    Thanks,

    Eugene

  • 0 in reply to Eugene Peng
    TI__Genius 12415 points
    Hi

    Default value for MAC_CFG_TX_MAX is 5 and default value for MAC_CFG_TX_DATA_MAX is 2. MAC_CFG_TX_MAX refers to the overall size of the buffer which include data and command packets such as association request and other. MAC_CFG_TX_DATA_MAX defines the maximum slots in the buffer that can be taken by data packets.

    You should be able to download the SDK and make changes to the coprocessor firmware.

    TX buffer is not a FIFO when it comes to indirect messages for sleepy devices, the packets will be sent out as soon as a device polls even if the packet for that specific device was added to the buffer after other packets in the buffer.

    When it comes to direct messages, then the buffer will act as a FIFO, since the packet should be sent basically as soon as the send message api is called.