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.

AM62P: IPC Vringbuf size and limitation

Part Number: AM62P

Tool/software:

Hi Expert,

from the guide, we can see below describe.

  • Fixed RPMsg packet size

    • total packet size of 512 bytes

    • 496 bytes of data

    • 16 bytes are a header

from below thread:

(+) AM623: M4F side packets can't exceed 256 bytes - Processors forum - Processors - TI E2E support forums

As far as IPC_RPESSAGE_NUM_VRING_BUF and IPC_RPESSAGE_MAX_VRING_BUF_SIZE:

IPC_RPESSAGE_NUM_VRING_BUF - this is the number of RPMsg messages that can be queued up in each direction (i.e., 256 from Linux to M4F, and 256 from M4F to Linux, for a total of 512 VRING buffers total)

IPC_RPESSAGE_MAX_VRING_BUF_SIZE - this should stay at 512 bytes total per VRING buffer.

This mean the M4F to Linux AND Linux to M4F are share the Vringbuf? Right? so the packet needs limited to 256? right?

BR,

Biao