IPC使用指南

此章节着重说明MCU侧的相关使用说明，更多的IPC的原理和使用可以查阅 IPC模块介绍章节。

IPC配置相关

一个IPC有8个channels，但是共享一个中断，因此一个IPC只能在MCU0或MCU1其中一个系统上使能。

当MCU1使用IPC时，需要配置两部分内容。

需要配置回调函数，作用是当IPC收到/发送数据时产生回调。当然客户可自行定制当传输数据错误时的回调函数。下文以IPC0为例介绍。

static Ipc_ChannelConfigType Ipc_ShmInstance0CfgChannel[8] = {
{
    .ChannelId = 0,
    .ChannelData   = {
        .NumPools = 1,
        .PoolCfg        = Ipc_ShmIpcInstance_0CfgIpcChannel_0BufPool,
        .RxCallback     = IpcTp_InsCan_RxCallback,
        .RxCallbackArg  = (NULL_PTR),
        .TxErrCallback    = DefaultTxErrCallback,
        .TxErrCallbackArg = (NULL_PTR),
    },
},
{
    .ChannelId = 1,
    .ChannelData   = {
        .NumPools = 1,
        .PoolCfg        = Ipc_ShmIpcInstance_0CfgIpcChannel_1BufPool,
        .RxCallback     = IpcTp_InsCan_RxCallback,
        .RxCallbackArg  = (NULL_PTR),
        .TxErrCallback    = DefaultTxErrCallback,
        .TxErrCallbackArg = (NULL_PTR),
    },
},
{
    .ChannelId = 2,
    .ChannelData   = {
        .NumPools = 1,
        .PoolCfg        = Ipc_ShmIpcInstance_0CfgIpcChannel_2BufPool,
        .RxCallback     = IpcTp_InsCan_RxCallback,
        .RxCallbackArg  = (NULL_PTR),
        .TxErrCallback    = DefaultTxErrCallback,
        .TxErrCallbackArg = (NULL_PTR),
    },
},
{
    .ChannelId = 3,
    .ChannelData   = {
        .NumPools = 1,
        .PoolCfg        = Ipc_ShmIpcInstance_0CfgIpcChannel_3BufPool,
        .RxCallback     = IpcTp_InsCan_RxCallback,
        .RxCallbackArg  = (NULL_PTR),
        .TxErrCallback    = DefaultTxErrCallback,
        .TxErrCallbackArg = (NULL_PTR),
    },
},
{
    .ChannelId = 4,
    .ChannelData   = {
        .NumPools = 1,
        .PoolCfg        = Ipc_ShmIpcInstance_0CfgIpcChannel_4BufPool,
        .RxCallback     = IpcTp_InsCan_RxCallback,
        .RxCallbackArg  = (NULL_PTR),
        .TxErrCallback    = DefaultTxErrCallback,
        .TxErrCallbackArg = (NULL_PTR),
    },
},
{
    .ChannelId = 5,
    .ChannelData   = {
        .NumPools = 1,
        .PoolCfg        = Ipc_ShmIpcInstance_0CfgIpcChannel_5BufPool,
        .RxCallback     = IpcTp_InsCan_RxCallback,
        .RxCallbackArg  = (NULL_PTR),
        .TxErrCallback    = DefaultTxErrCallback,
        .TxErrCallbackArg = (NULL_PTR),
    },
},
{
    .ChannelId = 6,
    .ChannelData   = {
        .NumPools = 1,
        .PoolCfg        = Ipc_ShmIpcInstance_0CfgIpcChannel_6BufPool,
        .RxCallback     = IpcTp_InsCan_RxCallback,
        .RxCallbackArg  = (NULL_PTR),
        .TxErrCallback    = DefaultTxErrCallback,
        .TxErrCallbackArg = (NULL_PTR),
    },
},
{
    .ChannelId = 7,
    .ChannelData   = {
        .NumPools = 1,
        .PoolCfg        = Ipc_ShmIpcInstance_0CfgIpcChannel_7BufPool,
        .RxCallback     = IpcTp_InsCan_RxCallback,
        .RxCallbackArg  = (NULL_PTR),
        .TxErrCallback    = DefaultTxErrCallback,
        .TxErrCallbackArg = (NULL_PTR),
    },
},
};

设置receive_coreid。如果是在MCU1上，则需要"receive_coreid=Ipc_Receive_Core1"。同时需要保障MCU0关于IPC设置相同。

MCU0文件地址：/mcu/Config/McalCdd/gen_s100_sip_B/Ipc/src/Ipc_Cfg.c
MCU1文件地址：/mcu/Config/McalCdd/gen_s100_sip_B_mcu1/Ipc/src/Ipc_Cfg.c

Ipc_InstanceConfigType Ipc_ShmCfgInstances0 = {
    .Ipc_InstanceId       = 0U,
    .Ipc_ChannelNum       = 8U,
    .LocalCtlAddr         = 0xcdd9e00,
    .RemoteCtlAddr        = 0xcdd9400,
    .CtlShmSize           = 0xa00,
    .LocalDataAddr        = 0xb4080000,
    .RemoteDataAddr       = 0xb4000000,
    .DataShmSize          = 0x80000,
    .SendDmaChanIdx       = 0xffU,
    .Async                = (TRUE),
    .HwInfo               = {
        .Ipc_HwId         = CPU_IPC0,/**< the id of the Hardware */
        .RecvIrqUsed      = (TRUE),/**< Whether to use Recv interrupt */
        .SendMboxId       = 0,/**< the mailbox id */
        .RecvMboxId       = 16,/**< the mailbox id */
        .RemoteIrq        = 16,
        .LocalIrq         = 0,
        .UseMDMA          = (TRUE),
    },
    .Ipc_ChannelConfigPtr = Ipc_ShmInstance0CfgChannel,
    .receive_coreid = Ipc_Receive_Core1,
};

IPC 使用情况

instance0

Instance	Channel	receive core id	Description
instance0	0	Ipc_Receive_Core1	CAN Reserve
instance0	1	Ipc_Receive_Core1	CAN Reserve
instance0	2	Ipc_Receive_Core1	CAN Reserve
instance0	3	Ipc_Receive_Core1	CAN9
instance0	4	Ipc_Receive_Core1	CAN5
instance0	5	Ipc_Receive_Core1	CAN Reserve
instance0	6	Ipc_Receive_Core1	CAN6
instance0	7	Ipc_Receive_Core1	CAN Reserve

instance1

Instance	Channel	receive core id	Description
instance1	0	Ipc_Receive_Core0	Regulatory Reserve
instance1	1	Ipc_Receive_Core0	Regulatory Reserve
instance1	2	Ipc_Receive_Core0	Regulatory Reserve
instance1	3	Ipc_Receive_Core0	Regulatory Reserve
instance1	4	Ipc_Receive_Core0	Regulatory Reserve
instance1	5	Ipc_Receive_Core0	Regulatory Reserve
instance1	6	Ipc_Receive_Core0	Regulatory Reserve
instance1	7	Ipc_Receive_Core0	Regulatory Reserve

instance2

Instance	Channel	receive core id	Description
instance2	0	Ipc_Receive_Core0	Regulatory Reserve
instance2	1	Ipc_Receive_Core0	Regulatory Reserve

instance3

Instance	Channel	receive core id	Description
instance3	0	Ipc_Receive_Core0	Crypto Reserve
instance3	1	Ipc_Receive_Core0	Crypto Reserve
instance3	2	Ipc_Receive_Core0	Crypto Reserve
instance3	3	Ipc_Receive_Core0	Crypto Reserve
instance3	4	Ipc_Receive_Core0	Crypto Reserve
instance3	5	Ipc_Receive_Core0	Crypto Reserve
instance3	6	Ipc_Receive_Core0	Crypto Reserve
instance3	7	Ipc_Receive_Core0	Crypto Reserve

instance4

Instance	Channel	receive core id	Description
instance4	0	Ipc_Receive_Core0	CAN Reserve （MCU2）
instance4	1	Ipc_Receive_Core0	CAN Reserve （MCU2）
instance4	2	Ipc_Receive_Core0	CAN Reserve （MCU2）
instance4	3	Ipc_Receive_Core0	CAN Reserve （MCU2）
instance4	4	Ipc_Receive_Core0	CAN Reserve （MCU2）
instance4	5	Ipc_Receive_Core0	CAN Reserve （MCU2）
instance4	6	Ipc_Receive_Core0	CAN Reserve （MCU2）
instance4	7	Ipc_Receive_Core0	CAN Reserve （MCU2）

instance5

Instance	Channel	receive core id	Description
instance5	0	Ipc_Receive_Core0	RTC驱动
instance5	1	Ipc_Receive_Core0	RTC驱动
instance5	2	Ipc_Receive_Core0	RTC驱动
instance5	3	Ipc_Receive_Core0	RTC驱动
instance5	4	Ipc_Receive_Core0	RTC驱动
instance5	5	Ipc_Receive_Core0	RTC驱动
instance5	6	Ipc_Receive_Core0	RTC驱动
instance5	7	Ipc_Receive_Core0	RTC驱动

instance6

Instance	Channel	receive core id	Description
instance6	0	Ipc_Receive_Core0	客户预留：Reserve
instance6	1	Ipc_Receive_Core0	客户预留：Reserve
instance6	2	Ipc_Receive_Core0	客户预留：Reserve
instance6	3	Ipc_Receive_Core0	客户预留：Reserve
instance6	4	Ipc_Receive_Core0	客户预留：Reserve
instance6	5	Ipc_Receive_Core0	客户预留：Reserve
instance6	6	Ipc_Receive_Core0	客户预留：Reserve
instance6	7	Ipc_Receive_Core0	客户预留：Reserve

instance7

Instance	Channel	receive core id	Description
instance7	0	Ipc_Receive_Core1	IpcBox runcmd
instance7	1	Ipc_Receive_Core1	IpcBox UART
instance7	2	Ipc_Receive_Core1	IpcBox SPI
instance7	3	Ipc_Receive_Core1	IpcBox I2C
instance7	4	Ipc_Receive_Core1	IpcBox 预留
instance7	5	Ipc_Receive_Core1	IpcBox 预留
instance7	6	Ipc_Receive_Core1	IpcBox 预留
instance7	7	Ipc_Receive_Core1	IpcBox 预留

instance8

Instance	Channel	Function	Description
instance8	0	Ipc_Receive_Core0	Reserve
instance8	1	Ipc_Receive_Core0	Reserve
instance8	2	Ipc_Receive_Core0	Reserve
instance8	3	Ipc_Receive_Core0	Reserve
instance8	4	Ipc_Receive_Core0	Reserve
instance8	5	Ipc_Receive_Core0	Reserve
instance8	6	Ipc_Receive_Core0	Reserve
instance8	7	Ipc_Receive_Core0	Crypto Reserve

应用sample

提示

所运行的应用程序sample均运行于Acore侧，并与MCU1进行通信，因此在使用前需运行MCU1的系统.

运行方式: MCU1启动步骤

IpcBox功能介绍

IpcBox基于MCU侧的IPC通信框架增加的应用扩展，用于管理外设的透传功能，其实现框图如下：各个外设通过统一的接口接入IpcBox中进行管理，简单来说就是外设数据经过IPC Box进行转发，并返回给Acore侧，同理Acore侧的数据通过IpcBox进行转发，并操作实际的外设，其数据流认为：Acore<->IPC<->MCU<->Peri

IPCBOX架构图

提示

配套的Acore侧应用见IPC模块介绍章节。

IpcBox在版本 RDKS100的V4.0.4-Beta -> RDKS100的V4.0.5-Beta 升级过程中进行了一次重构，修改范围包括数据包结构，Ipc通道，透传外设的默认配置，注意MCU侧和Acore侧的版本对应关系。

透传外设数据

实现情况：

项目	实现情况	备注
RunCmd	已实现	无
SPI	已实现	无
I2C	已实现	无
Uart	已实现	固定使用Uart5

协议包解析

在一般情况下，一共占128字节，可以根据末尾数据域2扩展数据包长度，建议保持128字节，这样在为数据包申请64bytes对齐的内存时，data[]数组仍为64bytes对齐。

typedef struct {
    uint32 magic; // 魔数
    uint32 version; // 版本号
    uint32 checksum; // 校验和
    uint32 length; //数据包总长度
    char cmd[MAX_CMD_LENGTH]; // 数据域1
    uint8 reserve[48]; // 预留
    uint8 data[]; // 数据域2
} IpcBoxPacket_t;

使用方式

由于IpcBox会占用外设资源，所以在开机时，此功能是默认关闭的，如需要使用，请手动打开。打开方式有以下两种：

通过修改MCU SDK中的数组配置,找到对应的外设，将DISABLE改为ENABLE

// Service/HouseKeeping/ipc_box/src/ipc_box.c
static Ipcbox_ComType IpcBox_InstanceMap[] = {
    { IPCBOX_COM_ID_RUNCMD, "runcmd", IpcConf_IpcInstance_IpcInstance_7,
    IpcConf_IpcInstance_7_IpcChannel_0, ENABLE, IPCBOX_PERIID_INVALID,
    IpcBox_RunCmdInit, IpcBox_RunCmdDeinit },
    { IPCBOX_COM_ID_UART, "uart", IpcConf_IpcInstance_IpcInstance_7,
    IpcConf_IpcInstance_7_IpcChannel_1, DISABLE, UART5_CHANNEL,
    IpcBox_UartInit, IpcBox_UartDeinit },
    { IPCBOX_COM_ID_SPI, "spi", IpcConf_IpcInstance_IpcInstance_7,
    IpcConf_IpcInstance_7_IpcChannel_2, DISABLE, IPCBOX_PERIID_INVALID,
    IpcBox_SpiInit, IpcBox_SpiDeinit },
    { IPCBOX_COM_ID_I2C, "i2c", IpcConf_IpcInstance_IpcInstance_7,
    IpcConf_IpcInstance_7_IpcChannel_3, DISABLE, IPCBOX_PERIID_INVALID,
    IpcBox_I2cInit, IpcBox_I2cDeinit },
};

这是临时打开的方式，可以通过MCU1的命令行进行打开，如：

查看外设透传功能使能情况

D-Robotics:/$ ipcbox_set_mode debug
[066378.758965 0]Module: runcmd, Enable
[066378.759240 0]Module: uart, Enable
[066378.759663 0]Module: spi, Enable
[066378.760075 0]Module: i2c, Enable

打开和关闭IpcBox透传uart外设功能

D-Robotics:/$ ipcbox_set_mode uart 1
[066386.990200 0]uart processing enabled
[066386.990487 0]IpcBox_FreeRtos_OsTask_IpcBox_Uart_ASW task is already initialized or running

D-Robotics:/$ ipcbox_set_mode uart 0
[066389.201404 0]uart processing disabled
[066389.267399 0]IpcBox_uart task resources released and terminating
[066389.701820 0]IpcBox_uart task exited properly

打开和关闭IpcBox透传I2C外设功能

D-Robotics:/$ ipcbox_set_mode i2c 1
[066394.631826 0]i2c processing enabled
[066394.632101 0]IpcBox_FreeRtos_OsTask_IpcBox_I2c_ASW task is already initialized or running

D-Robotics:/$ ipcbox_set_mode i2c 0
[066397.082288 0]i2c processing disabled
[066397.085213 0]IpcBox_i2c task resources released and terminating
[066397.087215 0]IpcBox_i2c task exited properly

打开和关闭IpcBox透传SPI外设功能

D-Robotics:/$ ipcbox_set_mode spi 1
[066403.227424 0]spi processing enabled
[066403.227699 0]IpcBox_Spi task is already initialized or running

D-Robotics:/$ ipcbox_set_mode spi 0
[066406.388582 0]spi processing disabled
[066406.389522 0]IpcBox_spi task resources released and terminating
[066406.393520 0]IpcBox_spi task exited properly

打印控制

IpcBox模块的打印信息可以动态开关，由ipcbox_loglevel命令控制，

D-Robotics:/$ ipcbox_loglevel help
Usage: loglevel <level|subcommand>
  level: 0=NO_LOG, 1=ERROR, 2=WARN, 3=INFO, 4=DEBUG
  subcommands:
    show - show current log level
    help - show this message

输入ipcbox_loglevel 0后打印最少，输入ipcbox_loglevel 4后打印最多

D-Robotics:/$ ipcbox_loglevel 0
[066736.123326 0]This is an ERROR message

D-Robotics:/$ ipcbox_loglevel 4
[066738.473668 0]Log level changed to 4
[066738.473942 0]This is an ERROR message
[066738.474408 0]This is a WARN message
[066738.474853 0]This is an INFO message
[066738.475309 0]This is a DEBUG message

IpcBox RunCmd的实现

根据Acore端传过来的命令，执行MCU侧的CMD应用，简称RunCmd应用。

各个外设经过IPC Box进行数据转发大同小异，实现原理主要分为以下两个过程：

Acore->Ipc->MCU过程
- Acore向MCU发送数据时触发mcu的中断，在中断的callback中将数据存储到队列中
MCU->Ipc->Acore过程
- MCU存在一个常驻线程，不断的在去读队列中的数据是否为空，若不为空，则校验并解析数据，识别出cmd命令并运行
- freertos的cmd的应用类似于uboot的cmd的命令，通过此方式用户可以很方便的定制化自己的应用，在此场景中，运行的cmd将adc的值读出，再通过ipc返回给Acore

Acore与MCU之间透传Can数据架构图

IpcBox Uart的实现

与Runcmd的实现类似，在此场景中，MCU向Acore发送数据时触发MCU的中断，但并不会使用队列存储

实现原理主要分为以下两个过程：

Acore->Ipc->MCU过程
- Acore向MCU发送数据时触发mcu的中断，在中断解析数据，并通过Uart外设发出
MCU->Ipc->Acore过程
- MCU存在一个常驻线程，不断的调用Uart外设接收数据，当存在数据时，将数据打包，转发到Acore

IpcBox I2c的实现

与Runcmd的实现类似，在此场景中，MCU向Acore发送数据时触发mcu的中断，在中断的callback中将数据存储到队列中，然后通过ipc返回给Acore 实现原理主要分为以下两个过程：

Acore->Ipc->MCU过程
- Acore向MCU发送数据时触发mcu的中断，在中断的callback中将数据存储到队列中
MCU->Ipc->Acore过程
- MCU存在一个常驻线程，不断的在去读队列中的数据是否为空，若不为空，则校验并解析数据
- 根据命令码实现detect/get/set操作。
- 由于Slave设备多样，例如地址宽度和操作步骤不同，所以get/set操作的实现不同，需要客户根据实际场景去实现IpcBox_I2cGetValue和IpcBox_I2cSetValue，这两个API位于Service/HouseKeeping/ipc_box/src/ipc_i2c.c

IpcBox Spi的实现

Acore->Ipc->MCU过程
- Acore向MCU发送数据时触发mcu的中断，在中断的callback中将数据存储到队列中
MCU->Ipc->Acore过程
- MCU存在一个常驻线程，不断的在去读队列中的数据是否为空，若不为空，则校验并解析数据
- 根据命令码执行读写、只读、只写功能，由于Spi是全双工通信，所以只读其实是发送了等长度的无效数据，只写同理

应用程序接口

此部分为MCU侧的IPC接口。

void Ipc_MDMA_Init(Ipc_InstanceConfigType* pConfigPtr, uint32 InstanceId)

Description：Ipc MDMA Init.

Sync/Async: Synchronous
Parameters(in)
    pConfigPtr：the pointer to the device configuration parameter
    InstanceId：InstanceId id
Parameters(inout)
    None
Parameters(out)
    None
Return value：None

void Ipc_MDMA_DeInit(uint32 InstanceId)

Description：Subsystem driver deinitialization function.

Sync/Async: Synchronous
Parameters(in)
    InstanceId：InstanceId id
Parameters(inout)
    None
Parameters(out)
    None
Return value：None

void Ipc_GetVersionInfo(Std_VersionInfoType * versioninfo)

Description：get driver version.

Sync/Async: Synchronous
Parameters(in)
    None
Parameters(inout)
    versioninfo: the pointer to Version Info
Parameters(out)
    None
Return value：None

Std_ReturnType Ipc_MDMA_CheckRemoteCoreReady(uint32 InstanceId)

Description：check whether remote core is ready.

Sync/Async: Synchronous
Parameters(in)
    InstanceId：InstanceId id
Parameters(inout)
    None
Parameters(out)
    None
Return value：Std_ReturnType
    E_OK: remote core is ready
    IPC_E_PARAM_ERROR: param illegal
    IPC_E_DRIVER_NOT_INIT: Driver is not init
    IPC_E_INSTANCE_NOT_READY_ERROR : remote core is Not ready
    IPC_E_CHANNEL_NOT_OPEN: Instance is not open

void Std_ReturnType Ipc_MDMA_SendMsg(uint32 InstanceId, uint32 ChanId, uint32 Size, uint8* Buf, uint32 Timeout)

Description：send message.

Sync/Async: Synchronous
Parameters(in)
    InstanceId: Instance id
    ChanId: channel id
    Size: the size of buf to be sent
    Buf: the pointer to the memory that contains the buf to be sent
    Timeout: timeout(us)
Parameters(inout)
    None
Parameters(out)
    None
Return value：Std_ReturnType
    E_OK: success
    IPC_E_PARAM_ERROR: param is illegal
    IPC_E_DRIVER_NOT_INIT: Driver is not init
    IPC_E_CHANNEL_NOT_OPEN: Instance is not open
    IPC_E_TIMEOUT_ERROR: send timeout
    IPC_E_NO_MEMORY_ERROR: no memory to send buf
    PC_E_CHECKRESERROR: check resource error

提示

dma硬件要求传输地址16字节对齐，buffer应该如下定义，首地址和size16字节对齐: static uint8 attribute((aligned(16))) Ipc_Send_Buf[8192];

Std_ReturnType Ipc_MDMA_PollMsg(uint32 InstanceId)

Description：poll message If the Instance does not receive data using interrupts.

Sync/Async: Synchronous
Parameters(in)
    InstanceId: Instance id
Parameters(inout)
    None
Parameters(out)
    None
Return value：Std_ReturnType
    E_OK: success
    IPC_E_PARAM_ERROR: param is illegal
    IPC_E_DRIVER_NOT_INIT: Driver is not init
    IPC_E_CHANNEL_NOT_OPEN: Instance is not open
    IPC_E_NO_DATA_TO_RECEIVE_ER ROR: No data to be recvived

Std_ReturnType Ipc_MDMA_OpenInstance(uint32 InstanceId)

Description：Open a Instance pointed to by ID.

Sync/Async: Synchronous
Parameters(in)
    InstanceId: Instance id
Parameters(inout)
    None
Parameters(out)
    None
Return value：Std_ReturnType
    E_OK: success
    IPC_E_DRIVER_NOT_INIT: Driver is not init
    IPC_E_CHANNEL_NOT_CLOSE: Instance has been opened
    IPC_E_PARAM_ERROR param is illegal

Std_ReturnType Ipc_MDMA_CloseInstance(uint32 InstanceId)

Description：close a Instance pointed to by ID.

Sync/Async: Synchronous
Parameters(in)
    InstanceId: Instance id
Parameters(inout)
    None
Parameters(out)
    None
Return value：Std_ReturnType
    E_OK: success
    IPC_E_DRIVER_NOT_INIT: Driver is not init
    IPC_E_CHANNEL_NOT_CLOSE: Instance has been opened
    IPC_E_PARAM_ERROR param is illegal

Std_ReturnType Ipc_MDMA_TryGetHwResource(uint32 InstanceId, uint32 ChanId, uint32 BufSize)

Description：try get Hardware resource.

Sync/Async: Synchronous
Parameters(in)
    InstanceId ChanId BufSize: Instance id Chanel Id buf size
Parameters(inout)
    None
Parameters(out)
    None
Return value：Std_ReturnType
    E_OK: success
    IPC_E_DRIVER_NOT_INIT: Driver is not init
    IPC_E_DEVICE_BUSY: Instance is busy.
    IPC_E_MDMA_BUSY: Send MDMA is busy.
    IPC_E_NO_BUF_ERROR: no buffer
    IPC_E_CHANNEL_NOT_OPEN: Instance has been closed

IPC配置相关​

IPC 使用情况​

instance0​

instance1​

instance2​

instance3​

instance4​

instance5​

instance6​

instance7​

instance8​

应用sample​

IpcBox功能介绍​

透传外设数据​

IpcBox RunCmd的实现​

IpcBox Uart的实现​

IpcBox I2c的实现​

IpcBox Spi的实现​

应用程序接口​

void Ipc_MDMA_Init(Ipc_InstanceConfigType* pConfigPtr, uint32 InstanceId)​

void Ipc_MDMA_DeInit(uint32 InstanceId)​

void Ipc_GetVersionInfo(Std_VersionInfoType * versioninfo)​

Std_ReturnType Ipc_MDMA_CheckRemoteCoreReady(uint32 InstanceId)​

void Std_ReturnType Ipc_MDMA_SendMsg(uint32 InstanceId, uint32 ChanId, uint32 Size, uint8* Buf, uint32 Timeout)​

Std_ReturnType Ipc_MDMA_PollMsg(uint32 InstanceId)​

Std_ReturnType Ipc_MDMA_OpenInstance(uint32 InstanceId)​

Std_ReturnType Ipc_MDMA_CloseInstance(uint32 InstanceId)​

Std_ReturnType Ipc_MDMA_TryGetHwResource(uint32 InstanceId, uint32 ChanId, uint32 BufSize)​