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.

TDA4VEN-Q1: How to use a dedicated Tx buffer for CAN messages

Part Number: TDA4VEN-Q1

Tool/software:

Hi,TI expert

1.The sending method I use is Tx buffer.
2.Can one dedicated Tx Buffer be configured with multiple message IDs?
3.If multiple message IDs can be assigned, what are the advantages and disadvantages.
4.Based on your experience, should one tx buffer be paired with one message ID or multiple message IDs.

5.int32_t MCAN_txBufTransIntrEnable(uint32_t baseAddr,uint32_t bufNum,uint32_t enable),this API interface is called only once during initialization or once after sending a message


Above, thank you

  • Hello,

    2. 

    Can one dedicated Tx Buffer be configured with multiple message IDs?

    Single Tx buffer is not "configured" with one ID permanently. one at a time but can send multiple message IDs


    3. 

    If multiple message IDs can be assigned, what are the advantages and disadvantages

    Advantage

    Fewer Tx buffers required, especially in systems with limited RAM.

    Disadvantage

    No concurrency: Only one message can be queued in a buffer at a time. Using the same buffer for multiple IDs means you can't queue them simultaneously.

    4.

    Based on your experience, should one tx buffer be paired with one message ID or multiple message IDs.

    Use dedicated Tx buffers per message ID.

    5.

    int32_t MCAN_txBufTransIntrEnable(uint32_t baseAddr,uint32_t bufNum,uint32_t enable)

    This API enables the interrupt for a given Tx buffer. Once it's enabled, you don’t need to call it again after each message.

    Regards

    Tarun Mukesh