MCUSW
Cdd Ipc User Guide

Introduction

This document details Cdd Ipc module implementations

  • Supported AUTOSAR Release : 4.3.1
  • Supported Configuration Variants : Pre-Compile
  • Vendor ID : CDD_IPC_VENDOR_ID (44)
  • Module ID : CDD_MODULE_ID (255)

Cdd Ipc modules allows core hosting MCAL/AUTOSAR to communicate with other cores (processing entities, with-in SoC) hosting PDK based IPC driver as well as HLOS Linux IPC driver. This driver could be used to transmit and receive variable length messages between cores, via logical communication channel ID's. Can be mapped to Sender-Receiver AUTOSAR interface, for data oriented communication between core that host AUTOSAR / NON AUTOSAR processing entities.

Some of key points to note

  1. Can inter-operate with MCU+SDK IPC and Linux IPC drivers for J722s variants.
  2. Ipc notify is not supported.
  3. Relies on shared memory (message would be copied into shared area and destination core notified, the destination core would read this message)
  4. Not configurable (via Cdd Ipc configuration parameters) to use different mailbox, FIFO & user
  5. Interrupt are used, to signal presence of new message destined to this core
  6. For a given channel local and remote endpoint pair is formed.
  7. In case of communication with Linux, remote endpoint is not published upfront, hence it is cached everytime a message a received.

Cdd Driver Architecture/Design

Please refer the Cdd IPC design page, which is part of CSP.[2]


Functional Description

As depicted in architecture figure below, Cdd Ipc implementation relies on mailbox, shared memory to transport messages between cores. The shared memory & other associated memories are provided via the configurator, Refer [Shared Memory Configuration] (Refer to Design Document provided in CSP) for details.

It's recommended to not change the recommended configuration for these parameters, unless the user comprehends methods to change memory location (and/or size) of the shared memory.

Communication Channel

A communication channel provides a logical communication channel between two processors. Identified uniquely by an un-signed sequential integer, represented by configurator defined [symbolic name] (Refer to Design Document provided in CSP).

  • Refer for Baremetal/NORTOS Application (SDK Install Directory)/mcusw.xx.yy.zz.bb/mcal_drv/mcal/examples_config/CddIpc_Demo_Cfg/output/generated/include/Cdd_IpcCfg.h for the generated communication channel identifiers.
  • Refer for Linux Application (SDK Install Directory)/mcusw.xx.yy.zz.bb/mcal_drv/mcal/examples_config/CddIpcLinux_Demo_Cfg/output/generated/include/Cdd_IpcCfg.h for the generated communication channel identifiers

There could be multiple unique communication channel between any given 2 cores.

End Point

There are two primary identifiers, identifying the end-points for a core. This is used by the driver to identify the source / destination of a message.

  • LocalEp : An unique, non-repetitive integer on the core that hosts MCAL/AUTOSAR
  • RemoteProcId : An unique processor identifiers, which determines the core that this communication channel is associated with (i.e. to be able to send and receive message to / from that core)
  • RemoteEp : An unique, non-repetitive integer on the remote core

Notes on EndPoints

  1. Shall be unique on a core (either local or remote cores)
  2. Need not be same i.e. localEp = X and remoteEp = Y, is a valid
  3. A communication channel shall have unique end-points, i.e. localEp shall be unique and on remote cores, remoteEp shall be unique

Buffer for each channel

  • MaxNumMsgQueued : Number of messages that could potentially be received & queued in the driver before, these messages could be received by applications
  • MaxMsgSize : Size of the largest message that could be received The MaxNumMsgQueued & MaxMsgSize is used to determine the memory reserved by the driver. The memory is reserved in (SDK Install Directory)/mcusw.xx.yy.zz.bb/mcal_drv/mcal/examples_config/CddIpc_Demo_Cfg/output/generated/src/Cdd_IpcCfg.c with variable (s) Cdd_IpcCommChBuf_<Channel ID>

Message reception process

  • Remote core sends a message
  • An interrupt occurs on the host core (On which MCAL AUTOSAR code is running)
  • Checks MBOX_IRQSTATUS_RAW register (BASE_ADDR + 0x100 + (n*16U)), corresponding mailbox bit is set if there is a message in MBOX.
  • Checks MBOX_MSGSTATUS register (BASE_ADDR + 0xC0 + (n*4U)), gives the number of messages available in MBOX.
  • Reads MBOX_MSG register (BASE_ADDR + 0x40 + (n*4U)), gives message written in MBOX. Transmitting core usually writes the remote core ID (core meant for message reception).
  • Clear interrupt by writing 1 to MBOX_IRQSTATUS_CLR (BASE_ADDR + 0x104 + (n*16U)) registers corresponding bit.
  • Read the actual message written in VRING.

Message transmission process

  • Write actual message to VRING.
  • Check if FIFO of specific MBOX is not already full in MBOX_FIFOSTATUS register (BASE_ADDR + 0x80 + (n*4U)), if FIFO is full bit 0 will be set else it will be cleared.
  • Write a message in MBOX via MBOX_MSG register (BASE_ADDR + 0x40 + (n*4U)), usually remote core ID is written (core meant for message reception).

Control End Point

The demo application by default uses control channel/Announce API's to notify remote cores of service availability. This feature could be turned OFF Refer for steps to turn OFF It is an endpoint which can be used to send or receive control messages, primarily used by Announce API�s to notify remote cores about the availability of service.

Back To Top



Configuration

The design document details the various configurable parameters of this implementation, please refer section Configurator of [2] (Refer to Design Document provided in CSP)

Note: For detailed descriptions of all configurable parameters, refer to the design document provided in the CSP package. The document is located at: "$(MCAL_INSTALL_PATH)/mcusw/csp"

Back To Top



Non Standard Service APIs


Cdd_IpcRegisterReadBack

As noted from the previous MCAL implementation, some of the critical configuration registers could potentially be corrupted by other entities (s/w or h/w). One of the recommended detection methods would be to periodically read-back the configuration and confirm configuration is consistent. The service API defined below shall be implemented to enable this detection

Description Comments
Service Name Cdd_IpcRegisterReadBack Can potentially be turned OFF (Refer to Design Document provided in CSP)
Syntax uint32 Cdd_IpcRegisterReadBack ( uint32 remoteProcId, P2VAR(Cdd_IpcRegRbValues, AUTOMATIC, CDD_APP_DATA) pRegArgs) E_OK: Register read back has been done, E_NOT_OK: Register read back failed
Service ID NA
Sync / Async Sync
Reentrancy Reentrant
Parameter in remoteProcId Remote Processor ID.
Parameters out pRegArgs - Pointer to where to store the readback values. If this pointer is NULL_PTR, then the API will return E_NOT_OK.
Return Value Std_ReturnType E_OK, E_NOT_OK

Cdd_IpcGetMailboxStatus

Service to get Mailbox state is FULL or not

Description Comments
Service Name Cdd_IpcGetMailboxStatus Service to get Mailbox state is FULL or not
Syntax uint32 Cdd_IpcGetMailboxStatus(uint32 chId) E_OK: Register read back has been done, E_NOT_OK: Register read back failed
Service ID CDD_IPC_SID_MAILBOX_STATE
Sync / Async Sync
Reentrancy Reentrant
Parameter in remoteProcId Remote ID.
Parameters out None
Return Value uint32 Returns the mailbox state

Back To Top


Power-up

The driver doesn't configure the functional clock and power for the Mailbox module. It is expected that the Secondary Bootloader (SBL) powers up the required modules. Please refer SBL documentation.

Note that, this implementation will NOT reset the Mailbox. Un Expected/stale messages could be delivered by the driver. It's recommended to drain stale messages before announcing the availability via service API Cdd_IpcAnnounce () if enabled.

Back To Top


To run the CddIpcRprocLinuxApp on mcu0_0

  1. Download and install the Linux installer
  2. Partition and flash the SD card using the below mentioned steps
    • SD CARD PREPARATION : Flash the above tisdk-default-wic-image on the SD card.
  3. Navigate to ${SD_CARD_PATH}/root/lib/firmware/ti-ipc/j722s
    • Remove ipc_echo_test_mcu2_0_release_strip.xer5f and move the cdd_ipc_app_rc_linux_mcu0_0_release_strip.xer5f
    • Rename the cdd_ipc_app_rc_linux_mcu0_0_release_strip.xer5f file to ipc_echo_test_mcu2_0_release_strip.xer5f
    • Remove the old symbolic firmware link for mcu0_0 in $SD_CARD_PATH/root/lib/firmware with rm root/lib/firmware/j722s-mcu-r5f0_0-fw
    • Recreate the symbolic link with the new firmware for J722S by sudo ln -s root/lib/firmware/ti-ipc/j722s/ipc_echo_test_mcu2_0_release_strip.xer5f j722s-mcu-r5f0_0-fw
    • Once the application core is booted, log in with username root.
    • Run "rpmsg_char_simple -r 0 -n 10" and "modprobe rpmsg_client_sample count=10" command to view the communication logs with all remote cores. Please refer the SOC user manual for cdd_ipc_app.

Back To Top


Build MCAL example application for Jacinto_plus_SDK variants

The MCAL example application could be built with the command

J722S

$ cd (SDK Install Directory)/mcusw.xx.yy.zz.bb/build
$ gmake -s cdd_ipc_app BOARD=j722s_evm SOC=j722s BUILD_PROFILE=release CORE=mcu0_0 BUILD_OS_TYPE=baremetal
$ OR
$ gmake -s cdd_ipc_app BOARD=j722s_evm SOC=j722s BUILD_PROFILE=debug CORE=mcu0_0 BUILD_OS_TYPE=baremetal
  • The generated executable is available at
    • (SDK Install Directory)/mcusw.xx.yy.zz.bb/binary/cdd_ipc_app/bin/(SoC)_evm/cdd_ipc_app_mcu0_0_(BUILD_PROFILE).xer5f
    • e.g. (SDK Install Directory)/mcusw.xx.yy.zz.bb/binary/cdd_ipc_app/bin/j722s_evm/cdd_ipc_app_mcu0_0_release.xer5f

Build for DMR5/WakeUp remote core example application

The remote core application implementation is available at

  • (SDK Install Directory)/mcu_plus_sdk_j722s_xx_yy_zz/examples/drivers/ipc/ipc_rpmsg_echo/j722s-evm/wkup-r5fss0-0/.
    please ensure that gmake is avaible in the mentioned path.

J722S

The DMR5 remote core example application could be built with the command

$ cd (SDK Install Directory)/mcu_plus_sdk_j722s_xx_yy_zz/examples/drivers/ipc/ipc_rpmsg_echo/j722s-evm/wkup-r5fss0-0/ti-arm-clang
$ gmake -s syscfg-gui
// Select IPC and make sure PDK IPC is checked. Save (ctrl + s) and close gui
$ gmake -s all

Note:
- Comment/remove the IpcNotify_syncAll API's from the path (SDK Install Directory)/mcu_plus_sdk_j722s_xx_yy_zz/examples/drivers/ipc/ipc_rpmsg_echo/ipc_rpmsg_echo.c.
  - Make sure to change gMainCoreID and gRemoteCoreId to correct ones. MCUR5 is main core and WKUP R5 is in the remote core list.
- Vring address and Vring size should match with host and remote application.
  • The generated executable is available at
    • e.g. (SDK Install Directory)/mcu_plus_sdk_j722s_xx_yy_zz/examples/drivers/ipc/ipc_rpmsg_echo/j722s-evm/wkup-r5fss0-0/ti-arm-clang/ipc_rpmsg_echo.release.out

Back To Top


Steps to run CDD_IPC example application

Running the CDD_IPC example application via CCS

J722S

steps to run


  • Remote cores on these devices are Wakeup Core, so it needs to be started by the SBL. It cannot be loaded through CCS
  • One way to run this is using default_sbl_null.cfg or default_sbl_null_hs_fs.cfg (depending on device type) and change the default hello world DM image to ipc_rpmsg_echo.release.appimage.
  • Then you can use CCS normally, connect to MCUR5 core, and load MCAL cdd_ipc_app to run it. Output will be shown.
  • Please view this mcu+sdk page for working with DMR5/WKUPR5/ core. This section of the AM62PX page will work for J722S

Memory Mapping

Various objects of this implementation (e.g. variables, functions, constants) are defined under different sections. The linker command file at (Examples Linker File (Select memory location to hold example binary)) defines separate section for these objects. When the driver is integrated, it is expected that these sections are created and placed in appropriate memory locations. (Locations of these objects depend on the system design and performance needs)

Section CDD_IPC_CODE CDD_IPC_VAR CDD_IPC_VAR_NOINIT CDD_IPC_CONST CDD_IPC_CONFIG
CDD_IPC_DATA_NO_INIT_UNSPECIFIED_SECTION (.data) USED
CDD_IPC_DATA_INIT_32_SECTION USED
CDD_IPC_TEXT_SECTION USED
CDD_IPC_DATA_NO_INIT_8_SECTION USED
CDD_IPC_CONFIG_SECTION USED
CDD_IPC_ISR_TEXT_SECTION USED
CDD_IPC_CONFIG_SECTION USED

Back To Top


Dependencies on SW Modules


DET

This implementation depends on the DET in order to report development errors and can be turned OFF. Refer to the Development Error Reporting section for detailed error codes.

Back To Top


SchM

This implementation requires 1 level of exclusive access to guard critical sections. Invokes SchM_Enter_Cdd_Ipc_IPC_EXCLUSIVE_AREA_0(), SchM_Exit_Cdd_Ipc_IPC_EXCLUSIVE_AREA_0() to enter critical section and exit.

In the example implementation (SchM_Cdd_Ipc.c), all the interrupts on CPU are disabled. However, disabling of the enabled Mailbox related interrupts should suffice.

Back To Top


File Structure

Cdd Ipc File Structure

  • Driver implemented by: Cdd_Ipc.c, Cdd_IpcIrq.c & Cdd_IpcPriv.h core driver files
  • Example Configuration by: Cdd_IpcCfg.c and Cdd_IpcCfg.h
  • Example Application by: CddIpcApp.c & CddIpcApp.h
  • Remote Core Application by: main_rtos.c, ipc_utils.c

Back To Top


Customizing Examples Application


Turn OFF Use Of Control End Point

IPC demo applications use atleast 2 applications running on 2 different cores. Namely ipc_remote_app & cdd_ipc_app OR cdd_ipc_profile_app , these two applications would have to be re built when this features requires to be turned OFF

  1. Update MCAL configuration
    1. Example Application
      1. The configuration used by this application is present in (SDK Install Directory)/mcusw/mcal_drv/mcal/examples_config/CddIpc_Demo_Cfg/output/generated/soc/(SOC)/mcu1_0
        • OR Incase application is being hosted on MCU 2 1 (SDK Install Directory)/mcusw/mcal_drv/mcal/examples_config/CddIpc_Demo_Cfg/output/generated/soc/(SOC)/mcu2_1
      2. The configuration used by this application in case of am62x is present in host R5F (SDK Install Directory)/mcusw/mcal_drv/mcal/examples_config/CddIpc_Demo_Cfg/output/generated/soc/am62x/mcu0_0
        1. The configuration used by this application in case of am62ax is present in host MCU R5FSS 0 0 (SDK Install Directory)/mcusw/mcal_drv/mcal/examples_config/CddIpc_Demo_Cfg/output/generated/soc/am62ax/mcu0_0
      3. The configuration used by this application in case of am62px is present in host MCU R5FSS 0 0 (SDK Install Directory)/mcusw/mcal_drv/mcal/examples_config/CddIpc_Demo_Cfg/output/generated/soc/am62px/mcu0_0
        1. Update the configurator to TURN OFF as show below
      4. Regenerate the configuration and copy the same into location specified above
      5. Alternately
        1. Set the macro CDD_IPC_ANNOUNCE_API to STD_OFF in Cdd_IpcCfg.h
        2. Re compile the MCAL demo application User Guide
    2. Profiling Application
      1. Update Remote Application configuration

Back To Top


Error Handling


Development Error Reporting

Development errors are reported to the DET using the service Det_ReportError(), when enabled. The driver interface files (Cdd_IpcCfg.h shown in the driver directory structure of the File Structure section)

Refer Design Document for detailed [Error Codes] (Refer to Design Document provided in CSP)

Back To Top


Error codes

Production error are reported to DET via Det_ReportError(). Only the error codes in the Cdd Ipc driver specifications are reported which are listed in [] (Refer to Design Document provided in CSP) Back To Top


API Description

The AUTOSAR BSW Eth Driver specification details the APIs [[2] (Refer to Design Document provided in CSP)]

Back To Top


Example Application

Flow Chart

The flow chart below depicts the demo application

  • ipc_remote_app_mpu1_0_release.xa53fg would be hosted on Remote Core (MPU 1 0)
  • cdd_ipc_app_mcu1_0_release.xer5f would be hosted on Local Core (MCU 1 0)
  • ipc_rpmsg_echo.release.out would be hosted on Remote Core (M4)
  • cdd_ipc_app_mcu0_0_release.xer5f would be hosted on Local Core (R5F)

Back To Top


Example Logs

J722S MCU_R5 to A53 Example Logs

    1. LINUX TERMINAL LOGS
         
    root@j722s-evm:~# rpmsg_char_simple -r 0 -n 10
    Created endpt device rpmsg-char-0-699, fd = 4 port = 1025
    Exchanging 10 messages with rpmsg device ti.ipc4.ping-pong on rproc id 0 ...

    Sending message #0: hello there 0!
    Receiving message #0: hello there 0!
    Sending message #1: hello there 1!
    Receiving message #1: hello there 1!
    Sending message #2: hello there 2!
    Receiving message #2: hello there 2!
    Sending message #3: hello there 3!
    Receiving message #3: hello there 3!
    Sending message #4: hello there 4!
    Receiving message #4: hello there 4!
    Sending message #5: hello there 5!
    Receiving message #5: hello there 5!
    Sending message #6: hello there 6!
    Receiving message #6: hello there 6!
    Sending message #7: hello there 7!
    Receiving message #7: hello there 7!
    Sending message #8: hello there 8!
    Receiving message #8: hello there 8!
    Sending message #9: hello there 9!
    Receiving message #9: hello there 9!

    Communicated 10 messages successfully on rpmsg-char-0-699

    TEST STATUS: PASSED
    root@j722s-evm:~# modprobe rpmsg_client_sample count=10
    [   93.561808] rpmsg_client_sample virtio0.ti.ipc4.ping-pong.-1.13: new channel: 0x401 -> 0xd!
    [   93.570354] rpmsg_client_sample virtio2.ti.ipc4.ping-pong.-1.13: new channel: 0x401 -> 0xd!
    [   93.570358] rpmsg_client_sample virtio0.ti.ipc4.ping-pong.-1.13: incoming msg 1 (src: 0xd)
    [   93.570567] rpmsg_client_sample virtio0.ti.ipc4.ping-pong.-1.13: incoming msg 2 (src: 0xd)
    [   93.579001] rpmsg_client_sample virtio1.ti.ipc4.ping-pong.-1.13: new channel: 0x401 -> 0xd!
    [   93.587086] rpmsg_client_sample virtio2.ti.ipc4.ping-pong.-1.13: incoming msg 1 (src: 0xd)
    [   93.612028] rpmsg_client_sample virtio0.ti.ipc4.ping-pong.-1.13: incoming msg 3 (src: 0xd)
    [   93.620325] rpmsg_client_sample virtio1.ti.ipc4.ping-pong.-1.13: incoming msg 1 (src: 0xd)
    root@j722s-evm:~# [   93.628624] rpmsg_client_sample virtio2.ti.ipc4.ping-pong.-1.13: incoming msg 2 (src: 0xd)
    [   93.638620] rpmsg_client_sample virtio0.ti.ipc4.ping-pong.-1.13: incoming msg 4 (src: 0xd)
    [   93.646920] rpmsg_client_sample virtio1.ti.ipc4.ping-pong.-1.13: incoming msg 2 (src: 0xd)
    [   93.655222] rpmsg_client_sample virtio1.ti.ipc4.ping-pong.-1.13: incoming msg 3 (src: 0xd)
    [   93.663504] rpmsg_client_sample virtio2.ti.ipc4.ping-pong.-1.13: incoming msg 3 (src: 0xd)
    [   93.671782] rpmsg_client_sample virtio0.ti.ipc4.ping-pong.-1.13: incoming msg 5 (src: 0xd)
    [   93.680075] rpmsg_client_sample virtio1.ti.ipc4.ping-pong.-1.13: incoming msg 4 (src: 0xd)
    [   93.688365] rpmsg_client_sample virtio1.ti.ipc4.ping-pong.-1.13: incoming msg 5 (src: 0xd)
    [   93.696644] rpmsg_client_sample virtio2.ti.ipc4.ping-pong.-1.13: incoming msg 4 (src: 0xd)
    [   93.704921] rpmsg_client_sample virtio0.ti.ipc4.ping-pong.-1.13: incoming msg 6 (src: 0xd)
    [   93.713204] rpmsg_client_sample virtio1.ti.ipc4.ping-pong.-1.13: incoming msg 6 (src: 0xd)
    [   93.721494] rpmsg_client_sample virtio1.ti.ipc4.ping-pong.-1.13: incoming msg 7 (src: 0xd)
    [   93.729779] rpmsg_client_sample virtio2.ti.ipc4.ping-pong.-1.13: incoming msg 5 (src: 0xd)
    [   93.738074] rpmsg_client_sample virtio0.ti.ipc4.ping-pong.-1.13: incoming msg 7 (src: 0xd)
    [   93.746367] rpmsg_client_sample virtio1.ti.ipc4.ping-pong.-1.13: incoming msg 8 (src: 0xd)
    [   93.754657] rpmsg_client_sample virtio1.ti.ipc4.ping-pong.-1.13: incoming msg 9 (src: 0xd)
    [   93.762947] rpmsg_client_sample virtio2.ti.ipc4.ping-pong.-1.13: incoming msg 6 (src: 0xd)
    [   93.771229] rpmsg_client_sample virtio0.ti.ipc4.ping-pong.-1.13: incoming msg 8 (src: 0xd)
    [   93.779514] rpmsg_client_sample virtio1.ti.ipc4.ping-pong.-1.13: incoming msg 10 (src: 0xd)
    [   93.787871] rpmsg_client_sample virtio1.ti.ipc4.ping-pong.-1.13: goodbye!
    [   93.794677] rpmsg_client_sample virtio2.ti.ipc4.ping-pong.-1.13: incoming msg 7 (src: 0xd)
    [   93.802956] rpmsg_client_sample virtio0.ti.ipc4.ping-pong.-1.13: incoming msg 9 (src: 0xd)
    [   93.811251] rpmsg_client_sample virtio2.ti.ipc4.ping-pong.-1.13: incoming msg 8 (src: 0xd)
    [   93.819536] rpmsg_client_sample virtio0.ti.ipc4.ping-pong.-1.13: incoming msg 10 (src: 0xd)
    [   93.827887] rpmsg_client_sample virtio0.ti.ipc4.ping-pong.-1.13: goodbye!
    [   93.834753] rpmsg_client_sample virtio2.ti.ipc4.ping-pong.-1.13: incoming msg 9 (src: 0xd)
    [   93.843129] rpmsg_client_sample virtio2.ti.ipc4.ping-pong.-1.13: incoming msg 10 (src: 0xd)
    [   93.851539] rpmsg_client_sample virtio2.ti.ipc4.ping-pong.-1.13: goodbye!

J722S CDD_IPC MCUR5F to DMR5 Example Logs

    [MCU_Cortex_R5_1]  
    CDD_IPC_APP : CDD IPC MCAL Version Info
    CDD_IPC_APP :---------------------
    CDD_IPC_APP : Vendor ID           : 44
    CDD_IPC_APP : Module ID           : 255
    CDD_IPC_APP : SW Major Version    : 10
    CDD_IPC_APP : SW Minor Version    : 0
    CDD_IPC_APP : SW Patch Version    : 1
    
    CDD_IPC_APP :
    CDD_IPC_APP : Sample Application - STARTS !!! 
    first ping sent to all cores

    ping sent to all cores

    inside loop for WKUPR5FSS0_0 remote core rec msg

    CDD_IPC_APP : Received ping 10 Iteration 10 from WKUPR5FSS0_0
    inside loop for WKUPR5FSS0_0 remote core rec msg

    CDD_IPC_APP : Received ping 9 Iteration 9 from WKUPR5FSS0_0
    inside loop for WKUPR5FSS0_0 remote core rec msg

    CDD_IPC_APP : Received ping 8 Iteration 8 from WKUPR5FSS0_0
    inside loop for WKUPR5FSS0_0 remote core rec msg

    CDD_IPC_APP : Received ping 7 Iteration 7 from WKUPR5FSS0_0
    inside loop for WKUPR5FSS0_0 remote core rec msg

    CDD_IPC_APP : Received ping 6 Iteration 6 from WKUPR5FSS0_0
    inside loop for WKUPR5FSS0_0 remote core rec msg

    CDD_IPC_APP : Received ping 5 Iteration 5 from WKUPR5FSS0_0
    inside loop for WKUPR5FSS0_0 remote core rec msg

    CDD_IPC_APP : Received ping 4 Iteration 4 from WKUPR5FSS0_0
    inside loop for WKUPR5FSS0_0 remote core rec msg

    CDD_IPC_APP : Received ping 3 Iteration 3 from WKUPR5FSS0_0
    inside loop for WKUPR5FSS0_0 remote core rec msg

    CDD_IPC_APP : Received ping 2 Iteration 2 from WKUPR5FSS0_0
    inside loop for WKUPR5FSS0_0 remote core rec msg

    CDD_IPC_APP : Received ping 1 Iteration 1 from WKUPR5FSS0_0
    CDD_IPC_APP : Transmitted and Received 10 times
    CDD_IPC_APP : All tests have passed !!!


    //In a Different UART Terminal
    [IPC RPMSG ECHO] Remote Core waiting for messages from main core ... !!!
    [IPC RPMSG ECHO] Received and echoed 10 messages ... !!!
    All tests have passed!!

Back To Top


References

Sl No Specification Comment / Link
1 AUTOSAR 4.3.1 AUTOSAR Specification for CDD Driver & Integration Intranet Link

Back To Top