Other Parts Discussed in Thread: TMP75, INA226
Hardware platform: EVM development board
SDK version: 8.00
Steps:
1. Download PROCESSOR-SDK-LINUX-J721E_08.00.00.08 and tisdk-default-image-j7-evm.tar.xz from www.ti.com/.../08.00.00.08
2. Download PROCESSOR-SDK-RTOS-J721E_08.00.00.12 from www.ti.com/.../08.00.00.12
3. Generate SBL boot images according to e2e.ti.com/.../tda4vm-how-to-boot-mcu-1-0-autosar-from-tiboot3 /3806320#3806320
4. Unzip the RTOS in step 2, enter the RTOS vision_apps directory, generate vision_apps image using "make sdk -j8"
5. Copy images generated in step3 to SD Card BOOT partition; extract the tisdk-default-image-j7-evm.tar.xz in step 1 to SD Card ROOTFS partition
6. Enter RTOS vision_apps directory, copy vision apps binaries to SD card using "make linux_fs_install_sd"
7. Reboot the EVM board in SD boot mode, a panic error will appear in the kerner log
[ 11.096852] Internal error: Oops: 96000007 [#1] PREEMPT SMP
[ 11.102969] Modules linked in: ti_k3_r5_remoteproc(+) pruss sa2ul sha512_generic authenc vxd_dec bluetooth ecdh_generic ecc rfkill pvrsrvkm(O) videobuf2_dma_sg ti_k3_dsp_remoteproc v4l2_mem2mem virtio_rpmsg_bus cdns_dphy videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 videobuf2_common cdns3_ti rti_wdt sch_fq_codel simple_mod(O) rpmsg_kdrv_switch max20087(O) cryptodev(O) ipv6
[ 11.136578] CPU: 1 PID: 214 Comm: systemd-udevd Tainted: G O 5.10.41-marsii-2.0-g4c2eade9f7 #1
[ 11.146467] Hardware name: Texas Instruments K3 J721E SoC (DT)
[ 11.152282] pstate: 00000005 (nzcv daif -PAN -UAO -TCO BTYPE=--)
[ 11.158280] pc : rproc_handle_resources.constprop.0+0x94/0x168
[ 11.164096] lr : rproc_boot+0x334/0x670
[ 11.167916] sp : ffff8000130af7a0
[ 11.171216] x29: ffff8000130af7a0 x28: ffff80001130b720
[ 11.176513] x27: ffff000827807000 x26: ffffffffffffffff
[ 11.181810] x25: ffff80001d000000 x24: ffff800010e20ff0
[ 11.187106] x23: ffff000827807038 x22: 0000000000000000
[ 11.192402] x21: ffff80001123cfc8 x20: ffff000827807000
[ 11.197698] x19: 0000000000000000 x18: 0000000000000000
[ 11.202994] x17: 0000000000000000 x16: 0000000000000000
[ 11.208290] x15: 0000a9c47d56a08c x14: fffff7fffffeffff
[ 11.213587] x13: ffffffffffffffff x12: fffffbffffffffbf
[ 11.218883] x11: ffffffffffffbfff x10: fffffeffffffffbf
[ 11.224179] x9 : ffffffffffffffff x8 : fffffffffffff7fd
[ 11.229475] x7 : fffffff7ffffffff x6 : ffff00082670f500
[ 11.234771] x5 : 0000000000000000 x4 : 0000000000000000
[ 11.240067] x3 : 00000000000000fd x2 : 00000000ffffffff
[ 11.245363] x1 : ffff80001d000003 x0 : ffff80001d000000
[ 11.250660] Call trace:
[ 11.253096] rproc_handle_resources.constprop.0+0x94/0x168
[ 11.258564] rproc_boot+0x334/0x670
[ 11.262039] rproc_add+0x88/0x158
[ 11.265351] k3_r5_probe+0x698/0xcf0 [ti_k3_r5_remoteproc]
[ 11.270821] platform_drv_probe+0x54/0xa8
[ 11.274815] really_probe+0xe4/0x3b0
[ 11.278375] driver_probe_device+0x58/0xb8
[ 11.282456] device_driver_attach+0x74/0x80
[ 11.286623] __driver_attach+0x58/0xe0
[ 11.290361] bus_for_each_dev+0x70/0xc0
[ 11.294181] driver_attach+0x24/0x30
[ 11.297742] bus_add_driver+0x14c/0x1f0
[ 11.301563] driver_register+0x64/0x120
[ 11.305384] __platform_driver_register+0x48/0x58
[ 11.310072] k3_r5_rproc_driver_init+0x20/0x10000 [ti_k3_r5_remoteproc]
[ 11.316668] do_one_initcall+0x54/0x1b8
[ 11.320492] do_init_module+0x54/0x208
[ 11.324227] load_module+0x1f28/0x24c8
[ 11.327962] __do_sys_finit_module+0xb8/0xf8
[ 11.332217] __arm64_sys_finit_module+0x20/0x30
[ 11.336733] el0_svc_common.constprop.0+0x78/0x1a0
[ 11.341507] do_el0_svc+0x24/0x90
[ 11.344809] el0_svc+0x14/0x20
[ 11.347849] el0_sync_handler+0xb0/0xb8
[ 11.351669] el0_sync+0x180/0x1c0
[ 11.354973] Code: 128002b3 913ee021 97ffe8cb 1400002e (b87a6b20)
[ 11.361050] ---[ end trace 992742233e6b2917 ]---
The same steps have been tested many times on EVM using SDK7.02, and no panic will occur.