• State Resolved
  • Locked Locked
  • Replies 14 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 648 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA4VEN-Q1: Displaying IMX219 Camera Footage in TDA4VEN (Linux + RTOS) Environment

Masao Takayama
Prodigy 245 points

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

We are attempting to display footage obtained from the IMX219 (Raspberry Pi Camera Module 2) on a display in a TDA4VEN (Linux + RTOS) environment.

Hardware Connection Status:

The camera is connected to CSI#0.
Connection configuration: TDA4VEN ↔ HBV-RPI-300FPC ↔ Raspberry Pi Camera Module 2.
Software Environment:

Built on a pre-installed full SDK environment located at /opt/ti-processor-sdk-rtos-j722s-evm-11_01_00_04/ with SD boot.
In the above setup, we have configured uEnv.txt with:

name_overlays=ti/k3-j722s-evm-csi2-quad-rpi-cam-imx219.dtbo
and booted the system.

In this state, we have tried running i2cdetect -y * on all buses, but the I2C address 0x10 for the IMX219 does not appear.

In the Supported Image Sensors PSDK Linux/QNX + RTOS documentation, the IMX219 is listed as unsupported. Could this be related to the issue we are experiencing?


[Supplement]

media-ctl -p
Media controller API version 6.12.35

Media device information
------------------------
driver          j721e-csi2rx
model           TI-CSI2RX
serial          
bus info        platform:30102000.ticsi2rx
hw revision     0x1
driver version  6.12.35

Device topology
- entity 1: 30102000.ticsi2rx (7 pads, 7 links, 1 route)
            type V4L2 subdev subtype Unknown flags 0
            device node name /dev/v4l-subdev0
        routes:
                0/0 -> 1/0 [ACTIVE]
        pad0: SINK
                [stream:0 fmt:UYVY8_1X16/640x480 field:none colorspace:srgb xfer:srgb ycbcr:601 quantization:lim-range]
                <- "cdns_csi2rx.30101000.csi-bridge":1 [ENABLED,IMMUTABLE]
        pad1: SOURCE
                [stream:0 fmt:UYVY8_1X16/640x480 field:none colorspace:srgb xfer:srgb ycbcr:601 quantization:lim-range]
                -> "30102000.ticsi2rx context 0":0 [ENABLED,IMMUTABLE]
        pad2: SOURCE
                -> "30102000.ticsi2rx context 1":0 [ENABLED,IMMUTABLE]
        pad3: SOURCE
                -> "30102000.ticsi2rx context 2":0 [ENABLED,IMMUTABLE]
        pad4: SOURCE
                -> "30102000.ticsi2rx context 3":0 [ENABLED,IMMUTABLE]
        pad5: SOURCE
                -> "30102000.ticsi2rx context 4":0 [ENABLED,IMMUTABLE]
        pad6: SOURCE
                -> "30102000.ticsi2rx context 5":0 [ENABLED,IMMUTABLE]

- entity 9: cdns_csi2rx.30101000.csi-bridge (5 pads, 2 links, 1 route)
            type V4L2 subdev subtype Unknown flags 0
            device node name /dev/v4l-subdev1
        routes:
                0/0 -> 1/0 [ACTIVE]
        pad0: SINK
                [stream:0 fmt:UYVY8_1X16/640x480 field:none colorspace:srgb xfer:srgb ycbcr:601 quantization:lim-range]
                <- "imx219 5-0010":0 [ENABLED,IMMUTABLE]
        pad1: SOURCE
                [stream:0 fmt:UYVY8_1X16/640x480 field:none colorspace:srgb xfer:srgb ycbcr:601 quantization:lim-range]
                -> "30102000.ticsi2rx":0 [ENABLED,IMMUTABLE]
        pad2: SOURCE
        pad3: SOURCE
        pad4: SOURCE

- entity 15: imx219 5-0010 (1 pad, 1 link, 0 routes)
             type V4L2 subdev subtype Sensor flags 0
             device node name /dev/v4l-subdev2
        pad0: SOURCE
                [stream:0 fmt:SRGGB10_1X10/3280x2464 field:none colorspace:raw xfer:none ycbcr:601 quantization:full-range
                 crop.bounds:(8,8)/3280x2464
                 crop:(8,8)/3280x2464]
                -> "cdns_csi2rx.30101000.csi-bridge":0 [ENABLED,IMMUTABLE]

- entity 21: 30102000.ticsi2rx context 0 (1 pad, 1 link)
             type Node subtype V4L flags 0
             device node name /dev/video2
        pad0: SINK
                <- "30102000.ticsi2rx":1 [ENABLED,IMMUTABLE]

- entity 27: 30102000.ticsi2rx context 1 (1 pad, 1 link)
             type Node subtype V4L flags 0
             device node name /dev/video3
        pad0: SINK
                <- "30102000.ticsi2rx":2 [ENABLED,IMMUTABLE]

- entity 33: 30102000.ticsi2rx context 2 (1 pad, 1 link)
             type Node subtype V4L flags 0
             device node name /dev/video4
        pad0: SINK
                <- "30102000.ticsi2rx":3 [ENABLED,IMMUTABLE]

- entity 39: 30102000.ticsi2rx context 3 (1 pad, 1 link)
             type Node subtype V4L flags 0
             device node name /dev/video5
        pad0: SINK
                <- "30102000.ticsi2rx":4 [ENABLED,IMMUTABLE]

- entity 45: 30102000.ticsi2rx context 4 (1 pad, 1 link)
             type Node subtype V4L flags 0
             device node name /dev/video6
        pad0: SINK
                <- "30102000.ticsi2rx":5 [ENABLED,IMMUTABLE]

- entity 51: 30102000.ticsi2rx context 5 (1 pad, 1 link)
             type Node subtype V4L flags 0
             device node name /dev/video7
        pad0: SINK
                <- "30102000.ticsi2rx":6 [ENABLED,IMMUTABLE]



  • 0
    TI__Mastermind 25360 points

    Hi ,

    Masao Takayama said:
    name_overlays=ti/k3-j722s-evm-csi2-quad-rpi-cam-imx219.dtbo

    Do you only have this overlay enabled, and no others?

    Masao Takayama said:
    Built on a pre-installed full SDK environment located at /opt/ti-processor-sdk-rtos-j722s-evm-11_01_00_04/ with SD boot.

    Can you try removing/disabling the R5 firmwares? The default firmwares will clash with Linux over control of the I2C buses.

    A better option would be to use the tisdk-default-image instead of the tisdk-adas-image.

    Masao Takayama said:

    In this state, we have tried running i2cdetect -y * on all buses, but the I2C address 0x10 for the IMX219 does not appear.

    Can you send the outputs of running i2cdetect?

    Additionally, can you send the dmesg logs?

    Best,
    Jared

  • 0 in reply to Jared McArthur
    Prodigy 245 points

    Fullscreen 1401.uEnv.txt Download 
    # This uEnv.txt file can contain additional environment settings that you
# want to set in U-Boot at boot time.  This can be simple variables such
# as the serverip or custom variables.  The format of this file is:
#    variable=value
# NOTE: This file will be evaluated after the bootcmd is run and the
#       bootcmd must be set to load this file if it exists (this is the
#       default on all newer U-Boot images.  This also means that some
#       variables such as bootdelay cannot be changed by this file since
#       it is not evaluated until the bootcmd is run.

# Update the Linux hostname based on board_name
# The SK also requires an additional dtbo to boot. Prepend it to name_overlays depending on board_name
uenvcmd=if test "$board_name" = "am67-sk"; then ; setenv args_all $args_all systemd.hostname=am67a-sk ; fi

# Setting the right U-Boot environment variables
dorprocboot=1
name_overlays=ti/k3-j722s-evm-csi2-quad-rpi-cam-imx219.dtbo
    Fullscreen i2cdetect.log Download 
    Script started on 2025-05-29 19:17:44+00:00 [TERM="vt220" TTY="/dev/ttyS2" COLUMNS="114" LINES="34"]
root@j722s-evm:/run/media/boot-mmcblk1p1# ls -al /dev/i2c-*
crw------- 1 root root 89,  0 May 29 19:14 /dev/i2c-0
crw------- 1 root root 89,  1 May 29 19:14 /dev/i2c-1
crw------- 1 root root 89, 10 May 29 19:14 /dev/i2c-10
crw------- 1 root root 89,  2 May 29 19:14 /dev/i2c-2
crw------- 1 root root 89,  3 May 29 19:14 /dev/i2c-3
crw------- 1 root root 89,  4 May 29 19:14 /dev/i2c-4
crw------- 1 root root 89,  5 May 29 19:14 /dev/i2c-5
crw------- 1 root root 89,  6 May 29 19:14 /dev/i2c-6
crw------- 1 root root 89,  7 May 29 19:14 /dev/i2c-7
crw------- 1 root root 89,  8 May 29 19:14 /dev/i2c-8
crw------- 1 root root 89,  9 May 29 19:14 /dev/i2c-9
root@j722s-evm:/run/media/boot-mmcblk1p1# i2cdetect -y 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: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60:                                                 
70:                                                 
root@j722s-evm:/run/media/boot-mmcblk1p1# i2cdetect -y 0 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: -- 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60:                                                 
70:                                                 
root@j722s-evm:/run/media/boot-mmcblk1p1# i2cdetect -y 1 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:                                                 
root@j722s-evm:/run/media/boot-mmcblk1p1# i2cdetect -y 2 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:                                                 
root@j722s-evm:/run/media/boot-mmcblk1p1# i2cdetect -y 3 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: -- -- -- -- -- -- -- --                         
40:                                                 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60:                                                 
70:                                                 
root@j722s-evm:/run/media/boot-mmcblk1p1# i2cdetect -y 4 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:                                                 
root@j722s-evm:/run/media/boot-mmcblk1p1# i2cdetect -y 5 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:                                                 
root@j722s-evm:/run/media/boot-mmcblk1p1# i2cdetect -y 6 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:                                                 
root@j722s-evm:/run/media/boot-mmcblk1p1# i2cdetect -y 7 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:                                                 
root@j722s-evm:/run/media/boot-mmcblk1p1# i2cdetect -y 89  9
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: -- -- ^C
root@j722s-evm:/run/media/boot-mmcblk1p1# i2cdetect -y 9 10
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
root@j722s-evm:/run/media/boot-mmcblk1p1# exit
exit

Script done on 2025-05-29 19:18:25+00:00 [COMMAND_EXIT_CODE="0"]
    Fullscreen fimeware.log Download 
    Script started on 2025-05-29 19:19:51+00:00 [TERM="vt220" TTY="/dev/ttyS2" COLUMNS="114" LINES="34"]
root@j722s-evm:/run/media/boot-mmcblk1p1# cd /lib/firmware/
root@j722s-evm:/lib/firmware# tree
sh: tree: command not found
root@j722s-evm:/lib/firmware# ls -al
total 29704
drwxr-xr-x  7 root root    4096 Mar  9  2018 .
drwxr-xr-x 85 root root   69632 Mar  9  2018 ..
-rw-r--r--  1 root root    2040 Mar  9  2018 LICENCE.ibt_firmware
-rw-r--r--  1 root root    2046 Mar  9  2018 LICENCE.iwlwifi_firmware
-rw-r--r--  1 root root  707968 Mar  9  2018 bl32.bin
-rw-r--r--  1 root root 4811024 Mar  9  2018 bl32.elf
drwxr-xr-x  2 root root    4096 Mar  9  2018 cnm
-rw-r--r--  1 root root   14980 Mar  9  2018 eip29t2_2.1.0.bin
drwxr-xr-x  2 root root    4096 Mar  9  2018 intel
-rw-r--r--  1 root root  918268 Mar  9  2018 iwlwifi-3160-17.ucode
-rw-r--r--  1 root root 2448976 Mar  9  2018 iwlwifi-8000C-34.ucode
-rw-r--r--  1 root root 2428004 Mar  9  2018 iwlwifi-8000C-36.ucode
-rw-r--r--  1 root root 2440780 Mar  9  2018 iwlwifi-8265-34.ucode
-rw-r--r--  1 root root 2436632 Mar  9  2018 iwlwifi-8265-36.ucode
-rw-r--r--  1 root root 2678092 Mar  9  2018 iwlwifi-9260-th-b0-jf-b0-34.ucode
-rw-r--r--  1 root root 2521412 Mar  9  2018 iwlwifi-9260-th-b0-jf-b0-38.ucode
-rw-r--r--  1 root root 1490508 Mar  9  2018 iwlwifi-9260-th-b0-jf-b0-46.ucode
lrwxrwxrwx  1 root root      61 Mar  9  2018 j722s-c71_0-fw -> /usr/lib/firmware/vision_apps_evm/vx_app_rtos_linux_c7x_1.out
lrwxrwxrwx  1 root root      68 Mar  9  2018 j722s-c71_0-fw-sec -> /usr/lib/firmware/vision_apps_evm/vx_app_rtos_linux_c7x_1.out.signed
lrwxrwxrwx  1 root root      61 Mar  9  2018 j722s-c71_1-fw -> /usr/lib/firmware/vision_apps_evm/vx_app_rtos_linux_c7x_2.out
lrwxrwxrwx  1 root root      68 Mar  9  2018 j722s-c71_1-fw-sec -> /usr/lib/firmware/vision_apps_evm/vx_app_rtos_linux_c7x_2.out.signed
lrwxrwxrwx  1 root root      62 Mar  9  2018 j722s-main-r5f0_0-fw -> /usr/lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu2_0.out
lrwxrwxrwx  1 root root      69 Mar  9  2018 j722s-main-r5f0_0-fw-sec -> /usr/lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu2_0.out.signed
-rw-r--r--  1 root root    5980 Mar  9  2018 regulatory.db
-rw-r--r--  1 root root    1085 Mar  9  2018 regulatory.db.p7s
-rw-r--r--  1 root root  147456 Mar  9  2018 rgx.fw.36.53.104.796
-rw-r--r--  1 root root  274840 Mar  9  2018 rgx.sh.36.53.104.796
-rw-r--r--  1 root root      28 Mar  9  2018 tee-header_v2.bin
-rw-r--r--  1 root root       0 Mar  9  2018 tee-pageable_v2.bin
-rw-r--r--  1 root root  707968 Mar  9  2018 tee-pager_v2.bin
-rw-r--r--  1 root root  707968 Mar  9  2018 tee-raw.bin
-rw-r--r--  1 root root  707996 Mar  9  2018 tee.bin
-rw-r--r--  1 root root 4811024 Mar  9  2018 tee.elf
drwxr-xr-x  2 root root    4096 Mar  9  2018 ti-connectivity
drwxr-xr-x  3 root root    4096 Mar  9  2018 ti-ipc
drwxr-xr-x  2 root root    4096 May 29 19:13 vision_apps_evm
lrwxrwxrwx  1 root root      46 Mar  9  2018 wave521c_k3_codec_fw.bin -> /usr/lib/firmware/cnm/wave521c_k3_codec_fw.bin
root@j722s-evm:/lib/firmware# cd vision_apps_evm/
root@j722s-evm:/lib/firmware/vision_apps_evm# ls -al
total 46028
drwxr-xr-x 2 root root     4096 May 29 19:13 .
drwxr-xr-x 7 root root     4096 Mar  9  2018 ..
-rw-r--r-- 1 root root 11159353 Mar  9  2018 vx_app_rtos_linux_c7x_1.out.signed_bk
-rw-r--r-- 1 root root 11157672 Mar  9  2018 vx_app_rtos_linux_c7x_1.out_bk
-rw-r--r-- 1 root root 11269945 Mar  9  2018 vx_app_rtos_linux_c7x_2.out.signed_bk
-rw-r--r-- 1 root root 11268264 Mar  9  2018 vx_app_rtos_linux_c7x_2.out_bk
-rw-r--r-- 1 root root  1126960 Mar  9  2018 vx_app_rtos_linux_mcu2_0.out.signed_bk
-rw-r--r-- 1 root root  1125280 Mar  9  2018 vx_app_rtos_linux_mcu2_0.out_bk
root@j722s-evm:/lib/firmware/vision_apps_evm# exit
exit

Script done on 2025-05-29 19:20:16+00:00 [COMMAND_EXIT_CODE="0"]
    Fullscreen 5125.dmesg.log Download 
    [    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 6.12.35-ti-00948-gce4785d01a0b-dirty (oe-user@oe-host) (aarch64-oe-linux-gcc (GCC) 13.4.0, GNU ld (GNU Binutils) 2.42.0.20240723) #1 SMP PREEMPT Thu Jul 31 11:28:39 UTC 2025
[    0.000000] KASLR disabled due to lack of seed
[    0.000000] Machine model: Texas Instruments J722S EVM
[    0.000000] earlycon: ns16550a0 at MMIO32 0x0000000002800000 (options '')
[    0.000000] printk: legacy bootconsole [ns16550a0] enabled
[    0.000000] efi: UEFI not found.
[    0.000000] Reserved memory: created CMA memory pool at 0x00000009c8000000, size 896 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[    0.000000] OF: reserved mem: 0x00000009c8000000..0x00000009ffffffff (917504 KiB) map reusable linux,cma
[    0.000000] OF: reserved mem: 0x000000009e800000..0x000000009fffffff (24576 KiB) nomap non-reusable optee@9e800000
[    0.000000] OF: reserved mem: 0x0000000080000000..0x000000008007ffff (512 KiB) nomap non-reusable tfa@80000000
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a0000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node r5f-dma-memory@a0000000, compatible id shared-dma-pool
[    0.000000] OF: reserved mem: 0x00000000a0000000..0x00000000a00fffff (1024 KiB) nomap non-reusable r5f-dma-memory@a0000000
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a0100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node r5f-memory@a0100000, compatible id shared-dma-pool
[    0.000000] OF: reserved mem: 0x00000000a0100000..0x00000000a0ffffff (15360 KiB) nomap non-reusable r5f-memory@a0100000
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a1000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node mcu-r5fss-dma-memory-region@a1000000, compatible id shared-dma-pool
[    0.000000] OF: reserved mem: 0x00000000a1000000..0x00000000a10fffff (1024 KiB) nomap non-reusable mcu-r5fss-dma-memory-region@a1000000
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a1100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node mcu-r5fss-memory-region@a1100000, compatible id shared-dma-pool
[    0.000000] OF: reserved mem: 0x00000000a1100000..0x00000000a1ffffff (15360 KiB) nomap non-reusable mcu-r5fss-memory-region@a1100000
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a2000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node main-r5fss-dma-memory-region@a2000000, compatible id shared-dma-pool
[    0.000000] OF: reserved mem: 0x00000000a2000000..0x00000000a20fffff (1024 KiB) nomap non-reusable main-r5fss-dma-memory-region@a2000000
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a2100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node main-r5fss-memory-region@a2100000, compatible id shared-dma-pool
[    0.000000] OF: reserved mem: 0x00000000a2100000..0x00000000a2ffffff (15360 KiB) nomap non-reusable main-r5fss-memory-region@a2100000
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a3000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node c7x-dma-memory@a3000000, compatible id shared-dma-pool
[    0.000000] OF: reserved mem: 0x00000000a3000000..0x00000000a30fffff (1024 KiB) nomap non-reusable c7x-dma-memory@a3000000
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a3100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node c7x-memory@a3100000, compatible id shared-dma-pool
[    0.000000] OF: reserved mem: 0x00000000a3100000..0x00000000a3ffffff (15360 KiB) nomap non-reusable c7x-memory@a3100000
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a4000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node c7x-dma-memory@a4000000, compatible id shared-dma-pool
[    0.000000] OF: reserved mem: 0x00000000a4000000..0x00000000a40fffff (1024 KiB) nomap non-reusable c7x-dma-memory@a4000000
[    0.000000] Reserved memory: created DMA memory pool at 0x00000000a4100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node c7x-memory@a4100000, compatible id shared-dma-pool
[    0.000000] OF: reserved mem: 0x00000000a4100000..0x00000000a4ffffff (15360 KiB) nomap non-reusable c7x-memory@a4100000
[    0.000000] OF: reserved mem: 0x00000000a5000000..0x00000000a6bfffff (28672 KiB) nomap non-reusable ipc-memories@a5000000
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000080000000-0x00000000ffffffff]
[    0.000000]   DMA32    empty
[    0.000000]   Normal   [mem 0x0000000100000000-0x00000009ffffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000080000000-0x000000008007ffff]
[    0.000000]   node   0: [mem 0x0000000080080000-0x000000009e7fffff]
[    0.000000]   node   0: [mem 0x000000009e800000-0x00000000a6bfffff]
[    0.000000]   node   0: [mem 0x00000000a6c00000-0x00000000ffffffff]
[    0.000000]   node   0: [mem 0x0000000880000000-0x00000009ffffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x00000009ffffffff]
[    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.5
[    0.000000] percpu: Embedded 22 pages/cpu s51672 r8192 d30248 u90112
[    0.000000] pcpu-alloc: s51672 r8192 d30248 u90112 alloc=22*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: GIC system register CPU interface
[    0.000000] CPU features: detected: ARM erratum 845719
[    0.000000] alternatives: applying boot alternatives
[    0.000000] Kernel command line: console=ttyS2,115200n8 earlycon=ns16550a,mmio32,0x02800000 root=PARTUUID=a7c38330-02 rw rootfstype=ext4 rootwait
[    0.000000] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear)
[    0.000000] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 2097152
[    0.000000] mem auto-init: stack:all(zero), heap alloc:off, heap free:off
[    0.000000] software IO TLB: area num 4.
[    0.000000] software IO TLB: mapped [mem 0x00000000fbfff000-0x00000000fffff000] (64MB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, 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=512 to nr_cpu_ids=4.
[    0.000000] 	Trampoline variant of Tasks RCU enabled.
[    0.000000] 	Tracing 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=4
[    0.000000] RCU Tasks: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=4.
[    0.000000] RCU Tasks Trace: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=4.
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[    0.000000] GICv3: 256 SPIs implemented
[    0.000000] GICv3: 0 Extended SPIs implemented
[    0.000000] Root IRQ handler: gic_handle_irq
[    0.000000] GICv3: GICv3 features: 16 PPIs
[    0.000000] GICv3: GICD_CTRL.DS=0, SCR_EL3.FIQ=1
[    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000001880000
[    0.000000] ITS [mem 0x01820000-0x0182ffff]
[    0.000000] GIC: enabling workaround for ITS: Socionext Synquacer pre-ITS
[    0.000000] ITS@0x0000000001820000: Devices Table too large, reduce ids 20->19
[    0.000000] ITS@0x0000000001820000: allocated 524288 Devices @880800000 (flat, esz 8, psz 64K, shr 0)
[    0.000000] ITS: using cache flushing for cmd queue
[    0.000000] GICv3: using LPI property table @0x0000000880050000
[    0.000000] GIC: using cache flushing for LPI property table
[    0.000000] GICv3: CPU0: using allocated LPI pending table @0x0000000880060000
[    0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[    0.000000] arch_timer: cp15 timer(s) running at 200.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0x3ffffffffffffff max_cycles: 0x2e2049d3e8, max_idle_ns: 440795210634 ns
[    0.000000] sched_clock: 58 bits at 200MHz, resolution 5ns, wraps every 4398046511102ns
[    0.008720] Console: colour dummy device 80x25
[    0.013320] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=800000)
[    0.023989] pid_max: default: 32768 minimum: 301
[    0.028786] LSM: initializing lsm=capability,selinux
[    0.033909] SELinux:  Initializing.
[    0.037906] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.045665] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.055807] rcu: Hierarchical SRCU implementation.
[    0.060753] rcu: 	Max phase no-delay instances is 1000.
[    0.066261] Timer migration: 1 hierarchy levels; 8 children per group; 1 crossnode level
[    0.075063] EFI services will not be available.
[    0.079954] smp: Bringing up secondary CPUs ...
[    0.085143] Detected VIPT I-cache on CPU1
[    0.085220] GICv3: CPU1: found redistributor 1 region 0:0x00000000018a0000
[    0.085235] GICv3: CPU1: using allocated LPI pending table @0x0000000880070000
[    0.085279] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.085962] Detected VIPT I-cache on CPU2
[    0.086020] GICv3: CPU2: found redistributor 2 region 0:0x00000000018c0000
[    0.086033] GICv3: CPU2: using allocated LPI pending table @0x0000000880080000
[    0.086064] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.086672] Detected VIPT I-cache on CPU3
[    0.086726] GICv3: CPU3: found redistributor 3 region 0:0x00000000018e0000
[    0.086740] GICv3: CPU3: using allocated LPI pending table @0x0000000880090000
[    0.086769] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.086886] smp: Brought up 1 node, 4 CPUs
[    0.166536] SMP: Total of 4 processors activated.
[    0.171342] CPU: All CPU(s) started at EL2
[    0.175542] CPU features: detected: 32-bit EL0 Support
[    0.180796] CPU features: detected: CRC32 instructions
[    0.186087] alternatives: applying system-wide alternatives
[    0.192362] Memory: 7077192K/8388608K available (12992K kernel code, 1256K rwdata, 4668K rodata, 2752K init, 642K bss, 384852K reserved, 917504K cma-reserved)
[    0.207902] devtmpfs: initialized
[    0.222779] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.232785] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.261679] 27136 pages in range for non-PLT usage
[    0.261702] 518656 pages in range for PLT usage
[    0.266919] pinctrl core: initialized pinctrl subsystem
[    0.277406] DMI not present or invalid.
[    0.283340] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    0.290513] DMA: preallocated 1024 KiB GFP_KERNEL pool for atomic allocations
[    0.297942] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    0.306045] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    0.314285] audit: initializing netlink subsys (disabled)
[    0.320026] audit: type=2000 audit(0.204:1): state=initialized audit_enabled=0 res=1
[    0.320446] thermal_sys: Registered thermal governor 'step_wise'
[    0.327951] thermal_sys: Registered thermal governor 'power_allocator'
[    0.334130] cpuidle: using governor menu
[    0.344956] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.351977] ASID allocator initialised with 65536 entries
[    0.365619] /bus@f0000/interrupt-controller@1800000: Fixed dependency cycle(s) with /bus@f0000/interrupt-controller@1800000
[    0.377141] /bus@f0000/i2c@20010000/bridge-hdmi@3b: Fixed dependency cycle(s) with /bus@f0000/dss@30220000
[    0.387032] /bus@f0000/i2c@20010000/dsi-edp-bridge@2c: Fixed dependency cycle(s) with /bus@f0000/dsi@30500000
[    0.397188] /bus@f0000/i2c@20020000/i2c-mux@70/i2c@1/sensor@10: Fixed dependency cycle(s) with /bus@f0000/ticsi2rx@30122000/csi-bridge@30121000
[    0.410355] /bus@f0000/i2c@20020000/i2c-mux@70/i2c@0/sensor@10: Fixed dependency cycle(s) with /bus@f0000/ticsi2rx@30102000/csi-bridge@30101000
[    0.423522] /bus@f0000/i2c@20020000/i2c-mux@71/i2c@1/sensor@10: Fixed dependency cycle(s) with /bus@f0000/ticsi2rx@30162000/csi-bridge@30161000
[    0.436688] /bus@f0000/i2c@20020000/i2c-mux@71/i2c@0/sensor@10: Fixed dependency cycle(s) with /bus@f0000/ticsi2rx@30142000/csi-bridge@30141000
[    0.449995] /bus@f0000/ticsi2rx@30102000/csi-bridge@30101000: Fixed dependency cycle(s) with /bus@f0000/i2c@20020000/i2c-mux@70/i2c@0/sensor@10
[    0.463173] /bus@f0000/dss@30220000: Fixed dependency cycle(s) with /bus@f0000/dsi@30500000
[    0.471711] /bus@f0000/dss@30220000: Fixed dependency cycle(s) with /bus@f0000/i2c@20010000/bridge-hdmi@3b
[    0.481606] /bus@f0000/dsi@30500000: Fixed dependency cycle(s) with /bus@f0000/dss@30220000
[    0.490149] /bus@f0000/dsi@30500000: Fixed dependency cycle(s) with /bus@f0000/i2c@20010000/dsi-edp-bridge@2c
[    0.500354] /bus@f0000/ticsi2rx@30122000/csi-bridge@30121000: Fixed dependency cycle(s) with /bus@f0000/i2c@20020000/i2c-mux@70/i2c@1/sensor@10
[    0.513528] /bus@f0000/ticsi2rx@30142000/csi-bridge@30141000: Fixed dependency cycle(s) with /bus@f0000/i2c@20020000/i2c-mux@71/i2c@0/sensor@10
[    0.526702] /bus@f0000/ticsi2rx@30162000/csi-bridge@30161000: Fixed dependency cycle(s) with /bus@f0000/i2c@20020000/i2c-mux@71/i2c@1/sensor@10
[    0.545579] /bus@f0000/i2c@20010000/bridge-hdmi@3b: Fixed dependency cycle(s) with /bus@f0000/dss@30220000
[    0.555511] /bus@f0000/i2c@20010000/dsi-edp-bridge@2c: Fixed dependency cycle(s) with /bus@f0000/dsi@30500000
[    0.565779] /bus@f0000/i2c@20020000/i2c-mux@70/i2c@1/sensor@10: Fixed dependency cycle(s) with /bus@f0000/ticsi2rx@30122000/csi-bridge@30121000
[    0.578955] /bus@f0000/i2c@20020000/i2c-mux@70/i2c@0/sensor@10: Fixed dependency cycle(s) with /bus@f0000/ticsi2rx@30102000/csi-bridge@30101000
[    0.592134] /bus@f0000/i2c@20020000/i2c-mux@71/i2c@1/sensor@10: Fixed dependency cycle(s) with /bus@f0000/ticsi2rx@30162000/csi-bridge@30161000
[    0.605305] /bus@f0000/i2c@20020000/i2c-mux@71/i2c@0/sensor@10: Fixed dependency cycle(s) with /bus@f0000/ticsi2rx@30142000/csi-bridge@30141000
[    0.620899] /bus@f0000/ticsi2rx@30102000/csi-bridge@30101000: Fixed dependency cycle(s) with /bus@f0000/i2c@20020000/i2c-mux@70/i2c@0/sensor@10
[    0.634426] /bus@f0000/i2c@20010000/bridge-hdmi@3b: Fixed dependency cycle(s) with /bus@f0000/dss@30220000
[    0.644370] /bus@f0000/dss@30220000: Fixed dependency cycle(s) with /bus@f0000/dsi@30500000
[    0.652923] /bus@f0000/dss@30220000: Fixed dependency cycle(s) with /bus@f0000/i2c@20010000/bridge-hdmi@3b
[    0.663000] /bus@f0000/dss@30220000: Fixed dependency cycle(s) with /bus@f0000/dsi@30500000
[    0.671596] /bus@f0000/i2c@20010000/dsi-edp-bridge@2c: Fixed dependency cycle(s) with /bus@f0000/dsi@30500000
[    0.681791] /bus@f0000/dsi@30500000: Fixed dependency cycle(s) with /bus@f0000/dss@30220000
[    0.690385] /bus@f0000/dsi@30500000: Fixed dependency cycle(s) with /bus@f0000/i2c@20010000/dsi-edp-bridge@2c
[    0.701150] /bus@f0000/ticsi2rx@30122000/csi-bridge@30121000: Fixed dependency cycle(s) with /bus@f0000/i2c@20020000/i2c-mux@70/i2c@1/sensor@10
[    0.714414] /bus@f0000/ticsi2rx@30142000/csi-bridge@30141000: Fixed dependency cycle(s) with /bus@f0000/i2c@20020000/i2c-mux@71/i2c@0/sensor@10
[    0.727677] /bus@f0000/ticsi2rx@30162000/csi-bridge@30161000: Fixed dependency cycle(s) with /bus@f0000/i2c@20020000/i2c-mux@71/i2c@1/sensor@10
[    0.743382] /bus@f0000/i2c@20010000/bridge-hdmi@3b: Fixed dependency cycle(s) with /connector-hdmi
[    0.752656] /connector-hdmi: Fixed dependency cycle(s) with /bus@f0000/i2c@20010000/bridge-hdmi@3b
[    0.762064] /bus@f0000/i2c@20010000/dsi-edp-bridge@2c: Fixed dependency cycle(s) with /connector-dp0
[    0.771485] /connector-dp0: Fixed dependency cycle(s) with /bus@f0000/i2c@20010000/dsi-edp-bridge@2c
[    0.781604] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
[    0.788564] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page
[    0.794965] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages
[    0.801896] HugeTLB: 0 KiB vmemmap can be freed for a 32.0 MiB page
[    0.808299] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
[    0.815229] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page
[    0.821629] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages
[    0.828561] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page
[    0.836525] k3-chipinfo 43000014.chipid: Family:J722S rev:SR1.0 JTAGID[0x0bba002f] Detected
[    0.845798] iommu: Default domain type: Translated
[    0.850716] iommu: DMA domain TLB invalidation policy: strict mode
[    0.857561] SCSI subsystem initialized
[    0.861586] libata version 3.00 loaded.
[    0.861760] usbcore: registered new interface driver usbfs
[    0.867397] usbcore: registered new interface driver hub
[    0.872846] usbcore: registered new device driver usb
[    0.878632] pps_core: LinuxPPS API ver. 1 registered
[    0.883709] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.893044] PTP clock support registered
[    0.897081] EDAC MC: Ver: 3.0.0
[    0.900597] scmi_core: SCMI protocol bus registered
[    0.905852] FPGA manager framework
[    0.909396] Advanced Linux Sound Architecture Driver Initialized.
[    0.916549] vgaarb: loaded
[    0.919659] clocksource: Switched to clocksource arch_sys_counter
[    0.926145] VFS: Disk quotas dquot_6.6.0
[    0.930177] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.943547] NET: Registered PF_INET protocol family
[    0.948834] IP idents hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    0.961286] tcp_listen_portaddr_hash hash table entries: 4096 (order: 4, 65536 bytes, linear)
[    0.970124] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.978059] TCP established hash table entries: 65536 (order: 7, 524288 bytes, linear)
[    0.986509] TCP bind hash table entries: 65536 (order: 9, 2097152 bytes, linear)
[    0.995777] TCP: Hash tables configured (established 65536 bind 65536)
[    1.002628] UDP hash table entries: 4096 (order: 5, 131072 bytes, linear)
[    1.009710] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes, linear)
[    1.017374] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    1.023638] RPC: Registered named UNIX socket transport module.
[    1.029726] RPC: Registered udp transport module.
[    1.034530] RPC: Registered tcp transport module.
[    1.039335] RPC: Registered tcp-with-tls transport module.
[    1.044941] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.051522] NET: Registered PF_XDP protocol family
[    1.056431] PCI: CLS 0 bytes, default 64
[    1.061763] Initialise system trusted keyrings
[    1.066555] workingset: timestamp_bits=46 max_order=21 bucket_order=0
[    1.073444] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    1.079671] NFS: Registering the id_resolver key type
[    1.084855] Key type id_resolver registered
[    1.089127] Key type id_legacy registered
[    1.093240] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.100089] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[    1.155061] Key type asymmetric registered
[    1.159263] Asymmetric key parser 'x509' registered
[    1.164307] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
[    1.172045] io scheduler mq-deadline registered
[    1.176682] io scheduler kyber registered
[    1.180805] io scheduler bfq registered
[    1.188208] pinctrl-single 4084000.pinctrl: 34 pins, size 136
[    1.194817] pinctrl-single f4000.pinctrl: 171 pins, size 684
[    1.202301] ledtrig-cpu: registered to indicate activity on CPUs
[    1.214396] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    1.229272] loop: module loaded
[    1.233629] megasas: 07.727.03.00-rc1
[    1.241386] tun: Universal TUN/TAP device driver, 1.6
[    1.247632] VFIO - User Level meta-driver version: 0.3
[    1.254273] usbcore: registered new interface driver usb-storage
[    1.261062] i2c_dev: i2c /dev entries driver
[    1.266686] sdhci: Secure Digital Host Controller Interface driver
[    1.273040] sdhci: Copyright(c) Pierre Ossman
[    1.277740] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.284257] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    1.291734] usbcore: registered new interface driver usbhid
[    1.297434] usbhid: USB HID core driver
[    1.302743] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 (0,8000003f) counters available
[    1.313065] optee: probing for conduit method.
[    1.317634] optee: revision 4.6 (71785645fa6ce42d)
[    1.317981] optee: dynamic shared memory is enabled
[    1.328519] optee: initialized driver
[    1.328618] random: crng init done
[    1.334564] Initializing XFRM netlink socket
[    1.340174] NET: Registered PF_PACKET protocol family
[    1.345410] Key type dns_resolver registered
[    1.357419] registered taskstats version 1
[    1.361767] Loading compiled-in X.509 certificates
[    1.377828] ti-sci 44043000.system-controller: ABI: 4.0 (firmware rev 0x000b '11.1.9--v11.01.09 (Fancy Rat)')
[    1.442148] omap_i2c 4900000.i2c: bus 0 rev0.12 at 400 kHz
[    1.449195] omap_i2c 2b200000.i2c: bus 1 rev0.12 at 400 kHz
[    1.456325] pca953x 2-0023: supply vcc not found, using dummy regulator
[    1.463238] pca953x 2-0023: using AI
[    1.482238] omap_i2c 20000000.i2c: bus 2 rev0.12 at 400 kHz
[    1.489328] /connector-hdmi: Fixed dependency cycle(s) with /bus@f0000/i2c@20010000/bridge-hdmi@3b
[    1.498626] /bus@f0000/dss@30220000: Fixed dependency cycle(s) with /bus@f0000/i2c@20010000/bridge-hdmi@3b
[    1.508550] /bus@f0000/i2c@20010000/bridge-hdmi@3b: Fixed dependency cycle(s) with /connector-hdmi
[    1.517765] /bus@f0000/i2c@20010000/bridge-hdmi@3b: Fixed dependency cycle(s) with /bus@f0000/dss@30220000
[    1.527898] /connector-dp0: Fixed dependency cycle(s) with /bus@f0000/i2c@20010000/dsi-edp-bridge@2c
[    1.537300] /bus@f0000/dsi@30500000: Fixed dependency cycle(s) with /bus@f0000/i2c@20010000/dsi-edp-bridge@2c
[    1.547491] /bus@f0000/i2c@20010000/dsi-edp-bridge@2c: Fixed dependency cycle(s) with /connector-dp0
[    1.556896] /bus@f0000/i2c@20010000/dsi-edp-bridge@2c: Fixed dependency cycle(s) with /bus@f0000/dsi@30500000
[    1.567282] omap_i2c 20010000.i2c: bus 3 rev0.12 at 100 kHz
[    1.574492] /bus@f0000/i2c@20020000/i2c-mux@70/i2c@1/sensor@10: Fixed dependency cycle(s) with /bus@f0000/ticsi2rx@30122000/csi-bridge@30121000
[    1.587773] /bus@f0000/i2c@20020000/i2c-mux@70/i2c@0/sensor@10: Fixed dependency cycle(s) with /bus@f0000/ticsi2rx@30102000/csi-bridge@30101000
[    1.601105] pca954x 4-0070: supply vdd not found, using dummy regulator
[    1.624047] /bus@f0000/ticsi2rx@30102000/csi-bridge@30101000: Fixed dependency cycle(s) with /bus@f0000/i2c@20020000/i2c-mux@70/i2c@0/sensor@10
[    1.637325] /bus@f0000/i2c@20020000/i2c-mux@70/i2c@0/sensor@10: Fixed dependency cycle(s) with /bus@f0000/ticsi2rx@30102000/csi-bridge@30101000
[    1.650659] i2c i2c-4: Added multiplexed i2c bus 5
[    1.655826] /bus@f0000/ticsi2rx@30122000/csi-bridge@30121000: Fixed dependency cycle(s) with /bus@f0000/i2c@20020000/i2c-mux@70/i2c@1/sensor@10
[    1.669086] /bus@f0000/i2c@20020000/i2c-mux@70/i2c@1/sensor@10: Fixed dependency cycle(s) with /bus@f0000/ticsi2rx@30122000/csi-bridge@30121000
[    1.682392] i2c i2c-4: Added multiplexed i2c bus 6
[    1.687295] pca954x 4-0070: registered 2 multiplexed busses for I2C switch pca9543
[    1.695265] /bus@f0000/i2c@20020000/i2c-mux@71/i2c@1/sensor@10: Fixed dependency cycle(s) with /bus@f0000/ticsi2rx@30162000/csi-bridge@30161000
[    1.708561] /bus@f0000/i2c@20020000/i2c-mux@71/i2c@0/sensor@10: Fixed dependency cycle(s) with /bus@f0000/ticsi2rx@30142000/csi-bridge@30141000
[    1.721931] pca954x 4-0071: supply vdd not found, using dummy regulator
[    1.729287] /bus@f0000/ticsi2rx@30142000/csi-bridge@30141000: Fixed dependency cycle(s) with /bus@f0000/i2c@20020000/i2c-mux@71/i2c@0/sensor@10
[    1.742564] /bus@f0000/i2c@20020000/i2c-mux@71/i2c@0/sensor@10: Fixed dependency cycle(s) with /bus@f0000/ticsi2rx@30142000/csi-bridge@30141000
[    1.755892] i2c i2c-4: Added multiplexed i2c bus 7
[    1.761056] /bus@f0000/ticsi2rx@30162000/csi-bridge@30161000: Fixed dependency cycle(s) with /bus@f0000/i2c@20020000/i2c-mux@71/i2c@1/sensor@10
[    1.774318] /bus@f0000/i2c@20020000/i2c-mux@71/i2c@1/sensor@10: Fixed dependency cycle(s) with /bus@f0000/ticsi2rx@30162000/csi-bridge@30161000
[    1.787622] i2c i2c-4: Added multiplexed i2c bus 8
[    1.792535] pca954x 4-0071: registered 2 multiplexed busses for I2C switch pca9543
[    1.800396] omap_i2c 20020000.i2c: bus 4 rev0.12 at 400 kHz
[    1.806518] ti-sci-intr 4210000.interrupt-controller: Interrupt Router 5 domain created
[    1.814894] ti-sci-intr bus@f0000:interrupt-controller@a00000: Interrupt Router 3 domain created
[    1.824132] ti-sci-inta 48000000.interrupt-controller: Interrupt Aggregator domain 28 created
[    1.833135] ti-sci-inta 4e400000.interrupt-controller: Interrupt Aggregator domain 200 created
[    1.847299] ti-udma 485c0100.dma-controller: Number of rings: 82
[    1.855547] ti-udma 485c0100.dma-controller: Channels: 44 (bchan: 16, tchan: 12, rchan: 16)
[    1.866209] ti-udma 485c0000.dma-controller: Number of rings: 150
[    1.876686] ti-udma 485c0000.dma-controller: Channels: 35 (tchan: 20, rchan: 15)
[    1.886082] ti-udma 4e230000.dma-controller: Number of rings: 40
[    1.894628] ti-udma 4e230000.dma-controller: Channels: 40 (bchan: 0, tchan: 8, rchan: 32)
[    1.905757] printk: legacy console [ttyS2] disabled
[    1.911082] 2800000.serial: ttyS2 at MMIO 0x2800000 (irq = 310, base_baud = 3000000) is a 8250
[    1.919966] printk: legacy console [ttyS2] enabled
[    1.929729] printk: legacy bootconsole [ns16550a0] disabled
[    1.954992] 7 fixed-partitions partitions found on MTD device fc40000.spi.0
[    1.961982] Creating 7 MTD partitions on "fc40000.spi.0":
[    1.967377] 0x000000000000-0x000000080000 : "ospi.tiboot3"
[    1.974066] 0x000000080000-0x000000280000 : "ospi.tispl"
[    1.980419] 0x000000280000-0x000000680000 : "ospi.u-boot"
[    1.986837] 0x000000680000-0x0000006c0000 : "ospi.env"
[    1.993029] 0x0000006c0000-0x000000700000 : "ospi.env.backup"
[    1.999879] 0x000000800000-0x000003fc0000 : "ospi.rootfs"
[    2.006313] 0x000003fc0000-0x000004000000 : "ospi.phypattern"
[    2.150264] am65-cpsw-nuss 8000000.ethernet: initializing am65 cpsw nuss version 0x6BA01903, cpsw version 0x6BA81903 Ports: 3 quirks:00000006
[    2.199672] davinci_mdio 8000f00.mdio: davinci mdio revision 17.7, bus freq 1000000
[    2.210791] davinci_mdio 8000f00.mdio: phy[0]: device 8000f00.mdio:00, driver TI DP83867
[    2.219004] am65-cpsw-nuss 8000000.ethernet: initialized cpsw ale version 1.5
[    2.226135] am65-cpsw-nuss 8000000.ethernet: ALE Table size 512, Policers 32
[    2.233912] am65-cpsw-nuss 8000000.ethernet: CPTS ver 0x4e8a010d, freq:500000000, add_val:1 pps:1
[    2.253524] am65-cpsw-nuss 8000000.ethernet: set new flow-id-base 19
[    2.267585] mmc0: CQHCI version 5.10
[    2.308242] mmc0: SDHCI controller on fa10000.mmc [fa10000.mmc] using ADMA 64-bit
[    2.342398] pca953x 3-0020: supply vcc not found, using dummy regulator
[    2.349176] pca953x 3-0020: using no AI
[    2.370591] mmc0: Command Queue Engine enabled
[    2.375102] mmc0: new HS200 MMC card at address 0001
[    2.376574] j721e-pcie f102000.pcie: host bridge /bus@f0000/pcie@f102000 ranges:
[    2.381040] mmcblk0: mmc0:0001 AAM20E 29.6 GiB
[    2.387539] j721e-pcie f102000.pcie:       IO 0x0600001000..0x0600100fff -> 0x0000001000
[    2.394129]  mmcblk0: p1 p2
[    2.400071] j721e-pcie f102000.pcie:      MEM 0x0600101000..0x06ffffffff -> 0x0000101000
[    2.403365] mmcblk0boot0: mmc0:0001 AAM20E 31.5 MiB
[    2.410947] j721e-pcie f102000.pcie:   IB MEM 0x0000000000..0xffffffffffff -> 0x0000000000
[    2.416724] mmcblk0boot1: mmc0:0001 AAM20E 31.5 MiB
[    2.429879] mmcblk0rpmb: mmc0:0001 AAM20E 4.00 MiB, chardev (239:0)
[    3.532501] j721e-pcie f102000.pcie: PCI host bridge to bus 0000:00
[    3.538834] pci_bus 0000:00: root bus resource [bus 00-ff]
[    3.544319] pci_bus 0000:00: root bus resource [io  0x0000-0xfffff] (bus address [0x1000-0x100fff])
[    3.553354] pci_bus 0000:00: root bus resource [mem 0x600101000-0x6ffffffff] (bus address [0x00101000-0xffffffff])
[    3.563716] pci 0000:00:00.0: [104c:b010] type 01 class 0x060400 PCIe Root Port
[    3.571031] pci 0000:00:00.0: PCI bridge to [bus 00]
[    3.575993] pci 0000:00:00.0:   bridge window [io  0x0000-0x0fff]
[    3.582080] pci 0000:00:00.0:   bridge window [mem 0x00000000-0x000fffff]
[    3.588864] pci 0000:00:00.0:   bridge window [mem 0x00000000-0x000fffff 64bit pref]
[    3.596654] pci 0000:00:00.0: supports D1
[    3.600661] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[    3.608898] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    3.617062] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    3.623696] pci 0000:00:00.0: PCI bridge to [bus 01]
[    3.628664] pci_bus 0000:00: resource 4 [io  0x0000-0xfffff]
[    3.634318] pci_bus 0000:00: resource 5 [mem 0x600101000-0x6ffffffff]
[    3.640878] pcieport 0000:00:00.0: of_irq_parse_pci: failed with rc=-22
[    3.647848] pcieport 0000:00:00.0: PME: Signaling with IRQ 566
[    3.653955] pcieport 0000:00:00.0: AER: enabled with IRQ 566
[    3.660975] clk: Disabling unused clocks
[    3.661461] mmc1: CQHCI version 5.10
[    3.674503] PM: genpd: Disabling unused power domains
[    3.679749] ALSA device list:
[    3.682711]   No soundcards found.
[    3.709937] mmc1: SDHCI controller on fa00000.mmc [fa00000.mmc] using ADMA 64-bit
[    3.717624] Waiting for root device PARTUUID=a7c38330-02...
[    3.784853] mmc1: new ultra high speed SDR104 SDHC card at address aaaa
[    3.792096] mmcblk1: mmc1:aaaa SL32G 29.7 GiB
[    3.801810]  mmcblk1: p1 p2
[    4.324826] EXT4-fs (mmcblk1p2): recovery complete
[    4.330692] EXT4-fs (mmcblk1p2): mounted filesystem dedc5f42-d9cf-4dc2-a20a-4a981930227e r/w with ordered data mode. Quota mode: none.
[    4.342853] VFS: Mounted root (ext4 filesystem) on device 179:98.
[    4.356385] devtmpfs: mounted
[    4.360093] Freeing unused kernel memory: 2752K
[    4.364706] Run /sbin/init as init process
[    4.368802]   with arguments:
[    4.368805]     /sbin/init
[    4.368809]   with environment:
[    4.368812]     HOME=/
[    4.368816]     TERM=linux
[    4.572252] systemd[1]: System time before build time, advancing clock.
[    4.619604] NET: Registered PF_INET6 protocol family
[    4.625586] Segment Routing with IPv6
[    4.629311] In-situ OAM (IOAM) with IPv6
[    4.665200] systemd[1]: systemd 255.21^ 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)
[    4.697159] systemd[1]: Detected architecture arm64.
[    4.714176] systemd[1]: Hostname set to <j722s-evm>.
[    5.028629] 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.
[    5.203192] systemd[1]: Queued start job for default target Graphical Interface.
[    5.245429] systemd[1]: Created slice Slice /system/getty.
[    5.266055] systemd[1]: Created slice Slice /system/modprobe.
[    5.286029] systemd[1]: Created slice Slice /system/serial-getty.
[    5.305474] systemd[1]: Created slice User and Session Slice.
[    5.324119] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[    5.344022] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    5.363873] systemd[1]: Expecting device /dev/ttyS2...
[    5.375923] systemd[1]: Reached target Path Units.
[    5.387799] systemd[1]: Reached target Remote File Systems.
[    5.403791] systemd[1]: Reached target Slice Units.
[    5.415826] systemd[1]: Reached target Swaps.
[    5.484785] systemd[1]: Listening on RPCbind Server Activation Socket.
[    5.507976] systemd[1]: Reached target RPC Port Mapper.
[    5.533001] systemd[1]: Listening on Process Core Dump Socket.
[    5.552220] systemd[1]: Listening on initctl Compatibility Named Pipe.
[    5.572982] systemd[1]: Listening on Journal Audit Socket.
[    5.592528] systemd[1]: Listening on Journal Socket (/dev/log).
[    5.612542] systemd[1]: Listening on Journal Socket.
[    5.624659] systemd[1]: Listening on Network Service Netlink Socket.
[    5.647445] systemd[1]: Listening on udev Control Socket.
[    5.664422] systemd[1]: Listening on udev Kernel Socket.
[    5.680447] systemd[1]: Listening on User Database Manager Socket.
[    5.724073] systemd[1]: Mounting Huge Pages File System...
[    5.740135] systemd[1]: Mounting POSIX Message Queue File System...
[    5.784095] systemd[1]: Mounting Kernel Debug File System...
[    5.796243] systemd[1]: Kernel Trace File System was skipped because of an unmet condition check (ConditionPathExists=/sys/kernel/tracing).
[    5.816084] systemd[1]: Mounting Temporary Directory /tmp...
[    5.833644] systemd[1]: Starting Create List of Static Device Nodes...
[    5.856558] systemd[1]: Starting Load Kernel Module configfs...
[    5.880610] systemd[1]: Starting Load Kernel Module drm...
[    5.896715] systemd[1]: Starting Load Kernel Module fuse...
[    5.922131] systemd[1]: Starting Start psplash boot splash screen...
[    5.939475] fuse: init (API version 7.41)
[    5.951718] systemd[1]: Starting RPC Bind...
[    5.968151] systemd[1]: File System Check on Root Device was skipped because of an unmet condition check (ConditionPathIsReadWrite=!/).
[    5.988906] systemd[1]: Starting Journal Service...
[    6.007416] systemd[1]: Starting Load Kernel Modules...
[    6.025221] systemd[1]: Starting Generate network units from Kernel command line...
[    6.049366] systemd[1]: Starting Remount Root and Kernel File Systems...
[    6.054869] cryptodev: loading out-of-tree module taints kernel.
[    6.064057] sysctl table check failed: ioctl/(null) procname is null
[    6.074568] sysctl table check failed: ioctl/(null) No proc_handler
[    6.081571] cryptodev: driver 1.14 loaded.
[    6.086649] systemd[1]: Starting Coldplug All udev Devices...
[    6.095026] systemd-journald[134]: Collecting audit messages is enabled.
[    6.123283] systemd[1]: Started RPC Bind.
[    6.142133] systemd[1]: Mounted Huge Pages File System.
[    6.144130] EXT4-fs (mmcblk1p2): re-mounted dedc5f42-d9cf-4dc2-a20a-4a981930227e.
[    6.174260] systemd[1]: Mounted POSIX Message Queue File System.
[    6.196370] systemd[1]: Started Journal Service.
[    6.536869] systemd-journald[134]: Received client request to flush runtime journal.
[    6.786456] audit: type=1334 audit(1748544504.208:2): prog-id=6 op=LOAD
[    6.793149] audit: type=1334 audit(1748544504.216:3): prog-id=7 op=LOAD
[    7.019788] audit: type=1334 audit(1748544504.444:4): prog-id=8 op=LOAD
[    7.026469] audit: type=1334 audit(1748544504.448:5): prog-id=9 op=LOAD
[    7.033141] audit: type=1334 audit(1748544504.456:6): prog-id=10 op=LOAD
[    7.399760] audit: type=1334 audit(1748544504.820:7): prog-id=11 op=LOAD
[    7.455784] audit: type=1334 audit(1748544504.876:8): prog-id=12 op=LOAD
[    8.084421] audit: type=1334 audit(1748546078.112:9): prog-id=13 op=LOAD
[    8.555953] omap-mailbox 29000000.mailbox: omap mailbox rev 0x66fca100
[    8.567331] omap-mailbox 29010000.mailbox: omap mailbox rev 0x66fca100
[    8.578231] omap-mailbox 29020000.mailbox: omap mailbox rev 0x66fca100
[    8.607336] omap-mailbox 29030000.mailbox: omap mailbox rev 0x66fca100
[    8.655383] CAN device driver interface
[    8.701248] mc: Linux media interface: v0.10
[    8.778978] videodev: Linux video capture interface: v2.00
[    8.867605] imx219 5-0010: supply VANA not found, using dummy regulator
[    8.891201] imx219 5-0010: supply VDIG not found, using dummy regulator
[    8.898086] k3-dsp-rproc 7e000000.dsp: assigned reserved memory node c7x-dma-memory@a3000000
[    8.909757] k3-dsp-rproc 7e000000.dsp: configured DSP for remoteproc mode
[    8.920526] imx219 5-0010: supply VDDL not found, using dummy regulator
[    8.948219] remoteproc remoteproc0: 7e000000.dsp is available
[    8.989703] audit: type=1334 audit(1748546079.016:10): prog-id=14 op=LOAD
[    9.003007] remoteproc remoteproc0: Direct firmware load for j722s-c71_0-fw failed with error -2
[    9.014360] remoteproc remoteproc0: powering up 7e000000.dsp
[    9.022204] remoteproc remoteproc0: Direct firmware load for j722s-c71_0-fw failed with error -2
[    9.033385] k3-dsp-rproc 7e200000.dsp: assigned reserved memory node c7x-dma-memory@a4000000
[    9.033605] imx219 6-0010: supply VANA not found, using dummy regulator
[    9.041921] remoteproc remoteproc0: request_firmware failed: -2
[    9.048840] audit: type=1334 audit(1748546079.076:11): prog-id=15 op=LOAD
[    9.049646] k3-dsp-rproc 7e200000.dsp: configured DSP for remoteproc mode
[    9.054721] platform 79000000.r5f: configured R5F for remoteproc mode
[    9.076701] platform 79000000.r5f: assigned reserved memory node mcu-r5fss-dma-memory-region@a1000000
[    9.084569] imx219 6-0010: supply VDIG not found, using dummy regulator
[    9.086481] remoteproc remoteproc1: 7e200000.dsp is available
[    9.105210] remoteproc remoteproc2: 79000000.r5f is available
[    9.111294] remoteproc remoteproc2: Direct firmware load for j722s-mcu-r5f0_0-fw failed with error -2
[    9.113562] imx219 6-0010: supply VDDL not found, using dummy regulator
[    9.114649] remoteproc remoteproc1: Direct firmware load for j722s-c71_1-fw failed with error -2
[    9.114678] remoteproc remoteproc1: powering up 7e200000.dsp
[    9.114742] remoteproc remoteproc1: Direct firmware load for j722s-c71_1-fw failed with error -2
[    9.114750] remoteproc remoteproc1: request_firmware failed: -2
[    9.120615] remoteproc remoteproc2: powering up 79000000.r5f
[    9.157292] vdec 30210000.video-codec: Added wave5 driver with caps: 'ENCODE' 'DECODE'
[    9.162792] platform 78000000.r5f: R5F core may have been powered on by a different host, programmed state (0) != actual state (1)
[    9.164523] remoteproc remoteproc2: Direct firmware load for j722s-mcu-r5f0_0-fw failed with error -2
[    9.164545] remoteproc remoteproc2: request_firmware failed: -2
[    9.173209] vdec 30210000.video-codec: Product Code:      0x521c
[    9.184673] imx219 6-0010: Error reading reg 0x0000: -121
[    9.192466] vdec 30210000.video-codec: Firmware Revision: 363254
[    9.199750] imx219 6-0010: error -EREMOTEIO: failed to read chip id 219
[    9.218590] platform 78000000.r5f: configured R5F for IPC-only mode
[    9.222967] imx219 6-0010: probe with driver imx219 failed with error -121
[    9.234095] platform 78000000.r5f: assigned reserved memory node r5f-dma-memory@a0000000
[    9.235426] imx219 7-0010: supply VANA not found, using dummy regulator
[    9.260103] remoteproc remoteproc3: 78000000.r5f is available
[    9.261941] imx219 7-0010: supply VDIG not found, using dummy regulator
[    9.270176] remoteproc remoteproc3: attaching to 78000000.r5f
[    9.275996] imx219 7-0010: supply VDDL not found, using dummy regulator
[    9.294040] rproc-virtio rproc-virtio.4.auto: assigned reserved memory node r5f-dma-memory@a0000000
[    9.300762] cdns-csi2rx 30101000.csi-bridge: Probed CSI2RX with 2/4 lanes, 4 streams, external D-PHY
[    9.307039] imx219 7-0010: Error reading reg 0x0000: -121
[    9.321441] imx219 7-0010: error -EREMOTEIO: failed to read chip id 219
[    9.322265] virtio_rpmsg_bus virtio0: rpmsg host is online
[    9.322309] rproc-virtio rproc-virtio.4.auto: registered virtio0 (type 7)
[    9.322318] remoteproc remoteproc3: remote processor 78000000.r5f is now attached
[    9.322383] virtio_rpmsg_bus virtio0: creating channel ti.ipc4.ping-pong addr 0xd
[    9.322520] virtio_rpmsg_bus virtio0: creating channel rpmsg_chrdev addr 0xe
[    9.330460] platform 78400000.r5f: configured R5F for remoteproc mode
[    9.344311] imx219 7-0010: probe with driver imx219 failed with error -121
[    9.397017] platform 78400000.r5f: assigned reserved memory node main-r5fss-dma-memory-region@a2000000
[    9.407997] imx219 8-0010: supply VANA not found, using dummy regulator
[    9.427894] imx219 8-0010: supply VDIG not found, using dummy regulator
[    9.428908] remoteproc remoteproc4: 78400000.r5f is available
[    9.435030] Bluetooth: Core ver 2.22
[    9.437591] imx219 8-0010: supply VDDL not found, using dummy regulator
[    9.450994] NET: Registered PF_BLUETOOTH protocol family
[    9.461760] Bluetooth: HCI device and connection manager initialized
[    9.469745] Bluetooth: HCI socket layer initialized
[    9.474807] Bluetooth: L2CAP socket layer initialized
[    9.480066] Bluetooth: SCO socket layer initialized
[    9.480569] rtc-ti-k3 2b1f0000.rtc: registered as rtc0
[    9.492590] /bus@f0000/i2c@20020000/i2c-mux@70/i2c@1/sensor@10: Fixed dependency cycle(s) with /bus@f0000/ticsi2rx@30122000/csi-bridge@30121000
[    9.505723] imx219 8-0010: Error reading reg 0x0000: -121
[    9.505914] /bus@f0000/ticsi2rx@30122000/csi-bridge@30121000: Fixed dependency cycle(s) with /bus@f0000/i2c@20020000/i2c-mux@70/i2c@1/sensor@10
[    9.511171] imx219 8-0010: error -EREMOTEIO: failed to read chip id 219
[    9.531321] imx219 8-0010: probe with driver imx219 failed with error -121
[    9.533678] cdns-csi2rx 30121000.csi-bridge: Probed CSI2RX with 2/4 lanes, 4 streams, external D-PHY
[    9.558648] remoteproc remoteproc4: Direct firmware load for j722s-main-r5f0_0-fw failed with error -2
[    9.568034] remoteproc remoteproc4: powering up 78400000.r5f
[    9.573901] remoteproc remoteproc4: Direct firmware load for j722s-main-r5f0_0-fw failed with error -2
[    9.599741] remoteproc remoteproc4: request_firmware failed: -2
[    9.673182] m_can_platform 4e08000.can: m_can device registered (irq=585, version=32)
[    9.681395] e5010 fd20000.e5010: Device registered as /dev/video8
[    9.690583] m_can_platform 4e18000.can: m_can device registered (irq=589, version=32)
[    9.737015] m_can_platform 20701000.can: m_can device registered (irq=592, version=32)
[    9.760806] PVR_K:  201: Device: fd80000.gpu
[    9.762328] sii902x 3-003b: supply iovcc not found, using dummy regulator
[    9.767973] PVR_K:  201: Read BVNC 36.53.104.796 from HW device registers
[    9.774351] sii902x 3-003b: supply cvcc12 not found, using dummy regulator
[    9.779199] PVR_K:  201: RGX Device registered BVNC 36.53.104.796 with 1 core in the system
[    9.798223] [drm] Initialized pvr 24.2.6643903 for fd80000.gpu on minor 0
[    9.801293] i2c i2c-3: Added multiplexed i2c bus 9
[    9.805762] /bus@f0000/i2c@20020000/i2c-mux@71/i2c@0/sensor@10: Fixed dependency cycle(s) with /bus@f0000/ticsi2rx@30142000/csi-bridge@30141000
[    9.805963] /bus@f0000/ticsi2rx@30142000/csi-bridge@30141000: Fixed dependency cycle(s) with /bus@f0000/i2c@20020000/i2c-mux@71/i2c@0/sensor@10
[    9.905526] cdns-csi2rx 30141000.csi-bridge: Probed CSI2RX with 2/4 lanes, 4 streams, external D-PHY
[    9.996244] [drm] Initialized tidss 1.0.0 for 30220000.dss on minor 1
[   10.007278] tidss 30220000.dss: [drm] Cannot find any crtc or sizes
[   10.016664] tidss 30220000.dss: [drm] Cannot find any crtc or sizes
[   10.026194] tidss 30220000.dss: [drm] Cannot find any crtc or sizes
[   10.100200] /bus@f0000/i2c@20020000/i2c-mux@71/i2c@1/sensor@10: Fixed dependency cycle(s) with /bus@f0000/ticsi2rx@30162000/csi-bridge@30161000
[   10.115166] /bus@f0000/ticsi2rx@30162000/csi-bridge@30161000: Fixed dependency cycle(s) with /bus@f0000/i2c@20020000/i2c-mux@71/i2c@1/sensor@10
[   10.133301] cdns-csi2rx 30161000.csi-bridge: Probed CSI2RX with 2/4 lanes, 4 streams, external D-PHY
[   10.284703] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   10.320840] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   10.327582] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   10.495604] am65-cpsw-nuss 8000000.ethernet eth0: PHY [8000f00.mdio:00] driver [TI DP83867] (irq=POLL)
[   10.509203] am65-cpsw-nuss 8000000.ethernet eth0: configuring for phy/rgmii-rxid link mode
[   10.875607] m_can_platform 20701000.can main_mcan0: renamed from can2
[   10.880888] xhci-hcd xhci-hcd.7.auto: xHCI Host Controller
[   10.888290] xhci-hcd xhci-hcd.7.auto: new USB bus registered, assigned bus number 1
[   10.910906] m_can_platform 4e08000.can mcu_mcan0: renamed from can0
[   10.917886] xhci-hcd xhci-hcd.7.auto: hcc params 0x200073c9 hci version 0x100 quirks 0x0000002000008010
[   10.930471] xhci-hcd xhci-hcd.7.auto: irq 591, io mem 0x31210000
[   10.940169] xhci-hcd xhci-hcd.7.auto: xHCI Host Controller
[   10.946714] xhci-hcd xhci-hcd.7.auto: new USB bus registered, assigned bus number 2
[   10.962292] xhci-hcd xhci-hcd.7.auto: Host supports USB 3.0 SuperSpeed
[   10.969882] m_can_platform 4e18000.can mcu_mcan1: renamed from can1
[   10.976303] hub 1-0:1.0: USB hub found
[   10.990538] hub 1-0:1.0: 1 port detected
[   10.996116] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[   11.005667] hub 2-0:1.0: USB hub found
[   11.009570] hub 2-0:1.0: 1 port detected
[   11.243962] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[   11.661457] hub 1-1:1.0: USB hub found
[   11.666547] hub 1-1:1.0: 4 ports detected
[   11.779768] usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd
[   11.801956] hub 2-1:1.0: USB hub found
[   11.805894] hub 2-1:1.0: 4 ports detected
[   11.935462] usbcore: registered new device driver onboard-usb-dev
[   14.924397] kauditd_printk_skb: 2 callbacks suppressed
[   14.924413] audit: type=1006 audit(1748546084.952:14): pid=1071 uid=0 subj=kernel old-auid=4294967295 auid=1000 tty=(none) old-ses=4294967295 ses=1 res=1
[   14.943445] audit: type=1300 audit(1748546084.952:14): arch=c00000b7 syscall=64 success=yes exit=4 a0=8 a1=fffff83ab1b8 a2=4 a3=1 items=0 ppid=1 pid=1071 auid=1000 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)
[   14.971355] audit: type=1327 audit(1748546084.952:14): proctitle="(systemd)"
[   16.493198] PVR_K:  1078: RGX Firmware image 'rgx.fw.36.53.104.796' loaded
[   16.507658] PVR_K:  1078: Shader binary image 'rgx.sh.36.53.104.796' loaded
[   17.473343] audit: type=1006 audit(1748546087.500:15): pid=1089 uid=0 subj=kernel old-auid=4294967295 auid=0 tty=(none) old-ses=4294967295 ses=2 res=1
[   17.486967] audit: type=1300 audit(1748546087.500:15): arch=c00000b7 syscall=64 success=yes exit=1 a0=8 a1=ffffe4feada8 a2=1 a3=1 items=0 ppid=1 pid=1089 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=2 comm="(systemd)" exe="/usr/lib/systemd/systemd-executor" subj=kernel key=(null)
[   17.514623] audit: type=1327 audit(1748546087.500:15): proctitle="(systemd)"
[   17.552645] audit: type=1334 audit(1748546087.580:16): prog-id=18 op=LOAD
[   17.559496] audit: type=1300 audit(1748546087.580:16): arch=c00000b7 syscall=280 success=yes exit=8 a0=5 a1=ffffd1cfba58 a2=90 a3=0 items=0 ppid=1 pid=1089 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=2 comm="systemd" exe="/usr/lib/systemd/systemd" subj=kernel key=(null)
[   17.586397] audit: type=1327 audit(1748546087.580:16): proctitle="(systemd)"
[   17.593564] audit: type=1334 audit(1748546087.580:17): prog-id=18 op=UNLOAD
    Hi Jared McArthur,

    Thank you for your prompt response and detailed suggestions.

    A log of dmesg and i2cdetect is attached.
    Since the imx219no camera only connects CSI #0, we recognize that errors occur for other CSI pins.

    >name_overlays=ti/k3-j722s-evm-csi2-quad-rpi-cam-imx219.dtbo Do you only have this overlay enabled, and no others?
    Is there another best dtbo to use the imx219 camera?

    >Can you try removing/disabling the R5 firmwares?
    A log that has been renamed (grant _bk) the file as shown below is attached.

    -rw-r--r-- 1 root root 11159353 Mar 9 2018 vx_app_rtos_linux_c7x_1.out.signed_bk
    -rw-r--r-- 1 root root 11157672 Mar 9 2018 vx_app_rtos_linux_c7x_1.out_bk
    -rw-r--r-- 1 root root 11269945 Mar 9 2018 vx_app_rtos_linux_c7x_2.out.signed_bk
    -rw-r--r-- 1 root root 11268264 Mar 9 2018 vx_app_rtos_linux_c7x_2.out_bk
    -rw-r--r-- 1 root root 1126960 Mar 9 2018 vx_app_rtos_linux_mcu2_0.out.signed_bk
    -rw-r--r-- 1 root root 1125280 Mar 9 2018 vx_app_rtos_linux_mcu2_0.out_bk

    Best regards,
    Masao Takayama

  • 0 in reply to Masao Takayama
    Prodigy 245 points

    Hi Jared McArthur,

    I am not sure how to create the tisdk-default-image.
    Could you please provide the steps to do so?
    If there is a website with consolidated information, could you share the URL?

    Do I need to change the device tree settings?

    Regarding the setup:
    I have connected the flex cable of the HBV-RPI-300FPC to the TDA4VEN+J722S EVM environment,
    and then connected the Raspberry Pi Camera Module 2.
    I believe the SK-TDA4VM supports the Raspberry Pi Camera Module 2 (IMX219),
    but when trying to achieve this with the J722S,
    are there any hardware constraints? I understand that the CSI terminals are different in terms of hardware.

    Best regards,
    Masao Takayama

  • 0 in reply to Masao Takayama
    Prodigy 245 points

    Hi Jared McArthur,

    Sorry for asking multiple times.

    >Do we need to modify the device tree settings?
    If modification of the device tree settings is necessary,
    we would like to create a DTBO based on a DTS that enables the IMX219 (also making changes to ensure GPIO and I2C can be used on the Linux side).
    Do you have any reference DTS files for the above?


    Best regards,
    Masao Takayama

  • 0 in reply to Masao Takayama
    TI__Mastermind 25360 points

    Hi ,

    Masao Takayama said:

    Is there another best dtbo to use the imx219 camera?

    No, this is the correct dtbo.

    Masao Takayama said:

    A log that has been renamed (grant _bk) the file as shown below is attached.

    It looks like all of the firmwares failed to load, so the firmware I2C conflict shouldn't be an issue.

    Masao Takayama said:
    I am not sure how to create the tisdk-default-image.
    Could you please provide the steps to do so?
    If there is a website with consolidated information, could you share the URL?

    Building the image is done using Yocto, but it doesn't appear that you need to do this. The steps are here: https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-j722s/11_01_00_03/exports/docs/linux/Overview_Building_the_SDK.html#building-the-sdk-with-yocto 

    Masao Takayama said:

    are there any hardware constraints? I understand that the CSI terminals are different in terms of hardware.

    The J722S uses a 22 pin FPC instead of a 15 pin FPC.

    For i2cdetect, can you add -r to the command?

    It appears that imx219 5-0010 probed properly. If you try each camera one at a time, do they all fail?

    Best,
    Jared

  • 0 in reply to Jared McArthur
    Prodigy 245 points

    Hi Jared McArthur,

    Thank you for your response.

    >For i2cdetect, can you add -r to the command?
    I was unable to specify the -r option for the command.
    ＝＝＝＝＝＝＝＝＝
    root@j722s-evm:~# i2cdetect -r
    Error: No i2c-bus specified!
    Usage: i2cdetect [-y] [-a] [-q|-r] I2CBUS [FIRST LAST]
    i2cdetect -F I2CBUS
    i2cdetect -l
    I2CBUS is an integer or an I2C bus name
    If provided, FIRST and LAST limit the probing range.
    ＝＝＝＝＝＝＝＝＝

    >It appears that imx219 5-0010 probed properly. If you try each camera one at a time, do they all fail?
    Unfortunately, all attempts resulted in failure.

    I believe that enabling the k3-j722s-evm-csi2-quad-rpi-cam-imx219.dtbo will activate the imx219 driver.
    However, even if the driver is active, will the I2C address be detectable using the i2cdetect command?

    In the default k3-j722s-evm-csi2-quad-rpi-cam-imx219.dtbo configuration,
    I understand that PIN11 (GPIO / XSHUTDOWN / Power Enable (board dependent)) of the IMX219 Camera Module (15pin) needs to be set to High.
    Since it was set to Low in the device tree, I changed it to High. If this setting and the initialization process performed by the imx219 driver are correct,
    I believe the camera should start capturing video and the video data should be accessible via /dev/media*.

    When functioning correctly, I understand that a command like:

    Best regards,
    Masao Takayama

  • 0 in reply to Masao Takayama
    TI__Mastermind 25360 points

    Hi ,

    Masao Takayama said:
    I was unable to specify the -r option for the command.

    I meant to run something like: i2cdetect -y -r 0

    Masao Takayama said:

    However, even if the driver is active, will the I2C address be detectable using the i2cdetect command?

    It should appear as UU if the address is in use.

    Masao Takayama said:
    I understand that PIN11 (GPIO / XSHUTDOWN / Power Enable (board dependent)) of the IMX219 Camera Module (15pin) needs to be set to High.
    Since it was set to Low in the device tree, I changed it to High. If this setting and the initialization process performed by the imx219 driver are correct,
    I believe the camera should start capturing video and the video data should be accessible via /dev/media*.

    This GPIO should be controlled by the driver. It shouldn't be controlled from userspace.

    Best,
    Jared

  • 0 in reply to Jared McArthur
    Prodigy 245 points

    Hi Jared McArthur,

    I was able to reference the I2C address 0x10 using the following commands:

    i2cdetect -y -r 4
i2cdetect -y -r 5

    In the SDK environment of ti-processor-sdk-linux-adas-j722s-evm-11_01_00_03, after executing bin/create-sdcard.sh and starting the software, I confirmed the state with the following line in uEnv.txt disabled:

    #name_overlays=ti/k3-j722s-vision-apps.dtbo

    1. When PIN11 (GPIO / XSHUTDOWN / Power Enable (board dependent)) of the IMX219 Camera Module (15-pin) is Low, it displays UU, indicating that the device is in use.

    2. When PIN11 (GPIO / XSHUTDOWN / Power Enable (board dependent)) of the IMX219 Camera Module (15-pin) is High, it displays 10, indicating that the device is not in use.

    Modified DT settings:
    k3-j722s-evm-si2-quad-rpi-cam-imx219.dts

    ==============
     sensor@10 {
     　compatible = "sony,imx219";
     　　reg = <0x10>;
     　　clocks = <0x01>;
     　　clock-names = "xclk";
     　　pinctrl-names = "default";
     　　pinctrl-0 = <0x02>;
     　　reset-gpios = <0xffffffff 0x0f 0x00>; ←    Changed 0x00 to 0x01
     　　port {

     　　　　endpoint {
     　　　　　　remote-endpoint = <0x03>;
     　　　　　　link-frequencies = <0x00 0x1b2e0200>;
     　　　　　　clock-lanes = <0x00>;
     　　　　　　data-lanes = <0x01 0x02>;
     　　　　　　phandle = <0x0a>;
     　　　　};
     　　};
     };
    ==============

    In my understanding, to use the camera, it is necessary to set the 11th pin (CAM_IO0 GPIO / XSHUTDOWN / Power Enable (board dependent)) of the IMX219 Camera Module (15-pin) to High. For this purpose, I believe it is necessary to set the 15th pin of the J722S SOC (CSI2_EXP_A_GPIO1 CSI2 Expansion/RPI Camera Board Specific. 1:2 Mux on the path) to High.

    However, in case ②, since it does not display UU, I suspect that there might be a failure in the driver control.

    Best regards,

    Masao Takayama

  • 0 in reply to Masao Takayama
    TI__Mastermind 25360 points

    Hi ,

    The 0x00 or 0x01 there just changes between GPIO_ACTIVE_HIGH or GPIO_ACTIVE_LOW. It should be GPIO_ACTIVE_HIGH (0x00). Keep the dtb the same as the one that came with the release.

    Masao Takayama said:
    I believe the camera should start capturing video and the video data should be accessible via /dev/media*.

    The camera will only start if you execute a command to start it. The device should appear somewhere in /dev/video*.

    The device will also appear when executing: "media-ctl -p"

    Can you send the output of "media-ctl -p"?

    Best,
    Jared

  • 0 in reply to Jared McArthur
    Prodigy 245 points

    Hi Jared McArthur,

    Thank you very much for your response.

    I understand that GPIO_ACTIVE_HIGH (0x00) is correct, and therefore no changes to the GPIO are required.
    The output of “media-ctl -p” is as shown in the supplementary information.

    Once again, I would like to confirm my current setup.
    Could you kindly advise whether the following configuration is incorrect as an environment for running the imx219 on Linux?

    =============

    • The camera is connected to CSI#0.
    • Connection setup: TDA4VEN Left right arrow HBV-RPI-300FPC Left right arrow Raspberry Pi Camera Module 2.

    Software environment:
    The system is built with SD boot on the full SDK environment pre-installed at /opt/ti-processor-sdk-rtos-j722s-evm-11_01_00_04/.
    In this setup, I have configured uEnv.txt as follows:

    name_overlays=ti/k3-j722s-evm-csi2-quad-rpi-cam-imx219.dtbo

    and then booted the system.


  • 0 in reply to Masao Takayama
    TI__Mastermind 25360 points

    Hi ,

    Masao Takayama said:

    The output of “media-ctl -p” is as shown in the supplementary information.

    Where is the supplementary information?

    Masao Takayama said:

    Could you kindly advise whether the following configuration is incorrect as an environment for running the imx219 on Linux?

    That looks good.

    Masao Takayama said:
    The system is built with SD boot on the full SDK environment pre-installed at /opt/ti-processor-sdk-rtos-j722s-evm-11_01_00_04/.

    If you're trying to run solely in Linux, I would recommend using the Linux release instead of the RTOS release.

    Best,
    Jared

  • +1 in reply to Jared McArthur
    Prodigy 245 points

    Hi Jared McArthur,

    After much trial and error, I was able to successfully set up the EdgeAI solution environment and obtain video footage from the IMX219 camera.
    Therefore, I would like to close this issue. Thank you very much for all your advice and assistance.

    Best regards,
    Masao Takayama

  • 0 in reply to Jared McArthur
    Prodigy 245 points

    Hi Jared McArthur,

    By using the Linux release (edgeAI), I was able to successfully capture the camera footage. Ideally, I would like to operate the IMX219 driver on RTOS, but considering the complexity of configuring the hardware accelerators and I2C settings, I understand that it is quite challenging. Therefore, I have decided to pause at this point.

    Best regards,
    Masao Takayama