• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 691 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.

Original question:

TDA4VM: IPC initialization errors

TDA4VM: TDA4VM: IPC initialization errors

user5113467
Intellectual 610 points
Part Number: TDA4VM

After upgrading to PSDKRA 6.02 and PSDKLA 6.02, I am able to boot into the linux shell and run the vision app initialization script, but when I attempt to run a vision app I get the following IPC errors:

APP: Init ... !!!
APP_LOG: Mapping 0xac000000 ...
APP_LOG: Mapped 0xac000000 -> 0xffffb3640000 of size 262144 bytes
MEM: Init ION ... !!!
MEM: Initialized ION (fd=4) !!!
MEM: Init ION ... Done !!!
IPC: Init ... !!!
APP_LOG: Mapping 0xac040000 ...
APP_LOG: Mapped 0xac040000 -> 0xffffb16a0000 of size 33161216 bytes
APP_LOG: Mapping 0x30e00000 ...
APP_LOG: Mapped 0x30e00000 -> 0xffffb3b30000 of size 3072 bytes
rproc_device_find_for_name: could not open virtio node directory for r5f-main-0-core-1
IPC: ERROR: Unable to find rproc_device for rproc CPU [r5f-main-0-core-1]
IPC: ERROR: Unable to create TX channels for CPU [mcu2_1] !!!
IPC: ERROR: All local endpoints MUST be the same value, mismatch for CPU [mcu2_1] local endpt -1 != excpected local endpt 1024 !!!
IPC: Init ... Done !!!
APP: ERROR: IPC init failed !!!
REMOTE_SERVICE: Init ... !!!
rproc_device_find_for_name: could not open virtio node directory for r5f-main-0-core-1
IPC: ERROR: Unable to find rproc_device for rproc CPU [r5f-main-0-core-1]
rproc_device_find_chrdev_by_remote_port: could not find a matching rpmsg_chrdev node
IPC: ERROR: Unable to find rproc_char_device for rproc CPU [c66-0] @ remote endpt 21
rproc_device_find_chrdev_by_remote_port: could not find a matching rpmsg_chrdev node
IPC: ERROR: Unable to find rproc_char_device for rproc CPU [c66-1] @ remote endpt 21
rproc_device_find_chrdev_by_remote_port: could not find a matching rpmsg_chrdev node
IPC: ERROR: Unable to find rproc_char_device for rproc CPU [c7x] @ remote endpt 21
REMOTE_SERVICE: Init ... Done !!!
APP: Init ... Done !!!

I tried doing a fresh install of both the PSDKRA and PSDKLA in attempt to solve this error but I have not had any luck so far, any advice on how to resolve these errors would be appreciated.

my question is same as one in E2E,but I do not know how to resolve this issue(detail way)

e2e.ti.com/.../883414

  • 0
    TI__Genius 13505 points

    Hi,

    Thank you for linking the other thread - I can help you walk through the solution.

    U-Boot stores environment configuration in non-volatile memory on the EVM and needs to be updated for the new SDK.  The instructions may not comprehend this step.

    You will need a serial terminal open to stop the boot process while in u-boot.

    - Power on the EVM.

    - Press any key to halt the boot process while u-boot is displaying the count down.

    - At the u-boot prompt, type the following two commands:

    env default -a
    saveenv

    - Power cycle the EVM and boot at normal

    - Re-try the vision app - it should work now.

    Regards,
    Mike

  • 0 in reply to Michael Erdahl
    Intellectual 610 points

    Hi

    thank you for you reply

    but I set u-boot env to default state by command env default -a,this issue is not be resolved

    Output of make sdk_show_config:

    ### Build flags in vision_apps/vision_apps_build_flags.mak,

    # BUILD_CPU_MPU1=yes
    # BUILD_CPU_MCU2_0=yes
    # BUILD_CPU_MCU2_1=yes
    # BUILD_CPU_C6x_1=yes
    # BUILD_CPU_C6x_2=yes
    # BUILD_CPU_C7x_1=yes
    # BUILD_CPU_MCU1_0=yes
    # BUILD_CPU_MCU1_1=no
    # BUILD_CPU_MCU3_0=no
    # BUILD_CPU_MCU3_1=no
    #
    # BUILD_APP_TIRTOS_FILEIO=no
    # BUILD_APP_TIRTOS_LINUX=yes
    #
    # BUILD_PDK_BOARD=j721e_evm
    #
    ### Build flags in tiovx/build_flags.mak,
    # PROFILE=release
    # BUILD_TARGET_MODE=yes
    # BUILD_EMULATION_MODE=no
    # BUILD_LINUX_A72=yes
    #
    # BUILD_CT_KHR=yes
    # BUILD_CT_TIOVX=yes
    # BUILD_CT_TIOVX_TEST_KERNELS=yes
    # BUILD_CT_TIOVX_IVISION=yes
    # BUILD_CT_TIOVX_TIDL=yes
    # BUILD_CT_TIOVX_HWA=yes
    # BUILD_CT_TIOVX_HWA_NEGATIVE_TESTS=yes
    #
    # BUILD_CONFORMANCE_TEST=yes
    # BUILD_TUTORIAL=yes
    # BUILD_BAM=no
    # BUILD_EMULATION_ARCH=x86_64
    #

  • 0 in reply to user5113467
    TI__Genius 13505 points

    Hi,

    My mistake, you want to send this command at u-boot:

    env default -f -a
    saveenv

    I missed the '-f' option.

    Regards,
    Mike