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.
Dear ti experts,
when we use the ti-processor-sdk-rtos-j721e-evm-08_01_00_13-prebuilt.tar.gz , the steps is:
a. tar -jxvf tisdk-default-image-j7-evm.tar.xz -C rootfsA
b. sync
c. cp -r rootfs/opt rootfsA/opt
d. cp -r rootfs/usr rootfsA/usr
then setup the board and enter the linux prompt:
a. cd /opt/vision_apps
b. ./vision_apps_init.sh
then in concle, there is no any log,why?
Thanks,
Ruijie Sun
Hi sun ruijie,
Could you build the SDK and try flashing SD card? I have checked from the source and it works fine.
Regards,
Brijesh
hi brijesh，
sorry ，we have the sd card
when run the vx_app_single_cam.out, show the error log,
the reason is dont load mcu2_0 and mcu2_1 firmware successfully?
thanks,
root@j7-evm:/opt/vision_apps# ./vision_apps_init.sh
root@j7-evm:/opt/vision_apps# ./vx_app_single_cam.out
APP: Init ... !!!
MEM: Init ... !!!
MEM: Initialized DMA HEAP (fd=4) !!!
MEM: Init ... Done !!!
IPC: Init ... !!!
_rpmsg_char_find_ctrldev: could not find the matching rpmsg_ctrl device for virtio2.rpmsg_chrdev.-1.13
_rpmsg_char_find_ctrldev: could not find the matching rpmsg_ctrl device for virtio3.rpmsg_chrdev.-1.13
_rpmsg_char_find_ctrldev: could not find the matching rpmsg_ctrl device for virtio0.rpmsg_chrdev.-1.13
_rpmsg_char_find_rproc: 4d81800000.dsp does not have any virtio devices!
_rpmsg_char_find_rproc: 64800000.dsp is either not probed or not a remoteproc!
IPC: ERROR: Unable to create TX channels for CPU [mcu2_0] !!!
IPC: ERROR: Unable to create TX channels for CPU [mcu2_1] !!!
IPC: ERROR: Unable to create TX channels for CPU [c6x_1] !!!
IPC: ERROR: Unable to create TX channels for CPU [c6x_2] !!!
IPC: ERROR: Unable to create TX channels for CPU [c7x_1] !!!
IPC: Init ... Done !!!
APP: ERROR: IPC init failed !!!
REMOTE_SERVICE: Init ... !!!
_rpmsg_char_find_ctrldev: could not find the matching rpmsg_ctrl device for virtio3.rpmsg_chrdev.-1.21
_rpmsg_char_find_ctrldev: could not find the matching rpmsg_ctrl device for virtio0.rpmsg_chrdev.-1.21
_rpmsg_char_find_rproc: 4d81800000.dsp does not have any virtio devices!
_rpmsg_char_find_rproc: 64800000.dsp is either not probed or not a remoteproc!
REMOTE_SERVICE: Init ... Done !!!
186.630479 s: GTC Frequency = 200 MHz
APP: Init ... Done !!!
186.634038 s: VX_ZONE_INIT:Enabled
186.634046 s: VX_ZONE_ERROR:Enabled
186.634051 s: VX_ZONE_WARNING:Enabled
186.635641 s: VX_ZONE_INIT:[tivxInitLocal:130] Initialization Done !!!
186.636817 s: VX_ZONE_INIT:[tivxHostInitLocal:86] Initialization Done for HOST !!!
Single Camera Demo - (c) Texas Instruments 2019
========================================================
Usage,
./vx_app_single_cam.out --cfg <config file>
Defaulting to interactive mode
IttCtrl_registerHandler: command echo registered at location 0
IttCtrl_registerHandler: command iss_read_2a_params registered at location 1
IttCtrl_registerHandler: command iss_write_2a_params registered at location 2
IttCtrl_registerHandler: command iss_raw_save registered at location 3
IttCtrl_registerHandler: command iss_yuv_save registered at location 4
IttCtrl_registerHandler: command iss_read_sensor_reg registered at location 5
IttCtrl_registerHandler: command iss_write_sensor_reg registered at location 6
IttCtrl_registerHandler: command dev_ctrl registered at location 7
IttCtrl_registerHandler: command iss_send_dcc_file registered at location 8
NETWORK: Opened at IP Addr = 1.4.16.64, socket port=5000!!!
186.639958 s: VX_ZONE_ERROR:[ownContextCreateCmdObj:161] context object descriptor [0] allocation failed
186.639973 s: VX_ZONE_ERROR:[vxCreateContext:946] context objection creation failed
186.639982 s: VX_ZONE_ERROR:[vxGetStatus:713] Reference is NULL
Select camera port index 0-7 : [ 245.943884] Initializing XFRM netlink socket
[ 247.567218] process 'docker/tmp/qemu-check411387089/check' started with executable stack
mmc0(part 0) is current deviceCore 1 is already in use. No rproc commands workCore 2 is already in use. No rproc commands work626036 bytes read in 5 ms (119.4 MiB/s)Load Remote Processor 2 with data@addr=0x82000000 626036 bytes: Success!97676 bytes read in 3 ms (31 MiB/s)Load Remote Processor 3 with data@addr=0x82000000 97676 bytes: Success!97676 bytes read in 3 ms (31 MiB/s)Load Remote Processor 4 with data@addr=0x82000000 97676 bytes: Success!97676 bytes read in 3 ms (31 MiB/s)Load Remote Processor 5 with data@addr=0x82000000 97676 bytes: Success!144332 bytes read in 3 ms (45.9 MiB/s)Load Remote Processor 6 with data@addr=0x82000000 144332 bytes: Success!144332 bytes read in 3 ms (45.9 MiB/s)Load Remote Processor 7 with data@addr=0x82000000 144332 bytes: Success!10489000 bytes read in 59 ms (169.5 MiB/s)Load Remote Processor 8 with data@addr=0x82000000 10489000 bytes: Success!19270144 bytes read in 105 ms (175 MiB/s)100199 bytes read in 2 ms (47.8 MiB/s)11211 bytes read in 1 ms (10.7 MiB/s)
I think firmwares are loaded correctly, but somehow Linux is not establishing ipc only channel between core. It does not look like it is because of mcu2_0 and mcu2_1 failure.
Are you also copying BOOT sector correctly ?
Regards,
Brijesh
Dear brijesh,
yes, sdk0703 is work well by the same load way.
the boot sector file iamge (tiboot3.bin, sysfw.itb, tispl.bin and u-boot.img) is from the ti-processor-sdk-linux-j7-evm-08_01_00_07-Linux-x86-Install.bin
and we only change to emmc startup
/* U-Boot MMC-specific configuration */
#define EXTRA_ENV_J721E_BOARD_SETTINGS_MMC \
"boot=mmc\0" \
"mmcdev=0\0" \
"bootpart=0:2\0" \
"bootdir=/boot\0"
Thanks,
Ruijie Sun
