• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 373 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TDA4VM: unable to create Tx channel for MCU1_0

Darshana Deore
Prodigy 100 points
Part Number: TDA4VM

I wanted to build the IPC example between main(A72->linux) to MCU (MCU1_0->tirtos)

I used 7.1 sdk. in main side try to buld the  app_ipc application-> vision_apps/make vx_arm_linux_ipc.out 

 and  in MCU side build the cddipcprocLinux in mcusw/build/sudo make cdd_ipc_profile_app_rc_linux_int BUILD_OS_TYPE=tirtos CORE=mcu1_0

I just wanted to transmit msg from A72 to MCU1_0 so that i make some changes like make yes for BUILD_CPU_MCU1_0 and make IPC ENABLE for MCU1_0

      1) vision_apps/vision_apps_build_flags.mak --->

BUILD_CPU_MPU1?=yes
BUILD_CPU_MCU1_0?=yes
BUILD_CPU_MCU2_0?=yes
BUILD_CPU_MCU2_1?=yes
BUILD_CPU_MCU3_0?=no
BUILD_CPU_MCU3_1?=no
BUILD_CPU_C6x_1?=yes
BUILD_CPU_C6x_2?=yes
BUILD_CPU_C7x_1?=yes

        2)vision_apps/apps/basic_demos/app_tirtos/common/app_cfg.h

#define ENABLE_TIOVX
#define ENABLE_IPC
#define ENABLE_PRINTF_REDIRECT

#define ENABLE_IPC_MPU1_0
#define ENABLE_IPC_MCU1_0

Then i follow the steps:

  •  cd PSDKLA_INTALL_PATH
    1) make u-boot-r5_clean
    2) make u-boot-a72_clean
    3) make u-boot-r5
    4)make u-boot-a72
     Replace the tiboot3.bin, tispl.bin and u-boot.img in the SD card BOOT/
  •  Copy the MCU1_0 firmware in the rootfs/lib/firmware
    cp mcusw/binary/can_profile_app/bin/j721e_evm/can_profile_app_mcu1_0_realease.xer5f  SD_CARD/rootfs/lib/firmware/j7-mcu-r5f0_0-fw

i followed the proper step for uboot image and check the logs then same problem occur for mcu1_0 like unable to create Tx channel for MCU1_0

Logs--->

./vx_app_linux_arm_ipc.out

APP: Init ... !!!
MEM: Init ... !!!
MEM: Initialized DMA HEAP (fd=4) !!!
MEM: Init ... Done !!!
enabled cpu mpu1_0...!!!
enabled cpu mcu1_0...!!!
IPC: Init ... !!!
In appIpcCreateTxCh...!!!
_rpmsg_char_find_ctrldev: could not find the matching rpmsg_ctrl device for virtio2.rpmsg_chrdev.-1.13
rproc_id: 0 remote_endpt: 13 eptdev_name:rpmsg-char-0-1013
IPC: mcu1_0 : rpmsg local endpt is -1

IPC: Init ... Done !!!
APP: ERROR: IPC init failed !!!

  rpmsg char driver is initialised by kernel and it creates a userspace /dev entry for each remote rpmsg_chrdev service  so please give me proper solution and steps to solved the following issue---->

 _rpmsg_char_find_ctrldev: could not find the matching rpmsg_ctrl device for virtio2.rpmsg_chrdev.-1.13   ---> how i solved this issue

  • 0
    TI__Guru** 112125 points

    Hi Darshana,

    The vx_arm_linux_ipc.out executable is designed to work with the Vision Apps firmwares. You cannot mix and match Vision Apps executable with regular PDK IPC example firmwares or MCUSW firmwares. Both have very different memory maps.

    If using vx_arm_linux_ipc_out executable, stick to Vision Apps firmware, you should be able to run the test.

    Also, is there a reason you still need to use 7.1 SDK? Can you move to a more latest SDK version? 

    regards

    Suman