TDA4VM: After activating the automatic parking function, the probability of mcan_ir=0x50 is very high

lify

Part Number: TDA4VM

HI TI

I found a problem is that after activating the automatic parking function, the probability of mcan_ir=0x50 is very high. Even if the automatic parking function is exited after startup, this issue still exists. But if the automatic parking function is not activated, this problem will not occur.In all cases, the frequency of can data sent to TDA4 on the can bus is the same。

The automatic parking function uses perception algorithms and Tidl, but runs on the A72 core C66 or C7x core. It's very strange why the can module of mcu1-0 has been affected？

I found that after entering the automatic parking function, the time for reading can data from the register occasionally increases.Even if I put the functions that read can data into internal memory for execution.
Can you provide some suggestions on how to analyze this phenomenon?

over 2 years ago

0 Tarun Mukesh Puvvada over 2 years ago

TI__Guru 50156 points

Hello,

1) Is you automatic parking function generating any CAN data or expecting CAN data on CAN BUS?

lify said:
the frequency of can data sent to TDA4 on the can bus is the same。

Is there no change on CAN Tx and Rx profile when running automatic parking function ?

2) Does the MCU1_0 share DDR with A72/C66/C7x. I see you mentioned that you are using the Internal Memory from MCU1_0 but want to make sure that you are not running into any DDR bandwidth issues.

lify said:
I found that after entering the automatic parking function, the time for reading can data from the register occasionally increases.Even if I put the functions that read can data into internal memory for execution.
Can you provide some suggestions on how to analyze this phenomenon?

3) How much is the time delta and how are you computing this? Is there any dependency between the MCU1_0 and the Automatic Parking function?

4) What are the messages on Rx FIFO1 when you get MCAN_IR=0x50 new message and Rx FIFO Full ?

Regards

Tarun Mukesh

0 lify over 2 years ago in reply to Tarun Mukesh Puvvada

Intellectual 290 points

hi Tarun

1)Is there no change on CAN Tx and Rx profile when running automatic parking function ?

----------> There is no change between parking and no parking

2) Does the MCU1_0 share DDR with A72/C66/C7x. I see you mentioned that you are using the Internal Memory from MCU1_0 but want to make sure that you are not running into any DDR bandwidth issues.

---------------> I think all cores share DDR, but I am not sure about this. How can I determine? how to confirm whether MCU1_0 share DDR with A72/C66/C7x?

3)How much is the time delta and how are you computing this? Is there any dependency between the MCU1_0 and the Automatic Parking function?

---------------> if not in automatic parking, read 1 frame can data about 20 ms,but in parking some time above 50ms 60ms Even greater than 100ms 。There is ipc data transmission between the parking application and the can, after mcu1-0 receives the can data, it is transmitted to A72 through ipc.

4）What are the messages on Rx FIFO1 when you get MCAN_IR=0x50 new message and Rx FIFO Full ?

--------->I can't determine which frame of can message it is because the message rate on the car is too fast

Does the MCAN function use DMA？

The project is approaching mass production and is very urgent. Please help analyze it as soon as possible. Thank you

0 Tarun Mukesh Puvvada over 2 years ago in reply to lify

TI__Guru 50156 points

Hello,

Sorry for the delay and by mistake " TI thinks resolved " got clicked.

Can you share below points

1. Map file of MCU1_0 application and Linux/HLOS boot logs.

2. Flow/Sequence diagram of MCU1_0 application and its interactions with A72 Parking app.

3. Profile points for the 50ms time for reading CAN frame.

4. What is the CAN driver being used? AutoSAR or CSL-FL? and which SDK version is being used ?

We get MCAN_IR=0x50 when Rx FIFO1 is full , the received messages are not getting drained as the incoming.

Thanks

Tarun Mukesh

0 lify over 2 years ago in reply to Tarun Mukesh Puvvada

Intellectual 290 points

hi Tarun Mukesh

1. Map file of MCU1_0 application and Linux/HLOS boot logs.

----------------->the map file do you mean the file linker_mem_map? we didn't change the file.

2. Flow/Sequence diagram of MCU1_0 application and its interactions with A72 Parking app.

------------------->can data-->can_driver(mcu1_0)---ipc---->A72

3.Profile points for the 50ms time for reading CAN frame.

------------------->I read the fifo all when interrupt arrive, The probability of fifo=50 will decrease。but i found that, The generated interrupt for receiving data is slightly less than the actual number of can messages on the can bus。

4.What is the CAN driver being used? AutoSAR or CSL-FL? and which SDK version is being used ?

------------- >We refer to the mcan_evm_loopback_app_main_k3.c file when writing the can driver program. our sdk is 08.02

0 lify over 2 years ago in reply to lify

Intellectual 290 points

Fullscreen 2112.txt Download

U-Boot SPL 2021.01 (May 17 2023 - 10:24:38 +0000)
Model: Texas Instruments K3 J721E SoC
SYSFW ABI: 3.1 (firmware rev 0x0016 '22.1.1--v2022.01 (Terrific Llam')
** File not found apainfo **
Trying to boot from MMC1
init_env from device 17 not supported!
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.5(release):08.01.00.006-dirty
NOTICE:  BL31: Built : 21:03:57, Mar 23 2022

U-Boot SPL 2021.01 (May 17 2023 - 10:30:28 +0000)
Model: Texas Instruments K3 J721E SoC
SYSFW ABI: 3.1 (firmware rev 0x0016 '22.1.1--v2022.01 (Terrific Llam')
Trying to boot from MMC1


U-Boot 2021.01 (May 17 2023 - 10:30:28 +0000)

SoC:   J721E SR1.1
Model: Texas Instruments K3 J721E SoC
DRAM:  4 GiB
Flash: 0 Bytes
MMC:   sdhci@4f80000: 0, sdhci@4fb0000: 1
In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
power lock set suc ...
switch to partitions #0, OK
mmc0(part 0) is current device
SD/MMC found on device 0
Failed to load 'boot.scr'
** Unrecognized filesystem type **
ab_boot: mmcdev = 0
ab_boot: boot_control_env size 4096
ab_boot: origin_mmc_hw_part 0
ab_boot: blk start 1DB0 cnt 8 result 8
ab_boot: boot_active_slot 1
ab_boot: boot_attempt_count 0
ab_boot: boot_slot1_priority 15
ab_boot: boot_slot1_success 1
ab_boot: boot_slot2_priority 15
ab_boot: boot_slot2_success 0
ab_boot: last active boot slot is 1
ab_boot: active slot can boot success, try count = 0
ab_boot: active slot 1, attemp count 0
ab_boot: set env bootpart(0:1) & active(1) success
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
867764 bytes read in 18 ms (46 MiB/s)
Load Remote Processor 2 with data@addr=0x82000000 867764 bytes: Success!
301944 bytes read in 11 ms (26.2 MiB/s)
Load Remote Processor 3 with data@addr=0x82000000 301944 bytes: Success!
212216 bytes read in 11 ms (18.4 MiB/s)
Load Remote Processor 4 with data@addr=0x82000000 212216 bytes: Success!
121752 bytes read in 10 ms (11.6 MiB/s)
Load Remote Processor 5 with data@addr=0x82000000 121752 bytes: Success!
1452820 bytes read in 25 ms (55.4 MiB/s)
Load Remote Processor 6 with data@addr=0x82000000 1452820 bytes: Success!
1452852 bytes read in 25 ms (55.4 MiB/s)
Load Remote Processor 7 with data@addr=0x82000000 1452852 bytes: Success!
13242432 bytes read in 158 ms (79.9 MiB/s)
Load Remote Processor 8 with data@addr=0x82000000 13242432 bytes: Success!
18071560 bytes read in 212 ms (81.3 MiB/s)
101153 bytes read in 9 ms (10.7 MiB/s)
11732 bytes read in 8 ms (1.4 MiB/s)
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
   Loading Device Tree to 000000008fee4000, end 000000008fffffff ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd080]
[    0.000000] Linux version 5.10.100-g7a7a3af903 (guoyongsheng@hw226) (aarch64-none-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 9.2.1 20191025, GNU ld (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 2.33.1.20191209) #1 SMP PREEMPT Thu May 11 10:44:52 UTC 2023
[    0.000000] Machine model: Texas Instruments J721E SK
[    0.000000] earlycon: ns16550a0 at MMIO32 0x0000000002800000 (options '')
[    0.000000] printk: bootconsole [ns16550a0] enabled
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a0000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node vision-apps-r5f-dma-memory@a0000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a0100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node vision-apps-r5f-memory@a0100000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a1000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node vision-apps-r5f-dma-memory@a1000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a1100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node vision-apps-r5f-memory@a1100000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a2000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node vision-apps-r5f-dma-memory@a2000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a2100000, size 31 MiB
[    0.000000] OF: reserved mem: initialized node vision-apps-r5f-memory@a2100000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a4000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node vision-apps-r5f-dma-memory@a4000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a4100000, size 31 MiB
[    0.000000] OF: reserved mem: initialized node vision-apps-r5f-memory@a4100000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a6000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node vision-apps-r5f-dma-memory@a6000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a6100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node vision-apps-r5f-memory@a6100000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a7000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node vision-apps-r5f-dma-memory@a7000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a7100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node vision-apps-r5f-memory@a7100000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a8000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node vision-apps-c66-dma-memory@a8000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a8100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node vision-apps-c66-memory@a8100000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a9000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node vision-apps-c66-dma-memory@a9000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a9100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node vision-apps-c66-memory@a9100000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000aa000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node vision-apps-c71-dma-memory@aa000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000aa100000, size 79 MiB
[    0.000000] OF: reserved mem: initialized node vision-apps-c71-memory@aa100000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000b2000000, size 96 MiB
[    0.000000] OF: reserved mem: initialized node vision-apps-dma-memory@b2000000, compatible id shared-dma-pool
[    0.000000] OF: reserved mem: initialized node vision_apps_shared-memories, compatible id dma-heap-carveout
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000d8000000, size 560 MiB
[    0.000000] OF: reserved mem: initialized node vision-apps-core-heap-memory-lo@d8000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000fb000000, size 8 MiB
[    0.000000] OF: reserved mem: initialized node vision-apps-r5f-virtual-eth-queues@fb000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000fb800000, size 24 MiB
[    0.000000] OF: reserved mem: initialized node vision-apps-r5f-virtual-eth-buffers@fb800000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x0000000880000000, size 256 MiB
[    0.000000] OF: reserved mem: initialized node vision-apps-core-heap-memory-hi@880000000, compatible id shared-dma-pool
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000080000000-0x00000000ffffffff]
[    0.000000]   DMA32    empty
[    0.000000]   Normal   [mem 0x0000000100000000-0x00000008ffffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000080000000-0x000000009e7fffff]
[    0.000000]   node   0: [mem 0x000000009e800000-0x00000000aeffffff]
[    0.000000]   node   0: [mem 0x00000000af000000-0x00000000afffffff]
[    0.000000]   node   0: [mem 0x00000000b0000000-0x00000000b7ffffff]
[    0.000000]   node   0: [mem 0x00000000b8000000-0x00000000d7ffffff]
[    0.000000]   node   0: [mem 0x00000000d8000000-0x00000000fcffffff]
[    0.000000]   node   0: [mem 0x00000000fd000000-0x00000000ffffffff]
[    0.000000]   node   0: [mem 0x0000000880000000-0x000000088fffffff]
[    0.000000]   node   0: [mem 0x0000000890000000-0x00000008ffffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x00000008ffffffff]
[    0.000000] cma: Failed to reserve 512 MiB
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: Trusted OS migration not required
[    0.000000] psci: SMC Calling Convention v1.2
[    0.000000] percpu: Embedded 2 pages/cpu s49368 r8192 d73512 u131072
[    0.000000] Detected PIPT I-cache on CPU0
[    0.000000] CPU features: detected: GIC system register CPU interface
[    0.000000] CPU features: detected: EL2 vector hardening
[    0.000000] CPU features: detected: ARM errata 1165522, 1319367, or 1530923
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 65472
[    0.000000] Kernel command line: console=ttyS2,115200n8 earlycon=ns16550a,mmio32,0x02800000 mtdparts=47040000.spi.0:512k(ospi.tiboot3),2m(ospi.tispl),4m(ospi.u-boot),256k(ospi.env),1m(ospi.sysfw),256k(ospi.env.backup),57088k@8m(ospi.rootfs),256k(ospi.phypattern);47034000.hyperbus:512k(hbmc.tiboot3),2m(hbmc.tispl),4m(hbmc.u-boot),256k(hbmc.env),1m(hbmc.sysfw),-@8m(hbmc.rootfs) root=PARTUUID=f281463c-c8ff-9243-99fa-079adbffd9cd rw rootfstype=ext4 rootwait
[    0.000000] Dentry cache hash table entries: 524288 (order: 6, 4194304 bytes, linear)
[    0.000000] Inode-cache hash table entries: 262144 (order: 5, 2097152 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] software IO TLB: mapped [mem 0x000000009a7c0000-0x000000009e7c0000] (64MB)
[    0.000000] Memory: 2303744K/4194304K available (10366K kernel code, 1264K rwdata, 4032K rodata, 1600K init, 735K bss, 1890560K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu:     RCU event tracing is enabled.
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=2.
[    0.000000]  Trampoline variant of Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[    0.000000] GICv3: 960 SPIs implemented
[    0.000000] GICv3: 0 Extended SPIs implemented
[    0.000000] GICv3: Distributor has no Range Selector support
[    0.000000] GICv3: 16 PPIs implemented
[    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000001900000
[    0.000000] ITS [mem 0x01820000-0x0182ffff]
[    0.000000] GIC: enabling workaround for ITS: Socionext Synquacer pre-ITS
[    0.000000] ITS@0x0000000001820000: allocated 1048576 Devices @8a0800000 (flat, esz 8, psz 64K, shr 0)
[    0.000000] ITS: using cache flushing for cmd queue
[    0.000000] GICv3: using LPI property table @0x00000008a00b0000
[    0.000000] GIC: using cache flushing for LPI property table
[    0.000000] GICv3: CPU0: using allocated LPI pending table @0x00000008a00c0000
[    0.000000] random: get_random_bytes called from start_kernel+0x31c/0x4cc with crng_init=0
[    0.000000] arch_timer: cp15 timer(s) running at 200.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x2e2049d3e8, max_idle_ns: 440795210634 ns
[    0.000002] sched_clock: 56 bits at 200MHz, resolution 5ns, wraps every 4398046511102ns
[    0.008377] Console: colour dummy device 80x25
[    0.012941] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=800000)
[    0.023611] pid_max: default: 32768 minimum: 301
[    0.028359] LSM: Security Framework initializing
[    0.033112] Mount-cache hash table entries: 8192 (order: 0, 65536 bytes, linear)
[    0.040686] Mountpoint-cache hash table entries: 8192 (order: 0, 65536 bytes, linear)
[    0.049876] rcu: Hierarchical SRCU implementation.
[    0.054975] Platform MSI: msi-controller@1820000 domain created
[    0.061373] smp: Bringing up secondary CPUs ...
[    0.066772] Detected PIPT I-cache on CPU1
[    0.066798] GICv3: CPU1: found redistributor 1 region 0:0x0000000001920000
[    0.066809] GICv3: CPU1: using allocated LPI pending table @0x00000008a00d0000
[    0.066846] CPU1: Booted secondary processor 0x0000000001 [0x411fd080]
[    0.066908] smp: Brought up 1 node, 2 CPUs
[    0.096256] SMP: Total of 2 processors activated.
[    0.101061] CPU features: detected: 32-bit EL0 Support
[    0.106315] CPU features: detected: CRC32 instructions
[    0.120854] CPU: All CPU(s) started at EL2
[    0.125049] alternatives: patching kernel code
[    0.130141] devtmpfs: initialized
[    0.138841] KASLR disabled due to lack of seed
[    0.143524] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.153487] futex hash table entries: 512 (order: -1, 32768 bytes, linear)
[    0.160659] pinctrl core: initialized pinctrl subsystem
[    0.166504] NET: Registered protocol family 16
[    0.171297] DMA: preallocated 256 KiB GFP_KERNEL pool for atomic allocations
[    0.178653] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    0.186635] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    0.194742] ramoops: using module parameters
[    0.199145] ramoops ramoops: no room for dmesg mem region (0xffffffffffffe000@0x9e7c0000) in (0x40000@0x9e7c0000)
[    0.209642] ramoops: probe of ramoops failed with error -12
[    0.215457] thermal_sys: Registered thermal governor 'step_wise'
[    0.215459] thermal_sys: Registered thermal governor 'power_allocator'
[    0.221903] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.235537] ASID allocator initialised with 65536 entries
[    0.241835] printk: console [ramoops-1] enabled
[    0.246471] pstore: Registered ramoops as persistent store backend
[    0.252786] ramoops: using 0x40000@0x9e7c0000, ecc: 0
[    0.270784] HugeTLB registered 16.0 GiB page size, pre-allocated 0 pages
[    0.277645] HugeTLB registered 512 MiB page size, pre-allocated 0 pages
[    0.284408] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.292262] cryptd: max_cpu_qlen set to 1000
[    0.298268] k3-chipinfo 43000014.chipid: Family:J721E rev:SR2.0 JTAGID[0x1bb6402f] Detected
[    0.307038] vsys_3v3: supplied by vusb-main5v0
[    0.312004] iommu: Default domain type: Translated 
[    0.317179] SCSI subsystem initialized
[    0.321077] usbcore: registered new interface driver usbfs
[    0.326696] usbcore: registered new interface driver hub
[    0.332134] usbcore: registered new device driver usb
[    0.337523] mc: Linux media interface: v0.10
[    0.341894] videodev: Linux video capture interface: v2.00
[    0.347518] pps_core: LinuxPPS API ver. 1 registered
[    0.352590] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.361928] PTP clock support registered
[    0.365950] EDAC MC: Ver: 3.0.0
[    0.370108] clocksource: Switched to clocksource arch_sys_counter
[    0.376549] VFS: Disk quotas dquot_6.6.0
[    0.380612] VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 bytes)
[    0.390429] Carveout Heap: Exported 512 MiB at 0x00000000b8000000
[    0.396735] NET: Registered protocol family 2
[    0.401358] IP idents hash table entries: 65536 (order: 3, 524288 bytes, linear)
[    0.410029] tcp_listen_portaddr_hash hash table entries: 4096 (order: 0, 65536 bytes, linear)
[    0.418819] TCP established hash table entries: 32768 (order: 2, 262144 bytes, linear)
[    0.427022] TCP bind hash table entries: 32768 (order: 3, 524288 bytes, linear)
[    0.434853] TCP: Hash tables configured (established 32768 bind 32768)
[    0.441614] UDP hash table entries: 2048 (order: 0, 65536 bytes, linear)
[    0.448507] UDP-Lite hash table entries: 2048 (order: 0, 65536 bytes, linear)
[    0.455904] NET: Registered protocol family 1
[    0.460657] RPC: Registered named UNIX socket transport module.
[    0.466717] RPC: Registered udp transport module.
[    0.471535] RPC: Registered tcp transport module.
[    0.476341] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.483293] hw perfevents: enabled with armv8_cortex_a72 PMU driver, 7 counters available
[    0.493798] Initialise system trusted keyrings
[    0.498426] workingset: timestamp_bits=46 max_order=16 bucket_order=0
[    0.506725] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.512990] NFS: Registering the id_resolver key type
[    0.518191] Key type id_resolver registered
[    0.522467] Key type id_legacy registered
[    0.526591] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.533441] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[    0.541094] 9p: Installing v9fs 9p2000 file system support
[    0.565943] Key type asymmetric registered
[    0.570133] Asymmetric key parser 'x509' registered
[    0.575135] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243)
[    0.582696] io scheduler mq-deadline registered
[    0.587324] io scheduler kyber registered
[    0.592538] pinctrl-single 4301c000.pinctrl: 94 pins, size 376
[    0.598698] pinctrl-single 11c000.pinctrl: 173 pins, size 692
[    0.606100] k3-ringacc 2b800000.ringacc: Failed to get MSI domain
[    0.612374] k3-ringacc 3c000000.ringacc: Failed to get MSI domain
[    0.620288] Serial: 8250/16550 driver, 10 ports, IRQ sharing enabled
[    0.628332] arm-smmu-v3 36600000.iommu: ias 48-bit, oas 48-bit (features 0x00001f8f)
[    0.638285] arm-smmu-v3 36600000.iommu: allocated 524288 entries for cmdq
[    0.649219] arm-smmu-v3 36600000.iommu: allocated 524288 entries for evtq
[    0.657411] arm-smmu-v3 36600000.iommu: msi_domain absent - falling back to wired irqs
[    0.670674] brd: module loaded
[    0.675818] loop: module loaded
[    0.679374] sysfs: cannot create duplicate filename '/devices/platform/dma_buf_phys'
[    0.687305] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.10.100-g7a7a3af903 #1
[    0.694595] Hardware name: Texas Instruments J721E SK (DT)
[    0.700197] Call trace:
[    0.702701]  dump_backtrace+0x0/0x1a0
[    0.706438]  show_stack+0x18/0x68
[    0.709826]  dump_stack+0xd0/0x12c
[    0.713298]  sysfs_warn_dup+0x60/0x80
[    0.717035]  sysfs_create_dir_ns+0xe0/0xf8
[    0.721218]  kobject_add_internal+0x98/0x288
[    0.725576]  kobject_add+0x94/0x100
[    0.729136]  device_add+0xe0/0x740
[    0.732608]  platform_device_add+0x100/0x238
[    0.736966]  platform_device_register_full+0xcc/0x150
[    0.742126]  dma_buf_phys_init+0x6c/0x9c
[    0.746130]  do_one_initcall+0x54/0x1b8
[    0.750047]  kernel_init_freeable+0x220/0x2a0
[    0.754495]  kernel_init+0x14/0x114
[    0.758053]  ret_from_fork+0x10/0x34
[    0.761711] kobject_add_internal failed for dma_buf_phys with -EEXIST, don't try to register things with the same name in the same directory.
[    0.776273] tun: Universal TUN/TAP device driver, 1.6
[    0.782258] VFIO - User Level meta-driver version: 0.3
[    0.787662] i2c /dev entries driver
[    0.791498] Error: Driver 'k3-soc-thermal' is already registered, aborting...
[    0.799080] sdhci: Secure Digital Host Controller Interface driver
[    0.805396] sdhci: Copyright(c) Pierre Ossman
[    0.810011] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.816212] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    0.822934] ashmem: initialized
[    0.826781] optee: probing for conduit method.
[    0.831339] optee: revision 3.12 (3d47a131)
[    0.831579] optee: initialized driver
[    0.840432] NET: Registered protocol family 17
[    0.845068] 9pnet: Installing 9P2000 support
[    0.849461] Key type dns_resolver registered
[    0.853917] registered taskstats version 1
[    0.858105] Loading compiled-in X.509 certificates
[    0.863619] pstore: Invalid compression size for deflate: 0
[    0.872211] k3-ringacc 2b800000.ringacc: Failed to get MSI domain
[    0.878544] k3-ringacc 3c000000.ringacc: Failed to get MSI domain
[    0.886908] ti-sci 44083000.dmsc: ABI: 3.1 (firmware rev 0x0016 '22.1.1--v2022.01 (Terrific Llam')
[    0.916503] random: fast init done
[    0.934159] omap_i2c 40b00000.i2c: bus 0 rev0.12 at 100 kHz
[    0.940273] omap_i2c 40b10000.i2c: bus 1 rev0.12 at 100 kHz
[    0.946383] omap_i2c 42120000.i2c: bus 2 rev0.12 at 100 kHz
[    0.952978] omap_i2c 2030000.i2c: bus 3 rev0.12 at 100 kHz
[    0.959444] ti-sci-intr bus@100000:bus@28380000:interrupt-controller2: Interrupt Router 137 domain created
[    0.969489] ti-sci-intr bus@100000:interrupt-controller0: Interrupt Router 131 domain created
[    0.978338] ti-sci-intr bus@100000:main-navss:interrupt-controller1: Interrupt Router 213 domain created
[    0.988270] ti-sci-inta 33d00000.interrupt-controller: Interrupt Aggregator domain 209 created
[    1.006593] k3-ringacc 2b800000.ringacc: Ring Accelerator probed rings:286, gp-rings[96,20] sci-dev-id:235
[    1.016477] k3-ringacc 2b800000.ringacc: dma-ring-reset-quirk: disabled
[    1.023238] k3-ringacc 2b800000.ringacc: RA Proxy rev. 66346100, num_proxies:64
[    1.032230] k3-ringacc 3c000000.ringacc: Ring Accelerator probed rings:1024, gp-rings[440,150] sci-dev-id:211
[    1.042392] k3-ringacc 3c000000.ringacc: dma-ring-reset-quirk: disabled
[    1.049154] k3-ringacc 3c000000.ringacc: RA Proxy rev. 66346100, num_proxies:64
[    1.058868] remoteproc remoteproc0: b034000.pru is available
[    1.064954] remoteproc remoteproc1: b004000.rtu is available
[    1.070977] remoteproc remoteproc2: b00a000.txpru is available
[    1.077224] remoteproc remoteproc3: b038000.pru is available
[    1.083302] remoteproc remoteproc4: b006000.rtu is available
[    1.089342] remoteproc remoteproc5: b00c000.txpru is available
[    1.097458] remoteproc remoteproc6: b134000.pru is available
[    1.103585] remoteproc remoteproc7: b104000.rtu is available
[    1.109616] remoteproc remoteproc8: b10a000.txpru is available
[    1.115850] remoteproc remoteproc9: b138000.pru is available
[    1.121911] remoteproc remoteproc10: b106000.rtu is available
[    1.128018] remoteproc remoteproc11: b10c000.txpru is available
[    1.134671] 40a00000.serial: ttyS1 at MMIO 0x40a00000 (irq = 15, base_baud = 6000000) is a 8250
[    1.144278] 2800000.serial: ttyS2 at MMIO 0x2800000 (irq = 26, base_baud = 3000000) is a 8250
[    1.153031] printk: console [ttyS2] enabled
[    1.153031] printk: console [ttyS2] enabled
[    1.161477] printk: bootconsole [ns16550a0] disabled
[    1.161477] printk: bootconsole [ns16550a0] disabled
[    1.172025] 2810000.serial: ttyS3 at MMIO 0x2810000 (irq = 27, base_baud = 3000000) is a 8250
[    1.181003] 2840000.serial: ttyS6 at MMIO 0x2840000 (irq = 28, base_baud = 3000000) is a 8250
[    1.230115] davinci_mdio 46000f00.mdio: davinci mdio revision 9.7, bus freq 1000000
[    1.238195] mdio_bus 46000f00.mdio: MDIO device at address 0 is missing.
[    1.244925] am65-cpsw-nuss 46000000.ethernet: initializing am65 cpsw nuss version 0x6BA00101, cpsw version 0x6BA80100 Ports: 2 quirks:00000000
[    1.258991] am65-cpts 310d0000.cpts: CPTS ver 0x4e8a010a, freq:200000000, add_val:4 pps:0
[    1.267456] k3_bandgap_probe:522 : probe enter
[    1.271922] WORKAROUND NOT NEEDED EFUSE0[31:30] = 0b11
[    1.372738] mmc0: CQHCI version 5.10
[    1.387636] vdd_mmc1: supplied by vsys_3v3
[    1.392486] omap-mailbox 31f80000.mailbox: omap mailbox rev 0x66fc7100
[    1.399425] omap-mailbox 31f81000.mailbox: omap mailbox rev 0x66fc7100
[    1.406335] omap-mailbox 31f82000.mailbox: omap mailbox rev 0x66fc7100
[    1.413238] omap-mailbox 31f83000.mailbox: omap mailbox rev 0x66fc7100
[    1.420100] omap-mailbox 31f84000.mailbox: omap mailbox rev 0x66fc7100
[    1.422359] mmc0: SDHCI controller on 4f80000.mmc [4f80000.mmc] using ADMA 64-bit
[    1.436884] ti-udma 285c0000.dma-controller: Channels: 26 (tchan: 13, rchan: 13, gp-rflow: 8)
[    1.447201] ti-udma 31150000.dma-controller: Channels: 84 (tchan: 42, rchan: 42, gp-rflow: 16)
[    1.500734] mmc0: Command Queue Engine enabled
[    1.502115] davinci_mdio 46000f00.mdio: davinci mdio revision 9.7, bus freq 1000000
[    1.505186] mmc0: new DDR MMC card at address 0001
[    1.513240] mdio_bus 46000f00.mdio: MDIO device at address 0 is missing.
[    1.517853] mmcblk0: mmc0:0001 AGUF4R 14.6 GiB 
[    1.524335] am65-cpsw-nuss 46000000.ethernet: initializing am65 cpsw nuss version 0x6BA00101, cpsw version 0x6BA80100 Ports: 2 quirks:00000000
[    1.528905] mmcblk0boot0: mmc0:0001 AGUF4R partition 1 31.9 MiB
[    1.547570] mmcblk0boot1: mmc0:0001 AGUF4R partition 2 31.9 MiB
[    1.553561] mmcblk0rpmb: mmc0:0001 AGUF4R partition 3 4.00 MiB, chardev (237:0)
[    1.561254] am65-cpsw-nuss 46000000.ethernet: set new flow-id-base 48
[    1.563124]  mmcblk0: p1 p2 p3 p4 p5
[    1.571863] am65-cpsw-nuss 46000000.ethernet: initialized cpsw ale version 1.4
[    1.579084] am65-cpsw-nuss 46000000.ethernet: ALE Table size 64
[    1.585551] am65-cpsw-nuss 46000000.ethernet: CPTS ver 0x4e8a010a, freq:500000000, add_val:1 pps:0
[    1.596945] mmc1: CQHCI version 5.10
[    1.601149] Enter canio_probe
[    1.604133] [can1043_request_io] get and request the can1043stb-gpios's number success!!
[    1.612273] [can1043_request_io] get and request the can1043en-gpios's number success!!
[    1.620275] Exit canio_probe
[    1.624482] k3-dsp-rproc 4d80800000.dsp: assigned reserved memory node vision-apps-c66-dma-memory@a9000000
[    1.634291] k3-dsp-rproc 4d80800000.dsp: configured DSP for IPC-only mode
[    1.641108] remoteproc remoteproc12: 4d80800000.dsp is available
[    1.647102] remoteproc remoteproc12: attaching to 4d80800000.dsp
[    1.653191] k3-dsp-rproc 4d80800000.dsp: DSP initialized in IPC-only mode
[    1.659968]  remoteproc12#vdev0buffer: assigned reserved memory node vision-apps-c66-dma-memory@a9000000
[    1.669749] virtio_rpmsg_bus virtio0: rpmsg host is online
[    1.674347] virtio_rpmsg_bus virtio0: creating channel rpmsg_chrdev addr 0xd
[    1.675413]  remoteproc12#vdev0buffer: registered virtio0 (type 7)
[    1.688475] remoteproc remoteproc12: remote processor 4d80800000.dsp is now attached
[    1.697149] k3-dsp-rproc 4d81800000.dsp: assigned reserved memory node vision-apps-c66-dma-memory@a8000000
[    1.706936] k3-dsp-rproc 4d81800000.dsp: configured DSP for IPC-only mode
[    1.713738] remoteproc remoteproc13: 4d81800000.dsp is available
[    1.719732] remoteproc remoteproc13: attaching to 4d81800000.dsp
[    1.725786] k3-dsp-rproc 4d81800000.dsp: DSP initialized in IPC-only mode
[    1.732562]  remoteproc13#vdev0buffer: assigned reserved memory node vision-apps-c66-dma-memory@a8000000
[    1.742306] virtio_rpmsg_bus virtio1: rpmsg host is online
[    1.746610] virtio_rpmsg_bus virtio1: creating channel rpmsg_chrdev addr 0xd
[    1.748051]  remoteproc13#vdev0buffer: registered virtio1 (type 7)
[    1.761019] remoteproc remoteproc13: remote processor 4d81800000.dsp is now attached
[    1.769630] k3-dsp-rproc 64800000.dsp: assigned reserved memory node vision-apps-c71-dma-memory@aa000000
[    1.779323] k3-dsp-rproc 64800000.dsp: configured DSP for IPC-only mode
[    1.785953] remoteproc remoteproc14: 64800000.dsp is available
[    1.791774] remoteproc remoteproc14: attaching to 64800000.dsp
[    1.797631] remoteproc remoteproc14: unsupported resource 65538
[    1.803591] k3-dsp-rproc 64800000.dsp: DSP initialized in IPC-only mode
[    1.810194]  remoteproc14#vdev0buffer: assigned reserved memory node vision-apps-c71-dma-memory@aa000000
[    1.819935] virtio_rpmsg_bus virtio2: rpmsg host is online
[    1.822385] virtio_rpmsg_bus virtio2: creating channel rpmsg_chrdev addr 0xd
[    1.825698]  remoteproc14#vdev0buffer: registered virtio2 (type 7)
[    1.838636] remoteproc remoteproc14: remote processor 64800000.dsp is now attached
[    1.847494] platform 41000000.r5f: R5F core may have been powered on by a different host, programmed state (0) != actual state (1)
[    1.859452] platform 41000000.r5f: configured R5F for IPC-only mode
[    1.865792] platform 41000000.r5f: assigned reserved memory node vision-apps-r5f-dma-memory@a0000000
[    1.874964] remoteproc remoteproc15: 41000000.r5f is available
[    1.880785] remoteproc remoteproc15: attaching to 41000000.r5f
[    1.886683] platform 41000000.r5f: R5F core initialized in IPC-only mode
[    1.893372]  remoteproc15#vdev0buffer: assigned reserved memory node vision-apps-r5f-dma-memory@a0000000
[    1.903111] virtio_rpmsg_bus virtio3: rpmsg host is online
[    1.908824]  remoteproc15#vdev0buffer: registered virtio3 (type 7)
[    1.915035] remoteproc remoteproc15: remote processor 41000000.r5f is now attached
[    1.924246] platform 5c00000.r5f: configured R5F for IPC-only mode
[    1.930502] platform 5c00000.r5f: assigned reserved memory node vision-apps-r5f-dma-memory@a2000000
[    1.939565] virtio_rpmsg_bus virtio3: creating channel rpmsg_chrdev addr 0xd
[    1.942272] remoteproc remoteproc16: 5c00000.r5f is available
[    1.952351] remoteproc remoteproc16: attaching to 5c00000.r5f
[    1.958181] platform 5c00000.r5f: R5F core initialized in IPC-only mode
[    1.964785]  remoteproc16#vdev0buffer: assigned reserved memory node vision-apps-r5f-dma-memory@a2000000
[    1.974503] virtio_rpmsg_bus virtio4: rpmsg host is online
[    1.980211]  remoteproc16#vdev0buffer: registered virtio4 (type 7)
[    1.986410] remoteproc remoteproc16: remote processor 5c00000.r5f is now attached
[    1.994279] platform 5d00000.r5f: configured R5F for IPC-only mode
[    1.997753] virtio_rpmsg_bus virtio4: creating channel rpmsg_chrdev addr 0xd
[    2.000525] platform 5d00000.r5f: assigned reserved memory node vision-apps-r5f-dma-memory@a4000000
[    2.016617] remoteproc remoteproc17: 5d00000.r5f is available
[    2.022357] remoteproc remoteproc17: attaching to 5d00000.r5f
[    2.028146] platform 5d00000.r5f: R5F core initialized in IPC-only mode
[    2.034751]  remoteproc17#vdev0buffer: assigned reserved memory node vision-apps-r5f-dma-memory@a4000000
[    2.044491] virtio_rpmsg_bus virtio5: rpmsg host is online
[    2.050207]  remoteproc17#vdev0buffer: registered virtio5 (type 7)
[    2.056405] remoteproc remoteproc17: remote processor 5d00000.r5f is now attached
[    2.065403] platform 5e00000.r5f: configured R5F for IPC-only mode
[    2.067602] virtio_rpmsg_bus virtio5: creating channel rpmsg_chrdev addr 0xd
[    2.071644] platform 5e00000.r5f: assigned reserved memory node vision-apps-r5f-dma-memory@a6000000
[    2.087720] remoteproc remoteproc18: 5e00000.r5f is available
[    2.093456] remoteproc remoteproc18: attaching to 5e00000.r5f
[    2.099265] platform 5e00000.r5f: R5F core initialized in IPC-only mode
[    2.105869]  remoteproc18#vdev0buffer: assigned reserved memory node vision-apps-r5f-dma-memory@a6000000
[    2.115592] virtio_rpmsg_bus virtio6: rpmsg host is online
[    2.121295]  remoteproc18#vdev0buffer: registered virtio6 (type 7)
[    2.127500] remoteproc remoteproc18: remote processor 5e00000.r5f is now attached
[    2.135338] platform 5f00000.r5f: configured R5F for IPC-only mode
[    2.138810] virtio_rpmsg_bus virtio6: creating channel rpmsg_chrdev addr 0xd
[    2.141567] platform 5f00000.r5f: assigned reserved memory node vision-apps-r5f-dma-memory@a7000000
[    2.157645] remoteproc remoteproc19: 5f00000.r5f is available
[    2.163385] remoteproc remoteproc19: attaching to 5f00000.r5f
[    2.169171] platform 5f00000.r5f: R5F core initialized in IPC-only mode
[    2.175773]  remoteproc19#vdev0buffer: assigned reserved memory node vision-apps-r5f-dma-memory@a7000000
[    2.185480] virtio_rpmsg_bus virtio7: rpmsg host is online
[    2.191222]  remoteproc19#vdev0buffer: registered virtio7 (type 7)
[    2.197482] remoteproc remoteproc19: remote processor 5f00000.r5f is now attached
[    2.208457] virtio_rpmsg_bus virtio7: creating channel rpmsg_chrdev addr 0xd
[    2.690125] virtio_rpmsg_bus virtio0: creating channel rpmsg_chrdev addr 0x15
[    2.786123] virtio_rpmsg_bus virtio1: creating channel rpmsg_chrdev addr 0x15
[    2.850129] virtio_rpmsg_bus virtio2: creating channel rpmsg_chrdev addr 0x15
[    2.978126] virtio_rpmsg_bus virtio3: creating channel rpmsg_chrdev addr 0x15
[    3.042120] virtio_rpmsg_bus virtio4: creating channel rpmsg_chrdev addr 0x15
[    3.106122] virtio_rpmsg_bus virtio5: creating channel rpmsg_chrdev addr 0x15
[    3.112216] sdhci-am654 4fb0000.mmc: Power on failed
[    3.148841] mmc1: SDHCI controller on 4fb0000.mmc [4fb0000.mmc] using ADMA 64-bit
[    3.170144] virtio_rpmsg_bus virtio6: creating channel rpmsg_chrdev addr 0x15
[    3.206459] EXT4-fs (mmcblk0p1): 1 orphan inode deleted
[    3.211688] EXT4-fs (mmcblk0p1): recovery complete
[    3.222638] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
[    3.230754] VFS: Mounted root (ext4 filesystem) on device 179:1.
[    3.237074] devtmpfs: mounted
[    3.238124] virtio_rpmsg_bus virtio7: creating channel rpmsg_chrdev addr 0x15
[    3.240296] Freeing unused kernel memory: 1600K
[    3.262131] Run /sbin/init as init process
[    3.352374] systemd[1]: System time before build time, advancing clock.
[    3.384936] NET: Registered protocol family 10
[    3.389808] Segment Routing with IPv6
[    3.402852] systemd[1]: systemd 244 running in system mode. (+PAM -AUDIT -SELINUX +IMA -APPARMOR -SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN2 -IDN -PCRE2 default-hierarchy=hybrid)
[    3.424406] systemd[1]: Detected architecture arm64.

Welcome to Arago 2021.09!

[    3.470361] systemd[1]: Set hostname to <j7-evm>.
[    3.575750] systemd[1]: multi-user.target: Wants dependency dropin /etc/systemd/system/multi-user.target.wants/systemd-bmculog.service.1 is not a valid unit name, ignoring.
[    3.591270] systemd[1]: multi-user.target: Wants dependency dropin /etc/systemd/system/multi-user.target.wants/systemd-kernellog.service.1 is not a valid unit name, ignoring.
[    3.616196] systemd[1]: Configuration file /etc/systemd/system/systemd-camera.service is marked executable. Please remove executable permission bits. Proceeding anyway.
[    3.670021] random: systemd: uninitialized urandom read (16 bytes read)
[    3.676739] systemd[1]: system-getty.slice: unit configures an IP firewall, but the local system does not support BPF/cgroup firewalling.
[    3.689067] systemd[1]: (This warning is only shown for the first unit using IP firewalling.)
[    3.698708] systemd[1]: Created slice system-getty.slice.
[  OK  ] Created slice system-getty.slice.
[    3.714132] virtio_rpmsg_bus virtio0: creating channel ti.ipc4.ping-pong addr 0xe
[    3.721675] random: systemd: uninitialized urandom read (16 bytes read)
[    3.728728] systemd[1]: Created slice system-serial\x2dgetty.slice.
[  OK  ] Created slice system-serial\x2dgetty.slice.
[    3.750169] random: systemd: uninitialized urandom read (16 bytes read)
[    3.757117] systemd[1]: Created slice User and Session Slice.
[  OK  ] Created slice User and Session Slice.
[    3.778273] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Started Dispatch Password …ts to Console Directory Watch.
[    3.802215] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Started Forward Password R…uests [    3.814125] virtio_rpmsg_bus virtio1: creating channel ti.ipc4.ping-pong addr 0xe
to Wall Directory Watch.
[    3.834238] systemd[1]: Reached target Remote File Systems.
[  OK  ] Reached target Remote File Systems.
[    3.854167] systemd[1]: Reached target Swap.
[  OK  ] Reached target Swap.
[    3.870753] systemd[1]: Listening on RPCbind Server Activation Socket.
[    3.874144] virtio_rpmsg_bus virtio2: creating channel ti.ipc4.ping-pong addr 0xe
[  OK  ] Listening on RPCbind Server Activation Socket.
[    3.902189] systemd[1]: Reached target RPC Port Mapper.
[  OK  ] Reached target RPC Port Mapper.
[    3.926756] systemd[1]: Condition check resulted in Journal Audit Socket being skipped.
[    3.935061] systemd[1]: Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Journal Socket (/dev/log).
[    3.958367] systemd[1]: Listening on Journal Socket.
[  OK  ] Listening on Journal Socket.
[    3.974342] systemd[1]: Listening on udev Control Socket.
[  OK  ] Listening on udev Control Socket.
[    3.994259] systemd[1]: Listening on udev Kernel Socket.
[  OK  ] Listening on udev Kernel Socket.
[    4.006127] virtio_rpmsg_bus virtio3: creating channel rpmsg_chrdev addr 0x27
[    4.016513] systemd[1]: Mounting Huge Pages File System...
         Mounting Huge Pages File System...
[    4.036785] systemd[1]: Mounting POSIX Message Queue File System...
         Mounting POSIX Message Queue File System...
[    4.058352] systemd[1]: Condition check resulted in Kernel Debug File System being skipped.
[    4.069342] systemd[1]: Mounting Temporary Directory (/tmp)...
[    4.070165] virtio_rpmsg_bus virtio4: creating channel ti.ipc4.ping-pong addr 0xe
         Mounting Temporary Directory (/tmp)...
[    4.096685] systemd[1]: Starting set ip bridge...
         Starting set ip bridge...
[    4.116346] systemd[1]: Starting roudi service...
         Starting roudi service...
[    4.130189] virtio_rpmsg_bus virtio5: creating channel ti.ipc4.ping-pong addr 0xe
[    4.140920] systemd[1]: Starting Create list of static device nodes for the current kernel...
         Starting Create list of st…odes for the current kernel...
[    4.168592] systemd[1]: Starting RPC Bind...
         Starting RPC Bind...
[    4.180975] systemd[1]: Starting service manager...
         Starting service manager...
[    4.194147] virtio_rpmsg_bus virtio6: creating channel rpmsg_chrdev addr 0x14
[    4.204943] systemd[1]: Starting logd...
         Starting logd...
[    4.214472] systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
[    4.227130] systemd[1]: Starting Journal Service...
         Starting Journal Service...
[    4.258217] virtio_rpmsg_bus virtio7: creating channel ti.ipc4.ping-pong addr 0xe
[    4.272561] systemd[1]: Starting Load Kernel Modules...
         Starting Load Kernel Modules...[    4.284478] cryptodev: loading out-of-tree module taints kernel.

[    4.305522] systemd[1]: Starting mount_auto...
         Starting mount_auto...[    4.310642] logd.auditd: start
[    4.314263] cryptodev: driver 1.10 loaded.

[    4.327387] max2008x_cam_probe started!
[    4.331550] max2008x_cam 3-0029: probe end
[    4.338399] systemd[1]: Starting Remount Root and Kernel File Systems...
         Starting Remount Root and Kernel File Systems max2008x_radar_probe started!
[0m...
[    4.356116] max2008x_radar 3-0028: probe end
[    4.369692] systemd[1]: Starting udev Coldplug all Devices...
         Starting udev Coldplug all Devices...[    4.377032] EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)
[    4.378995] tps4h000bq_probe: CAM_SW_ID is low, power protect ic is max20086

[    4.389726] EXT4-fs (mmcblk0p3): recovery complete
[    4.399461] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
[    4.400866] systemd[1]: Started RPC Bind.
[  OK  ] Started RPC Bind.
[    4.423473] systemd[1]: Condition check resulted in /cache being skipped.
[    4.430680] systemd[1]: Unnecessary job for /dev/mmcblk0p3 was removed.
[    4.438017] systemd[1]: Started Journal Service.
[  OK  ] Started Journal Service.[    4.447581] EXT4-fs (mmcblk0p4): recovery complete

[    4.452901] EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: (null)
[  OK  ] Mounted Huge Pages File System.
[  OK  ] Mounted POSIX Message Queue File System.
[    4.489915] EXT4-fs (mmcblk0p5): recovery complete
[    4.495331] EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: (null)
[  OK  ] Mounted Temporary Directory (/tmp).
[  OK  ] Started set ip bridge.
[  OK  ] Started roudi service.
[  OK  ] Started Create list of sta… nodes for the current kernel.
[  OK  ] Started service manager.
[  OK  ] Started logd.
[  OK  ] Started Load Kernel Modules.
[  OK  ] Started mount_auto.
[  OK  ] Started Remount Root and Kernel File Systems.
         Mounting Kernel Configuration File System...
         Starting logcat...
         Starting auto service...
         Starting Flush Journal to Persistent Storage...
[    4.702522] systemd-journald[214]: Received client request to flush runtime journal.
         Starting Apply Kernel Variables...
         Starting udev Kernel Device Manager...
         Starting Load/Save Random Seed...
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Started logcat.
[  OK  ] Started auto service.
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Started Flush Journal to Persistent Storage.
[  OK  ] Started Apply Kernel Variables.
         Starting dtc...
         Starting Network Service...
[  OK  ] Started dtc.
         Starting cameraservice...
[  OK  ] Started cameraservice.
[  OK  ] Reached target Local File Systems (Pre).
[  OK  ] Reached target Local File Systems.
         Starting Create Volatile Files and Directories...
[  OK  ] Started Network Service.
[  OK  ] Reached target Network.
[  OK  ] Started Create Volatile Files and D[    5.026175] virtio_rpmsg_bus virtio3: creating channel ti.ipc4.ping-pong addr 0xe
irectories.
[  OK  ] Reached target System Initialization.
[  OK  ] Reached target Basic System.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Started D-Bus System Message Bus.
         Starting rc.pvr.service...
         Starting service manager...
         Starting factory aging test...
         Starting Login Service...
         Starting ota service...
         Starting system time...[    5.218168] virtio_rpmsg_bus virtio6: creating channel ti.ipc4.ping-pong addr 0xe

         Starting Create Static Device Nodes in /dev...
         Starting Update UTMP about System Boot/Shutdown...
         Starting Permit User Sessions...
[  OK  ] Started service manager.
[FAILED] Failed to start factory aging test.
[    5.341622] PVR_K:  339: Read BVNC 22.104.208.318 from HW device registers
See 'systemctl status systemd-factory.service' for details.[    5.355386] PVR_K:  339: RGX Device registered with BVNC 22.104.208.318

[  OK  ] Started ota service.
[    5.374624] [drm] Initialized pvr 1.13.5776728 20170530 for 4e20000000.gpu on minor 0
[  OK  ] Started system time.
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Started Permit User Sessions.
[    5.422275] img_enc 4200000.video-encoder: vxe_enc_probe: using heap 1 for internal alloc
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Started Getty on tty1.
[    5.496835] img_dec 4300000.video-decoder: decoder registered as /dev/video0
[  OK  ] Started Serial Getty on ttyS2.
[  OK  ] Started Serial Getty on ttyS3.
[  OK  ] Reached target Login Prompts.
         Starting crash log...
[    5.558232] img_enc 4200000.video-encoder: encoder registered as /dev/video1
[  OK  ] Started Login Service.
[  OK  ] Started crash log.
[  OK  ] Created slice system-systemd\x2dfsck.slice.
[    7.214147] random: crng init done
[    7.217562] random: 7 urandom warning(s) missed due to ratelimiting
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Found device /dev/mmcblk0p2.
         Starting File System Check on /dev/mmcblk0p2...
[    7.729635] omap_rng 4e10000.rng: Random Number Generator ver. 241b34c
[  OK  ] Started rc.pvr.service.
         Starting sshd.service...
[  OK  ] Started File System Check on /dev/mmcblk0p2.
         Mounting /run/media/mmcblk0p2...
         Starting udev Wait for Complete Device Initial[    7.829880] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
ization...
[  OK  ] Mounted /run/media/mmcblk0p2.
[  OK  ] Started sshd.service.
         Starting SYSV: BydProcessManager service script...
[  OK  ] Started SYSV: BydProcessManager service script.
         Starting otg_upgrade.service...
[  OK  ] Started otg_upgrade.service.
         Starting adbd.service...
[  OK  ] Reached target Hardware activated U[    9.153849] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
SB gadget.
[    9.161082] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 1
[    9.170970] xhci-hcd xhci-hcd.2.auto: hcc params 0x200073c9 hci version 0x100 quirks 0x0000002000010010
[    9.180439] xhci-hcd xhci-hcd.2.auto: irq 615, io mem 0x06410000
[    9.186518] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[    9.194786] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    9.202001] usb usb1: Product: xHCI Host Controller
[    9.206875] usb usb1: Manufacturer: Linux 5.10.100-g7a7a3af903 xhci-hcd
[    9.213486] usb usb1: SerialNumber: xhci-hcd.2.auto
[    9.218618] hub 1-0:1.0: USB hub found
[    9.222406] hub 1-0:1.0: 1 port detected
[    9.226904] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
[    9.232805] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 2
[    9.240532] xhci-hcd xhci-hcd.2.auto: Host supports USB 3.0 SuperSpeed
[    9.247149] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    9.255298] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.10
[    9.263599] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    9.271036] usb usb2: Product: xHCI Host Controller
[    9.275886] Need at least one configuration in g1.
[    9.275992] usb usb2: Manufacturer: Linux 5.10.100-g7a7a3af903 xhci-hcd
[    9.280995] configfs-gadget 6000000.usb: failed to start g1: -22
[    9.287297] usb usb2: SerialNumber: xhci-hcd.2.auto
[    9.298434] hub 2-0:1.0: USB hub found
[    9.302212] hub 2-0:1.0: 1 port detected
[  OK  ] Started udev Wait for Complete Device Initialization.
[  OK  ] Started Hardware RNG Entropy Gatherer Daemon.
[   10.007655] file system registered
[   11.040453] read descriptors
[   11.043404] read strings

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

Arago Project http://arago-project.org j7-evm ttyS2

Arago 2021.09 j7-evm ttyS2

0 Tarun Mukesh Puvvada over 2 years ago in reply to lify

TI__Guru 50156 points

Hello,

Is it this way after receiving CAN messages the CAN ISR gets triggered and the data is transferred. Now IPC comes into picture and start sending data to A72 again via interrupt mechanism ?

Are any other features running on mcu1_0 other that CAN and IPC ?

Is IPC being implemented inside the CAN ISR?

After receiving CAN messages those are directly getting transferred to IPC buffers ?

Regards

Tarun Mukesh

0 lify over 2 years ago in reply to Tarun Mukesh Puvvada

Intellectual 290 points

hi Tarun Mukesh

1.Is it this way after receiving CAN messages the CAN ISR gets triggered and the data is transferred. Now IPC comes into picture and start sending data to A72 again via interrupt mechanism ?

------------------>can data-->can_driver(mcu1_0)---ipc---->A72. The can driver has been receiving can data and sending it to A72, regardless of whether it enters the auto parking or no. The logic of CAN driver sending and receiving data is not related to whether enter into auto parking function. mcu1_ 0 always receives data, processes it, and then sends it to A72 via ipc.

2.Are any other features running on mcu1_0 other that CAN and IPC ?

----------> there is no other feathres in mcu1-0 rather than can and ipc

3.Is IPC being implemented inside the CAN ISR?

------------------>no, ipc is not in interrupt function, is in another task to deal with the ipc data sending.

4.After receiving CAN messages those are directly getting transferred to IPC buffers ?

---------->no, after receiving can messages, will do some processing on can data, but it is not processed in the interrupt, but specifically handles the task of receiving data. then transferred to ipc buffers .

Our problem now becomes that we receive fewer interrupts than the data on the bus。

0 Tarun Mukesh Puvvada over 2 years ago in reply to lify

TI__Guru 50156 points

Hello,

lify said:
1. Map file of MCU1_0 application and Linux/HLOS boot logs.

----------------->the map file do you mean the file linker_mem_map? we didn't change the file.

No not linker map file. I am asking for final built mem map file "xer5f.map".

Regards

Tarun Mukesh

0 lify over 2 years ago in reply to Tarun Mukesh Puvvada

Intellectual 290 points

hi Tarun Mukesh

No not linker map file. I am asking for final built mem map file "xer5f.map".

----------> can you list the full name of the xer5f.map file or the path of the file ? thanks. (We are boot with SPL)

0 Tarun Mukesh Puvvada over 2 years ago in reply to lify

TI__Guru 50156 points

Hello,

After compilation you will have the executable in PDK_INSTALL_DIR/packages/ti/binary/<example> , in the same folder you will have mem map file.

Regards

Tarun Mukesh

0 lify over 2 years ago in reply to Tarun Mukesh Puvvada

Intellectual 290 points

hi Tarun Mukesh

From the path i didn't found the file

0 Tarun Mukesh Puvvada over 2 years ago in reply to lify

TI__Guru 50156 points

Hello,

For example we have it in

ti-processor-sdk-rtos-j721e-evm-08_05_00_11/pdk_jacinto_08_05_00_36/packages/ti/binary/csl_mcan_evm_loopback_app/bin/j721e_evm/csl_mcan_evm_loopback_app_mcu1_0_release.xer5f.map

The same executable file loaction from where you are flashing the SW and testing

Regards

Tarun Mukesh

0 lify over 2 years ago in reply to Tarun Mukesh Puvvada

Intellectual 290 points

Our can module file path is as follows:rtos-sdk\vision_apps\platform\j721e\rtos\mcu1_0\can. And this module has been compiled into Execution file of mcu1_0 . And where can i get the file? thanks.

0 Tarun Mukesh Puvvada over 2 years ago in reply to lify

TI__Guru 50156 points

Hello,

The issue you are facing ,can be of multiple reasons.

If A72 is busy in performing automatic parking functionality or any other and not receiving IPC messages, in that case mcu1_0 is blocked trying to send the CAN data via IPC to A72.

Can you share the performance statistics of open vx parking application ? I would like to analyze any higher bandwidth A72 uses.

Can you share in detail can data-->can_driver(mcu1_0)---ipc---->A72 ? Where exactly the received CAN messages are processing and ipc sending those message ? and what is present in CAN Interrupt ISR

because whatever might be reason CAN interrupt has to come after receiving message

Regards

Tarun Mukesh

0 lify over 2 years ago in reply to Tarun Mukesh Puvvada

Intellectual 290 points

hi Tarun Mukesh

Can you share in detail can data-->can_driver(mcu1_0)---ipc---->A72 ? Where exactly the received CAN messages are processing and ipc sending those message ? and what is present in CAN Interrupt ISR

---------->can_isr(mcan_ir bit[4]=1)-->SemaphoreP_post(receive)---> recevie_task(process can data)---->ipc_send_task--->A72

The recevie_task is pending for the SemaphoreP(receive), i just read the mcan_ir status in can isr function , if mcan_ir bit[4]=1,SemaphoreP_post(receive), recevie_task begin to read can data in the ram and processe it.

we receive fewer interrupt ISR than the data on the bus. What could be the reason？

0 Tarun Mukesh Puvvada over 2 years ago in reply to lify

TI__Guru 50156 points

Hello,

The reasons usually could be

Interrupt priority :It's possible that another higher-priority interrupt is currently being serviced, preventing the CAN interrupt from being processed.

Interrupt latency :If the interrupt service routine (ISR) for CAN messages takes longer to execute than the time between incoming messages, it's possible that the interrupts are being missed or delayed.

But as you suggest you are reading only status and no doing anything inside ISR. Interrupt latency can be ignored.

There can be another scenarios

where A node receives a CAN message, it checks the message's identifier (ID) against its configured filters to determine if the message is relevant to that node. If the ID matches one of the filters, the node processes the message, and it triggers an interrupt to notify.

However, if the received message does not match any of the filters or if the node is not configured to receive that particular message, no interrupt will be generated. The node will simply ignore the message and continue to monitor the bus for new messages.

and lastly Hardware issues.

The above are possible scenarios for interrupt not getting triggered.

Regards

Tarun Mukesh

0 Tarun Mukesh Puvvada over 2 years ago in reply to Tarun Mukesh Puvvada

TI__Guru 50156 points

One way to debug is to remove the IPC mechanism and check all the CAN interrupts are being received or not.

0 lify over 2 years ago in reply to Tarun Mukesh Puvvada

Intellectual 290 points

hi Tarun Mukesh

I have remove ipc mechanism, the CAN interrupts are not being received all also. Any other debug method?

0 Tarun Mukesh Puvvada over 2 years ago in reply to lify

TI__Guru 50156 points

Hello ,

Can you share me the details of previous posted questions

lify said:
Our can module file path is as follows:rtos-sdk\vision_apps\platform\j721e\rtos\mcu1_0\can. And this module has been compiled into Execution file of mcu1_0 . And where can i get the file

Can you search in the binary folder of vision apps with executable file name ".out.map" ?

Tarun Mukesh Puvvada said:
Can you share the performance statistics of open vx parking application ? I would like to analyze any higher bandwidth A72 uses.

and may I know the CPU load on MCU1_0 ?

along with the above details ,Can you share external (another) CAN node settings and details ?

If automatic parking function is turned ON then CAN interrupts are getting blocked and if not in automatic parking then all the CAN interrupts are being received ?

Am i right?

Regards

Tarun Mukesh

0 lify over 2 years ago in reply to Tarun Mukesh Puvvada

Intellectual 290 points

hi Tarun Mukesh

out.map vx_app_rtos_linux_mcu1_0.out.map.zip

0 lify over 2 years ago in reply to Tarun Mukesh Puvvada

Intellectual 290 points

hi Tarun Mukesh

1.may I know the CPU load on MCU1_0 ?

--------->CPU load on MCU1_0 is less than 30%。

2. If automatic parking function is turned ON then CAN interrupts are getting blocked and if not in automatic parking then all the CAN interrupts are being received ?

---------->no, Latest test， even not in automatic parking then not all the CAN interrupts are being received.

3.along with the above details ,Can you share external (another) CAN node settings and details ?

--------->I'm sorry, I can't know the settings of other can nodes on the car

0 Tarun Mukesh Puvvada over 2 years ago in reply to lify

TI__Guru 50156 points

Hello,

lify said:
no, Latest test， even not in automatic parking then not all the CAN interrupts are being received.

What has been changed from earlier test to now latest one? why earlier all the interrupt are being received and not now?

Are all the messages on the bus intended to be received by TDA4VM ? and all configuration settings met accordingly.

Can you share me the register Dump of CAN_IE register ? and raw interrupt status ?

Irrespective of Automatic parking function or not , CAN interrupts are missing and Rx FIFO1 is getting full. Is my understanding correct ?

Regards

Tarun Mukesh

Processors

Processors forum

TDA4VM: After activating the automatic parking function, the probability of mcan_ir=0x50 is very high