TDA4VM: Changed MCU1_0 binary and now I have an boot error

Hi Mircea,

ti-dm/j721e/ipc_echo_testb_mcu1_0_release_strip.xer5f

The post you referred is pointing to the above file. Could you try with the above file in your build and then incrementally add your changes.

Best Regards,

Keerthy 

whats the diference between these 2? :

ipc_echo_testb_mcu1_0_release_strip.xer5f

ipc_echo_test_mcu1_0_release_strip.xer5f

I will try it the next day, currently trying to read on how the TI boot loaders work, having to ask e2e constantly for support is not a good engineering practice :(

Still, I am wondering, if I use the other approach, to create one big file "app" with all cores, as SDK RTOS chapter 9.2.2 says, that would solve my issues right? there is just one unknown, will there be any software booted on mcu1_0 as this would be the core running the "tiboot3.bin" right?

Br, Mircea

I do not have the projects to output the "ipc_echo_testb_mcu1_0_release_strip"

All I have is this:

ipc_echo_testb_freertos

ipc_rtos_echo_testb_freertos

ipc_qnx_echo_testb_freertos

ipc_rtos_multicore_echo_testb_freertos

I used the : ipc_echo_testb_freertos, but with no luck, the board does not boot:

I copied it to ti-bm, prebuild images location, made make u-boot , make u-boot_install, checked the BOOT to see updated timestamps, they where uptdated, copied the binary to /lib/firmware, made the links, got this output on uart:

U-Boot SPL 2023.04 (Nov 24 2023 - 09:33:06 +0200)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.6--v09.00.06 (Kool Koala)')
Trying to boot from MMC2
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Loading Environment from nowhere... OK
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.9(release):v2.9.0-dirty
NOTICE:  BL31: Built : 14:12:59, May 22 2023
I/TC:  
I/TC: OP-TEE version: 3.20.0 (gcc version 11.3.0 (GCC)) #1 Fri Jan 20 15:42:54 UTC 2023 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check optee.readthedocs.io/.../porting_guidelines.html
I/TC: Primary CPU initializing
I/TC: SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.6--v09.00.06 (Kool Koala)')
I/TC: HUK Initialized
I/TC: Activated SA2UL device
I/TC: Fixing SA2UL firewall owner for GP device
I/TC: Enabled firewalls for SA2UL TRNG device
I/TC: SA2UL TRNG initialized
I/TC: SA2UL Drivers initialized
I/TC: Primary CPU switching to normal world boot

U-Boot SPL 2023.04 (Nov 24 2023 - 09:33:03 +0200)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.6--v09.00.06 (Kool Koala)')
Detected: J7X-BASE-CPB rev A
Detected: J7X-VSC8514-ETH rev E2
Trying to boot from MMC2
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted


U-Boot 2023.04 (Nov 24 2023 - 09:33:03 +0200)

SoC:   J721E SR1.1 GP
Model: Texas Instruments K3 J721E SoC
Board: J721EX-PM2-SOM rev A
DRAM:  4 GiB
Core:  125 devices, 34 uclasses, devicetree: separate
Flash: 0 Bytes
MMC:   mmc@4f80000: 0, mmc@4fb0000: 1
Loading Environment from nowhere... OK
In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
am65_cpsw_nuss ethernet@46000000: K3 CPSW: nuss_ver: 0x6BA00101 cpsw_ver: 0x6BA80100 ale_ver: 0x00293904 Ports:1 mdio_freq:1000000
Detected: J7X-BASE-CPB rev A
Detected: J7X-VSC8514-ETH rev E2
cdns,sierra serdes@5000000: sierra probed
Net:   eth0: ethernet@46000000port@1
Hit any key to stop autoboot:  0  
switch to partitions #0, OK
mmc1 is current device
SD/MMC found on device 1
Failed to load 'boot.scr'
0 bytes read in 1 ms (0 Bytes/s)
Loaded env from uEnv.txt
Importing environment from mmc1 ...
gpio: pin gpio@22_17 (gpio 281) value is 1
gpio: pin gpio@22_16 (gpio 280) value is 0
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
626036 bytes read in 42 ms (14.2 MiB/s)
Load Remote Processor 2 with data@addr=0x82000000 626036 bytes: Success!
98444 bytes read in 33 ms (2.8 MiB/s)
Load Remote Processor 3 with data@addr=0x82000000 98444 bytes: Success!
98444 bytes read in 31 ms (3 MiB/s)
Load Remote Processor 4 with data@addr=0x82000000 98444 bytes: Success!
98444 bytes read in 32 ms (2.9 MiB/s)
Load Remote Processor 5 with data@addr=0x82000000 98444 bytes: Success!
144692 bytes read in 33 ms (4.2 MiB/s)
Load Remote Processor 6 with data@addr=0x82000000 144692 bytes: Success!
144692 bytes read in 33 ms (4.2 MiB/s)
Load Remote Processor 7 with data@addr=0x82000000 144692 bytes: Success!
10489000 bytes read in 272 ms (36.8 MiB/s)
Load Remote Processor 8 with data@addr=0x82000000 10489000 bytes: Success!
19276288 bytes read in 443 ms (41.5 MiB/s)
Failed to load '/boot/dtb/ti/k3-j721e-common-proc-board.dtb'
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
switch to partitions #0, OK
mmc0(part 0) is current device
** No partition table - mmc 0 **
Couldn't find partition mmc 0:1
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
No EFI system partition
No EFI system partition
Failed to persist EFI variables
BootOrder not defined
EFI boot manager: Cannot load any image
starting USB...
Bus usb@6400000: cdns-usb3-host usb@6400000: Unable to get USB2 phy (ret -61)
cdns-usb3-host usb@6400000: Unable to get USB3 phy (ret -61)
cdns-usb3-host usb@6400000: DRD version v1 (ID: 0004024e, rev: 00000200)
Register 2000840 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus usb@6400000 for devices... 4 USB Device(s) found
      scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device
k3-navss-ringacc ringacc@2b800000: Ring Accelerator probed rings:286, gp-rings[96,20] sci-dev-id:235
k3-navss-ringacc ringacc@2b800000: dma-ring-reset-quirk: disabled
am65_cpsw_nuss_port ethernet@46000000port@1: K3 CPSW: rflow_id_base: 2
ethernet@46000000port@1 Waiting for PHY auto negotiation to complete......... TIMEOUT !
am65_cpsw_nuss_port ethernet@46000000port@1: phy_startup failed
am65_cpsw_nuss_port ethernet@46000000port@1: am65_cpsw_start end error
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/01-34-08-e1-5b-64-7e
am65_cpsw_nuss_port ethernet@46000000port@1: K3 CPSW: rflow_id_base: 2
ethernet@46000000port@1 Waiting for PHY auto negotiation to complete......... TIMEOUT !
am65_cpsw_nuss_port ethernet@46000000port@1: phy_startup failed
am65_cpsw_nuss_port ethernet@46000000port@1: am65_cpsw_start end error

Hello again,

I put the  pre-build image from the sdk ( latest one ), and replace the u-boot, recompiled with my can application, updated the binman file, made u-boot and -uboot install, replaced in the firmware folder, made links, and no luck:

U-Boot SPL 2023.04 (Nov 24 2023 - 11:46:28 +0200)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.6--v09.00.06 (Kool Koala)')
Trying to boot from MMC2
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Loading Environment from nowhere... OK
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.9(release):v2.9.0-dirty
NOTICE:  BL31: Built : 14:12:59, May 22 2023
I/TC:  
I/TC: OP-TEE version: 3.20.0 (gcc version 11.3.0 (GCC)) #1 Fri Jan 20 15:42:54 UTC 2023 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check optee.readthedocs.io/.../porting_guidelines.html
I/TC: Primary CPU initializing
I/TC: SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.6--v09.00.06 (Kool Koala)')
I/TC: HUK Initialized
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 sa2ul_init:59 Failed to get SA2UL device
E/TC:0 0 call_initcalls:43 Initcall __text_start + 0x00067bf8 failed
I/TC: Primary CPU switching to normal world boot
E/TC:0 0  
E/TC:0 0 Core data-abort at address 0x10 (translation fault)
E/TC:0 0  esr 0x96000005  ttbr0 0x9e898000   ttbr1 0x00000000   cidr 0x0
E/TC:0 0  cpu #0          cpsr 0x800003c4
E/TC:0 0  x0  0000000000000010 x1  0000000000000001
E/TC:0 0  x2  0000000000000000 x3  0000000000000000
E/TC:0 0  x4  000000009e86c000 x5  0000000000ffffff
E/TC:0 0  x6  0000000000000002 x7  000000009e8a0190
E/TC:0 0  x8  0000000000000020 x9  000000009e8a0190
E/TC:0 0  x10 0000000000000000 x11 0000000000000000
E/TC:0 0  x12 0000000000000000 x13 000000009e8618f0
E/TC:0 0  x14 0000000000000000 x15 0000000000000000
E/TC:0 0  x16 000000009e8149e4 x17 0000000000000000
E/TC:0 0  x18 0000000000000000 x19 000000009e8a2ca0
E/TC:0 0  x20 000000009e8a2ca8 x21 0000000000000007
E/TC:0 0  x22 000000009e878000 x23 000000009e878b50
E/TC:0 0  x24 0000000100000000 x25 0000000000000000
E/TC:0 0  x26 0000000000000000 x27 0000000000000000
E/TC:0 0  x28 0000000000000000 x29 000000009e8a2c30
E/TC:0 0  x30 000000009e80eb7c elr 000000009e80eb9c
E/TC:0 0  sp_el0 000000009e8a2c30
E/TC:0 0 TEE load address @ 0x9e800000
E/TC:0 0 Call stack:
E/TC:0 0  0x9e80eb9c
E/TC:0 0 Panic 'unhandled pageable abort' at core/arch/arm/kernel/abort.c:572 <abort_handler>
E/TC:0 0 TEE load address @ 0x9e800000
E/TC:0 0 Call stack:
E/TC:0 0  0x9e808b04
E/TC:0 0  0x9e815f88
E/TC:0 0  0x9e808260
E/TC:0 0  0x9e805584

This uses the TCM - B. Hence the b is additional.

Mircea Cociuba said:

ipc_echo_testb_freertos

This clubbed with CORE=MCU1_0 should build the necessary firmware.

- Keerthy

I did not understand you :), please can you expand the explanation, maybe point to what I am doing wrong?

Hi Mircea,

I believe you have the RTOS SDK for TDA4VM: https://www.ti.com/tool/download/PROCESSOR-SDK-RTOS-J721E/09.00.01.01

cd $SDK_PATH/pdk_jacinto_09_00_00_45/packages/ti/build

make ipc_echo_testb_freertos

The above should generate:

Mircea Cociuba said:

ipc_echo_testb_mcu1_0_release_strip.xer5f

Please use that to boot & let me know if that is working. Post that you can do your changes incrementally.

Regards,
Keerthy

mircea@chimen:~/Downloads/ti-processor-sdk-rtos-j721e-evm-09_00_01_01/pdk_jacinto_09_00_01_04/packages$ make ipc_echo_testb_freertos

make: *** No rule to make target 'ipc_echo_testb_freertos'.  Stop.
mircea@chimen:~/Downloads/ti-processor-sdk-rtos-j721e-evm-09_00_01_01/pdk_jacinto_09_00_01_04/packages$

Mircea Cociuba said:

mircea@chimen:~/Downloads/ti-processor-sdk-rtos-j721e-evm-09_00_01_01/pdk_jacinto_09_00_01_04/packages$ make ipc_echo_testb_freertos

Wrong folder.

Please check:

Keerthy J said:

cd $SDK_PATH/pdk_jacinto_09_00_00_45/packages/ti/build

- Keerthy

yes.....rookie mistake....sorry for that, doing the tests now

it booted :) now what, how can I check that the mcu1_0 is doing what should do?

Mircea,

That's cool. So this is DM - Device Manager binary. You can add your custom changes incrementally and see if that fails?

Best Regards,

Keerthy 

sporadic I have kernel panics:

Can you make heads or tails of this log:

[   12.026241] PVR_K:  659: RGX Firmware image 'rgx.fw.22.104.208.318' loaded
[   12.037382] input: Dell KB216 Wired Keyboard as /devices/platform/bus@100000/4114000.cdns-usb/6400000.usb/xhci-hcd.13.auto/usb1/1-1/1-1.3/1-1.3:1.0/00032
[   12.065378] PVR_K:  659: Shader binary image 'rgx.sh.22.104.208.318' loaded
[   12.113052] hid-generic 0003:413C:2113.0002: input: USB HID v1.11 Keyboard [Dell KB216 Wired Keyboard] on usb-xhci-hcd.13.auto-1.3/input0
[   12.130226] input: Dell KB216 Wired Keyboard System Control as /devices/platform/bus@100000/4114000.cdns-usb/6400000.usb/xhci-hcd.13.auto/usb1/1-1/1-1.33
[   12.144675] ti-sci 44083000.system-controller: Mbox timedout in resp(caller: sci_clk_determine_rate+0x64/0xe4)
[   12.147862] ti-sci 44083000.system-controller: Mbox timedout in resp(caller: k3_ringacc_ring_reset_sci+0x68/0xbc)
[   12.157602] ti-sci 44083000.system-controller: Mbox send fail -110
[   12.169163] ti-sci 44083000.system-controller: RM_RA:Mbox config send fail -110
[   12.174002] ti-sci-clk 44083000.system-controller:clock-controller: determine-rate failed for dev=277, clk=0, ret=-110
[   12.181719] k3-ringacc 3c000000.ringacc: TISCI reset ring fail (-110) ring_idx 370
[   12.191971] cdns-ufshcd 4e84000.ufs: ufshcd_init_clocks: core_clk clk set rate(250000000Hz) failed, -22
[   12.208905] cdns-ufshcd 4e84000.ufs: Initialization failed
[   12.212846] input: Dell KB216 Wired Keyboard Consumer Control as /devices/platform/bus@100000/4114000.cdns-usb/6400000.usb/xhci-hcd.13.auto/usb1/1-1/1-14
[   12.232012] hid-generic 0003:413C:2113.0003: input: USB HID v1.11 Device [Dell KB216 Wired Keyboard] on usb-xhci-hcd.13.auto-1.3/input1
[   12.245501] cdns-ufshcd 4e84000.ufs: ufshcd_pltfrm_init() failed -22
[   12.251944] cdns-ufshcd: probe of 4e84000.ufs failed with error -22

_____                    _____           _         _    
|  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_  
|     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
|__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|   
             |___|                    |___|             

Arago Project j721e-evm -

Arago 2023.04 j721e-evm -

j721e-evm login: [   13.008670] ti-sci 44083000.system-controller: Mbox timedout in resp(caller: ti_sci_cmd_get_device_exclusive+0x18/0x2c)
[   13.019482] ti-sci 44083000.system-controller: Mbox send fail -110
[   13.104665] ti-sci 44083000.system-controller: Mbox timedout in resp(caller: ti_sci_cmd_get_device_exclusive+0x18/0x2c)
[   13.115458] ti-sci 44083000.system-controller: Mbox send fail -110
[   13.121637] PVR_K:  659: SysDevPostPowerState: failed to resume
[   13.127556] PVR_K:(Error):   659: PVRSRVDeviceFinalise: Failed to set device 000000000530ba13 power state to 'on' (PVRSRV_ERROR_DEVICE_POWER_CHANGE_FAIL]
[   13.142135] PVR_K:(Error):   659: PVRSRVDeviceFinalise() failed (PVRSRV_ERROR_DEVICE_POWER_CHANGE_FAILURE) in PVRSRVCommonDeviceInitialise() [2487]
[   13.155330] PVR_K:(Error):   659: PVRSRVDeviceServicesOpen: Failed to initialise device (PVRSRV_ERROR_DEVICE_POWER_CHANGE_FAILURE) [512]
[   13.200690] ti-sci 44083000.system-controller: Mbox timedout in resp(caller: k3_ringacc_ring_reset_sci+0x68/0xbc)
[   13.211004] ti-sci 44083000.system-controller: RM_RA:Mbox config send fail -110
[   13.218335] k3-ringacc 3c000000.ringacc: TISCI reset ring fail (-110) ring_idx 473
[   14.032759] ti-sci 44083000.system-controller: Mbox timedout in resp(caller: ti_sci_cmd_get_device_exclusive+0x18/0x2c)
[   14.043654] ti-sci 44083000.system-controller: Mbox send fail -110
[   14.256694] ti-sci 44083000.system-controller: Mbox timedout in resp(caller: ti_sci_cmd_free_event_map+0x40/0x50)
[   14.267010] ti-sci 44083000.system-controller: Mbox send fail -110
[   15.056665] ti-sci 44083000.system-controller: Mbox timedout in resp(caller: ti_sci_cmd_get_device_exclusive+0x18/0x2c)
[   15.056666] ti-sci 44083000.system-controller: Mbox timedout in resp(caller: ti_sci_cmd_get_device_exclusive+0x18/0x2c)
[   15.056704] ti-sci 44083000.system-controller: Mbox send fail -110
[   15.067465] ti-sci 44083000.system-controller: Mbox send fail -110
[   15.067542] ------------[ cut here ]------------
[   15.095140] WARNING: CPU: 1 PID: 711 at drivers/gpu/drm/tidss/tidss_drv.c:37 tidss_runtime_get+0x30/0x50 [tidss]
[   15.105311] Modules linked in: xhci_plat_hcd pci_endpoint_test overlay rpmsg_ctrl rpmsg_char omap_rng ti_am335x_adc(+) kfifo_buf pru_rproc irq_pruss_intt
[   15.105428]  cryptodev(O) fuse drm drm_panel_orientation_quirks ipv6
[   15.197923] CPU: 1 PID: 711 Comm: kworker/u4:4 Tainted: G      D    O       6.1.46-gf8110d9ce8 #1
[   15.206773] Hardware name: Texas Instruments J721e EVM (DT)
[   15.212328] Workqueue: events_unbound commit_work [drm_kms_helper]
[   15.218529] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[   15.225472] pc : tidss_runtime_get+0x30/0x50 [tidss]
[   15.230428] lr : tidss_runtime_get+0x18/0x50 [tidss]
[   15.235382] sp : ffff80000abdbd50
[   15.238683] x29: ffff80000abdbd50 x28: 0000000000000000 x27: 0000000000000000
[   15.245801] x26: ffff8000093f9b78 x25: ffff000800009005 x24: ffff00080add44e0
[   15.252919] x23: ffff000800009000 x22: ffff800001186cc8 x21: 000000033cfc4d76
[   15.260036] x20: ffff000807642000 x19: ffff00080add4480 x18: ffffffffffffffff
[   15.267154] x17: 3a72656c6c616328 x16: 70736572206e6920 x15: ffff80000940dd98
[   15.274271] x14: 0000000000000000 x13: ffff80000940dd93 x12: fffffffffffcdcdf
[   15.281389] x11: ffff8000092d1540 x10: 000000000000000a x9 : 000000000000006e
[   15.288506] x8 : ffff8000092d14f8 x7 : ffff80000abdb810 x6 : ffff000800d20990
[   15.295624] x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffff000800d208f4
[   15.302742] x2 : 0000000000000000 x1 : ffff00080ae74740 x0 : 00000000ffffff92
[   15.309860] Call trace:
[   15.312293]  tidss_runtime_get+0x30/0x50 [tidss]
[   15.316902]  tidss_atomic_commit_tail+0x20/0x80 [tidss]
[   15.322117]  commit_tail+0xa4/0x190 [drm_kms_helper]
[   15.327090]  commit_work+0x14/0x20 [drm_kms_helper]
[   15.331976]  process_one_work+0x1d0/0x320
[   15.335976]  worker_thread+0x14c/0x444
[   15.339711]  kthread+0x10c/0x110
[   15.342930]  ret_from_fork+0x10/0x20
[   15.346495] ---[ end trace 0000000000000000 ]---
[   15.351313] ti-sci 44083000.system-controller: Mbox timedout in resp(caller: ti_sci_cmd_free_irq+0x40/0x50)
[   15.353084] SError Interrupt on CPU0, code 0x00000000bf000000 -- SError
[   15.353092] CPU: 0 PID: 711 Comm: kworker/u4:4 Tainted: G      D W  O       6.1.46-gf8110d9ce8 #1
[   15.353097] Hardware name: Texas Instruments J721e EVM (DT)
[   15.353099] Workqueue: events_unbound commit_work [drm_kms_helper]
[   15.353143] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[   15.353147] pc : dispc_plane_setup+0x114/0x760 [tidss]
[   15.353161] lr : dispc_plane_setup+0xc8/0x760 [tidss]
[   15.353170] sp : ffff80000abdbc10
[   15.353172] x29: ffff80000abdbc10 x28: 0000000000000004 x27: ffff00080ab51a00
[   15.353177] x26: 00000008e0c00000 x25: 0000000034325258 x24: 0000000000000001
[   15.353181] x23: 0000000000000780 x22: 0000000000000001 x21: ffff000802362480
[   15.353186] x20: ffff8000011877e8 x19: 0000000000000001 x18: ffffffffffffffff
[   15.353190] x17: 3a72656c6c616328 x16: 70736572206e6920 x15: ffff80000940dd98
[   15.353194] x14: 0000000000000000 x13: ffff80000940dd93 x12: fffffffffffcdcdf
[   15.353198] x11: ffff8000092d1540 x10: 000000000000000a x9 : ffff0008076e7800
[   15.353202] x8 : ffff80000abdbcd8 x7 : 0000000000000000 x6 : 000000003231564e
[   15.353206] x5 : 0000000034325258 x4 : ffff800001187ac8 x3 : 0000000000000027
[   15.353210] x2 : 0000000000000780 x1 : ffff000802362488 x0 : 0000000000000000
[   15.353216] Kernel panic - not syncing: Asynchronous SError Interrupt
[   15.353219] SMP: stopping secondary CPUs
[   15.361075] Kernel Offset: disabled
[   15.361076] CPU features: 0x40000,20028084,0000420b
[   15.361079] Memory Limit: none
[   15.501425] ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]---

Hi,

Mircea Cociuba said:

[   13.019482] ti-sci 44083000.system-controller: Mbox send fail -110
[   13.104665] ti-sci 44083000.system-controller: Mbox timedout in resp(caller: ti_sci_cmd_get_device_exclusive+0x18/0x2c)
[   13.115458] ti-sci 44083000.system-controller: Mbox send fail -110

This is bad. MCU1_0 is not responding. Is this something that you got with the firmware you built without making any of your code changes?

- Keerthy

Hi Mircea,

These errors typically happen when the MCU1_0 firmware is not responding properly to the TI-SCI message requests from the Linux-side.

It is very strange that you are seeing this with your version of the ipc_echo_testb_freertos. Do you see the same issues with the prebuilt bootloader or prebuilt firmware image (found is board-support/prebuilt-images).

regards

Suman

Hello Suman and Keerthy,

I do not see these error with the default binary that Keerthy sugested to use. I added the CAN code and freertos to it to have a working CAN, I copy pasted the CAN code from csl_mcan_testapp., I added the freertos myself based on other sample codes.Maybe there is some synergy between MCU1_0 and Linux that I am not seeing, must I respect some timeline for starting the CAN tasks between the bootup and CAN task start?

small update: if Canoe ( the can monitoring tool) is not connected, measuring and recording can data, there is no error, it boots normaly.

Hi Mircea,

Are you pausing the MCU1_0 core, while trying to run other cores?

regards

Suman

No ideea, I am merging a baremetal csl_mcan application with the ipc_rtos_testb_echo. Do you happen to have  some freertos can demo code for MCU1_0 ( non mcsw) that I can re-use? 

Hi Mircea,

There's a csl_mcan_unit_test_app_freertos application, but it is not meant to be run with Linux.

The CSL applications by nature are standalone applications. I will reassign this thread to an engineer who supports CAN, if that is the IP of interest (deviation from original thread title again).

regards

Suman

The boot errors are mostly gone, but still the Linux u-boot is unstable.

Regarding deviation, how about this, I stick to one thread if you realy start helping me out get something up and running, fair exchange :). 

Creating Frankenstein software from demo code is not a good practice, and I am tired of it, especially given what we have time left.

If TI does not help with this, then it is what it is.

Thanks for quick answers btw.

Mircea

Ok, you can close this thread.