• State Resolved
  • Locked Locked
  • Replies 19 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 738 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:

TDA4VE-Q1: We want build MCU1_0 , and loading on SPL

TDA4VE-Q1: How to run MCU1_0 on J721S2 08.04

Ming Lu
Prodigy 120 points
Part Number: TDA4VE-Q1

Hi Al

I have benn build up th mcu1_0, and out->  vx_app_rtos_linux_mcu1_0.out  already exist.

I change the uboot and /lib/firmware/j721s2-main-r5f0_0-fw.

check the process that mcu1_0 seems not runing .

I also change the uboot, still the same.

k3_r5f_rproc r5f@41000000: Core 1 is already in use. No rproc commands work 
k3_r5f_rproc r5f@41400000: Core 2 is already in use. No rproc commands work
1064128 bytes read in 12 ms (84.6 MiB/s)
Load Remote Processor 2 with data@addr=0x82000000 1064128 bytes: Success!
425420 bytes read in 9 ms (45.1 MiB/s)
Load Remote Processor 3 with data@addr=0x82000000 425420 bytes: Success!
199632 bytes read in 8 ms (23.8 MiB/s)
Load Remote Processor 4 with data@addr=0x82000000 199632 bytes: Success!
187344 bytes read in 7 ms (25.5 MiB/s)
Load Remote Processor 5 with data@addr=0x82000000 187344 bytes: Success!
14946336 bytes read in 85 ms (167.7 MiB/s)
Load Remote Processor 6 with data@addr=0x82000000 14946336 bytes: Success!
10489864 bytes read in 61 ms (164 MiB/s)
Load Remote Processor 7 with data@addr=0x82000000 10489864 bytes: Success!

What's the next step?

Did I missed somethings?

Thanks for your help.

Best Regards,

Ming Lu

  • 0
    Prodigy 120 points

    Sorry not j721s2-main-r5f0_0-fw. , change  721s2-mcu-r5f0_0-fw

  • 0
    Prodigy 120 points

    k3_r5f_rproc r5f@41000000: Invalid op: Trying to load/start on already running core 1
    Load Remote Processor 0 with data@addr=0x82000000 1357256 bytes: Failed!
    1064128 bytes read in 12 ms (84.6 MiB/s)

  • 0
    Prodigy 120 points
     rproc_fw_binaries
    0 j721s2-mcu-r5f0_0-fw 2 j721s2-main-r5f0_0-fw 3 j721s2-main-r5f0_1-fw 4 j721s2-main-r5f1_0-fw 5 j721s2-main-r5f1_1-fw 6 j721s2-c71_0-fw 7 j721s2-c71_1-fw
  • 0
    Prodigy 120 points
    when I enable app_cfg.h
    #define     ENABLE_IPC_MCU1_0

    all mcu will stuck at 
    APP: Syncing with 7 CPUs ... !!! 
    never go to Done......
  • 0
    Prodigy 120 points

    I finial know that we need reboot uboot on vision_app , 

    And replace the tispl.bin and u-boot.img

    Then MCU1_0  will start running.

    But next issue that will cause linux kernel panic?

    [MCU1_0]      0.040068 s: | I[    9.443611] NET: Registered protocol family 31
    [MCU1_0]      0.040149 s: | I | default | ### CPU Frequency = 1000000000 Hz
    [MCU1_0]      0.040202 s: | I | default | APP: Init ... !!!
    [MCU1_0]      0.040236 s: | I | default | MEM: Init ... !!!
    [MCU1_0]      0.040285 s: | I | default | MEM: Created heap (DDR_LOCAL_MEM, id=0, flags=0x00000004) @ df800000 of size 8388608 bytes !!!
    [MCU1_0]      0.040372 s: | I | default | MEM: Init ... Done !!!
    [MCU1_0]      0.040408 s: | I | default | IPC: Init ... !!!
    [MCU1_0]      0.040479 s: | I | default | IPC: 8 CPU[    9.587733] Bluetooth: HCI device and connection manager initialized
    [MCU1_0]      0.040541 s: | I | default | IPC: Waiting for HLOS to be ready ... !!!
    [MCU1_0]      9.620645 s: | I | default | IPC: HLOS is ready !!!
    [MCU1_0]      9.649695 s: | I | default | IPC: Init ... Done !!!
    [MCU1_0]     11.061783 s: | I | default | APP: Syncing with 7 CPUs ... Don[    9.686542] Bluetooth: SCO socket layer initialized
    [MCU1_0]     11.061959 s: | I | default | REMOTE_SERVICE: Init ... !!!
    [MCU1_0]     11.073126 s: | I | default | REMOTE_SERVICE: Init ... Done !!!
    [MCU1_0]     11.073217 s: | I | default | Joe g_cSelfCpuID = 1
    [MCU1_0]     11.073286 s: | I | default | Create oToShmComm mutex handler success
    [MCU1_0]     11.073337 s: | I | default | CPU(1) init oto share memory(a0102000), input=a0102000 !!
    [MCU1_0]     11.073481 s: | I | default | pShmLayout=0xA0102000, oToShmLayout Size=2281216
    [MCU1_0]     11.073546 s: | I | default | [oToA[    9.785241] PVR_K:  1168: Read BVNC 36.53.104.796 from HW device registers
    [MCU1_0]     11.073583 s: | I | default | [oToApp_debug]R5F init start !!
    [MCU1_0]     11.073622 s: | I[    9.807371] PVR_K:  1168: RGX Device registered BVNC 36.53.104.796 with 1 core in the system
    [MCU1_0]     11.073658 s: | I | default | [oToApp_msg]init end !!
    [MCU1_0]     11.073693 s: | I | default | APP: Init ... Done !!!
    [MCU1_0]     11.073731 s: | I | default | APP: Run ... !!!
    [MCU1_0]     11.073764 s: | I | default | IPC: Starting echo test ...
    [MCU1_0]     11.078091 s: | I | default | IPC: Echo status: mpu1_0[x] mcu1_0[s] mcu2_0[x] mcu2_1[x] mcu3_0[P] mcu3_1[x] C7X_1[x] C7X_2[x]
    [MCU1_0]     11.078861 s: | I | default | IPC: Echo status: mpu1_0[x] mcu1_0[s] mcu2_0[x] mcu2_1[x] mcu3_0[P] mcu3_1[P] C7X_1[x] C7X_2[x]
    [MCU1_0]     11.079590 s: | I | default | IPC: Echo status: mpu1_0[x] mcu1_0[s] mcu2_0[x] mcu2_1[x] mcu3_0[P] mcu3_1[P] C7X_1[P] C7X_2[x]
    [MCU1_0]     11.080129 s: | I | default | APP: Run ... Done !!!
    [MCU1_0]     11.080270 s: | I | default | IPC: Echo status: mpu1_0[x] mcu1_0[s] mcu2_0[x] mcu2_1[x] mcu3_0[P] mcu3_1[P] C7X_1[P] C7X_2[P]
    [MCU1_0]     11.415709 s: | I | default | IPC: Echo status: mpu1_0[x] mcu1_0[s] mcu2_0[x] mcu2_1[P] mcu3_0[P] mcu3_1[P] C7X_1[P] C7X_2[P]
    [MCU1_0]     11.654071 s: | I | default | IPC: Echo status: mpu1_0[x] mcu1_0[s] mcu2_0[P] mcu2_1[P] mcu3_0[P] mcu3_1[P] C7X_1[P] C7X_2[P]
    [MCU2_0]      3.243446 s: | I | default | CIO: Init ... Done !!!
    [MCU2_0]      3.243498 s: | I | default | ### CPU Frequency = 1000000000 Hz
    [MCU2_0]      3.243535 s: | I | default | APP: Init ... !!!
    [MCU2_0]      3.243557 s: | I | default | SCICLIENT: Init ... !!!
    [MCU2_0]      3.243697 s: | I | default | SCICLIENT: DMSC FW version [8.4.1--v08.04.01 (Jolly Jellyfi]
    [MCU2_0]      3.243732 s: | I | default | SCICLIENT: DMSC FW revision 0x8
    [MCU2_0]      3.243763 s: | I | default | SCICLIENT: DMSC FW ABI revision 3.1
    [MCU2_0]      3.243796 s: | I | default | SCICLIENT: Init ... Done !!!
    [MCU2_0]      3.243822 s: | I | default | UDMA: Init ... !!!
    [MCU2_0]      3.244734 s: | I | default | UDMA: Init ... Done !!!
    [MCU2_0]      3.244769 s: | I | default | UDMA: Init ... !!!
    [MCU2_0]      3.245259 s: | I | default | UDMA: Init for CSITX/CSIRX ... Done !!!
    [MCU2_0]      3.245296 s: | I | default | MEM: Init ... !!!
    [MCU2_0]      3.245332 s: | I | default | MEM: Created heap (DDR_LOCAL_MEM, id=0, flags=0x00000004) @ e0800000 of size 16777216 bytes !!!
    [MCU2_0]      3.245391 s: | I | default | MEM: Init ... Done !!!
    [MCU2_0]      3.245416 s: | I | default | IPC: Init ... !!!
    [MCU2_0]      3.245465 s: | I | default | IPC: 8 CPUs participating in IPC !!!
    [MCU2_0]      3.245505 s: | I | default | IPC: Waiting for HLOS to be ready ... !!!
    [MCU2_0]     10.147353 s: | I | default | IPC: HLOS is rea[   10.244807] EXT4-fs (mmcblk0p11): recovery complete
    dy !!!
    [MCU2_0]     10.162859 s: | I | default | IPC: Init ... Done !!!
    [MCU2_0]     10.162902 s: | I | default | APP: Synci[   10.265810] EXT4-fs (mmcblk0p11): mounted filesystem with ordered data mode. Opts: (null)
    ng with 7 CPUs ... !!!
    [MCU2_0]     11.061782 s: | I | default | APP: Syncing with 7 CPUs ... Done !!!
    [   10.294138] ext4 filesystem being mounted at /log supports timestamps until 2038 (0x7fffffff)
    [   10.324518] ------------[ cut here ]------------RVICE: Init ... !!!
    [   10.324543] ------------[ cut here ]------------
    [   10.330285] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.336034] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.342648] ------------[ cut here ]------------
    [   10.349263] ------------[ cut here ]------------
    [   10.355012] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.360760] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.367374] ------------[ cut here ]------------
    [   10.373990] ------------[ cut here ]------------
    [   10.379738] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.385487] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.392101] ------------[ cut here ]------------
    [   10.398716] ------------[ cut here ]------------
    [   10.404465] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.410213] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.416828] ------------[ cut here ]------------
    [   10.423443] ------------[ cut here ]------------
    [   10.429191] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.434940] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.441554] ------------[ cut here ]------------
    [   10.448169] ------------[ cut here ]------------
    [   10.453918] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.459666] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.466280] ------------[ cut here ]------------
    [   10.472896] ------------[ cut here ]------------
    [   10.478644] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.484392] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.491006] ------------[ cut here ]------------
    [   10.497621] ------------[ cut here ]------------
    [   10.503369] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.509117] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.515731] ------------[ cut here ]------------
    [   10.522345] ------------[ cut here ]------------
    [   10.528094] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.533842] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.540456] ------------[ cut here ]------------
    [   10.547071] ------------[ cut here ]------------
    [   10.552818] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.558566] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.565180] ------------[ cut here ]------------
    [   10.571796] ------------[ cut here ]------------
    [   10.577544] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.583292] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.589906] ------------[ cut here ]------------
    [   10.596520] ------------[ cut here ]------------
    [   10.602269] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.608017] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.614631] ------------[ cut here ]------------
    [   10.621245] ------------[ cut here ]------------
    [   10.626993] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.632742] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.639356] ------------[ cut here ]------------
    [   10.645972] ------------[ cut here ]------------
    [   10.651720] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.657468] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.664084] ------------[ cut here ]------------
    [   10.670698] ------------[ cut here ]------------
    [   10.676446] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.682194] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.688808] ------------[ cut here ]------------
    [   10.695422] ------------[ cut here ]------------
    [   10.701171] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.706919] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.713535] ------------[ cut here ]------------
    [   10.720149] ------------[ cut here ]------------
    [   10.725897] kernel BUG at arch/arm64/kernel/traps.c:407!
  • 0 in reply to Ming Lu
    TI__Guru**** 475745 points

    Hi,

    did you run "make linux_fs_install_sd" command, after building vision apps? Because this command should take care of copying all dependent files when this core is enabled? 

    Regards,

    Brijesh

  • 0 in reply to Brijesh Jadav
    Prodigy 120 points

    Hi Brijesh jadav:

    Because our uboot is run in emmc.
    I rewirte  the command as makefile_uboot.mak  about the uboot_linux_install_sd as follow

    uboot_oto_install: uboot_check uboot_check_firmware
    ifeq ($(BUILD_TARGET_MODE),yes)
        cp $(VISION_APPS_LINUX_DM) $(VISION_APPS_LINUX_DM_STRIP)
        $(TIARMCGT_LLVM_ROOT)/bin/tiarmstrip -p $(VISION_APPS_LINUX_DM_STRIP)
        $(MAKE) -C $(PSDK_LINUX_PATH)/board-support/u-boot-* ARCH=arm CROSS_COMPILE=$(GCC_LINUX_ARM_ROOT)/bin/aarch64-none-linux-gnu- O=$(SOC)-arm64-linux -j8 $(SOC)_evm_a72_defconfig
        $(MAKE) -C $(PSDK_LINUX_PATH)/board-support/u-boot-* ARCH=arm CROSS_COMPILE=$(GCC_LINUX_ARM_ROOT)/bin/aarch64-none-linux-gnu- ATF=$(PSDK_LINUX_PATH)/board-support/prebuilt-images/bl31.bin TEE=$(PSDK_LINUX_PATH)/board-support/prebuilt-images/bl32.bin DM=$(VISION_APPS_LINUX_DM_STRIP) O=$(SOC)-arm64-linux
        cp $(PSDK_LINUX_PATH)/board-support/u-boot-*/$(SOC)-arm64-linux/tispl.bin $(PSDK_LINUX_PATH)/../bootfs
        cp $(PSDK_LINUX_PATH)/board-support/u-boot-*/$(SOC)-arm64-linux/u-boot.img $(PSDK_LINUX_PATH)/../bootfs
        sync
    endif


    uboot_linux_install_sd: uboot_check
    ifeq ($(BUILD_TARGET_MODE),yes)
        cp $(PSDK_LINUX_PATH)/board-support/u-boot-*/$(SOC)-arm64-linux/tispl.bin $(LINUX_SD_FS_BOOT_PATH)/
        cp $(PSDK_LINUX_PATH)/board-support/u-boot-*/$(SOC)-arm64-linux/u-boot.img $(LINUX_SD_FS_BOOT_PATH)/
        sync
    endif

  • 0 in reply to Ming Lu
    TI__Guru**** 475745 points

    Hi,

    When you include mcu1_0 in vision apps, it rebuilds uboot components, because mcu1_0 firmware will be part of one of the uboot component, so after rebuilding, please copy uboot components to eMMC. 

    Regards,

    Brijesh

  • 0 in reply to Brijesh Jadav
    Prodigy 120 points

    Hi,

    MCU1_0 already runing on my side .

    But it will cause linux kernel panic.

    Remove mcu1_0, all will be ok.

    Do you know , what cause this issue?

    [MCU1_0]      0.040068 s: | I[    9.443611] NET: Registered protocol family 31
    [MCU1_0]      0.040149 s: | I | default | ### CPU Frequency = 1000000000 Hz
    [MCU1_0]      0.040202 s: | I | default | APP: Init ... !!!
    [MCU1_0]      0.040236 s: | I | default | MEM: Init ... !!!
    [MCU1_0]      0.040285 s: | I | default | MEM: Created heap (DDR_LOCAL_MEM, id=0, flags=0x00000004) @ df800000 of size 8388608 bytes !!!
    [MCU1_0]      0.040372 s: | I | default | MEM: Init ... Done !!!
    [MCU1_0]      0.040408 s: | I | default | IPC: Init ... !!!
    [MCU1_0]      0.040479 s: | I | default | IPC: 8 CPU[    9.587733] Bluetooth: HCI device and connection manager initialized
    [MCU1_0]      0.040541 s: | I | default | IPC: Waiting for HLOS to be ready ... !!!
    [MCU1_0]      9.620645 s: | I | default | IPC: HLOS is ready !!!
    [MCU1_0]      9.649695 s: | I | default | IPC: Init ... Done !!!
    [MCU1_0]     11.061783 s: | I | default | APP: Syncing with 7 CPUs ... Don[    9.686542] Bluetooth: SCO socket layer initialized
    [MCU1_0]     11.061959 s: | I | default | REMOTE_SERVICE: Init ... !!!
    [MCU1_0]     11.073126 s: | I | default | REMOTE_SERVICE: Init ... Done !!!
    [MCU1_0]     11.073217 s: | I | default | Joe g_cSelfCpuID = 1
    [MCU1_0]     11.073286 s: | I | default | Create oToShmComm mutex handler success
    [MCU1_0]     11.073337 s: | I | default | CPU(1) init oto share memory(a0102000), input=a0102000 !!
    [MCU1_0]     11.073481 s: | I | default | pShmLayout=0xA0102000, oToShmLayout Size=2281216
    [MCU1_0]     11.073546 s: | I | default | [oToA[    9.785241] PVR_K:  1168: Read BVNC 36.53.104.796 from HW device registers
    [MCU1_0]     11.073583 s: | I | default | [oToApp_debug]R5F init start !!
    [MCU1_0]     11.073622 s: | I[    9.807371] PVR_K:  1168: RGX Device registered BVNC 36.53.104.796 with 1 core in the system
    [MCU1_0]     11.073658 s: | I | default | [oToApp_msg]init end !!
    [MCU1_0]     11.073693 s: | I | default | APP: Init ... Done !!!
    [MCU1_0]     11.073731 s: | I | default | APP: Run ... !!!
    [MCU1_0]     11.073764 s: | I | default | IPC: Starting echo test ...
    [MCU1_0]     11.078091 s: | I | default | IPC: Echo status: mpu1_0[x] mcu1_0[s] mcu2_0[x] mcu2_1[x] mcu3_0[P] mcu3_1[x] C7X_1[x] C7X_2[x]
    [MCU1_0]     11.078861 s: | I | default | IPC: Echo status: mpu1_0[x] mcu1_0[s] mcu2_0[x] mcu2_1[x] mcu3_0[P] mcu3_1[P] C7X_1[x] C7X_2[x]
    [MCU1_0]     11.079590 s: | I | default | IPC: Echo status: mpu1_0[x] mcu1_0[s] mcu2_0[x] mcu2_1[x] mcu3_0[P] mcu3_1[P] C7X_1[P] C7X_2[x]
    [MCU1_0]     11.080129 s: | I | default | APP: Run ... Done !!!
    [MCU1_0]     11.080270 s: | I | default | IPC: Echo status: mpu1_0[x] mcu1_0[s] mcu2_0[x] mcu2_1[x] mcu3_0[P] mcu3_1[P] C7X_1[P] C7X_2[P]
    [MCU1_0]     11.415709 s: | I | default | IPC: Echo status: mpu1_0[x] mcu1_0[s] mcu2_0[x] mcu2_1[P] mcu3_0[P] mcu3_1[P] C7X_1[P] C7X_2[P]
    [MCU1_0]     11.654071 s: | I | default | IPC: Echo status: mpu1_0[x] mcu1_0[s] mcu2_0[P] mcu2_1[P] mcu3_0[P] mcu3_1[P] C7X_1[P] C7X_2[P]
    [MCU2_0]      3.243446 s: | I | default | CIO: Init ... Done !!!
    [MCU2_0]      3.243498 s: | I | default | ### CPU Frequency = 1000000000 Hz
    [MCU2_0]      3.243535 s: | I | default | APP: Init ... !!!
    [MCU2_0]      3.243557 s: | I | default | SCICLIENT: Init ... !!!
    [MCU2_0]      3.243697 s: | I | default | SCICLIENT: DMSC FW version [8.4.1--v08.04.01 (Jolly Jellyfi]
    [MCU2_0]      3.243732 s: | I | default | SCICLIENT: DMSC FW revision 0x8
    [MCU2_0]      3.243763 s: | I | default | SCICLIENT: DMSC FW ABI revision 3.1
    [MCU2_0]      3.243796 s: | I | default | SCICLIENT: Init ... Done !!!
    [MCU2_0]      3.243822 s: | I | default | UDMA: Init ... !!!
    [MCU2_0]      3.244734 s: | I | default | UDMA: Init ... Done !!!
    [MCU2_0]      3.244769 s: | I | default | UDMA: Init ... !!!
    [MCU2_0]      3.245259 s: | I | default | UDMA: Init for CSITX/CSIRX ... Done !!!
    [MCU2_0]      3.245296 s: | I | default | MEM: Init ... !!!
    [MCU2_0]      3.245332 s: | I | default | MEM: Created heap (DDR_LOCAL_MEM, id=0, flags=0x00000004) @ e0800000 of size 16777216 bytes !!!
    [MCU2_0]      3.245391 s: | I | default | MEM: Init ... Done !!!
    [MCU2_0]      3.245416 s: | I | default | IPC: Init ... !!!
    [MCU2_0]      3.245465 s: | I | default | IPC: 8 CPUs participating in IPC !!!
    [MCU2_0]      3.245505 s: | I | default | IPC: Waiting for HLOS to be ready ... !!!
    [MCU2_0]     10.147353 s: | I | default | IPC: HLOS is rea[   10.244807] EXT4-fs (mmcblk0p11): recovery complete
    dy !!!
    [MCU2_0]     10.162859 s: | I | default | IPC: Init ... Done !!!
    [MCU2_0]     10.162902 s: | I | default | APP: Synci[   10.265810] EXT4-fs (mmcblk0p11): mounted filesystem with ordered data mode. Opts: (null)
    ng with 7 CPUs ... !!!
    [MCU2_0]     11.061782 s: | I | default | APP: Syncing with 7 CPUs ... Done !!!
    [   10.294138] ext4 filesystem being mounted at /log supports timestamps until 2038 (0x7fffffff)
    [   10.324518] ------------[ cut here ]------------RVICE: Init ... !!!
    [   10.324543] ------------[ cut here ]------------
    [   10.330285] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.336034] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.342648] ------------[ cut here ]------------
    [   10.349263] ------------[ cut here ]------------
    [   10.355012] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.360760] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.367374] ------------[ cut here ]------------
    [   10.373990] ------------[ cut here ]------------
    [   10.379738] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.385487] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.392101] ------------[ cut here ]------------
    [   10.398716] ------------[ cut here ]------------
    [   10.404465] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.410213] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.416828] ------------[ cut here ]------------
    [   10.423443] ------------[ cut here ]------------
    [   10.429191] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.434940] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.441554] ------------[ cut here ]------------
    [   10.448169] ------------[ cut here ]------------
    [   10.453918] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.459666] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.466280] ------------[ cut here ]------------
    [   10.472896] ------------[ cut here ]------------
    [   10.478644] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.484392] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.491006] ------------[ cut here ]------------
    [   10.497621] ------------[ cut here ]------------
    [   10.503369] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.509117] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.515731] ------------[ cut here ]------------
    [   10.522345] ------------[ cut here ]------------
    [   10.528094] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.533842] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.540456] ------------[ cut here ]------------
    [   10.547071] ------------[ cut here ]------------
    [   10.552818] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.558566] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.565180] ------------[ cut here ]------------
    [   10.571796] ------------[ cut here ]------------
    [   10.577544] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.583292] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.589906] ------------[ cut here ]------------
    [   10.596520] ------------[ cut here ]------------
    [   10.602269] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.608017] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.614631] ------------[ cut here ]------------
    [   10.621245] ------------[ cut here ]------------
    [   10.626993] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.632742] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.639356] ------------[ cut here ]------------
    [   10.645972] ------------[ cut here ]------------
    [   10.651720] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.657468] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.664084] ------------[ cut here ]------------
    [   10.670698] ------------[ cut here ]------------
    [   10.676446] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.682194] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.688808] ------------[ cut here ]------------
    [   10.695422] ------------[ cut here ]------------
    [   10.701171] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.706919] kernel BUG at arch/arm64/kernel/traps.c:407!
    [   10.713535] ------------[ cut here ]------------
    [   10.720149] ------------[ cut here ]------------
    [   10.725897] kernel BUG at arch/arm64/kernel/traps.c:407!
  • 0 in reply to Ming Lu
    TI__Guru* 84746 points

    Hi,

    Are you observing this is the default SDK?

    Or are there changes made in the SDK (for eg. either memory related etc.)

    Is it possible to take the default SDK, enable MCU1_0 on vision_apps and test it using the SD Card first and check if you are seeing this error?

    If not seen, you could copy the contents to eMMC and verify there too.

    Please let me know if this is feasible at your end?

    Regards,

    Nikhil

  • 0 in reply to Nikhil Dasan
    Prodigy 120 points

    Hi Nikhil,

    I have some findings from my tests that I'd like to share with you.

    The good news is that the EVM board with 8GB RAM performed well . Additionally, our board with 8GB DDR RAM also passed without any issues.

    However, I encountered a kernel panic issue while testing the board with 4GB DDR RAM. The main difference between these two boards lies in their memory capacity, with one having 4GB and the other 8GB DDR.

    Upon careful inspection, it seems to be related to memory overlap. I thoroughly checked the memory map on the R5 map and confirmed that the memory mapping for the 4GB and 8GB boards is the same. Even the device tree configurations are identical.

    I'm reaching out to you to inquire whether you might have any insights or suggestions regarding this matter.
    It's possible that I missed some modifications or settings that need to be adjusted to address this discrepancy.

    Thank you for your attention, and I'm looking forward to your guidance on resolving this issue.

    Best regards,
    Ming Lu

  • 0 in reply to Ming Lu
    TI__Guru* 84746 points

    Hi Ming Lu,

    Thats great. 

    By any chance have you tested by reducing DDR on EVM to 4GB?

    You could refer the below FAQ to configure DDR on EVM to 4GB 

    https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1227640/faq-tda4vm-tda4vl-tda4al-tda4vh-dra821-how-can-we-make-the-jacinto-sdk-compatible-for-device-variants#:~:text=the%20below%20changes.-,1.%20Reduction%20in%20the%20number%20of%20DDR%20Instances,-Some%20of%20the

    Once this is done and if this is working, you could compare the changes here with the custom board.

    Regards,

    Nikhil

  • 0 in reply to Nikhil Dasan
    Prodigy 120 points

    Hello NiKhil Dassan,

    I've been working on modifying the device tree and evm.c to accommodate a 4GB configuration.
    The changes appear to work seamlessly on j721s2 EVM board, and even when transitioning our 8GB DDR (Micron) to a 4GB DDR configuration.

    However, I've hit a roadblock with our 4GB setup utilizing Hynix memory.
    When building u-boot boot up with mcu1_0, we encounter a kernel panic. 
    I've meticulously reviewed both the DDR configuration and the device tree, and they seem to be in perfect order.

    Without mcu1_0 (Mark IPC(//#define ENABLE_IPC_MCU1_0) and without build uboot again on vision_apps).
    All functions execute properly, and the system behaves as expected, 


    I was wondering if you might have any insights or suggestions regarding this matter. Your expertise would be greatly appreciated.

    Thank you for your time and consideration.

    Best regards, Ming Lu

  • 0 in reply to Ming Lu
    TI__Guru* 84746 points

    Hi Ming Lu,

    Nikhil Dasan said:
    Is it possible to take the default SDK, enable MCU1_0 on vision_apps and test it using the SD Card first and check if you are seeing this error?

    If not seen, you could copy the contents to eMMC and verify there too.

    Could you please confirm the above? 
    This would be a good way to confirm if the issue is due to different files in the boot media.

    Regards,

    Nikhil

  • +1 in reply to Nikhil Dasan
    Prodigy 120 points

    Hi NiKhil Dassan,
    u-boot-a72:

            $(MAKE) -j $(MAKE_JOBS) -C $(TI_SDK_PATH)/board-support/u-boot-* CROSS_COMPILE=$(CROSS_COMPILE) \
            CONFIG_MKIMAGE_DTC_PATH=$(UBOOT_A72_BUILD_DIR)/scripts/dtc/dtc \
            ATF=$(UBOOT_ATF) TEE=$(UBOOT_TEE) DM=$(UBOOT_DM) \
            O=$(UBOOT_A72_BUILD_DIR)

    type1:  
    UBOOT_DM=$(TI_SDK_PATH)/board-support/prebuilt-images/ipc_echo_testb_mcu1_0_release_strip.xer5f.signed

    type2:

    UBOOT_DM=$(VISION_APP_R5F_OUR_DIR)/vx_app_rtos_linux_mcu1_0_strip.out


    I changed tispl.bin ,DM with both type are ok.

    But type2 u-boot.img will cause boot failed on (Hynix 4g) 

    It's strange that why different mcu1_0 image build different uboot image....?

    Our pdk is 08.04 j721s2.

  • 0 in reply to Ming Lu
    Prodigy 120 points

    It's ok now. Our 4G can run mcu1_0.

    Cross compler seem have some problem.

    When build in psdk_linux (modify makefile, make u-boot) image is ok on 4G.

    When build in psdk_rtos/vision_apps/ (modify makefile_uboot.mak make uboot) image will kernel panic on 4g.

    Linux use prebuild cross complier , version is 9.2.1

    RTOS use download gcc, version also 9.2.1 

    But result is different.

  • 0 in reply to Ming Lu
    TI__Guru* 84746 points

    Hi

    Ming Lu said:
    It's ok now. Our 4G can run mcu1_0.

    I see that you have clicked the thread as resolved. Could you please confirm if you are able to resolve the issue with MCU1_0 enabled on vision_apps?

    Regards,

    Nikhil

  • 0 in reply to Nikhil Dasan
    Prodigy 120 points

    Yes, this issue is ok now. Build Mcu1_0 is ok .  Use linux complier build tispl.bin and uboot.image also ok on 4g.

  • 0 in reply to Ming Lu
    TI__Guru* 84746 points

    Thank you for the confirmation.

    Closing this thread.