[FAQ] TDA4VM: How do we avoid UDMA resource conflict issues when integrating the MCAL Eth module with other modules?

MCAL Eth module has a static configuration of UDMA resources instead depends on the UDMA driver from PDK.

Whereas other MCAL modules still depend on PDK UDMA Driver.

When using the Eth module and other MCAL modules integrated, there will be a resource conflict between them as there is no synchronization of resource usage among both modules.

To avoid resource conflict, we need to modify the Eth configuration to use other resources (last or unallocated) from the RM table (refer to .sysconfig file from SDK and sysconfig tool from ti.com for the resources allocated to each core), and the PDK UDMA driver will use initial resources from the RM table.

Below is the reference of various Eth configuration parameters with default and recommended modified values to avoid resource conflict.

D: Default Configuration value
M: Modified configuration value