• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 721 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.

PROCESSOR-SDK-DRA8X-TDA4X: How to build with mcu2_1 open and how to run applications of MCAN in mcu2_1

bin li2
Expert 1290 points
Part Number: PROCESSOR-SDK-DRA8X-TDA4X


Hi,

    As i know from e2e, mcu2_0 is used exclusively by ethfw. So i modify the vision_apps_build_flags.mak in psdkra, set the BUILD_CPU_MCU2_1 = yes

  Then i rebuild it by "make sdk".
   install it by " make linux_fs_install_sd". And i see the new file j7-main-r5f0_1-fw copied to /lib/firmware.

But when i boot the EVM and run "source ./vision_apps_init.sh", I can't see [MCU2_1] logs like [MCU2_0].

2. how can i run the MCAN application csl_mcan_evm_loopback_app?

Thanks a lot.

  • 0
    TI__Guru* 77924 points

    Hi,

    bin li2 said:
    But when i boot the EVM and run "source ./vision_apps_init.sh", I can't see [MCU2_1] logs like [MCU2_0].

    Which SDK version is this on?

    bin li2 said:
    2. how can i run the MCAN application csl_mcan_evm_loopback_app?

    Do you want to run the csl_mcan_evm_loopback_app example in context of vision_apps or can you also try CCS based approach for standalone testing of this application?

    Regards,

    Karan

  • 0 in reply to Karan Saxena
    Expert 1290 points

    Hi,

        1.SDK version is psdk_rtos_auto_j7_07_00_00_11.

        2.yes, i want to run mcan demo in MCU2_1, and MCU2_0 is for ethfw. I add some log in \\192.168.12.70\share\psdk_rtos_auto_j7_07_00_00_11\vision_apps\apps\basic_demos\app_tirtos\tirtos_linux\mcu2_0\main.c ,and also mcu2_1 main.c.
    I found the firmware j7-main-r5f0_0-fw and j7-main-r5f0_1-fw has the log in binarty file .And mcu2_0 has log when excute vision_apps_init.sh, mcu2_1 has no log output. So i guess the vision_apps_init.sh has not call the mcu2_1 procedure.

         And i can see loading mcu2_0 and mcu2_1 is success. log is :

    [   12.646935] remoteproc remoteproc4: Booting fw image j7-main-r5f0_0-fw, size 4839748
    [   12.659883] platform 5c00000.r5f: R5F core initialized in IPC-only mode
    [   12.664586] platform 5d00000.r5f: assigned reserved memory node r5f-dma-memory@a3000000
    [   12.669855]  remoteproc4#vdev0buffer: assigned reserved memory node r5f-dma-memory@a1000000
    [   12.689753] virtio_rpmsg_bus virtio3: rpmsg host is online
    [   12.699596]  remoteproc4#vdev0buffer: registered virtio3 (type 7)
    [   12.705759] remoteproc remoteproc4: remote processor 5c00000.r5f is now up
    [   12.717972] virtio_rpmsg_bus virtio2: creating channel rpmsg_chrdev addr 0x15
    [   12.729288] virtio_rpmsg_bus virtio2: creating channel ti.ipc4.ping-pong addr 0xe
    [   12.739719] virtio_rpmsg_bus virtio3: creating channel rpmsg_chrdev addr 0xd
    [   12.751666] virtio_rpmsg_bus virtio3: creating channel rpmsg_chrdev addr 0x15
    [   12.763687] virtio_rpmsg_bus virtio0: creating channel rpmsg_chrdev addr 0x15
    [   12.770940] virtio_rpmsg_bus virtio0: creating channel ti.ipc4.ping-pong addr 0xe
    [   12.783676] virtio_rpmsg_bus virtio1: creating channel rpmsg_chrdev addr 0x15
    [   12.795668] virtio_rpmsg_bus virtio1: creating channel ti.ipc4.ping-pong addr 0xe
    [   12.808006] virtio_rpmsg_bus virtio3: creating channel ti.ethfw.notifyservice addr 0x1e
    [   12.829734] virtio_rpmsg_bus virtio3: creating channel rpmsg-kdrv addr 0x1a
    [   12.840153] rpmsg-kdrv-eth-switch rpmsg-kdrv-2-mpu_1_0_ethswitch-device-0: Device info: permissions: 07FFFFFF uart_id: 2
    [   12.859574] rpmsg-kdrv-eth-switch rpmsg-kdrv-2-mpu_1_0_ethswitch-device-0: FW ver 0.1 (rev 1) 10/Sep/2020 SHA:
    [   12.870305] virtio_rpmsg_bus virtio3: creating channel ti.ipc4.ping-pong addr 0xe
    [   12.891793] remoteproc remoteproc5: 5d00000.r5f is available
    [   12.918866] j721e-audio sound@0: pcm3168a-dac <-> 2ba0000.mcasp mapping ok
    [   12.925990] remoteproc remoteproc5: powering up 5d00000.r5f
    [   12.931591] remoteproc remoteproc5: Booting fw image j7-main-r5f0_1-fw, size 210796
    [   12.943705] platform 5d00000.r5f: R5F core initialized in IPC-only mode
    [   12.955578]  remoteproc5#vdev0buffer: assigned reserved memory node r5f-dma-memory@a3000000
    [   12.967996] virtio_rpmsg_bus virtio4: rpmsg host is online
    [   12.976813]  remoteproc5#vdev0buffer: registered virtio4 (type 7)
    [   12.987614] remoteproc remoteproc5: remote processor 5d00000.r5f is now up
    [   12.999757] virtio_rpmsg_bus virtio4: creating channel rpmsg_chrdev addr 0xd
    [   13.035852] platform 5e00000.r5f: configured R5F for remoteproc mode
    [   13.043330] j721e-cpsw-virt-mac main_r5fss_cpsw9g_virt_mac0: virt_cpsw_nuss mac loaded
    [   13.055572] j721e-cpsw-virt-mac main_r5fss_cpsw9g_virt_mac0: rdev_features:00000003 rdev_mtu:1522 flow_id:172 tx_psil_dst_id:4A00
    [   13.071579] j721e-cpsw-virt-mac main_r5fss_cpsw9g_virt_mac0: local_mac_addr:00:00:00:00:00:00 rdev_mac_addr:70:ff:76:1d:92:c1
    [   13.085110] j721e-audio sound@0: pcm3168a-adc <-> 2ba0000.mcasp mapping ok
    [   13.151823] platform 5e00000.r5f: assigned reserved memory node r5f-dma-memory@a4000000
    [   13.330180] remoteproc remoteproc6: 5e00000.r5f is available
    [   13.430472] remoteproc remoteproc6: Direct firmware load for j7-main-r5f1_0-fw failed with error -2
    [   13.441321] remoteproc remoteproc6: powering up 5e00000.r5f
    [   13.451598] remoteproc remoteproc6: Direct firmware load for j7-main-r5f1_0-fw failed with error -2
    [   13.466093] remoteproc remoteproc6: request_firmware failed: -2
    [   13.489113] platform 5f00000.r5f: configured R5F for remoteproc mode
    [   13.568792] platform 5f00000.r5f: assigned reserved memory node r5f-dma-memory@a5000000
    [   13.712124] remoteproc remoteproc7: 5f00000.r5f is available
    [   13.784328] remoteproc remoteproc7: Direct firmware load for j7-main-r5f1_1-fw failed with error -2
    [   13.795656] remoteproc remoteproc7: powering up 5f00000.r5f
    [   13.807598] remoteproc remoteproc7: Direct firmware load for j7-main-r5f1_1-fw failed with error -2

    The main thing i want is to run MCAN functions on main domain, and test it like tidl when linux is running.

  • 0
    TI__Guru* 77924 points

    Hi,

    bin li2 said:
    But when i boot the EVM and run "source ./vision_apps_init.sh", I can't see [MCU2_1] logs like [MCU2_0].

    Along with BUILD_CPU_MCU2_1 = yes, please also enable the ENABLE_IPC_MCU2_1 in the vision_apps/apps/basic_demos/app_tirtos/common/app_cfg.h

    This will enable logging.

    Regards,

    Karan

  • 0 in reply to Karan Saxena
    Expert 1290 points

    Hi,

        Thanks for your reply. Before your suggestion, i have done this, set the ENABLE_IPC_MCU2_1, because i grep the ENABLE_IPC_MCU2_0 and find it.

    But also the problem is exist.

    Can you help me to check it more?

  • 0 in reply to Karan Saxena
    Expert 1290 points

    Hi，

         Thanks a lot. i found i made a mistake before. Because after modified the .h file ,i had not clean it.

        Now it's ok, after i rebuild the sdk. I can see MCU2_1 log.