SK-TDA4VM: Overheating problem

Elchin Aslanli

Part Number: SK-TDA4VM
Other Parts Discussed in Thread: TDA4VM

Tool/software:

Hi,

Today I started to get into SK-TDA4VM development board for edge AI.

Flashed this wic file into microSD card : https://www.ti.com/tool/download/PROCESSOR-SDK-LINUX-SK-TDA4VM

When I start the board, it starts without problem, but the thing is even without doing anything it reaches up to 55 degree Celcius.

When I start the custom AI tab for the images, giving a photo to identify it (default photos, like flamingo or elephant), it reaches up to 75 degree Celcius.

The thing is also it cannot identify any image(I tried for 10+ minutes), so that I have to turn off the board.

Is it a normal behaviour? If no what can be the problem of the board?

As you can see from below given photos, all board is on fire.

P.S. I am using 20V 5A type c adapter to supply power to the board.

Thanks for your help in advance,

8 months ago

0 Takuma Fujiwara 8 months ago

TI__Guru 57023 points

Hi Elchin,

Elchin Aslanli said:
When I start the board, it starts without problem, but the thing is even without doing anything it reaches up to 55 degree Celcius.

Yes, this is expected. The board runs quite hot. I have seen it sit around 80~90C when running the demos. Operating temperature of TDA4VM itself is -40 to 105C, so it should be able to handle the heat. However, you may put a fan on the heatsink, or direct airflow from a desk fan if desired.

Elchin Aslanli said:
The thing is also it cannot identify any image(I tried for 10+ minutes), so that I have to turn off the board.

This is not expected. Does any of the demos using pre-recorded video input work? Demo pipeline-wise, the video input should be identical to the live camera input with the only change at the input portion of the pipeline.

Regards,

Takuma

0 Elchin Aslanli 8 months ago in reply to Takuma Fujiwara

Prodigy 10 points

Takuma Fujiwara said:
Yes, this is expected. The board runs quite hot. I have seen it sit around 80~90C when running the demos. Operating temperature of TDA4VM itself is -40 to 105C, so it should be able to handle the heat. However, you may put a fan on the heatsink, or direct airflow from a desk fan if desired.

Hi Takuma, to test this I run a multichannel test to test the maximum temperature that board can reach to. The problem is it is resetting itself after 92-93 degree celcius? Is it expected also? I guess that it should bear until 105 degrees(on paper).

Takuma Fujiwara said:
This is not expected. Does any of the demos using pre-recorded video input work? Demo pipeline-wise, the video input should be identical to the live camera input with the only change at the input portion of the pipeline.

Seems like the problem was only about flamingo and elephant :D the other inputs are working fine, haven't tried camera input though.

Thanks for the help in advance,
Regards

0 Takuma Fujiwara 8 months ago in reply to Elchin Aslanli

TI__Guru 57023 points

Hi Elchin,

Elchin Aslanli said:
Hi Takuma, to test this I run a multichannel test to test the maximum temperature that board can reach to. The problem is it is resetting itself after 92-93 degree celcius? Is it expected also? I guess that it should bear until 105 degrees(on paper).

No, it should not be resetting at 92-93 degree celsius. This is unexpected. There were some issues we had fixed in the past where the SoC was resetting itself at around 90C due to some instability with some of the power rails caused by high temperature and the PMIC settings. However, latest SDK should have fixes.

I assumed the latest SDK was used, but could you confirm which SDK version is in-use?

Elchin Aslanli said:
Seems like the problem was only about flamingo and elephant :D the other inputs are working fine, haven't tried camera input though.

Probably the performance of some of the demo model was mediocre and/or the threshold for detection was set too high in the application. Should be fine

Regards,

Takuma

0 Elchin Aslanli 8 months ago in reply to Takuma Fujiwara

Prodigy 10 points

Hi again Takuma,

I am using this image:

https://dr-download.ti.com/software-development/software-development-kit-sdk/MD-4K6R4tqhZI/11.00.00.08/tisdk-edgeai-image-j721e-evm.wic.xz

Since I dont have any access to terminal in this image, the only info I can provide you about the SDK version, is the written version number on demo image main screen: 11.0

Is it enough?

Regards,

0 Takuma Fujiwara 8 months ago in reply to Elchin Aslanli

TI__Guru 57023 points

Hi Elchin,

Yes, that is exactly the info I was looking for. 11.0 is the latest, so it should have the fixes for PMIC integrated.

I will attach a bash script that can be ran on the board which does some register settings on the PMIC. Could you try running this script before running the demo?

sk_pmic_reboot_fix.sh.zip

Regards,

Takuma

0 Elchin Aslanli 8 months ago in reply to Takuma Fujiwara

Prodigy 10 points

Hi Takuma,

I applied your bash script, here is the output of it:

root@tda4vm-sk:/opt/edgeai-gst-apps# ./sk_pmic_reboot_fix.sh 
Error: Write failed
Error: Write failed
Error: Write failed
Error: Write failed
Error: Write failed
Error: Write failed
Error: Read failed
PMIC A register value failed to change
Error: Read failed
PMIC A register value failed to change
Error: Read failed
PMIC A register value failed to change
Error: Read failed
PMIC B register value failed to change
Error: Read failed
PMIC B register value failed to change
Error: Read failed
PMIC B register value failed to change
PMIC registers successfully updated!
root@tda4vm-sk:/opt/edgeai-gst-apps# ./sk_pmic_reboot_fix.sh 
Error: Write failed
Error: Write failed
Error: Write failed
Error: Write failed
Error: Write failed
Error: Write failed
Error: Read failed
PMIC A register value failed to change
Error: Read failed
PMIC A register value failed to change
Error: Read failed
PMIC A register value failed to change
Error: Read failed
PMIC B register value failed to change
Error: Read failed
PMIC B register value failed to change
Error: Read failed
PMIC B register value failed to change
PMIC registers successfully updated!
root@tda4vm-sk:/opt/edgeai-gst-apps#

As you can see all of the commands are failing, I tried it several times, with sudo, without sudo and etc.

Despite of this, I tried to run multichannel test again, and it rebooted after 87 degree, so the problem still persists.

Best regards,

0 Takuma Fujiwara 8 months ago in reply to Elchin Aslanli

TI__Guru 57023 points

Hi Elchin,

Could you share the revision number of the board? There should be a sticker on the bottom and/or top of the board that says "PROC112A1" or something slightly different. The "PROC112" will not change, but the "A1" might change.

It could be that the board is a different revision number and something has changed in terms of PMIC.

Regards,

Takuma

0 Elchin Aslanli 8 months ago in reply to Takuma Fujiwara

Prodigy 10 points

Hi Takuma,

The board revision number is PROC112B (001).

Regards,
Elchin

0 Takuma Fujiwara 8 months ago in reply to Elchin Aslanli

TI__Guru 57023 points

Hi Elchin,

Looks to be a newer revision board. Although, looking through our schematics file, it should be the same between revision A, A1, and B in terms of how the PMIC is integrated, so the commands should work.

To troubleshoot, can you run "i2cdetect -y -r 0x2"? This should print out that there is a device on address 0x48~0x4F for the two PMICs that each have 4 I2C addresses.

Regards,

Takuma

0 Elchin Aslanli 8 months ago in reply to Takuma Fujiwara

Prodigy 10 points

Hi Takuma,

root@tda4vm-sk:/opt/edgeai-gst-apps# i2cdetect -y -r 0x2
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- 21 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- UU -- -- -- -- -- --                         
root@tda4vm-sk:/opt/edgeai-gst-apps#

This is the output of that command.

Regards,
Elchin

0 Takuma Fujiwara 8 months ago in reply to Elchin Aslanli

TI__Guru 57023 points

Hi Elchin,

That is strange. It looks like the PMIC is on a different I2C bus than before.

Can you do an i2cdetect on all the busses to see if there is any bus that has the 8 different I2C addresses populated? In parallel, I will try to find a revision B board in office.

Regards,

Takuma

0 Elchin Aslanli 8 months ago in reply to Elchin Aslanli

Prodigy 10 points

root@tda4vm-sk:~# i2cdetect -y -r 0x2
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- 21 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- UU -- -- -- -- -- --                         
root@tda4vm-sk:~# i2cdetect -y -r 0x1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- 21 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- UU -- -- -- -- -- --                         
root@tda4vm-sk:~# i2cdetect -y -r 0x3
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- 21 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- UU -- -- -- -- -- --                         
root@tda4vm-sk:~# i2cdetect -y -r

Fullscreen 1234.bootlog.txt Download

[Wed Mar  5 18:17:16 2025] Booting Linux on physical CPU 0x0000000000 [0x411fd080]
[Wed Mar  5 18:17:16 2025] Linux version 6.12.17-ti-00773-gcdcaeac783e3-dirty (oe-user@oe-host) (aarch64-oe-linux-gcc (GCC) 13.3.0, GNU ld (GNU Binutils) 2.42.0.20240723) #1 SMP PREEMPT Thu Apr  3 17:42:36 UTC 2025
[Wed Mar  5 18:17:16 2025] KASLR disabled due to lack of seed
[Wed Mar  5 18:17:16 2025] Machine model: Texas Instruments J721E SK
[Wed Mar  5 18:17:16 2025] earlycon: ns16550a0 at MMIO32 0x0000000002800000 (options '')
[Wed Mar  5 18:17:16 2025] printk: legacy bootconsole [ns16550a0] enabled
[Wed Mar  5 18:17:16 2025] efi: UEFI not found.
[Wed Mar  5 18:17:16 2025] Reserved memory: created CMA memory pool at 0x00000008e0000000, size 512 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000008e0000000..0x00000008ffffffff (524288 KiB) map reusable linux,cma
[Wed Mar  5 18:17:16 2025] Reserved memory: created DMA memory pool at 0x0000000880000000, size 624 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision-apps-core-heap-memory-hi@880000000, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x0000000880000000..0x00000008a6ffffff (638976 KiB) nomap non-reusable vision-apps-core-heap-memory-hi@880000000
[Wed Mar  5 18:17:16 2025] Reserved memory: created DMA memory pool at 0x00000000e4800000, size 24 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision-apps-r5f-virtual-eth-buffers@e4800000, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000e4800000..0x00000000e5ffffff (24576 KiB) nomap non-reusable vision-apps-r5f-virtual-eth-buffers@e4800000
[Wed Mar  5 18:17:16 2025] Reserved memory: created DMA memory pool at 0x00000000e4000000, size 8 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision-apps-r5f-virtual-eth-queues@e4000000, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000e4000000..0x00000000e47fffff (8192 KiB) nomap non-reusable vision-apps-r5f-virtual-eth-queues@e4000000
[Wed Mar  5 18:17:16 2025] Reserved memory: created DMA memory pool at 0x00000000d8000000, size 192 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision-apps-core-heap-memory-lo@d8000000, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000d8000000..0x00000000e3ffffff (196608 KiB) nomap non-reusable vision-apps-core-heap-memory-lo@d8000000
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision_apps_shared-memories, compatible id dma-heap-carveout
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000b8000000..0x00000000d7ffffff (524288 KiB) map non-reusable vision_apps_shared-memories
[Wed Mar  5 18:17:16 2025] Reserved memory: created DMA memory pool at 0x00000000b2100000, size 95 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision-apps-c71-memory@b2100000, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000b2100000..0x00000000b7ffffff (97280 KiB) nomap non-reusable vision-apps-c71-memory@b2100000
[Wed Mar  5 18:17:16 2025] Reserved memory: created DMA memory pool at 0x00000000b2000000, size 1 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision-apps-c71-dma-memory@b2000000, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000b2000000..0x00000000b20fffff (1024 KiB) nomap non-reusable vision-apps-c71-dma-memory@b2000000
[Wed Mar  5 18:17:16 2025] Reserved memory: created DMA memory pool at 0x00000000ac000000, size 96 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision-apps-dma-memory@ac000000, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000ac000000..0x00000000b1ffffff (98304 KiB) nomap non-reusable vision-apps-dma-memory@ac000000
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000aa000000..0x00000000abffffff (32768 KiB) nomap non-reusable vision-apps-rtos-ipc-memory-region
[Wed Mar  5 18:17:16 2025] Reserved memory: created DMA memory pool at 0x00000000a9100000, size 15 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision-apps-c66-memory@a9100000, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000a9100000..0x00000000a9ffffff (15360 KiB) nomap non-reusable vision-apps-c66-memory@a9100000
[Wed Mar  5 18:17:16 2025] Reserved memory: created DMA memory pool at 0x00000000a9000000, size 1 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision-apps-c66-dma-memory@a9000000, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000a9000000..0x00000000a90fffff (1024 KiB) nomap non-reusable vision-apps-c66-dma-memory@a9000000
[Wed Mar  5 18:17:16 2025] Reserved memory: created DMA memory pool at 0x00000000a8100000, size 15 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision-apps-c66-memory@a8100000, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000a8100000..0x00000000a8ffffff (15360 KiB) nomap non-reusable vision-apps-c66-memory@a8100000
[Wed Mar  5 18:17:16 2025] Reserved memory: created DMA memory pool at 0x00000000a8000000, size 1 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision-apps-c66-dma-memory@a8000000, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000a8000000..0x00000000a80fffff (1024 KiB) nomap non-reusable vision-apps-c66-dma-memory@a8000000
[Wed Mar  5 18:17:16 2025] Reserved memory: created DMA memory pool at 0x00000000a7100000, size 15 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision-apps-r5f-memory@a7100000, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000a7100000..0x00000000a7ffffff (15360 KiB) nomap non-reusable vision-apps-r5f-memory@a7100000
[Wed Mar  5 18:17:16 2025] Reserved memory: created DMA memory pool at 0x00000000a7000000, size 1 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision-apps-r5f-dma-memory@a7000000, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000a7000000..0x00000000a70fffff (1024 KiB) nomap non-reusable vision-apps-r5f-dma-memory@a7000000
[Wed Mar  5 18:17:16 2025] Reserved memory: created DMA memory pool at 0x00000000a6100000, size 15 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision-apps-r5f-memory@a6100000, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000a6100000..0x00000000a6ffffff (15360 KiB) nomap non-reusable vision-apps-r5f-memory@a6100000
[Wed Mar  5 18:17:16 2025] Reserved memory: created DMA memory pool at 0x00000000a6000000, size 1 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision-apps-r5f-dma-memory@a6000000, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000a6000000..0x00000000a60fffff (1024 KiB) nomap non-reusable vision-apps-r5f-dma-memory@a6000000
[Wed Mar  5 18:17:16 2025] Reserved memory: created DMA memory pool at 0x00000000a4100000, size 31 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision-apps-r5f-memory@a4100000, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000a4100000..0x00000000a5ffffff (31744 KiB) nomap non-reusable vision-apps-r5f-memory@a4100000
[Wed Mar  5 18:17:16 2025] Reserved memory: created DMA memory pool at 0x00000000a4000000, size 1 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision-apps-r5f-dma-memory@a4000000, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000a4000000..0x00000000a40fffff (1024 KiB) nomap non-reusable vision-apps-r5f-dma-memory@a4000000
[Wed Mar  5 18:17:16 2025] Reserved memory: created DMA memory pool at 0x00000000a2100000, size 31 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision-apps-r5f-memory@a2100000, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000a2100000..0x00000000a3ffffff (31744 KiB) nomap non-reusable vision-apps-r5f-memory@a2100000
[Wed Mar  5 18:17:16 2025] Reserved memory: created DMA memory pool at 0x00000000a2000000, size 1 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision-apps-r5f-dma-memory@a2000000, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000a2000000..0x00000000a20fffff (1024 KiB) nomap non-reusable vision-apps-r5f-dma-memory@a2000000
[Wed Mar  5 18:17:16 2025] Reserved memory: created DMA memory pool at 0x00000000a1100000, size 15 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision-apps-r5f-memory@a1100000, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000a1100000..0x00000000a1ffffff (15360 KiB) nomap non-reusable vision-apps-r5f-memory@a1100000
[Wed Mar  5 18:17:16 2025] Reserved memory: created DMA memory pool at 0x00000000a1000000, size 1 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision-apps-r5f-dma-memory@a1000000, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000a1000000..0x00000000a10fffff (1024 KiB) nomap non-reusable vision-apps-r5f-dma-memory@a1000000
[Wed Mar  5 18:17:16 2025] Reserved memory: created DMA memory pool at 0x00000000a0100000, size 15 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision-apps-r5f-memory@a0100000, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000a0100000..0x00000000a0ffffff (15360 KiB) nomap non-reusable vision-apps-r5f-memory@a0100000
[Wed Mar  5 18:17:16 2025] Reserved memory: created DMA memory pool at 0x00000000a0000000, size 1 MiB
[Wed Mar  5 18:17:16 2025] OF: reserved mem: initialized node vision-apps-r5f-dma-memory@a0000000, compatible id shared-dma-pool
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x00000000a0000000..0x00000000a00fffff (1024 KiB) nomap non-reusable vision-apps-r5f-dma-memory@a0000000
[Wed Mar  5 18:17:16 2025] OF: reserved mem: 0x000000009e800000..0x000000009fffffff (24576 KiB) nomap non-reusable optee@9e800000
[Wed Mar  5 18:17:16 2025] Zone ranges:
[Wed Mar  5 18:17:16 2025]   DMA      [mem 0x0000000080000000-0x00000000ffffffff]
[Wed Mar  5 18:17:16 2025]   DMA32    empty
[Wed Mar  5 18:17:16 2025]   Normal   [mem 0x0000000100000000-0x00000008ffffffff]
[Wed Mar  5 18:17:16 2025] Movable zone start for each node
[Wed Mar  5 18:17:16 2025] Early memory node ranges
[Wed Mar  5 18:17:16 2025]   node   0: [mem 0x0000000080000000-0x000000009e7fffff]
[Wed Mar  5 18:17:16 2025]   node   0: [mem 0x000000009e800000-0x00000000b7ffffff]
[Wed Mar  5 18:17:16 2025]   node   0: [mem 0x00000000b8000000-0x00000000d7ffffff]
[Wed Mar  5 18:17:16 2025]   node   0: [mem 0x00000000d8000000-0x00000000e5ffffff]
[Wed Mar  5 18:17:16 2025]   node   0: [mem 0x00000000e6000000-0x00000000ffffffff]
[Wed Mar  5 18:17:16 2025]   node   0: [mem 0x0000000880000000-0x00000008a6ffffff]
[Wed Mar  5 18:17:16 2025]   node   0: [mem 0x00000008a7000000-0x00000008ffffffff]
[Wed Mar  5 18:17:16 2025] Initmem setup node 0 [mem 0x0000000080000000-0x00000008ffffffff]
[Wed Mar  5 18:17:16 2025] psci: probing for conduit method from DT.
[Wed Mar  5 18:17:16 2025] psci: PSCIv1.1 detected in firmware.
[Wed Mar  5 18:17:16 2025] psci: Using standard PSCI v0.2 function IDs
[Wed Mar  5 18:17:16 2025] psci: Trusted OS migration not required
[Wed Mar  5 18:17:16 2025] psci: SMC Calling Convention v1.5
[Wed Mar  5 18:17:16 2025] percpu: Embedded 22 pages/cpu s51672 r8192 d30248 u90112
[Wed Mar  5 18:17:16 2025] pcpu-alloc: s51672 r8192 d30248 u90112 alloc=22*4096
[Wed Mar  5 18:17:16 2025] pcpu-alloc: [0] 0 [0] 1 
[Wed Mar  5 18:17:16 2025] Detected PIPT I-cache on CPU0
[Wed Mar  5 18:17:16 2025] CPU features: detected: GIC system register CPU interface
[Wed Mar  5 18:17:16 2025] CPU features: detected: Spectre-v3a
[Wed Mar  5 18:17:16 2025] CPU features: detected: Spectre-BHB
[Wed Mar  5 18:17:16 2025] CPU features: detected: ARM erratum 1742098
[Wed Mar  5 18:17:16 2025] CPU features: detected: ARM errata 1165522, 1319367, or 1530923
[Wed Mar  5 18:17:16 2025] alternatives: applying boot alternatives
[Wed Mar  5 18:17:16 2025] 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),57344k@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) systemd.hostname=tda4vm-sk root=PARTUUID=076c4a2a-02 rw rootfstype=ext4 rootwait
[Wed Mar  5 18:17:16 2025] Unknown kernel command line parameters "mtdparts=47040000.spi.0:512k(ospi.tiboot3),2m(ospi.tispl),4m(ospi.u-boot),256k(ospi.env),1m(ospi.sysfw),256k(ospi.env.backup),57344k@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)", will be passed to user space.
[Wed Mar  5 18:17:16 2025] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[Wed Mar  5 18:17:16 2025] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[Wed Mar  5 18:17:16 2025] Built 1 zonelists, mobility grouping on.  Total pages: 1048576
[Wed Mar  5 18:17:16 2025] mem auto-init: stack:all(zero), heap alloc:off, heap free:off
[Wed Mar  5 18:17:16 2025] software IO TLB: area num 2.
[Wed Mar  5 18:17:16 2025] software IO TLB: mapped [mem 0x00000000fbfff000-0x00000000fffff000] (64MB)
[Wed Mar  5 18:17:16 2025] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[Wed Mar  5 18:17:16 2025] rcu: Preemptible hierarchical RCU implementation.
[Wed Mar  5 18:17:16 2025] rcu: 	RCU event tracing is enabled.
[Wed Mar  5 18:17:16 2025] rcu: 	RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=2.
[Wed Mar  5 18:17:16 2025] 	Trampoline variant of Tasks RCU enabled.
[Wed Mar  5 18:17:16 2025] 	Tracing variant of Tasks RCU enabled.
[Wed Mar  5 18:17:16 2025] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[Wed Mar  5 18:17:16 2025] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[Wed Mar  5 18:17:16 2025] RCU Tasks: Setting shift to 1 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=2.
[Wed Mar  5 18:17:16 2025] RCU Tasks Trace: Setting shift to 1 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=2.
[Wed Mar  5 18:17:16 2025] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[Wed Mar  5 18:17:16 2025] GICv3: GIC: Using split EOI/Deactivate mode
[Wed Mar  5 18:17:16 2025] GICv3: 960 SPIs implemented
[Wed Mar  5 18:17:16 2025] GICv3: 0 Extended SPIs implemented
[Wed Mar  5 18:17:16 2025] Root IRQ handler: gic_handle_irq
[Wed Mar  5 18:17:16 2025] GICv3: GICv3 features: 16 PPIs
[Wed Mar  5 18:17:16 2025] GICv3: GICD_CTRL.DS=0, SCR_EL3.FIQ=1
[Wed Mar  5 18:17:16 2025] GICv3: CPU0: found redistributor 0 region 0:0x0000000001900000
[Wed Mar  5 18:17:16 2025] ITS [mem 0x01820000-0x0182ffff]
[Wed Mar  5 18:17:16 2025] GIC: enabling workaround for ITS: Socionext Synquacer pre-ITS
[Wed Mar  5 18:17:16 2025] ITS@0x0000000001820000: Devices Table too large, reduce ids 20->19
[Wed Mar  5 18:17:16 2025] ITS@0x0000000001820000: allocated 524288 Devices @8a7800000 (flat, esz 8, psz 64K, shr 0)
[Wed Mar  5 18:17:16 2025] ITS: using cache flushing for cmd queue
[Wed Mar  5 18:17:16 2025] GICv3: using LPI property table @0x00000008a7040000
[Wed Mar  5 18:17:16 2025] GIC: using cache flushing for LPI property table
[Wed Mar  5 18:17:16 2025] GICv3: CPU0: using allocated LPI pending table @0x00000008a7050000
[Wed Mar  5 18:17:16 2025] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[Wed Mar  5 18:17:16 2025] arch_timer: cp15 timer(s) running at 200.00MHz (phys).
[Wed Mar  5 18:17:16 2025] clocksource: arch_sys_counter: mask: 0x3ffffffffffffff max_cycles: 0x2e2049d3e8, max_idle_ns: 440795210634 ns
[Wed Mar  5 18:17:16 2025] sched_clock: 58 bits at 200MHz, resolution 5ns, wraps every 4398046511102ns
[Wed Mar  5 18:17:16 2025] Console: colour dummy device 80x25
[Wed Mar  5 18:17:16 2025] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=800000)
[Wed Mar  5 18:17:16 2025] pid_max: default: 32768 minimum: 301
[Wed Mar  5 18:17:16 2025] LSM: initializing lsm=capability,selinux
[Wed Mar  5 18:17:16 2025] SELinux:  Initializing.
[Wed Mar  5 18:17:16 2025] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[Wed Mar  5 18:17:16 2025] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[Wed Mar  5 18:17:16 2025] rcu: Hierarchical SRCU implementation.
[Wed Mar  5 18:17:16 2025] rcu: 	Max phase no-delay instances is 1000.
[Wed Mar  5 18:17:16 2025] Timer migration: 1 hierarchy levels; 8 children per group; 1 crossnode level
[Wed Mar  5 18:17:16 2025] EFI services will not be available.
[Wed Mar  5 18:17:16 2025] smp: Bringing up secondary CPUs ...
[Wed Mar  5 18:17:16 2025] Detected PIPT I-cache on CPU1
[Wed Mar  5 18:17:16 2025] GICv3: CPU1: found redistributor 1 region 0:0x0000000001920000
[Wed Mar  5 18:17:16 2025] GICv3: CPU1: using allocated LPI pending table @0x00000008a7060000
[Wed Mar  5 18:17:16 2025] CPU1: Booted secondary processor 0x0000000001 [0x411fd080]
[Wed Mar  5 18:17:16 2025] smp: Brought up 1 node, 2 CPUs
[Wed Mar  5 18:17:16 2025] SMP: Total of 2 processors activated.
[Wed Mar  5 18:17:16 2025] CPU: All CPU(s) started at EL2
[Wed Mar  5 18:17:16 2025] CPU features: detected: 32-bit EL0 Support
[Wed Mar  5 18:17:16 2025] CPU features: detected: CRC32 instructions
[Wed Mar  5 18:17:16 2025] alternatives: applying system-wide alternatives
[Wed Mar  5 18:17:16 2025] Memory: 1687660K/4194304K available (12928K kernel code, 1254K rwdata, 4644K rodata, 2752K init, 639K bss, 1974384K reserved, 524288K cma-reserved)
[Wed Mar  5 18:17:16 2025] devtmpfs: initialized
[Wed Mar  5 18:17:16 2025] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[Wed Mar  5 18:17:16 2025] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
[Wed Mar  5 18:17:16 2025] 27152 pages in range for non-PLT usage
[Wed Mar  5 18:17:16 2025] 518672 pages in range for PLT usage
[Wed Mar  5 18:17:16 2025] pinctrl core: initialized pinctrl subsystem
[Wed Mar  5 18:17:16 2025] DMI not present or invalid.
[Wed Mar  5 18:17:16 2025] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[Wed Mar  5 18:17:16 2025] DMA: preallocated 512 KiB GFP_KERNEL pool for atomic allocations
[Wed Mar  5 18:17:16 2025] DMA: preallocated 512 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[Wed Mar  5 18:17:16 2025] DMA: preallocated 512 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[Wed Mar  5 18:17:16 2025] audit: initializing netlink subsys (disabled)
[Wed Mar  5 18:17:16 2025] audit: type=2000 audit(0.204:1): state=initialized audit_enabled=0 res=1
[Wed Mar  5 18:17:16 2025] thermal_sys: Registered thermal governor 'step_wise'
[Wed Mar  5 18:17:16 2025] thermal_sys: Registered thermal governor 'power_allocator'
[Wed Mar  5 18:17:16 2025] cpuidle: using governor menu
[Wed Mar  5 18:17:16 2025] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[Wed Mar  5 18:17:16 2025] ASID allocator initialised with 65536 entries
[Wed Mar  5 18:17:16 2025] /bus@100000/interrupt-controller@1800000: Fixed dependency cycle(s) with /bus@100000/interrupt-controller@1800000
[Wed Mar  5 18:17:16 2025] /bus@100000/dp-bridge@a000000: Fixed dependency cycle(s) with /bus@100000/dss@4a00000
[Wed Mar  5 18:17:16 2025] /bus@100000/dss@4a00000: Fixed dependency cycle(s) with /bus@100000/dp-bridge@a000000
[Wed Mar  5 18:17:16 2025] /bus@100000/dp-bridge@a000000: Fixed dependency cycle(s) with /bus@100000/dss@4a00000
[Wed Mar  5 18:17:16 2025] /bus@100000/dp-bridge@a000000: Fixed dependency cycle(s) with /bus@100000/dss@4a00000
[Wed Mar  5 18:17:16 2025] /bus@100000/dss@4a00000: Fixed dependency cycle(s) with /bus@100000/dp-bridge@a000000
[Wed Mar  5 18:17:16 2025] /bus@100000/dp-bridge@a000000: Fixed dependency cycle(s) with /connector
[Wed Mar  5 18:17:16 2025] /connector: Fixed dependency cycle(s) with /bus@100000/dp-bridge@a000000
[Wed Mar  5 18:17:16 2025] /hdmi-connector: Fixed dependency cycle(s) with /dvi-bridge
[Wed Mar  5 18:17:16 2025] /bus@100000/dss@4a00000: Fixed dependency cycle(s) with /dvi-bridge
[Wed Mar  5 18:17:16 2025] /dvi-bridge: Fixed dependency cycle(s) with /hdmi-connector
[Wed Mar  5 18:17:16 2025] /dvi-bridge: Fixed dependency cycle(s) with /bus@100000/dss@4a00000
[Wed Mar  5 18:17:16 2025] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
[Wed Mar  5 18:17:16 2025] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page
[Wed Mar  5 18:17:16 2025] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages
[Wed Mar  5 18:17:16 2025] HugeTLB: 0 KiB vmemmap can be freed for a 32.0 MiB page
[Wed Mar  5 18:17:16 2025] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
[Wed Mar  5 18:17:16 2025] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page
[Wed Mar  5 18:17:16 2025] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages
[Wed Mar  5 18:17:16 2025] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page
[Wed Mar  5 18:17:16 2025] k3-chipinfo 43000014.chipid: Family:J721E rev:SR1.1 JTAGID[0x1bb6402f] Detected
[Wed Mar  5 18:17:16 2025] iommu: Default domain type: Translated
[Wed Mar  5 18:17:16 2025] iommu: DMA domain TLB invalidation policy: strict mode
[Wed Mar  5 18:17:16 2025] SCSI subsystem initialized
[Wed Mar  5 18:17:16 2025] libata version 3.00 loaded.
[Wed Mar  5 18:17:16 2025] usbcore: registered new interface driver usbfs
[Wed Mar  5 18:17:16 2025] usbcore: registered new interface driver hub
[Wed Mar  5 18:17:16 2025] usbcore: registered new device driver usb
[Wed Mar  5 18:17:16 2025] pps_core: LinuxPPS API ver. 1 registered
[Wed Mar  5 18:17:16 2025] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[Wed Mar  5 18:17:16 2025] PTP clock support registered
[Wed Mar  5 18:17:16 2025] EDAC MC: Ver: 3.0.0
[Wed Mar  5 18:17:16 2025] scmi_core: SCMI protocol bus registered
[Wed Mar  5 18:17:16 2025] FPGA manager framework
[Wed Mar  5 18:17:16 2025] Advanced Linux Sound Architecture Driver Initialized.
[Wed Mar  5 18:17:16 2025] vgaarb: loaded
[Wed Mar  5 18:17:16 2025] clocksource: Switched to clocksource arch_sys_counter
[Wed Mar  5 18:17:16 2025] VFS: Disk quotas dquot_6.6.0
[Wed Mar  5 18:17:16 2025] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[Wed Mar  5 18:17:16 2025] Carveout Heap: Exported 512 MiB at 0x00000000b8000000
[Wed Mar  5 18:17:16 2025] NET: Registered PF_INET protocol family
[Wed Mar  5 18:17:16 2025] IP idents hash table entries: 32768 (order: 6, 262144 bytes, linear)
[Wed Mar  5 18:17:16 2025] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear)
[Wed Mar  5 18:17:16 2025] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[Wed Mar  5 18:17:16 2025] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear)
[Wed Mar  5 18:17:16 2025] TCP bind hash table entries: 16384 (order: 7, 524288 bytes, linear)
[Wed Mar  5 18:17:16 2025] TCP: Hash tables configured (established 16384 bind 16384)
[Wed Mar  5 18:17:16 2025] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)
[Wed Mar  5 18:17:16 2025] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear)
[Wed Mar  5 18:17:16 2025] NET: Registered PF_UNIX/PF_LOCAL protocol family
[Wed Mar  5 18:17:16 2025] RPC: Registered named UNIX socket transport module.
[Wed Mar  5 18:17:16 2025] RPC: Registered udp transport module.
[Wed Mar  5 18:17:16 2025] RPC: Registered tcp transport module.
[Wed Mar  5 18:17:16 2025] RPC: Registered tcp-with-tls transport module.
[Wed Mar  5 18:17:16 2025] RPC: Registered tcp NFSv4.1 backchannel transport module.
[Wed Mar  5 18:17:16 2025] NET: Registered PF_XDP protocol family
[Wed Mar  5 18:17:16 2025] PCI: CLS 0 bytes, default 64
[Wed Mar  5 18:17:16 2025] Initialise system trusted keyrings
[Wed Mar  5 18:17:16 2025] workingset: timestamp_bits=46 max_order=20 bucket_order=0
[Wed Mar  5 18:17:16 2025] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[Wed Mar  5 18:17:16 2025] NFS: Registering the id_resolver key type
[Wed Mar  5 18:17:16 2025] Key type id_resolver registered
[Wed Mar  5 18:17:16 2025] Key type id_legacy registered
[Wed Mar  5 18:17:16 2025] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[Wed Mar  5 18:17:16 2025] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[Wed Mar  5 18:17:17 2025] Key type asymmetric registered
[Wed Mar  5 18:17:17 2025] Asymmetric key parser 'x509' registered
[Wed Mar  5 18:17:17 2025] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
[Wed Mar  5 18:17:17 2025] io scheduler mq-deadline registered
[Wed Mar  5 18:17:17 2025] io scheduler kyber registered
[Wed Mar  5 18:17:17 2025] io scheduler bfq registered
[Wed Mar  5 18:17:17 2025] pinctrl-single 4301c000.pinctrl: 94 pins, size 376
[Wed Mar  5 18:17:17 2025] pinctrl-single 11c000.pinctrl: 173 pins, size 692
[Wed Mar  5 18:17:17 2025] pinctrl-single 104200.pinctrl: 20 pins, size 80
[Wed Mar  5 18:17:17 2025] pinctrl-single 104280.pinctrl: 8 pins, size 32
[Wed Mar  5 18:17:17 2025] ledtrig-cpu: registered to indicate activity on CPUs
[Wed Mar  5 18:17:17 2025] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[Wed Mar  5 18:17:17 2025] arm-smmu-v3 36600000.iommu: ias 48-bit, oas 48-bit (features 0x00101faf)
[Wed Mar  5 18:17:17 2025] arm-smmu-v3 36600000.iommu: allocated 65536 entries for cmdq
[Wed Mar  5 18:17:17 2025] arm-smmu-v3 36600000.iommu: allocated 32768 entries for evtq
[Wed Mar  5 18:17:17 2025] arm-smmu-v3 36600000.iommu: msi_domain absent - falling back to wired irqs
[Wed Mar  5 18:17:17 2025] loop: module loaded
[Wed Mar  5 18:17:17 2025] megasas: 07.727.03.00-rc1
[Wed Mar  5 18:17:17 2025] tun: Universal TUN/TAP device driver, 1.6
[Wed Mar  5 18:17:17 2025] VFIO - User Level meta-driver version: 0.3
[Wed Mar  5 18:17:17 2025] usbcore: registered new interface driver usb-storage
[Wed Mar  5 18:17:17 2025] i2c_dev: i2c /dev entries driver
[Wed Mar  5 18:17:17 2025] sdhci: Secure Digital Host Controller Interface driver
[Wed Mar  5 18:17:17 2025] sdhci: Copyright(c) Pierre Ossman
[Wed Mar  5 18:17:17 2025] sdhci-pltfm: SDHCI platform and OF driver helper
[Wed Mar  5 18:17:17 2025] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[Wed Mar  5 18:17:17 2025] usbcore: registered new interface driver usbhid
[Wed Mar  5 18:17:17 2025] usbhid: USB HID core driver
[Wed Mar  5 18:17:17 2025] hw perfevents: enabled with armv8_cortex_a72 PMU driver, 7 (0,8000003f) counters available
[Wed Mar  5 18:17:17 2025] optee: probing for conduit method.
[Wed Mar  5 18:17:17 2025] optee: revision 4.5 (ef1ebdc23034a804)
[Wed Mar  5 18:17:17 2025] optee: dynamic shared memory is enabled
[Wed Mar  5 18:17:17 2025] optee: initialized driver
[Wed Mar  5 18:17:17 2025] random: crng init done
[Wed Mar  5 18:17:17 2025] Initializing XFRM netlink socket
[Wed Mar  5 18:17:17 2025] NET: Registered PF_PACKET protocol family
[Wed Mar  5 18:17:17 2025] Key type dns_resolver registered
[Wed Mar  5 18:17:17 2025] registered taskstats version 1
[Wed Mar  5 18:17:17 2025] Loading compiled-in X.509 certificates
[Wed Mar  5 18:17:17 2025] ti-sci 44083000.system-controller: ABI: 4.0 (firmware rev 0x000b '11.0.9--v11.00.09+ (Fancy Rat)')
[Wed Mar  5 18:17:17 2025] omap_i2c 42120000.i2c: bus 0 rev0.12 at 400 kHz
[Wed Mar  5 18:17:17 2025] pca954x 1-0071: supply vdd not found, using dummy regulator
[Wed Mar  5 18:17:17 2025] i2c i2c-1: Added multiplexed i2c bus 2
[Wed Mar  5 18:17:17 2025] i2c i2c-1: Added multiplexed i2c bus 3
[Wed Mar  5 18:17:17 2025] pca954x 1-0071: registered 2 multiplexed busses for I2C switch pca9543
[Wed Mar  5 18:17:17 2025] omap_i2c 2000000.i2c: bus 1 rev0.12 at 400 kHz
[Wed Mar  5 18:17:17 2025] omap_i2c 2010000.i2c: bus 4 rev0.12 at 100 kHz
[Wed Mar  5 18:17:17 2025] pca954x 5-0070: supply vdd not found, using dummy regulator
[Wed Mar  5 18:17:17 2025] i2c i2c-5: Added multiplexed i2c bus 6
[Wed Mar  5 18:17:17 2025] i2c i2c-5: Added multiplexed i2c bus 7
[Wed Mar  5 18:17:17 2025] pca954x 5-0070: registered 2 multiplexed busses for I2C switch pca9543
[Wed Mar  5 18:17:17 2025] omap_i2c 2030000.i2c: bus 5 rev0.12 at 400 kHz
[Wed Mar  5 18:17:17 2025] omap_i2c 2050000.i2c: bus 8 rev0.12 at 400 kHz
[Wed Mar  5 18:17:17 2025] ti-sci-intr 42200000.interrupt-controller: Interrupt Router 137 domain created
[Wed Mar  5 18:17:17 2025] ti-sci-intr bus@100000:interrupt-controller@a00000: Interrupt Router 131 domain created
[Wed Mar  5 18:17:17 2025] ti-sci-intr 310e0000.interrupt-controller: Interrupt Router 213 domain created
[Wed Mar  5 18:17:17 2025] ti-sci-inta 33d00000.interrupt-controller: Interrupt Aggregator domain 209 created
[Wed Mar  5 18:17:17 2025] k3-ringacc 2b800000.ringacc: Ring Accelerator probed rings:286, gp-rings[96,20] sci-dev-id:235
[Wed Mar  5 18:17:17 2025] k3-ringacc 2b800000.ringacc: dma-ring-reset-quirk: disabled
[Wed Mar  5 18:17:17 2025] k3-ringacc 2b800000.ringacc: RA Proxy rev. 66346100, num_proxies:64
[Wed Mar  5 18:17:17 2025] k3-ringacc 3c000000.ringacc: Ring Accelerator probed rings:1024, gp-rings[440,150] sci-dev-id:211
[Wed Mar  5 18:17:17 2025] k3-ringacc 3c000000.ringacc: dma-ring-reset-quirk: disabled
[Wed Mar  5 18:17:17 2025] k3-ringacc 3c000000.ringacc: RA Proxy rev. 66346100, num_proxies:64
[Wed Mar  5 18:17:17 2025] 40a00000.serial: ttyS1 at MMIO 0x40a00000 (irq = 206, base_baud = 6000000) is a 8250
[Wed Mar  5 18:17:17 2025] 2800000.serial: ttyS2 at MMIO 0x2800000 (irq = 207, base_baud = 3000000) is a 8250
[Wed Mar  5 18:17:17 2025] printk: legacy console [ttyS2] enabled
[Wed Mar  5 18:17:17 2025] printk: legacy bootconsole [ns16550a0] disabled
[Wed Mar  5 18:17:17 2025] 2810000.serial: ttyS3 at MMIO 0x2810000 (irq = 208, base_baud = 3000000) is a 8250
[Wed Mar  5 18:17:17 2025] davinci_mdio 46000f00.mdio: Configuring MDIO in manual mode
[Wed Mar  5 18:17:17 2025] davinci_mdio 46000f00.mdio: davinci mdio revision 9.7, bus freq 1000000
[Wed Mar  5 18:17:17 2025] davinci_mdio 46000f00.mdio: phy[0]: device 46000f00.mdio:00, driver TI DP83867
[Wed Mar  5 18:17:17 2025] am65-cpsw-nuss 46000000.ethernet: initializing am65 cpsw nuss version 0x6BA00101, cpsw version 0x6BA80100 Ports: 2 quirks:00000000
[Wed Mar  5 18:17:17 2025] am65-cpsw-nuss 46000000.ethernet: initialized cpsw ale version 1.4
[Wed Mar  5 18:17:17 2025] am65-cpsw-nuss 46000000.ethernet: ALE Table size 64, Policers 8
[Wed Mar  5 18:17:17 2025] am65-cpsw-nuss 46000000.ethernet: CPTS ver 0x4e8a010a, freq:500000000, add_val:1 pps:0
[Wed Mar  5 18:17:17 2025] am65-cpts 310d0000.cpts: CPTS ver 0x4e8a010a, freq:200000000, add_val:4 pps:0
[Wed Mar  5 18:17:18 2025] tps6594-rtc tps6594-rtc.4.auto: registered as rtc0
[Wed Mar  5 18:17:18 2025] tps6594 0-004c: Error IRQ trap undervoltage for LDO1
[Wed Mar  5 18:17:18 2025] j721e-pcie 2900000.pcie: host bridge /bus@100000/pcie@2900000 ranges:
[Wed Mar  5 18:17:18 2025] j721e-pcie 2900000.pcie:       IO 0x0010001000..0x0010010fff -> 0x0010001000
[Wed Mar  5 18:17:18 2025] j721e-pcie 2900000.pcie:      MEM 0x0010011000..0x0017ffffff -> 0x0010011000
[Wed Mar  5 18:17:18 2025] j721e-pcie 2900000.pcie:   IB MEM 0x0000000000..0xffffffffffff -> 0x0000000000
[Wed Mar  5 18:17:19 2025] j721e-pcie 2900000.pcie: PCI host bridge to bus 0000:00
[Wed Mar  5 18:17:19 2025] pci_bus 0000:00: root bus resource [bus 00-ff]
[Wed Mar  5 18:17:19 2025] pci_bus 0000:00: root bus resource [io  0x0000-0xffff] (bus address [0x10001000-0x10010fff])
[Wed Mar  5 18:17:19 2025] pci_bus 0000:00: root bus resource [mem 0x10011000-0x17ffffff]
[Wed Mar  5 18:17:19 2025] pci 0000:00:00.0: [104c:b00d] type 01 class 0x060400 PCIe Root Port
[Wed Mar  5 18:17:19 2025] pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
[Wed Mar  5 18:17:19 2025] pci 0000:00:00.0: PCI bridge to [bus 00]
[Wed Mar  5 18:17:19 2025] pci 0000:00:00.0:   bridge window [io  0x0000-0x0fff]
[Wed Mar  5 18:17:19 2025] pci 0000:00:00.0:   bridge window [mem 0x00000000-0x000fffff]
[Wed Mar  5 18:17:19 2025] pci 0000:00:00.0:   bridge window [mem 0x00000000-0x000fffff 64bit pref]
[Wed Mar  5 18:17:19 2025] pci 0000:00:00.0: supports D1
[Wed Mar  5 18:17:19 2025] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[Wed Mar  5 18:17:19 2025] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[Wed Mar  5 18:17:19 2025] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[Wed Mar  5 18:17:19 2025] pci 0000:00:00.0: PCI bridge to [bus 01]
[Wed Mar  5 18:17:19 2025] pci_bus 0000:00: resource 4 [io  0x0000-0xffff]
[Wed Mar  5 18:17:19 2025] pci_bus 0000:00: resource 5 [mem 0x10011000-0x17ffffff]
[Wed Mar  5 18:17:19 2025] pcieport 0000:00:00.0: of_irq_parse_pci: failed with rc=-22
[Wed Mar  5 18:17:19 2025] pcieport 0000:00:00.0: PME: Signaling with IRQ 654
[Wed Mar  5 18:17:19 2025] pcieport 0000:00:00.0: AER: enabled with IRQ 654
[Wed Mar  5 18:17:19 2025] j721e-pcie 2910000.pcie: host bridge /bus@100000/pcie@2910000 ranges:
[Wed Mar  5 18:17:19 2025] j721e-pcie 2910000.pcie:       IO 0x0018001000..0x0018010fff -> 0x0018001000
[Wed Mar  5 18:17:19 2025] j721e-pcie 2910000.pcie:      MEM 0x0018011000..0x001fffffff -> 0x0018011000
[Wed Mar  5 18:17:19 2025] j721e-pcie 2910000.pcie:   IB MEM 0x0000000000..0xffffffffffff -> 0x0000000000
[Wed Mar  5 18:17:20 2025] j721e-pcie 2910000.pcie: PCI host bridge to bus 0001:00
[Wed Mar  5 18:17:20 2025] pci_bus 0001:00: root bus resource [bus 00-ff]
[Wed Mar  5 18:17:20 2025] pci_bus 0001:00: root bus resource [io  0x10000-0x1ffff] (bus address [0x18001000-0x18010fff])
[Wed Mar  5 18:17:20 2025] pci_bus 0001:00: root bus resource [mem 0x18011000-0x1fffffff]
[Wed Mar  5 18:17:20 2025] pci 0001:00:00.0: [104c:b00d] type 01 class 0x060400 PCIe Root Port
[Wed Mar  5 18:17:20 2025] pci_bus 0001:00: 2-byte config write to 0001:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
[Wed Mar  5 18:17:20 2025] pci 0001:00:00.0: PCI bridge to [bus 00]
[Wed Mar  5 18:17:20 2025] pci 0001:00:00.0:   bridge window [io  0x0000-0x0fff]
[Wed Mar  5 18:17:20 2025] pci 0001:00:00.0:   bridge window [mem 0x00000000-0x000fffff]
[Wed Mar  5 18:17:20 2025] pci 0001:00:00.0:   bridge window [mem 0x00000000-0x000fffff 64bit pref]
[Wed Mar  5 18:17:20 2025] pci 0001:00:00.0: supports D1
[Wed Mar  5 18:17:20 2025] pci 0001:00:00.0: PME# supported from D0 D1 D3hot
[Wed Mar  5 18:17:20 2025] pci 0001:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[Wed Mar  5 18:17:20 2025] pci_bus 0001:01: busn_res: [bus 01-ff] end is updated to 01
[Wed Mar  5 18:17:20 2025] pci 0001:00:00.0: PCI bridge to [bus 01]
[Wed Mar  5 18:17:20 2025] pci_bus 0001:00: resource 4 [io  0x10000-0x1ffff]
[Wed Mar  5 18:17:20 2025] pci_bus 0001:00: resource 5 [mem 0x18011000-0x1fffffff]
[Wed Mar  5 18:17:20 2025] pcieport 0001:00:00.0: of_irq_parse_pci: failed with rc=-22
[Wed Mar  5 18:17:20 2025] pcieport 0001:00:00.0: PME: Signaling with IRQ 656
[Wed Mar  5 18:17:20 2025] pcieport 0001:00:00.0: AER: enabled with IRQ 656
[Wed Mar  5 18:17:20 2025] ti-udma 285c0000.dma-controller: Channels: 26 (tchan: 13, rchan: 13, gp-rflow: 8)
[Wed Mar  5 18:17:20 2025] ti-udma 31150000.dma-controller: Channels: 122 (tchan: 61, rchan: 61, gp-rflow: 16)
[Wed Mar  5 18:17:20 2025] 8 fixed-partitions partitions found on MTD device 47040000.spi.0
[Wed Mar  5 18:17:20 2025] Creating 8 MTD partitions on "47040000.spi.0":
[Wed Mar  5 18:17:20 2025] 0x000000000000-0x000000080000 : "ospi.tiboot3"
[Wed Mar  5 18:17:20 2025] 0x000000080000-0x000000280000 : "ospi.tispl"
[Wed Mar  5 18:17:20 2025] 0x000000280000-0x000000680000 : "ospi.u-boot"
[Wed Mar  5 18:17:20 2025] 0x000000680000-0x0000006c0000 : "ospi.env"
[Wed Mar  5 18:17:20 2025] 0x0000006c0000-0x0000007c0000 : "ospi.sysfw"
[Wed Mar  5 18:17:20 2025] 0x0000007c0000-0x000000800000 : "ospi.env.backup"
[Wed Mar  5 18:17:20 2025] 0x000000800000-0x000003fc0000 : "ospi.rootfs"
[Wed Mar  5 18:17:20 2025] 0x000003fc0000-0x000004000000 : "ospi.phypattern"
[Wed Mar  5 18:17:21 2025] davinci_mdio 46000f00.mdio: Configuring MDIO in manual mode
[Wed Mar  5 18:17:21 2025] davinci_mdio 46000f00.mdio: davinci mdio revision 9.7, bus freq 1000000
[Wed Mar  5 18:17:21 2025] davinci_mdio 46000f00.mdio: phy[0]: device 46000f00.mdio:00, driver TI DP83867
[Wed Mar  5 18:17:21 2025] am65-cpsw-nuss 46000000.ethernet: initializing am65 cpsw nuss version 0x6BA00101, cpsw version 0x6BA80100 Ports: 2 quirks:00000000
[Wed Mar  5 18:17:21 2025] am65-cpsw-nuss 46000000.ethernet: initialized cpsw ale version 1.4
[Wed Mar  5 18:17:21 2025] am65-cpsw-nuss 46000000.ethernet: ALE Table size 64, Policers 8
[Wed Mar  5 18:17:21 2025] am65-cpsw-nuss 46000000.ethernet: CPTS ver 0x4e8a010a, freq:500000000, add_val:1 pps:0
[Wed Mar  5 18:17:21 2025] am65-cpsw-nuss 46000000.ethernet: set new flow-id-base 48
[Wed Mar  5 18:17:21 2025] mmc1: CQHCI version 5.10
[Wed Mar  5 18:17:21 2025] clk: Disabling unused clocks
[Wed Mar  5 18:17:21 2025] PM: genpd: Disabling unused power domains
[Wed Mar  5 18:17:21 2025] ALSA device list:
[Wed Mar  5 18:17:21 2025]   No soundcards found.
[Wed Mar  5 18:17:21 2025] mmc1: SDHCI controller on 4fb0000.mmc [4fb0000.mmc] using ADMA 64-bit
[Wed Mar  5 18:17:21 2025] Waiting for root device PARTUUID=076c4a2a-02...
[Wed Mar  5 18:17:21 2025] mmc1: new ultra high speed DDR50 SDHC card at address aaaa
[Wed Mar  5 18:17:21 2025] mmcblk1: mmc1:aaaa SL32G 29.7 GiB
[Wed Mar  5 18:17:21 2025]  mmcblk1: p1 p2
[Wed Mar  5 18:17:21 2025] EXT4-fs (mmcblk1p2): mounted filesystem 14ed6634-5437-4722-8e8e-18f6950870e0 r/w with ordered data mode. Quota mode: none.
[Wed Mar  5 18:17:21 2025] VFS: Mounted root (ext4 filesystem) on device 179:2.
[Wed Mar  5 18:17:21 2025] devtmpfs: mounted
[Wed Mar  5 18:17:21 2025] Freeing unused kernel memory: 2752K
[Wed Mar  5 18:17:21 2025] Run /sbin/init as init process
[Wed Mar  5 18:17:21 2025]   with arguments:
[Wed Mar  5 18:17:21 2025]     /sbin/init
[Wed Mar  5 18:17:21 2025]   with environment:
[Wed Mar  5 18:17:21 2025]     HOME=/
[Wed Mar  5 18:17:21 2025]     TERM=linux
[Wed Mar  5 18:17:21 2025]     mtdparts=47040000.spi.0:512k(ospi.tiboot3),2m(ospi.tispl),4m(ospi.u-boot),256k(ospi.env),1m(ospi.sysfw),256k(ospi.env.backup),57344k@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)
[Wed Mar  5 18:17:21 2025] systemd[1]: System time before build time, advancing clock.
[Wed Mar  5 18:17:21 2025] NET: Registered PF_INET6 protocol family
[Wed Mar  5 18:17:21 2025] Segment Routing with IPv6
[Wed Mar  5 18:17:21 2025] In-situ OAM (IOAM) with IPv6
[Wed Mar  5 18:17:21 2025] systemd[1]: systemd 255.18^ running in system mode (+PAM -AUDIT -SELINUX -APPARMOR +IMA -SMACK +SECCOMP -GCRYPT -GNUTLS -OPENSSL +ACL +BLKID -CURL -ELFUTILS -FIDO2 -IDN2 -IDN -IPTC +KMOD -LIBCRYPTSETUP +LIBFDISK -PCRE2 -PWQUALITY -P11KIT -QRENCODE -TPM2 -BZIP2 -LZ4 -XZ -ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
[Wed Mar  5 18:17:21 2025] systemd[1]: Detected architecture arm64.
[Wed Mar  5 18:17:22 2025] systemd[1]: Hostname set to <tda4vm-sk>.
[Wed Mar  5 18:17:22 2025] systemd-sysv-generator[98]: SysV service '/etc/init.d/edgeai-launcher.sh' lacks a native systemd unit file, automatically generating a unit file for compatibility.
[Wed Mar  5 18:17:22 2025] systemd-sysv-generator[98]: Please update package to include a native systemd unit file.
[Wed Mar  5 18:17:22 2025] systemd-sysv-generator[98]: ! This compatibility logic is deprecated, expect removal soon. !
[Wed Mar  5 18:17:22 2025] systemd[1]: /usr/lib/systemd/system/bt-enable.service:9: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
[Wed Mar  5 18:17:22 2025] systemd[1]: Queued start job for default target Graphical Interface.
[Wed Mar  5 18:17:22 2025] systemd[1]: Created slice Slice /system/getty.
[Wed Mar  5 18:17:22 2025] systemd[1]: Created slice Slice /system/modprobe.
[Wed Mar  5 18:17:22 2025] systemd[1]: Created slice Slice /system/serial-getty.
[Wed Mar  5 18:17:22 2025] systemd[1]: Created slice User and Session Slice.
[Wed Mar  5 18:17:22 2025] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[Wed Mar  5 18:17:22 2025] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[Wed Mar  5 18:17:22 2025] systemd[1]: Expecting device /dev/ttyS2...
[Wed Mar  5 18:17:22 2025] systemd[1]: Reached target Path Units.
[Wed Mar  5 18:17:22 2025] systemd[1]: Reached target Remote File Systems.
[Wed Mar  5 18:17:22 2025] systemd[1]: Reached target Slice Units.
[Wed Mar  5 18:17:22 2025] systemd[1]: Reached target Swaps.
[Wed Mar  5 18:17:22 2025] systemd[1]: Listening on RPCbind Server Activation Socket.
[Wed Mar  5 18:17:22 2025] systemd[1]: Reached target RPC Port Mapper.
[Wed Mar  5 18:17:22 2025] systemd[1]: Listening on Process Core Dump Socket.
[Wed Mar  5 18:17:22 2025] systemd[1]: Listening on initctl Compatibility Named Pipe.
[Wed Mar  5 18:17:22 2025] systemd[1]: Listening on Journal Audit Socket.
[Wed Mar  5 18:17:22 2025] systemd[1]: Listening on Journal Socket (/dev/log).
[Wed Mar  5 18:17:22 2025] systemd[1]: Listening on Journal Socket.
[Wed Mar  5 18:17:22 2025] systemd[1]: Listening on Network Service Netlink Socket.
[Wed Mar  5 18:17:22 2025] systemd[1]: Listening on udev Control Socket.
[Wed Mar  5 18:17:22 2025] systemd[1]: Listening on udev Kernel Socket.
[Wed Mar  5 18:17:22 2025] systemd[1]: Listening on User Database Manager Socket.
[Wed Mar  5 18:17:22 2025] systemd[1]: Mounting Huge Pages File System...
[Wed Mar  5 18:17:22 2025] systemd[1]: Mounting POSIX Message Queue File System...
[Wed Mar  5 18:17:22 2025] systemd[1]: Mounting Kernel Debug File System...
[Wed Mar  5 18:17:22 2025] systemd[1]: Kernel Trace File System was skipped because of an unmet condition check (ConditionPathExists=/sys/kernel/tracing).
[Wed Mar  5 18:17:22 2025] systemd[1]: Mounting Temporary Directory /tmp...
[Wed Mar  5 18:17:22 2025] systemd[1]: Starting Create List of Static Device Nodes...
[Wed Mar  5 18:17:22 2025] systemd[1]: Starting Load Kernel Module configfs...
[Wed Mar  5 18:17:23 2025] systemd[1]: Starting Load Kernel Module drm...
[Wed Mar  5 18:17:23 2025] systemd[1]: Starting Load Kernel Module fuse...
[Wed Mar  5 18:17:23 2025] systemd[1]: Starting Start psplash boot splash screen...
[Wed Mar  5 18:17:23 2025] fuse: init (API version 7.41)
[Wed Mar  5 18:17:23 2025] systemd[1]: Starting RPC Bind...
[Wed Mar  5 18:17:23 2025] systemd[1]: File System Check on Root Device was skipped because of an unmet condition check (ConditionPathIsReadWrite=!/).
[Wed Mar  5 18:17:23 2025] systemd[1]: Starting Journal Service...
[Wed Mar  5 18:17:23 2025] systemd[1]: Starting Load Kernel Modules...
[Wed Mar  5 18:17:23 2025] systemd[1]: Starting Generate network units from Kernel command line...
[Wed Mar  5 18:17:23 2025] systemd-journald[116]: Collecting audit messages is enabled.
[Wed Mar  5 18:17:23 2025] cryptodev: loading out-of-tree module taints kernel.
[Wed Mar  5 18:17:23 2025] sysctl table check failed: ioctl/(null) procname is null
[Wed Mar  5 18:17:23 2025] sysctl table check failed: ioctl/(null) No proc_handler
[Wed Mar  5 18:17:23 2025] cryptodev: driver 1.14 loaded.
[Wed Mar  5 18:17:23 2025] systemd[1]: Starting Remount Root and Kernel File Systems...
[Wed Mar  5 18:17:23 2025] systemd[1]: Starting Coldplug All udev Devices...
[Wed Mar  5 18:17:23 2025] systemd[1]: Started RPC Bind.
[Wed Mar  5 18:17:23 2025] EXT4-fs (mmcblk1p2): re-mounted 14ed6634-5437-4722-8e8e-18f6950870e0 r/w. Quota mode: none.
[Wed Mar  5 18:17:23 2025] systemd[1]: Started Journal Service.
[Wed Mar  5 18:17:23 2025] systemd-journald[116]: Received client request to flush runtime journal.
[Wed Mar  5 18:17:23 2025] audit: type=1334 audit(1741187611.004:2): prog-id=6 op=LOAD
[Wed Mar  5 18:17:23 2025] audit: type=1334 audit(1741187611.012:3): prog-id=7 op=LOAD
[Wed Mar  5 18:17:24 2025] audit: type=1334 audit(1741187611.164:4): prog-id=8 op=LOAD
[Wed Mar  5 18:17:24 2025] audit: type=1334 audit(1741187611.192:5): prog-id=9 op=LOAD
[Wed Mar  5 18:17:24 2025] audit: type=1334 audit(1741187611.232:6): prog-id=10 op=LOAD
[Wed Mar  5 18:17:24 2025] audit: type=1334 audit(1741187611.244:7): prog-id=11 op=LOAD
[Wed Mar  5 18:17:24 2025] audit: type=1334 audit(1741187611.248:8): prog-id=12 op=LOAD
[Wed Mar  5 18:17:24 2025] audit: type=1334 audit(1741198644.432:9): prog-id=13 op=LOAD
[Wed Mar  5 18:17:25 2025] audit: type=1334 audit(1741198644.960:10): prog-id=14 op=LOAD
[Wed Mar  5 18:17:25 2025] audit: type=1334 audit(1741198644.980:11): prog-id=15 op=LOAD
[Wed Mar  5 18:17:25 2025] CAN device driver interface
[Wed Mar  5 18:17:25 2025] omap_rng 4e10000.rng: Random Number Generator ver. 241b34c
[Wed Mar  5 18:17:25 2025] mc: Linux media interface: v0.10
[Wed Mar  5 18:17:25 2025] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[Wed Mar  5 18:17:25 2025] PVR_K:  185: Device: 4e20000000.gpu
[Wed Mar  5 18:17:25 2025] videodev: Linux video capture interface: v2.00
[Wed Mar  5 18:17:25 2025] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[Wed Mar  5 18:17:25 2025] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[Wed Mar  5 18:17:25 2025] Bluetooth: Core ver 2.22
[Wed Mar  5 18:17:25 2025] NET: Registered PF_BLUETOOTH protocol family
[Wed Mar  5 18:17:25 2025] cdns-mhdp8546 a000000.dp-bridge: error -EINVAL: invalid resource (null)
[Wed Mar  5 18:17:25 2025] Bluetooth: HCI device and connection manager initialized
[Wed Mar  5 18:17:25 2025] Bluetooth: HCI socket layer initialized
[Wed Mar  5 18:17:25 2025] Bluetooth: L2CAP socket layer initialized
[Wed Mar  5 18:17:25 2025] Bluetooth: SCO socket layer initialized
[Wed Mar  5 18:17:25 2025] cdns-mhdp8546 a000000.dp-bridge: Failed to get SAPB memory resource, HDCP not supported
[Wed Mar  5 18:17:25 2025] PVR_K:  185: Read BVNC 22.104.208.318 from HW device registers
[Wed Mar  5 18:17:25 2025] PVR_K:  185: RGX Device registered with BVNC 22.104.208.318
[Wed Mar  5 18:17:25 2025] [drm] Initialized pvr 24.2.6643903 for 4e20000000.gpu on minor 0
[Wed Mar  5 18:17:25 2025] at24 0-0051: supply vcc not found, using dummy regulator
[Wed Mar  5 18:17:25 2025] at24 0-0051: 65536 byte 24c512 EEPROM, writable, 1 bytes/write
[Wed Mar  5 18:17:25 2025] img_enc 4200000.video-encoder: vxe_enc_probe: using heap 1 for internal alloc
[Wed Mar  5 18:17:26 2025] am65-cpsw-nuss 46000000.ethernet eth0: PHY [46000f00.mdio:00] driver [TI DP83867] (irq=POLL)
[Wed Mar  5 18:17:26 2025] img_enc 4200000.video-encoder: encoder registered as /dev/video1
[Wed Mar  5 18:17:26 2025] am65-cpsw-nuss 46000000.ethernet eth0: configuring for phy/rgmii-rxid link mode
[Wed Mar  5 18:17:26 2025] k3_r5_rproc bus@100000:bus@28380000:r5fss@41000000: k3_r5_cluster_rproc_init failed, ret = -517
[Wed Mar  5 18:17:26 2025] img_dec 4300000.video-decoder: decoder registered as /dev/video0
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc0: releasing 41000000.r5f
[Wed Mar  5 18:17:26 2025] omap-mailbox 31f80000.mailbox: omap mailbox rev 0x66fc7100
[Wed Mar  5 18:17:26 2025] platform 41000000.r5f: R5F core may have been powered on by a different host, programmed state (0) != actual state (1)
[Wed Mar  5 18:17:26 2025] k3_r5_rproc bus@100000:r5fss@5c00000: k3_r5_cluster_rproc_init failed, ret = -517
[Wed Mar  5 18:17:26 2025] platform 41000000.r5f: configured R5F for IPC-only mode
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc1: releasing 5c00000.r5f
[Wed Mar  5 18:17:26 2025] platform 41000000.r5f: assigned reserved memory node vision-apps-r5f-dma-memory@a0000000
[Wed Mar  5 18:17:26 2025] omap-mailbox 31f81000.mailbox: omap mailbox rev 0x66fc7100
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc0: 41000000.r5f is available
[Wed Mar  5 18:17:26 2025] omap-mailbox 31f82000.mailbox: omap mailbox rev 0x66fc7100
[Wed Mar  5 18:17:26 2025] omap-mailbox 31f83000.mailbox: omap mailbox rev 0x66fc7100
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc0: attaching to 41000000.r5f
[Wed Mar  5 18:17:26 2025] omap-mailbox 31f84000.mailbox: omap mailbox rev 0x66fc7100
[Wed Mar  5 18:17:26 2025] rproc-virtio rproc-virtio.11.auto: assigned reserved memory node vision-apps-r5f-dma-memory@a0000000
[Wed Mar  5 18:17:26 2025] virtio_rpmsg_bus virtio0: rpmsg host is online
[Wed Mar  5 18:17:26 2025] rproc-virtio rproc-virtio.11.auto: registered virtio0 (type 7)
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc0: remote processor 41000000.r5f is now attached
[Wed Mar  5 18:17:26 2025] virtio_rpmsg_bus virtio0: creating channel ti.ipc4.ping-pong addr 0xd
[Wed Mar  5 18:17:26 2025] platform 5e00000.r5f: configured R5F for remoteproc mode
[Wed Mar  5 18:17:26 2025] virtio_rpmsg_bus virtio0: creating channel rpmsg_chrdev addr 0xe
[Wed Mar  5 18:17:26 2025] platform 5e00000.r5f: assigned reserved memory node vision-apps-r5f-dma-memory@a6000000
[Wed Mar  5 18:17:26 2025] platform 41400000.r5f: configured R5F for remoteproc mode
[Wed Mar  5 18:17:26 2025] platform 41400000.r5f: assigned reserved memory node vision-apps-r5f-dma-memory@a1000000
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc1: 5e00000.r5f is available
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc2: 41400000.r5f is available
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc1: Direct firmware load for j7-main-r5f1_0-fw failed with error -2
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc2: Direct firmware load for j7-mcu-r5f0_1-fw failed with error -2
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc1: powering up 5e00000.r5f
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc2: powering up 41400000.r5f
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc1: Direct firmware load for j7-main-r5f1_0-fw failed with error -2
[Wed Mar  5 18:17:26 2025] k3-dsp-rproc 4d80800000.dsp: assigned reserved memory node vision-apps-c66-dma-memory@a9000000
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc1: request_firmware failed: -2
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc2: Direct firmware load for j7-mcu-r5f0_1-fw failed with error -2
[Wed Mar  5 18:17:26 2025] k3-dsp-rproc 4d80800000.dsp: configured DSP for IPC-only mode
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc2: request_firmware failed: -2
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc3: 4d80800000.dsp is available
[Wed Mar  5 18:17:26 2025] platform 5f00000.r5f: configured R5F for remoteproc mode
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc3: attaching to 4d80800000.dsp
[Wed Mar  5 18:17:26 2025] rproc-virtio rproc-virtio.12.auto: assigned reserved memory node vision-apps-c66-dma-memory@a9000000
[Wed Mar  5 18:17:26 2025] platform 5f00000.r5f: assigned reserved memory node vision-apps-r5f-dma-memory@a7000000
[Wed Mar  5 18:17:26 2025] virtio_rpmsg_bus virtio1: rpmsg host is online
[Wed Mar  5 18:17:26 2025] virtio_rpmsg_bus virtio1: creating channel rpmsg_chrdev addr 0xd
[Wed Mar  5 18:17:26 2025] rproc-virtio rproc-virtio.12.auto: registered virtio1 (type 7)
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc3: remote processor 4d80800000.dsp is now attached
[Wed Mar  5 18:17:26 2025] k3-dsp-rproc 4d81800000.dsp: assigned reserved memory node vision-apps-c66-dma-memory@a8000000
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc4: 5f00000.r5f is available
[Wed Mar  5 18:17:26 2025] k3-dsp-rproc 4d81800000.dsp: configured DSP for IPC-only mode
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc4: Direct firmware load for j7-main-r5f1_1-fw failed with error -2
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc5: 4d81800000.dsp is available
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc4: powering up 5f00000.r5f
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc5: attaching to 4d81800000.dsp
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc4: Direct firmware load for j7-main-r5f1_1-fw failed with error -2
[Wed Mar  5 18:17:26 2025] rproc-virtio rproc-virtio.13.auto: assigned reserved memory node vision-apps-c66-dma-memory@a8000000
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc4: request_firmware failed: -2
[Wed Mar  5 18:17:26 2025] virtio_rpmsg_bus virtio2: rpmsg host is online
[Wed Mar  5 18:17:26 2025] virtio_rpmsg_bus virtio2: creating channel rpmsg_chrdev addr 0xd
[Wed Mar  5 18:17:26 2025] rproc-virtio rproc-virtio.13.auto: registered virtio2 (type 7)
[Wed Mar  5 18:17:26 2025] gpio-mux mux-controller: 2-way mux-controller registered
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc5: remote processor 4d81800000.dsp is now attached
[Wed Mar  5 18:17:26 2025] k3-dsp-rproc 64800000.dsp: assigned reserved memory node vision-apps-c71-dma-memory@b2000000
[Wed Mar  5 18:17:26 2025] k3-dsp-rproc 64800000.dsp: configured DSP for IPC-only mode
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc6: 64800000.dsp is available
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc6: attaching to 64800000.dsp
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc6: unsupported resource 65538
[Wed Mar  5 18:17:26 2025] rproc-virtio rproc-virtio.14.auto: assigned reserved memory node vision-apps-c71-dma-memory@b2000000
[Wed Mar  5 18:17:26 2025] virtio_rpmsg_bus virtio3: rpmsg host is online
[Wed Mar  5 18:17:26 2025] virtio_rpmsg_bus virtio3: creating channel rpmsg_chrdev addr 0xd
[Wed Mar  5 18:17:26 2025] rproc-virtio rproc-virtio.14.auto: registered virtio3 (type 7)
[Wed Mar  5 18:17:26 2025] remoteproc remoteproc6: remote processor 64800000.dsp is now attached
[Wed Mar  5 18:17:26 2025] m_can_platform 40528000.can: m_can device registered (irq=829, version=32)
[Wed Mar  5 18:17:26 2025] m_can_platform 2701000.can: m_can device registered (irq=830, version=32)
[Wed Mar  5 18:17:26 2025] m_can_platform 2751000.can: m_can device registered (irq=831, version=32)
[Wed Mar  5 18:17:26 2025] m_can_platform 2791000.can: m_can device registered (irq=832, version=32)
[Wed Mar  5 18:17:27 2025] [drm] Initialized tidss 1.0.0 for 4a00000.dss on minor 1
[Wed Mar  5 18:17:27 2025] Console: switching to colour frame buffer device 240x67
[Wed Mar  5 18:17:27 2025] remoteproc remoteproc7: b034000.pru is available
[Wed Mar  5 18:17:27 2025] remoteproc remoteproc8: b004000.rtu is available
[Wed Mar  5 18:17:27 2025] tidss 4a00000.dss: [drm] fb0: tidssdrmfb frame buffer device
[Wed Mar  5 18:17:27 2025] remoteproc remoteproc9: b00a000.txpru is available
[Wed Mar  5 18:17:27 2025] remoteproc remoteproc10: b038000.pru is available
[Wed Mar  5 18:17:27 2025] remoteproc remoteproc11: b006000.rtu is available
[Wed Mar  5 18:17:27 2025] remoteproc remoteproc12: b00c000.txpru is available
[Wed Mar  5 18:17:27 2025] platform 5c00000.r5f: configured R5F for IPC-only mode
[Wed Mar  5 18:17:27 2025] remoteproc remoteproc14: b134000.pru is available
[Wed Mar  5 18:17:27 2025] platform 5c00000.r5f: assigned reserved memory node vision-apps-r5f-dma-memory@a2000000
[Wed Mar  5 18:17:27 2025] remoteproc remoteproc15: b104000.rtu is available
[Wed Mar  5 18:17:27 2025] remoteproc remoteproc13: 5c00000.r5f is available
[Wed Mar  5 18:17:27 2025] remoteproc remoteproc13: attaching to 5c00000.r5f
[Wed Mar  5 18:17:27 2025] remoteproc remoteproc16: b10a000.txpru is available
[Wed Mar  5 18:17:27 2025] rproc-virtio rproc-virtio.15.auto: assigned reserved memory node vision-apps-r5f-dma-memory@a2000000
[Wed Mar  5 18:17:27 2025] remoteproc remoteproc17: b138000.pru is available
[Wed Mar  5 18:17:27 2025] virtio_rpmsg_bus virtio4: rpmsg host is online
[Wed Mar  5 18:17:27 2025] virtio_rpmsg_bus virtio4: creating channel rpmsg_chrdev addr 0xd
[Wed Mar  5 18:17:27 2025] rproc-virtio rproc-virtio.15.auto: registered virtio4 (type 7)
[Wed Mar  5 18:17:27 2025] remoteproc remoteproc18: b106000.rtu is available
[Wed Mar  5 18:17:27 2025] remoteproc remoteproc19: b10c000.txpru is available
[Wed Mar  5 18:17:27 2025] remoteproc remoteproc13: remote processor 5c00000.r5f is now attached
[Wed Mar  5 18:17:27 2025] platform 5d00000.r5f: configured R5F for IPC-only mode
[Wed Mar  5 18:17:27 2025] platform 5d00000.r5f: assigned reserved memory node vision-apps-r5f-dma-memory@a4000000
[Wed Mar  5 18:17:27 2025] remoteproc remoteproc20: 5d00000.r5f is available
[Wed Mar  5 18:17:27 2025] remoteproc remoteproc20: attaching to 5d00000.r5f
[Wed Mar  5 18:17:27 2025] rproc-virtio rproc-virtio.16.auto: assigned reserved memory node vision-apps-r5f-dma-memory@a4000000
[Wed Mar  5 18:17:27 2025] virtio_rpmsg_bus virtio5: rpmsg host is online
[Wed Mar  5 18:17:27 2025] virtio_rpmsg_bus virtio5: creating channel rpmsg_chrdev addr 0xd
[Wed Mar  5 18:17:27 2025] rproc-virtio rproc-virtio.16.auto: registered virtio5 (type 7)
[Wed Mar  5 18:17:27 2025] virtio_rpmsg_bus virtio5: creating channel rpmsg_chrdev addr 0x15
[Wed Mar  5 18:17:27 2025] virtio_rpmsg_bus virtio5: creating channel ti.ipc4.ping-pong addr 0xe
[Wed Mar  5 18:17:27 2025] remoteproc remoteproc20: remote processor 5d00000.r5f is now attached
[Wed Mar  5 18:17:27 2025] virtio_rpmsg_bus virtio3: creating channel rpmsg_chrdev addr 0x15
[Wed Mar  5 18:17:27 2025] virtio_rpmsg_bus virtio3: creating channel ti.ipc4.ping-pong addr 0xe
[Wed Mar  5 18:17:27 2025] virtio_rpmsg_bus virtio1: creating channel rpmsg_chrdev addr 0x15
[Wed Mar  5 18:17:27 2025] virtio_rpmsg_bus virtio1: creating channel ti.ipc4.ping-pong addr 0xe
[Wed Mar  5 18:17:27 2025] virtio_rpmsg_bus virtio2: creating channel rpmsg_chrdev addr 0x15
[Wed Mar  5 18:17:27 2025] virtio_rpmsg_bus virtio2: creating channel ti.ipc4.ping-pong addr 0xe
[Wed Mar  5 18:17:27 2025] virtio_rpmsg_bus virtio4: creating channel rpmsg_chrdev addr 0x15
[Wed Mar  5 18:17:27 2025] virtio_rpmsg_bus virtio4: creating channel ti.ipc4.ping-pong addr 0xe
[Wed Mar  5 18:17:27 2025] m_can_platform 40528000.can mcu_mcan0: renamed from can0
[Wed Mar  5 18:17:27 2025] m_can_platform 2751000.can main_mcan5: renamed from can2
[Wed Mar  5 18:17:27 2025] m_can_platform 2701000.can main_mcan0: renamed from can1
[Wed Mar  5 18:17:27 2025] m_can_platform 2791000.can main_mcan9: renamed from can3
[Wed Mar  5 18:17:27 2025] xhci-hcd xhci-hcd.17.auto: xHCI Host Controller
[Wed Mar  5 18:17:27 2025] xhci-hcd xhci-hcd.17.auto: new USB bus registered, assigned bus number 1
[Wed Mar  5 18:17:27 2025] xhci-hcd xhci-hcd.17.auto: hcc params 0x200073c9 hci version 0x100 quirks 0x0000002000008010
[Wed Mar  5 18:17:27 2025] xhci-hcd xhci-hcd.17.auto: irq 853, io mem 0x06410000
[Wed Mar  5 18:17:27 2025] xhci-hcd xhci-hcd.17.auto: xHCI Host Controller
[Wed Mar  5 18:17:27 2025] xhci-hcd xhci-hcd.17.auto: new USB bus registered, assigned bus number 2
[Wed Mar  5 18:17:27 2025] xhci-hcd xhci-hcd.17.auto: Host supports USB 3.0 SuperSpeed
[Wed Mar  5 18:17:27 2025] hub 1-0:1.0: USB hub found
[Wed Mar  5 18:17:27 2025] hub 1-0:1.0: 1 port detected
[Wed Mar  5 18:17:28 2025] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[Wed Mar  5 18:17:28 2025] hub 2-0:1.0: USB hub found
[Wed Mar  5 18:17:28 2025] hub 2-0:1.0: 1 port detected
[Wed Mar  5 18:17:28 2025] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[Wed Mar  5 18:17:28 2025] hub 1-1:1.0: USB hub found
[Wed Mar  5 18:17:28 2025] hub 1-1:1.0: 4 ports detected
[Wed Mar  5 18:17:28 2025] usbcore: registered new device driver onboard-usb-dev
[Wed Mar  5 18:17:28 2025] usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd
[Wed Mar  5 18:17:28 2025] hub 2-1:1.0: USB hub found
[Wed Mar  5 18:17:28 2025] hub 2-1:1.0: 4 ports detected
[Wed Mar  5 18:17:38 2025] kauditd_printk_skb: 2 callbacks suppressed
[Wed Mar  5 18:17:38 2025] audit: type=1006 audit(1741198658.400:14): pid=1167 uid=0 subj=kernel old-auid=4294967295 auid=0 tty=(none) old-ses=4294967295 ses=1 res=1
[Wed Mar  5 18:17:38 2025] audit: type=1300 audit(1741198658.400:14): arch=c00000b7 syscall=64 success=yes exit=1 a0=8 a1=ffffc6be9ca8 a2=1 a3=1 items=0 ppid=1 pid=1167 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=1 comm="(systemd)" exe="/usr/lib/systemd/systemd-executor" subj=kernel key=(null)
[Wed Mar  5 18:17:38 2025] audit: type=1327 audit(1741198658.400:14): proctitle="(systemd)"
[Wed Mar  5 18:17:38 2025] audit: type=1334 audit(1741198658.484:15): prog-id=18 op=LOAD
[Wed Mar  5 18:17:38 2025] audit: type=1300 audit(1741198658.484:15): arch=c00000b7 syscall=280 success=yes exit=8 a0=5 a1=ffffc7194c18 a2=90 a3=0 items=0 ppid=1 pid=1167 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=1 comm="systemd" exe="/usr/lib/systemd/systemd" subj=kernel key=(null)
[Wed Mar  5 18:17:38 2025] audit: type=1327 audit(1741198658.484:15): proctitle="(systemd)"
[Wed Mar  5 18:17:38 2025] audit: type=1334 audit(1741198658.484:16): prog-id=18 op=UNLOAD
[Wed Mar  5 18:17:38 2025] audit: type=1300 audit(1741198658.484:16): arch=c00000b7 syscall=57 success=yes exit=0 a0=8 a1=1 a2=0 a3=ffffbba26c60 items=0 ppid=1 pid=1167 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=1 comm="systemd" exe="/usr/lib/systemd/systemd" subj=kernel key=(null)
[Wed Mar  5 18:17:38 2025] audit: type=1327 audit(1741198658.484:16): proctitle="(systemd)"
[Wed Mar  5 18:17:38 2025] audit: type=1334 audit(1741198658.484:17): prog-id=19 op=LOAD

Here are some additional information, you may need them to solve the problem.

On the snippet, I showed you i2c mapping on different ports, and on the file, I send you the bootlog of the board.

Regards,
Elchin

0 Elchin Aslanli 8 months ago in reply to Elchin Aslanli

Prodigy 10 points

Takuma Fujiwara said:
Can you do an i2cdetect on all the busses to see if there is any bus that has the 8 different I2C addresses populated? In parallel, I will try to find a revision B board in office.

Here is the snippet of all i2c busses

root@tda4vm-sk:/opt/edgeai-gst-apps# for bus in $(seq 0 9); do     echo "====== Scanning I2C bus $bus ======";     i2cdetect -y $bus;     echo ""; done
====== Scanning I2C bus 0 ======
Warning: Can't use SMBus Quick Write command, will skip some addresses
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                                                 
10:                                                 
20:                                                 
30: -- -- -- -- -- -- -- --                         
40:                                                 
50: -- UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60:                                                 
70:                                                 

====== Scanning I2C bus 1 ======
Warning: Can't use SMBus Quick Write command, will skip some addresses
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                                                 
10:                                                 
20:                                                 
30: -- -- -- -- -- -- -- --                         
40:                                                 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60:                                                 
70:                                                 

====== Scanning I2C bus 2 ======
Warning: Can't use SMBus Quick Write command, will skip some addresses
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                                                 
10:                                                 
20:                                                 
30: -- -- -- -- -- -- -- --                         
40:                                                 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60:                                                 
70:                                                 

====== Scanning I2C bus 3 ======
Warning: Can't use SMBus Quick Write command, will skip some addresses
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                                                 
10:                                                 
20:                                                 
30: -- -- -- -- -- -- -- --                         
40:                                                 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60:                                                 
70:                                                 

====== Scanning I2C bus 4 ======
Warning: Can't use SMBus Quick Write command, will skip some addresses
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                                                 
10:                                                 
20:                                                 
30: 30 -- -- -- -- -- -- 37                         
40:                                                 
50: 50 -- -- -- 54 -- -- -- -- -- -- -- -- -- -- -- 
60:                                                 
70:                                                 

====== Scanning I2C bus 5 ======
Warning: Can't use SMBus Quick Write command, will skip some addresses
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                                                 
10:                                                 
20:                                                 
30: -- -- -- -- -- -- -- --                         
40:                                                 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60:                                                 
70:                                                 

====== Scanning I2C bus 6 ======
Warning: Can't use SMBus Quick Write command, will skip some addresses
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                                                 
10:                                                 
20:                                                 
30: -- -- -- -- -- -- -- --                         
40:                                                 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60:                                                 
70:                                                 

====== Scanning I2C bus 7 ======
Warning: Can't use SMBus Quick Write command, will skip some addresses
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                                                 
10:                                                 
20:                                                 
30: -- -- -- -- -- -- -- --                         
40:                                                 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60:                                                 
70:                                                 

====== Scanning I2C bus 8 ======
Warning: Can't use SMBus Quick Write command, will skip some addresses
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                                                 
10:                                                 
20:                                                 
30: -- -- -- -- -- -- -- --                         
40:                                                 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60:                                                 
70:                                                 

====== Scanning I2C bus 9 ======
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --

0 Takuma Fujiwara 8 months ago in reply to Elchin Aslanli

TI__Guru 57023 points

Hi Elchin,

Can you include the -r option for the i2cdetect command and re-run?

Regards,

Takuma

0 Elchin Aslanli 8 months ago in reply to Takuma Fujiwara

Prodigy 10 points

for bus in $(seq 0 9); do
>     echo "====== Scanning I2C bus $bus ======"
>     i2cdetect -y -r $bus
>     echo ""
> done
====== Scanning I2C bus 0 ======
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- 13 -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- UU 49 4a 4b UU 4d 4e 4f 
50: -- UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         

====== Scanning I2C bus 1 ======
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- 21 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- UU -- -- -- -- -- --                         

====== Scanning I2C bus 2 ======
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- 21 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- UU -- -- -- -- -- --                         

====== Scanning I2C bus 3 ======
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- 21 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- UU -- -- -- -- -- --                         

====== Scanning I2C bus 4 ======
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: 30 -- -- -- -- -- -- 37 -- -- 3a -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: 50 -- -- -- 54 -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         

====== Scanning I2C bus 5 ======
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: UU -- -- -- -- -- -- --                         

====== Scanning I2C bus 6 ======
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: UU -- -- -- -- -- -- --                         

====== Scanning I2C bus 7 ======
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: UU -- -- -- -- -- -- --                         

====== Scanning I2C bus 8 ======
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         

====== Scanning I2C bus 9 ======
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --

Hi Takuma,

Here is the result with -r option,

Thanks

0 Takuma Fujiwara 8 months ago in reply to Elchin Aslanli

TI__Guru 57023 points

Hi Elchin,

Could you try running below script and then running the demos?

https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/sk_5F00_pmic_5F00_reboot_5F00_fix_5F00_bus0.sh

Regards,

Takuma

0 Elchin Aslanli 8 months ago in reply to Takuma Fujiwara

Prodigy 10 points

root@tda4vm-sk:/opt/edgeai-gst-apps# ./sk_pmic_reboot_fix_bus0.sh 
Error: Could not set address to 0x48: Device or resource busy
PMIC A register value failed to change
Error: Could not set address to 0x48: Device or resource busy
PMIC A register value failed to change
Error: Could not set address to 0x48: Device or resource busy
PMIC A register value failed to change
Error: Could not set address to 0x4c: Device or resource busy
PMIC B register value failed to change
Error: Could not set address to 0x4c: Device or resource busy
PMIC B register value failed to change
Error: Could not set address to 0x4c: Device or resource busy
PMIC B register value failed to change
PMIC registers successfully updated!
root@tda4vm-sk:/opt/edgeai-gst-apps#

This is the output of the given sh file.

Seems like the problem is solved, it does not reset itself at 94 degree right now.

After this modification, It is fluctuating around 102 degrees. I also encapsulated it to reach maximum degree, and at that time it reset at 114 degree. Are these measurements normal?

Thanks,
Elchin

0 Takuma Fujiwara 8 months ago in reply to Elchin Aslanli

TI__Guru 57023 points

Hi Elchin,

In theory, the TDA4VM can go up to 125C degrees. In software, we have some mechanism enabled to trigger a reset when it reaches around 123~124C.

Although, 114C is a bit high. I have only seen these values when we have a ThermoStream setup in the lab to intentionally heat up the SoC.

On the other hand, 102C degrees would be something I have seen when there is a lot of activity on the board. And I think I mentioned before, but 80~90C degrees would be what I see when running demos.

Thermally, I believe SK-TDA4VM is a board that can have improvements in design. As an example, there is a community board called BeagleBoneAI64 that has a TDA4VM SoC, but one side of the board is all one large heat sink: https://www.beagleboard.org/boards/beaglebone-ai-64

Regards,

Takuma

Processors

Processors forum

SK-TDA4VM: Overheating problem