Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

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.

no signal from DP when using DP-to-HDMI adapter and HDMI grabber

Other Parts Discussed in Thread: TDA4VM, TDA4VL

HI Ti members

I would like to ask about the display port on TDA4VM EVM.

I used DP with DP-to-HDMI adapter on EVM like below. And it works in PSDK8.6.

1. EVM --> DP-to-HDMI adapter --> portable monitor

2. EVM --> DP-to-HDMI adapter --> HDMI grabber(https://www.avermedia.com/product-detail/GC513)

But after upgrading to PSDK9.0, there is no signal in 2nd case. But it works in 1st case.

Which dts should I modify to use a HDMI grabber?

Best regards

Yongsig

  • Hi Yongsig,

    Are you using vision apps on R5F firmware? 

    Regards,

    Brijesh

  • Hi Brijesh

    I'm not using it on R5F.

    So I had to disable some of options on 'ti-processor-sdk-linux-adas-j721e-evm-09_00_00_08/board-support/linux-6.1.33+gitAUTOINC+8f7f371be2-g8f7f371be2/arch/arm64/boot/dts/ti/k3-j721e-vision-apps.dtso' like below.

    /*
    &serdes_wiz4 {
    	status = "disabled";
    };
    
    &mhdp {
    	status = "disabled";
    };
    
    &dss {
    	status = "disabled";
    };
    
    &main_i2c1 {
    	status = "disabled";
    };
    */

    Best regards

    Yongsig

  • Hi Yongsig,

    I have not seen this kind of issue yet where we see a regression between 8.6 and 9.0 SDK for Linux display. However, we could do some experiments to do some root causing. Looking through device tree between Linux kernel 5.10 and 6.1 that are used for 8.6 and 9.0 SDK respectively, I see a few changes regarding DP. I will list them out here:

    I think above two bullet points would be a good start in troubleshooting what could be different. If they do not resolve the issue, we can dig a little deeper.

    Regards,

    Takuma

  • Hi Takuma

    First, thanks for replying.

    I tried using two options as below. And both failed to resolve this issue.

    -  

    	dp_pwr_3v3: regulator-dp-pwr {
    		compatible = "regulator-fixed";
    		regulator-name = "dp-pwr";
    		regulator-min-microvolt = <3300000>;
    		regulator-max-microvolt = <3300000>;
    		gpio = <&exp4 0 0>; /* P0 - DP0_PWR_SW_EN */
    		enable-active-high;
    
    		/* Always on for now, until dp-connector driver can handle this */
    		regulator-always-on;
    	};

    -  

    	dp_pwr_3v3: regulator-dp-pwr {
    		compatible = "regulator-fixed";
    		regulator-name = "dp-pwr";
    		regulator-min-microvolt = <3300000>;
    		regulator-max-microvolt = <3300000>;
    		gpio = <&exp4 0 GPIO_ACTIVE_HIGH>; /* P0 - DP0_PWR_SW_EN */
    		enable-active-high;
    
    		/* Always on for now, until dp-connector driver can handle this */
    		regulator-always-on;
    	};

    And serdes4 is defined as below

    &serdes4 {
    	torrent_phy_dp: phy@0 {
    		reg = <0>;
    		resets = <&serdes_wiz4 1>;
    		cdns,phy-type = <PHY_TYPE_DP>;
    		cdns,num-lanes = <4>;
    		cdns,max-bit-rate = <5400>;
    		#phy-cells = <0>;
    	};
    };

    So I modified 'max-bit-rate' to 2700 as PSDK8.6

    But it failed as well.

    It's weird because there is no signal when I use Grabber. (As I mentioned above question, it works in PSDK8.6 with the 'regulator-always-on' option)

    When I connect with Grabber, how can I check if DP has read HDCP well or not? or Is it possible to check the HPD(Hot plugged detect) like hdmi?

    Best regards

    yongsig

  • Hi Yongsig,

    Understood. I tried digging through our driver to see if there are anything that stood out. Listing some observations here:

    There has been some changes to how hotplug events are handled in the driver. For example, I see the following irq changed its behavior somewhat between 9.0 SDK: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/drivers/gpu/drm/bridge/cadence/cdns-mhdp8546-core.c?h=ti-linux-6.1.y#n2379, and 8.6 SDK: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/drivers/gpu/drm/bridge/cadence/cdns-mhdp8546-core.c?h=ti-linux-5.10.y#n2310. An experiment you could try is adding in some printk's to see if you see any differences in behavior between 9.0 and 8.6, and/or try rolling back to the older version if you see some differences.

    Additionally, there is a "cdns,no-hpd" property for the display node that you could add. I think this was used to correct an issue we had with a separate SoC (TDA4VL/J721S2) where the HPD line was incorrectly routed on the board. I think we could use this as a way to troubleshoot whether the HPD is causing issues in our case as well. Details of this can be found in this commit message: https://lore.kernel.org/lkml/20230405142440.191939-3-j-choudhary@ti.com/.

    Otherwise, I also see there is some newly added logic for HDCP here: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/drivers/gpu/drm/bridge/cadence/cdns-mhdp8546-core.c?h=ti-linux-6.1.y#n2487. Although, looking through the device tree, I have some doubts on whether hdcp is enabled since I do not see the register for mhdptx-sapb defined in device tree. I also see on the website of the Grabber the following note: "LGP2 PLUS does not support viewing/recording/streaming of HDCP protected signals" which makes me further have suspicion on whether this is causing issues. Nonetheless, you could also add some print statements in this logic to see which path is being taken to troubleshoot this as well.

    Regards,

    Takuma

  • Hi Takuma.

    There has been some changes to how hotplug events are handled in the driver. For example, I see the following irq changed its behavior somewhat between 9.0 SDK: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/drivers/gpu/drm/bridge/cadence/cdns-mhdp8546-core.c?h=ti-linux-6.1.y#n2379, and 8.6 SDK: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/drivers/gpu/drm/bridge/cadence/cdns-mhdp8546-core.c?h=ti-linux-5.10.y#n2310. An experiment you could try is adding in some printk's to see if you see any differences in behavior between 9.0 and 8.6, and/or try rolling back to the older version if you see some differences.
    Additionally, there is a "cdns,no-hpd" property for the display node that you could add. I think this was used to correct an issue we had with a separate SoC (TDA4VL/J721S2) where the HPD line was incorrectly routed on the board. I think we could use this as a way to troubleshoot whether the HPD is causing issues in our case as well. Details of this can be found in this commit message: https://lore.kernel.org/lkml/20230405142440.191939-3-j-choudhary@ti.com/.

    --> I'm trying to resolve it using these method.

    I had to add an option in ti_arm64_prune.config.

    - CONFIG_LOCALVERSION="-g8f7f371be2"

    and then build, copy cdns-mhdp8546.ko to sdcard.

    after booting, I put modprobe cdns_mhdp8546, then I've checked if the driver is loaded well via lsmod.

    But the screen via Grabber is not displayed still.

    Do you have another idea?

    Best regards

    Yongsig

  • Hi Yongsig,

    Thank you for trying out the experiments. I'll search for some other things that may be related to this issue.

    One thing that I have found so far that I plan to look into is this E2E thread: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1311552/tda4vm-sdk-9-0-patch-for-edp-to-hdmi-bug/5035861#5035861 

    I will try to look into this today and tomorrow deeper, but if you have some bandwidth on your end, please feel free to review this thread as well. Similarities I see is that it is related to an eDP to HDMI adapter, and the issue is seen during migration between 8.6 and 9.0 versions of SDK.

    However, the hard part is that this thread is for the RTOS driver for display instead of the Linux driver for display, so it is unclear how much this is applicable. But, the patch looks pretty short and deals with the timeout for DP configuration training so you could try to experiment around with this logic in the Linux driver if you do not have other ideas or experiments to try out.

    Regards,

    Takuma

  • Actually, DP-to-HDMI works in my case. But I applied this patch and it failed again. 

    I think I found a clue. In PSDK9.0, I can see this message after booting despite patching 'regulator-always-on'.

    [   21.089904] platform connector: deferred probe pending
    [   21.095058] platform regulator-dp-pwr: deferred probe pending

    Also, the screen shows up well via Grabber in PSDK linux 9.1.0.6 (and there is no regulator message in kernel)

    So I've compared the difference between two versions and then applied it to PSDK Linux 9.0.0.8.

    1. Modified and Added DTS list

    • k3-j721e-vision-apps.dtso

    • k3-j721e-mcu-wakeup.dtsi

    • k3-j721e-main.dtsi

    • k3-j721e-evm-virt-mac-client.dtso

    • k3-j721e-common-proc-board.dts

    • k3-j721e-beagleboneai64.dts

    • k3-j721e-beagleboneai64-dsi-rpi-7inch-panel.dtso(added)

    2. \board-support\linux-6.1.33+gitAUTOINC+8f7f371be2-g8f7f371be2\drivers\gpu\drm\bridges\cadence is same as PSDK Linux 9.1.0.8

    3. packages\ti\drv\dss driver of PSDK rtos 9.0.0.2  is same as PSDK rtos 9.1.0.8.

    After patching all the above things, it failed still.

    But there are differences things between two versions. These are messages from 'dmesg | grep "platform*"'.

    If you have another idea, please let me know.

    Best regards

    Yongsig

  • Hi Yongsig,

    Those messages are a bit concerning. Could you send the full dmesg logs from when you have the HDMI grabber connected.

    And could you also provide details about the DP-to-HDMI adapter? May make sense to see if we can procure the same adapter and HDMI grabber to try to reproduce the issue on our end.

    Regards,

    Takuma

  • Hi Takuma,

    I'm using the DP-to-HDMI from GENDER master company.

    https://naroit.co.kr/product/detail.html?product_no=17&cate_no=26&display_group=1#prdDetail

    It's a Korean company but I believe you can read the specifications on the website.

    First, I attached my dtbs. Please go through them.

    4152.dtb.zip

    after updating dtbs, platform regulator-dp-pwr messages were disappeared.

    7446.full_dmesg.txt
    root@j721e-evm:~# dmesg
    [    0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd080]
    [    0.000000] Linux version 6.1.33-g8f7f371be2 (oe-user@oe-host) (aarch64-oe-linux-gcc (GCC) 11.3.0, GNU ld (GNU Binutils) 2.38.20220708) #1 SMP PREEMPT Fri Jul 14 00:39:55 UTC 2023
    [    0.000000] Machine model: Texas Instruments J721e EVM
    [    0.000000] earlycon: ns16550a0 at MMIO32 0x0000000002800000 (options '')
    [    0.000000] printk: bootconsole [ns16550a0] enabled
    [    0.000000] efi: UEFI not found.
    [    0.000000] Reserved memory: created CMA memory pool at 0x00000008e0000000, size 512 MiB
    [    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x00000000a0000000, size 1 MiB
    [    0.000000] OF: reserved mem: initialized node vision-apps-r5f-dma-memory@a0000000, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x00000000a0100000, size 15 MiB
    [    0.000000] OF: reserved mem: initialized node vision-apps-r5f-memory@a0100000, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x00000000a1000000, size 1 MiB
    [    0.000000] OF: reserved mem: initialized node vision-apps-r5f-dma-memory@a1000000, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x00000000a1100000, size 15 MiB
    [    0.000000] OF: reserved mem: initialized node vision-apps-r5f-memory@a1100000, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x00000000a2000000, size 1 MiB
    [    0.000000] OF: reserved mem: initialized node vision-apps-r5f-dma-memory@a2000000, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x00000000a2100000, size 31 MiB
    [    0.000000] OF: reserved mem: initialized node vision-apps-r5f-memory@a2100000, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x00000000a4000000, size 1 MiB
    [    0.000000] OF: reserved mem: initialized node vision-apps-r5f-dma-memory@a4000000, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x00000000a4100000, size 31 MiB
    [    0.000000] OF: reserved mem: initialized node vision-apps-r5f-memory@a4100000, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x00000000a6000000, size 1 MiB
    [    0.000000] OF: reserved mem: initialized node vision-apps-r5f-dma-memory@a6000000, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x00000000a6100000, size 15 MiB
    [    0.000000] OF: reserved mem: initialized node vision-apps-r5f-memory@a6100000, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x00000000a7000000, size 1 MiB
    [    0.000000] OF: reserved mem: initialized node vision-apps-r5f-dma-memory@a7000000, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x00000000a7100000, size 15 MiB
    [    0.000000] OF: reserved mem: initialized node vision-apps-r5f-memory@a7100000, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x00000000a8000000, size 1 MiB
    [    0.000000] OF: reserved mem: initialized node vision-apps-c66-dma-memory@a8000000, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x00000000a8100000, size 15 MiB
    [    0.000000] OF: reserved mem: initialized node vision-apps-c66-memory@a8100000, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x00000000a9000000, size 1 MiB
    [    0.000000] OF: reserved mem: initialized node vision-apps-c66-dma-memory@a9000000, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x00000000a9100000, size 15 MiB
    [    0.000000] OF: reserved mem: initialized node vision-apps-c66-memory@a9100000, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x00000000ac000000, size 96 MiB
    [    0.000000] OF: reserved mem: initialized node vision-apps-dma-memory@ac000000, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x00000000b2000000, size 1 MiB
    [    0.000000] OF: reserved mem: initialized node vision-apps-c71-dma-memory@b2000000, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x00000000b2100000, size 95 MiB
    [    0.000000] OF: reserved mem: initialized node vision-apps-c71-memory@b2100000, compatible id shared-dma-pool
    [    0.000000] OF: reserved mem: initialized node vision_apps_shared-memories, compatible id dma-heap-carveout
    [    0.000000] Reserved memory: created DMA memory pool at 0x00000000d8000000, size 192 MiB
    [    0.000000] OF: reserved mem: initialized node vision-apps-core-heap-memory-lo@d8000000, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x00000000e4000000, size 8 MiB
    [    0.000000] OF: reserved mem: initialized node vision-apps-r5f-virtual-eth-queues@e4000000, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x00000000e4800000, size 24 MiB
    [    0.000000] OF: reserved mem: initialized node vision-apps-r5f-virtual-eth-buffers@e4800000, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x0000000880000000, size 624 MiB
    [    0.000000] OF: reserved mem: initialized node vision-apps-core-heap-memory-hi@880000000, compatible id shared-dma-pool
    [    0.000000] Zone ranges:
    [    0.000000]   DMA      [mem 0x0000000080000000-0x00000000ffffffff]
    [    0.000000]   DMA32    empty
    [    0.000000]   Normal   [mem 0x0000000100000000-0x00000008ffffffff]
    [    0.000000] Movable zone start for each node
    [    0.000000] Early memory node ranges
    [    0.000000]   node   0: [mem 0x0000000080000000-0x000000009e7fffff]
    [    0.000000]   node   0: [mem 0x000000009e800000-0x00000000b7ffffff]
    [    0.000000]   node   0: [mem 0x00000000b8000000-0x00000000d7ffffff]
    [    0.000000]   node   0: [mem 0x00000000d8000000-0x00000000e5ffffff]
    [    0.000000]   node   0: [mem 0x00000000e6000000-0x00000000ffffffff]
    [    0.000000]   node   0: [mem 0x0000000880000000-0x00000008a6ffffff]
    [    0.000000]   node   0: [mem 0x00000008a7000000-0x00000008ffffffff]
    [    0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x00000008ffffffff]
    [    0.000000] psci: probing for conduit method from DT.
    [    0.000000] psci: PSCIv1.1 detected in firmware.
    [    0.000000] psci: Using standard PSCI v0.2 function IDs
    [    0.000000] psci: Trusted OS migration not required
    [    0.000000] psci: SMC Calling Convention v1.2
    [    0.000000] percpu: Embedded 19 pages/cpu s38376 r8192 d31256 u77824
    [    0.000000] pcpu-alloc: s38376 r8192 d31256 u77824 alloc=19*4096
    [    0.000000] pcpu-alloc: [0] 0 [0] 1
    [    0.000000] Detected PIPT I-cache on CPU0
    [    0.000000] CPU features: detected: GIC system register CPU interface
    [    0.000000] CPU features: detected: Spectre-v3a
    [    0.000000] CPU features: detected: Spectre-BHB
    [    0.000000] CPU features: detected: ARM erratum 1742098
    [    0.000000] CPU features: detected: ARM errata 1165522, 1319367, or 1530923
    [    0.000000] alternatives: applying boot alternatives
    [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 1032192
    [    0.000000] Kernel command line: console=ttyS2,115200n8 earlycon=ns16550a,mmio32,0x02800000 root=PARTUUID=0fbe0baf-02 rw rootfstype=ext4 rootwait
    [    0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
    [    0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
    [    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
    [    0.000000] software IO TLB: area num 2.
    [    0.000000] software IO TLB: mapped [mem 0x00000000fbfff000-0x00000000fffff000] (64MB)
    [    0.000000] Memory: 1694412K/4194304K available (12480K kernel code, 1294K rwdata, 4048K rodata, 2176K init, 498K bss, 1975604K reserved, 524288K cma-reserved)
    [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
    [    0.000000] rcu: Preemptible hierarchical RCU implementation.
    [    0.000000] rcu:     RCU event tracing is enabled.
    [    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=2.
    [    0.000000]  Trampoline variant of Tasks RCU enabled.
    [    0.000000]  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=2
    [    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
    [    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
    [    0.000000] GICv3: 960 SPIs implemented
    [    0.000000] GICv3: 0 Extended SPIs implemented
    [    0.000000] Root IRQ handler: gic_handle_irq
    [    0.000000] GICv3: GICv3 features: 16 PPIs
    [    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000001900000
    [    0.000000] ITS [mem 0x01820000-0x0182ffff]
    [    0.000000] GIC: enabling workaround for ITS: Socionext Synquacer pre-ITS
    [    0.000000] ITS@0x0000000001820000: Devices Table too large, reduce ids 20->19
    [    0.000000] ITS@0x0000000001820000: allocated 524288 Devices @8a7800000 (flat, esz 8, psz 64K, shr 0)
    [    0.000000] ITS: using cache flushing for cmd queue
    [    0.000000] GICv3: using LPI property table @0x00000008a7030000
    [    0.000000] GIC: using cache flushing for LPI property table
    [    0.000000] GICv3: CPU0: using allocated LPI pending table @0x00000008a7040000
    [    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.008476] Console: colour dummy device 80x25
    [    0.013041] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=800000)
    [    0.023712] pid_max: default: 32768 minimum: 301
    [    0.028451] LSM: Security Framework initializing
    [    0.033236] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
    [    0.040810] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
    [    0.049665] cblist_init_generic: Setting adjustable number of callback queues.
    [    0.057079] cblist_init_generic: Setting shift to 1 and lim to 1.
    [    0.063340] cblist_init_generic: Setting shift to 1 and lim to 1.
    [    0.069655] rcu: Hierarchical SRCU implementation.
    [    0.074552] rcu:     Max phase no-delay instances is 1000.
    [    0.080083] Platform MSI: msi-controller@1820000 domain created
    [    0.086399] PCI/MSI: /bus@100000/interrupt-controller@1800000/msi-controller@1820000 domain created
    [    0.096421] EFI services will not be available.
    [    0.101179] smp: Bringing up secondary CPUs ...
    [    0.114453] Detected PIPT I-cache on CPU1
    [    0.114517] GICv3: CPU1: found redistributor 1 region 0:0x0000000001920000
    [    0.114529] GICv3: CPU1: using allocated LPI pending table @0x00000008a7050000
    [    0.114564] CPU1: Booted secondary processor 0x0000000001 [0x411fd080]
    [    0.114617] smp: Brought up 1 node, 2 CPUs
    [    0.143962] SMP: Total of 2 processors activated.
    [    0.148766] CPU features: detected: 32-bit EL0 Support
    [    0.154020] CPU features: detected: CRC32 instructions
    [    0.159301] CPU: All CPU(s) started at EL2
    [    0.163482] alternatives: applying system-wide alternatives
    [    0.170122] devtmpfs: initialized
    [    0.181122] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
    [    0.191125] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
    [    0.206606] pinctrl core: initialized pinctrl subsystem
    [    0.212310] DMI not present or invalid.
    [    0.216572] NET: Registered PF_NETLINK/PF_ROUTE protocol family
    [    0.223280] DMA: preallocated 512 KiB GFP_KERNEL pool for atomic allocations
    [    0.230605] DMA: preallocated 512 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
    [    0.238611] DMA: preallocated 512 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
    [    0.246736] audit: initializing netlink subsys (disabled)
    [    0.252367] audit: type=2000 audit(0.164:1): state=initialized audit_enabled=0 res=1
    [    0.252611] thermal_sys: Registered thermal governor 'step_wise'
    [    0.260288] thermal_sys: Registered thermal governor 'power_allocator'
    [    0.266501] cpuidle: using governor menu
    [    0.277261] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
    [    0.284229] ASID allocator initialised with 65536 entries
    [    0.299889] platform a000000.dp-bridge: Fixed dependency cycle(s) with /bus@100000/dss@4a00000
    [    0.311196] platform a000000.dp-bridge: Fixed dependency cycle(s) with /connector
    [    0.319086] KASLR disabled due to lack of seed
    [    0.326669] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
    [    0.333611] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page
    [    0.340014] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages
    [    0.346947] HugeTLB: 0 KiB vmemmap can be freed for a 32.0 MiB page
    [    0.353348] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
    [    0.360281] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page
    [    0.366683] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages
    [    0.373616] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page
    [    0.380989] k3-chipinfo 43000014.chipid: Family:J721E rev:SR2.0 JTAGID[0x1bb6402f] Detected
    [    0.390253] iommu: Default domain type: Translated
    [    0.395240] iommu: DMA domain TLB invalidation policy: strict mode
    [    0.401765] SCSI subsystem initialized
    [    0.405674] libata version 3.00 loaded.
    [    0.405767] usbcore: registered new interface driver usbfs
    [    0.411394] usbcore: registered new interface driver hub
    [    0.416830] usbcore: registered new device driver usb
    [    0.422293] pps_core: LinuxPPS API ver. 1 registered
    [    0.427367] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
    [    0.436707] PTP clock support registered
    [    0.440796] EDAC MC: Ver: 3.0.0
    [    0.444582] FPGA manager framework
    [    0.448094] Advanced Linux Sound Architecture Driver Initialized.
    [    0.454729] clocksource: Switched to clocksource arch_sys_counter
    [    0.461080] VFS: Disk quotas dquot_6.6.0
    [    0.465113] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    [    0.475118] Carveout Heap: Exported 512 MiB at 0x00000000b8000000
    [    0.481419] NET: Registered PF_INET protocol family
    [    0.486605] IP idents hash table entries: 65536 (order: 7, 524288 bytes, linear)
    [    0.495620] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes, linear)
    [    0.504390] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
    [    0.512315] TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear)
    [    0.520527] TCP bind hash table entries: 32768 (order: 8, 1048576 bytes, linear)
    [    0.529240] TCP: Hash tables configured (established 32768 bind 32768)
    [    0.536042] UDP hash table entries: 2048 (order: 4, 65536 bytes, linear)
    [    0.542967] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear)
    [    0.550428] NET: Registered PF_UNIX/PF_LOCAL protocol family
    [    0.556584] RPC: Registered named UNIX socket transport module.
    [    0.562652] RPC: Registered udp transport module.
    [    0.567456] RPC: Registered tcp transport module.
    [    0.572258] RPC: Registered tcp NFSv4.1 backchannel transport module.
    [    0.578850] NET: Registered PF_XDP protocol family
    [    0.583752] PCI: CLS 0 bytes, default 64
    [    0.588167] hw perfevents: enabled with armv8_cortex_a72 PMU driver, 7 counters available
    [    0.597368] Initialise system trusted keyrings
    [    0.602037] workingset: timestamp_bits=46 max_order=20 bucket_order=0
    [    0.611269] squashfs: version 4.0 (2009/01/31) Phillip Lougher
    [    0.617582] NFS: Registering the id_resolver key type
    [    0.622768] Key type id_resolver registered
    [    0.627039] Key type id_legacy registered
    [    0.631163] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
    [    0.638011] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
    [    0.645669] 9p: Installing v9fs 9p2000 file system support
    [    0.670750] Key type asymmetric registered
    [    0.674933] Asymmetric key parser 'x509' registered
    [    0.679941] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
    [    0.687598] io scheduler mq-deadline registered
    [    0.692244] io scheduler kyber registered
    [    0.698447] pinctrl-single 4301c000.pinctrl: 94 pins, size 376
    [    0.704720] pinctrl-single 11c000.pinctrl: 173 pins, size 692
    [    0.711078] pinctrl-single a40000.pinctrl: 512 pins, size 2048
    [    0.721709] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
    [    0.729452] arm-smmu-v3 36600000.iommu: ias 48-bit, oas 48-bit (features 0x00001faf)
    [    0.737687] arm-smmu-v3 36600000.iommu: allocated 65536 entries for cmdq
    [    0.744841] arm-smmu-v3 36600000.iommu: allocated 32768 entries for evtq
    [    0.752882] arm-smmu-v3 36600000.iommu: msi_domain absent - falling back to wired irqs
    [    0.764044] loop: module loaded
    [    0.768121] megasas: 07.719.03.00-rc1
    [    0.774134] tun: Universal TUN/TAP device driver, 1.6
    [    0.779691] thunder_xcv, ver 1.0
    [    0.783005] thunder_bgx, ver 1.0
    [    0.786308] nicpf, ver 1.0
    [    0.789329] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version
    [    0.796713] hns3: Copyright (c) 2017 Huawei Corporation.
    [    0.802163] hclge is initializing
    [    0.805561] e1000: Intel(R) PRO/1000 Network Driver
    [    0.810542] e1000: Copyright (c) 1999-2006 Intel Corporation.
    [    0.816431] e1000e: Intel(R) PRO/1000 Network Driver
    [    0.821500] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
    [    0.827559] igb: Intel(R) Gigabit Ethernet Network Driver
    [    0.833073] igb: Copyright (c) 2007-2014 Intel Corporation.
    [    0.838777] igbvf: Intel(R) Gigabit Virtual Function Network Driver
    [    0.845179] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
    [    0.851298] sky2: driver version 1.30
    [    0.855463] VFIO - User Level meta-driver version: 0.3
    [    0.861166] usbcore: registered new interface driver usb-storage
    [    0.867782] i2c_dev: i2c /dev entries driver
    [    0.873221] sdhci: Secure Digital Host Controller Interface driver
    [    0.879549] sdhci: Copyright(c) Pierre Ossman
    [    0.884331] Synopsys Designware Multimedia Card Interface Driver
    [    0.890764] sdhci-pltfm: SDHCI platform and OF driver helper
    [    0.897116] ledtrig-cpu: registered to indicate activity on CPUs
    [    0.903361] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
    [    0.910122] usbcore: registered new interface driver usbhid
    [    0.915816] usbhid: USB HID core driver
    [    0.920527] optee: probing for conduit method.
    [    0.925089] optee: revision 3.20 (8e74d476)
    [    0.941509] optee: dynamic shared memory is enabled
    [    0.950990] optee: initialized driver
    [    0.956160] Initializing XFRM netlink socket
    [    0.960550] NET: Registered PF_PACKET protocol family
    [    0.965783] 9pnet: Installing 9P2000 support
    [    0.970180] Key type dns_resolver registered
    [    0.974770] registered taskstats version 1
    [    0.978966] Loading compiled-in X.509 certificates
    [    0.989177] ti-sci 44083000.system-controller: ABI: 3.1 (firmware rev 0x0009 '9.0.6--v09.00.06 (Kool Koala)')
    [    1.049627] omap_i2c 42120000.i2c: bus 0 rev0.12 at 400 kHz
    [    1.056030] pca953x 1-0020: supply vcc not found, using dummy regulator
    [    1.062859] pca953x 1-0020: using no AI
    [    1.091421] pca953x 1-0022: supply vcc not found, using dummy regulator
    [    1.098237] pca953x 1-0022: using AI
    [    1.102502] gpio-480 (CTRL_PM_I2C_OE): hogged as output/high
    [    1.108478] gpio-481 (MCASP/TRACE_MUX_S0): hogged as output/low
    [    1.114719] gpio-482 (MCASP/TRACE_MUX_S1): hogged as output/high
    [    1.121222] omap_i2c 2000000.i2c: bus 1 rev0.12 at 400 kHz
    [    1.127401] omap_i2c 2010000.i2c: bus 2 rev0.12 at 400 kHz
    [    1.134264] omap_i2c 2020000.i2c: bus 3 rev0.12 at 400 kHz
    [    1.140393] pca953x 4-0020: supply vcc not found, using dummy regulator
    [    1.147227] pca953x 4-0020: using no AI
    [    1.175198] omap_i2c 2030000.i2c: bus 4 rev0.12 at 400 kHz
    [    1.181117] ti-sci-intr 42200000.interrupt-controller: Interrupt Router 137 domain created
    [    1.189678] ti-sci-intr bus@100000:interrupt-controller@a00000: Interrupt Router 131 domain created
    [    1.199026] ti-sci-intr 310e0000.interrupt-controller: Interrupt Router 213 domain created
    [    1.207661] ti-sci-inta 33d00000.interrupt-controller: Interrupt Aggregator domain 209 created
    [    1.224336] k3-ringacc 2b800000.ringacc: Ring Accelerator probed rings:286, gp-rings[96,20] sci-dev-id:235
    [    1.234233] k3-ringacc 2b800000.ringacc: dma-ring-reset-quirk: disabled
    [    1.240998] k3-ringacc 2b800000.ringacc: RA Proxy rev. 66346100, num_proxies:64
    [    1.250147] k3-ringacc 3c000000.ringacc: Ring Accelerator probed rings:1024, gp-rings[440,150] sci-dev-id:211
    [    1.260315] k3-ringacc 3c000000.ringacc: dma-ring-reset-quirk: disabled
    [    1.267074] k3-ringacc 3c000000.ringacc: RA Proxy rev. 66346100, num_proxies:64
    [    1.275125] 40a00000.serial: ttyS1 at MMIO 0x40a00000 (irq = 193, base_baud = 6000000) is a 8250
    [    1.284627] 2800000.serial: ttyS2 at MMIO 0x2800000 (irq = 194, base_baud = 3000000) is a 8250
    [    1.293481] printk: console [ttyS2] enabled
    [    1.301925] printk: bootconsole [ns16550a0] disabled
    [    1.312382] 2810000.serial: ttyS3 at MMIO 0x2810000 (irq = 195, base_baud = 3000000) is a 8250
    [    1.321396] 2840000.serial: ttyS0 at MMIO 0x2840000 (irq = 196, base_baud = 3000000) is a 8250
    [    1.332298] davinci_mdio 46000f00.mdio: Configuring MDIO in manual mode
    [    1.378734] davinci_mdio 46000f00.mdio: davinci mdio revision 9.7, bus freq 1000000
    [    1.387227] davinci_mdio 46000f00.mdio: phy[0]: device 46000f00.mdio:00, driver TI DP83867
    [    1.395499] am65-cpsw-nuss 46000000.ethernet: initializing am65 cpsw nuss version 0x6BA00101, cpsw version 0x6BA80100 Ports: 2 quirks:00000000
    [    1.408305] am65-cpsw-nuss 46000000.ethernet: initialized cpsw ale version 1.4
    [    1.415513] am65-cpsw-nuss 46000000.ethernet: ALE Table size 64
    [    1.421752] pps pps0: new PPS source ptp0
    [    1.425881] am65-cpsw-nuss 46000000.ethernet: CPTS ver 0x4e8a010a, freq:500000000, add_val:1 pps:1
    [    1.436402] am65-cpts 310d0000.cpts: CPTS ver 0x4e8a010a, freq:200000000, add_val:4 pps:0
    [    1.546398] mmc0: CQHCI version 5.10
    [    1.590755] mmc0: SDHCI controller on 4f80000.mmc [4f80000.mmc] using ADMA 64-bit
    [    1.682385] mmc0: Command Queue Engine enabled
    [    1.686846] mmc0: new HS200 MMC card at address 0001
    [    1.692321] mmcblk0: mmc0:0001 S0J56X 14.8 GiB
    [    1.698318] mmcblk0boot0: mmc0:0001 S0J56X 31.5 MiB
    [    1.704216] mmcblk0boot1: mmc0:0001 S0J56X 31.5 MiB
    [    1.709909] mmcblk0rpmb: mmc0:0001 S0J56X 4.00 MiB, chardev (240:0)
    [    1.882789] tps6594-rtc tps6594-rtc.4.auto: registered as rtc0
    [    1.888757] tps6594-rtc tps6594-rtc.4.auto: hctosys: unable to read the hardware clock
    [    2.160087] pca953x 2-0020: supply vcc not found, using dummy regulator
    [    2.166777] pca953x 2-0020: using no AI
    [    2.191712] omap-mailbox 31f80000.mailbox: omap mailbox rev 0x66fc7100
    [    2.198546] omap-mailbox 31f81000.mailbox: omap mailbox rev 0x66fc7100
    [    2.205360] omap-mailbox 31f82000.mailbox: omap mailbox rev 0x66fc7100
    [    2.212175] omap-mailbox 31f83000.mailbox: omap mailbox rev 0x66fc7100
    [    2.218971] omap-mailbox 31f84000.mailbox: omap mailbox rev 0x66fc7100
    [    2.233328] ti-udma 285c0000.dma-controller: Channels: 26 (tchan: 13, rchan: 13, gp-rflow: 8)
    [    2.244169] ti-udma 31150000.dma-controller: Channels: 122 (tchan: 61, rchan: 61, gp-rflow: 16)
    [    2.258137] spi-nor spi0.0: mt35xu512aba (65536 Kbytes)
    [    2.263438] 8 fixed-partitions partitions found on MTD device 47040000.spi.0
    [    2.270475] Creating 8 MTD partitions on "47040000.spi.0":
    [    2.275946] 0x000000000000-0x000000080000 : "ospi.tiboot3"
    [    2.282053] 0x000000080000-0x000000280000 : "ospi.tispl"
    [    2.287839] 0x000000280000-0x000000680000 : "ospi.u-boot"
    [    2.293678] 0x000000680000-0x0000006a0000 : "ospi.env"
    [    2.299299] 0x0000006a0000-0x0000006c0000 : "ospi.env.backup"
    [    2.305482] 0x0000006c0000-0x0000007c0000 : "ospi.sysfw"
    [    2.311254] 0x000000800000-0x000003fc0000 : "ospi.rootfs"
    [    2.317110] 0x000003fe0000-0x000004000000 : "ospi.phypattern"
    [    2.326148] spi-nor spi1.0: mt25qu512a (65536 Kbytes)
    [    2.331251] 8 fixed-partitions partitions found on MTD device 47050000.spi.0
    [    2.338287] Creating 8 MTD partitions on "47050000.spi.0":
    [    2.343758] 0x000000000000-0x000000080000 : "qspi.tiboot3"
    [    2.349773] 0x000000080000-0x000000280000 : "qspi.tispl"
    [    2.355537] 0x000000280000-0x000000680000 : "qspi.u-boot"
    [    2.361392] 0x000000680000-0x0000006a0000 : "qspi.env"
    [    2.366981] 0x0000006a0000-0x0000006c0000 : "qspi.env.backup"
    [    2.373201] 0x0000006c0000-0x0000007c0000 : "qspi.sysfw"
    [    2.379005] 0x000000800000-0x000003fc0000 : "qspi.rootfs"
    [    2.384867] 0x000003fe0000-0x000004000000 : "qspi.phypattern"
    [    2.391745] davinci_mdio 46000f00.mdio: Configuring MDIO in manual mode
    [    2.434733] davinci_mdio 46000f00.mdio: davinci mdio revision 9.7, bus freq 1000000
    [    2.443219] davinci_mdio 46000f00.mdio: phy[0]: device 46000f00.mdio:00, driver TI DP83867
    [    2.451489] am65-cpsw-nuss 46000000.ethernet: initializing am65 cpsw nuss version 0x6BA00101, cpsw version 0x6BA80100 Ports: 2 quirks:00000000
    [    2.464297] am65-cpsw-nuss 46000000.ethernet: initialized cpsw ale version 1.4
    [    2.471504] am65-cpsw-nuss 46000000.ethernet: ALE Table size 64
    [    2.477738] pps pps0: new PPS source ptp1
    [    2.481899] am65-cpsw-nuss 46000000.ethernet: CPTS ver 0x4e8a010a, freq:500000000, add_val:1 pps:1
    [    2.492410] am65-cpsw-nuss 46000000.ethernet: set new flow-id-base 48
    [    2.501325] mmc1: CQHCI version 5.10
    [    2.509093] input: gpio-keys as /devices/platform/gpio-keys/input/input0
    [    2.531290] ALSA device list:
    [    2.534250]   No soundcards found.
    [    2.546476] mmc1: SDHCI controller on 4fb0000.mmc [4fb0000.mmc] using ADMA 64-bit
    [    2.554051] Waiting for root device PARTUUID=0fbe0baf-02...
    [    2.613179] mmc1: new ultra high speed DDR50 SDHC card at address aaaa
    [    2.620126] mmcblk1: mmc1:aaaa SL32G 29.7 GiB
    [    2.629357]  mmcblk1: p1 p2
    [    3.070455] EXT4-fs (mmcblk1p2): recovery complete
    [    3.076110] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Quota mode: none.
    [    3.084654] VFS: Mounted root (ext4 filesystem) on device 179:98.
    [    3.098453] devtmpfs: mounted
    [    3.102586] Freeing unused kernel memory: 2176K
    [    3.107208] Run /sbin/init as init process
    [    3.111296]   with arguments:
    [    3.111298]     /sbin/init
    [    3.111300]   with environment:
    [    3.111302]     HOME=/
    [    3.111304]     TERM=linux
    [    3.332885] systemd[1]: System time before build time, advancing clock.
    [    3.383055] NET: Registered PF_INET6 protocol family
    [    3.388539] Segment Routing with IPv6
    [    3.392219] In-situ OAM (IOAM) with IPv6
    [    3.428828] systemd[1]: systemd 250.5+ 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 -BZIP2 -LZ4 -XZ -ZLIB +ZSTD -BPF_FRAMEWORK +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=hybrid)
    [    3.460203] systemd[1]: Detected architecture arm64.
    [    3.550716] systemd[1]: Hostname set to <j721e-evm>.
    [    3.643906] systemd-sysv-generator[145]: SysV service '/etc/init.d/thermal-zone-init' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
    [    3.669669] systemd-sysv-generator[145]: SysV service '/etc/init.d/umountfs' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
    [    3.694060] systemd-sysv-generator[145]: SysV service '/etc/init.d/umountnfs.sh' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
    [    3.718665] systemd-sysv-generator[145]: SysV service '/etc/init.d/single' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
    [    3.742405] systemd-sysv-generator[145]: SysV service '/etc/init.d/netopeer2-server' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
    [    3.767445] systemd-sysv-generator[145]: SysV service '/etc/init.d/psplash.sh' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
    [    3.791445] systemd-sysv-generator[145]: SysV service '/etc/init.d/inetd.busybox' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
    [    3.817112] systemd-sysv-generator[145]: SysV service '/etc/init.d/reboot' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
    [    3.841638] systemd-sysv-generator[145]: SysV service '/etc/init.d/sysrepo' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
    [    3.865382] systemd-sysv-generator[145]: SysV service '/etc/init.d/autolaunch-demo' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
    [    3.889809] systemd-sysv-generator[145]: SysV service '/etc/init.d/netperf' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
    [    3.915138] systemd-sysv-generator[145]: SysV service '/etc/init.d/save-rtc.sh' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
    [    3.939551] systemd-sysv-generator[145]: SysV service '/etc/init.d/sendsigs' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
    [    3.963430] systemd-sysv-generator[145]: SysV service '/etc/init.d/docker.init' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
    [    3.987527] systemd-sysv-generator[145]: SysV service '/etc/init.d/halt' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
    [    4.011126] systemd-sysv-generator[145]: SysV service '/etc/init.d/telnetd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
    [    4.034863] systemd-sysv-generator[145]: SysV service '/etc/init.d/dropbear' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
    [    4.198669] systemd[1]: /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.
    [    4.246086] systemd[1]: /etc/systemd/system/sync-clocks.service:11: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
    [    4.298611] systemd[1]: Queued start job for default target Graphical Interface.
    [    4.336953] systemd[1]: Created slice Slice /system/getty.
    [    4.360209] systemd[1]: Created slice Slice /system/modprobe.
    [    4.384130] systemd[1]: Created slice Slice /system/serial-getty.
    [    4.407823] systemd[1]: Created slice User and Session Slice.
    [    4.430968] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    [    4.454874] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
    [    4.478944] systemd[1]: Reached target Path Units.
    [    4.494806] systemd[1]: Reached target Remote File Systems.
    [    4.514787] systemd[1]: Reached target Slice Units.
    [    4.530799] systemd[1]: Reached target Swaps.
    [    4.581891] systemd[1]: Listening on RPCbind Server Activation Socket.
    [    4.602894] systemd[1]: Reached target RPC Port Mapper.
    [    4.627999] systemd[1]: Listening on Process Core Dump Socket.
    [    4.650972] systemd[1]: Listening on initctl Compatibility Named Pipe.
    [    4.675160] systemd[1]: Listening on Journal Audit Socket.
    [    4.695048] systemd[1]: Listening on Journal Socket (/dev/log).
    [    4.715063] systemd[1]: Listening on Journal Socket.
    [    4.731147] systemd[1]: Listening on Network Service Netlink Socket.
    [    4.755135] systemd[1]: Listening on udev Control Socket.
    [    4.775002] systemd[1]: Listening on udev Kernel Socket.
    [    4.795015] systemd[1]: Listening on User Database Manager Socket.
    [    4.839122] systemd[1]: Mounting Huge Pages File System...
    [    4.857408] systemd[1]: Mounting POSIX Message Queue File System...
    [    4.881523] systemd[1]: Mounting Kernel Debug File System...
    [    4.899070] systemd[1]: Kernel Trace File System was skipped because of a failed condition check (ConditionPathExists=/sys/kernel/tracing).
    [    4.917271] systemd[1]: Mounting Temporary Directory /tmp...
    [    4.938034] systemd[1]: Starting Create List of Static Device Nodes...
    [    4.979266] systemd[1]: Starting Load Kernel Module configfs...
    [    5.001572] systemd[1]: Starting Load Kernel Module drm...
    [    5.025533] systemd[1]: Starting Load Kernel Module fuse...
    [    5.104154] fuse: init (API version 7.37)
    [    5.123334] systemd[1]: Starting Start psplash boot splash screen...
    [    5.150690] systemd[1]: Starting RPC Bind...
    [    5.170994] systemd[1]: File System Check on Root Device was skipped because of a failed condition check (ConditionPathIsReadWrite=!/).
    [    5.203559] systemd[1]: Starting Journal Service...
    [    5.233741] systemd[1]: Starting Load Kernel Modules...
    [    5.250660] cryptodev: loading out-of-tree module taints kernel.
    [    5.257832] cryptodev: driver 1.12 loaded.
    [    5.280746] systemd[1]: Starting Generate network units from Kernel command line...
    [    5.309947] systemd[1]: Starting Remount Root and Kernel File Systems...
    [    5.325282] EXT4-fs (mmcblk1p2): re-mounted. Quota mode: none.
    [    5.334629] systemd[1]: Starting Coldplug All udev Devices...
    [    5.355556] systemd[1]: Started RPC Bind.
    [    5.371168] systemd[1]: Started Journal Service.
    [    5.722359] systemd-journald[160]: Received client request to flush runtime journal.
    [    5.933225] audit: type=1334 audit(1651167747.600:2): prog-id=5 op=LOAD
    [    5.940196] audit: type=1334 audit(1651167747.608:3): prog-id=6 op=LOAD
    [    6.417080] random: crng init done
    [    6.451229] CAN device driver interface
    [    6.488301] j721e-pcie-host 2900000.pcie: host bridge /bus@100000/pcie@2900000 ranges:
    [    6.500771] ina2xx 3-0040: power monitor ina226 (Rshunt = 10000 uOhm)
    [    6.500897] j721e-pcie-host 2900000.pcie:       IO 0x0010001000..0x0010010fff -> 0x0010001000
    [    6.515720] ina2xx 3-0041: power monitor ina226 (Rshunt = 10000 uOhm)
    [    6.517271] j721e-pcie-host 2900000.pcie:      MEM 0x0010011000..0x0017ffffff -> 0x0010011000
    [    6.530718] j721e-pcie-host 2900000.pcie:   IB MEM 0x0000000000..0xffffffffffff -> 0x0000000000
    [    6.536766] ina2xx 3-0042: power monitor ina226 (Rshunt = 10000 uOhm)
    [    6.547889] ina2xx 3-0043: power monitor ina226 (Rshunt = 10000 uOhm)
    [    6.559857] ina2xx 3-0044: power monitor ina226 (Rshunt = 10000 uOhm)
    [    6.571252] ina2xx 3-0045: power monitor ina226 (Rshunt = 5000 uOhm)
    [    6.583748] ina2xx 3-0046: power monitor ina226 (Rshunt = 10000 uOhm)
    [    6.591467] ina2xx 3-0047: power monitor ina226 (Rshunt = 10000 uOhm)
    [    6.599366] ina2xx 3-0048: power monitor ina226 (Rshunt = 10000 uOhm)
    [    6.612030] ina2xx 3-0049: power monitor ina226 (Rshunt = 10000 uOhm)
    [    6.620289] ina2xx 3-004a: power monitor ina226 (Rshunt = 10000 uOhm)
    [    6.627852] ina2xx 3-004b: power monitor ina226 (Rshunt = 10000 uOhm)
    [    6.635618] ina2xx 3-004c: power monitor ina226 (Rshunt = 10000 uOhm)
    [    6.647611] ina2xx 3-004d: power monitor ina226 (Rshunt = 10000 uOhm)
    [    6.654872] ina2xx 3-004e: power monitor ina226 (Rshunt = 10000 uOhm)
    [    6.663097] ina2xx 3-004f: power monitor ina226 (Rshunt = 10000 uOhm)
    [    6.732747] mc: Linux media interface: v0.10
    [    6.752619] k3-dsp-rproc 4d80800000.dsp: assigned reserved memory node vision-apps-c66-dma-memory@a9000000
    [    6.780984] videodev: Linux video capture interface: v2.00
    [    6.794004] k3-dsp-rproc 4d80800000.dsp: configured DSP for IPC-only mode
    [    6.804586] remoteproc remoteproc0: 4d80800000.dsp is available
    [    6.815077] remoteproc remoteproc0: attaching to 4d80800000.dsp
    [    6.821996] k3-dsp-rproc 4d80800000.dsp: DSP initialized in IPC-only mode
    [    6.829850] rproc-virtio rproc-virtio.10.auto: assigned reserved memory node vision-apps-c66-dma-memory@a9000000
    [    6.841495] virtio_rpmsg_bus virtio0: rpmsg host is online
    [    6.845329] virtio_rpmsg_bus virtio0: creating channel rpmsg_chrdev addr 0xd
    [    6.851392] rproc-virtio rproc-virtio.10.auto: registered virtio0 (type 7)
    [    6.866677] remoteproc remoteproc0: remote processor 4d80800000.dsp is now attached
    [    6.885716] k3-dsp-rproc 4d81800000.dsp: assigned reserved memory node vision-apps-c66-dma-memory@a8000000
    [    6.888527] PVR_K:  193: Device: 4e20000000.gpu
    [    6.901005] PVR_K:  193: Read BVNC 22.104.208.318 from HW device registers
    [    6.902038] k3-dsp-rproc 4d81800000.dsp: configured DSP for IPC-only mode
    [    6.908998] PVR_K:  193: RGX Device registered with BVNC 22.104.208.318
    [    6.915018] remoteproc remoteproc1: 4d81800000.dsp is available
    [    6.927715] remoteproc remoteproc1: attaching to 4d81800000.dsp
    [    6.931791] [drm] Initialized pvr 23.1.6404501 20170530 for 4e20000000.gpu on minor 0
    [    6.934290] k3-dsp-rproc 4d81800000.dsp: DSP initialized in IPC-only mode
    [    6.948656] rproc-virtio rproc-virtio.11.auto: assigned reserved memory node vision-apps-c66-dma-memory@a8000000
    [    6.964474] virtio_rpmsg_bus virtio1: rpmsg host is online
    [    6.968037] virtio_rpmsg_bus virtio1: creating channel rpmsg_chrdev addr 0xd
    [    6.970116] rproc-virtio rproc-virtio.11.auto: registered virtio1 (type 7)
    [    6.984483] remoteproc remoteproc1: remote processor 4d81800000.dsp is now attached
    [    6.992922] k3-dsp-rproc 64800000.dsp: assigned reserved memory node vision-apps-c71-dma-memory@b2000000
    [    7.007916] k3-dsp-rproc 64800000.dsp: configured DSP for IPC-only mode
    [    7.014666] remoteproc remoteproc2: 64800000.dsp is available
    [    7.021757] remoteproc remoteproc2: attaching to 64800000.dsp
    [    7.028961] remoteproc remoteproc2: unsupported resource 65538
    [    7.036015] k3-dsp-rproc 64800000.dsp: DSP initialized in IPC-only mode
    [    7.044069] rproc-virtio rproc-virtio.12.auto: assigned reserved memory node vision-apps-c71-dma-memory@b2000000
    [    7.056535] virtio_rpmsg_bus virtio2: rpmsg host is online
    [    7.062133] virtio_rpmsg_bus virtio2: creating channel rpmsg_chrdev addr 0xd
    [    7.070133] rproc-virtio rproc-virtio.12.auto: registered virtio2 (type 7)
    [    7.130916] remoteproc remoteproc2: remote processor 64800000.dsp is now attached
    [    7.152921] cdns-mhdp8546 a000000.dp-bridge: invalid resource
    [    7.186069] img_enc 4200000.video-encoder: vxe_enc_probe: using heap 1 for internal alloc
    [    7.189371] cdns-mhdp8546 a000000.dp-bridge: Failed to get SAPB memory resource, HDCP not supported
    [    7.221829] img_enc 4200000.video-encoder: encoder registered as /dev/video0
    [    7.234239] img_dec 4300000.video-decoder: decoder registered as /dev/video1
    [    7.248042] [drm] Initialized tidss 1.0.0 20180215 for 4a00000.dss on minor 1
    [    7.265164] tidss 4a00000.dss: [drm] Cannot find any crtc or sizes
    [    7.353973] Console: switching to colour frame buffer device 240x67
    [    7.377013] tidss 4a00000.dss: [drm] fb0: tidssdrmfb frame buffer device
    [    7.482028] audit: type=1334 audit(1651185532.716:4): prog-id=7 op=LOAD
    [    7.490302] audit: type=1334 audit(1651185532.728:5): prog-id=8 op=LOAD
    [    7.604387] j721e-pcie-host 2900000.pcie: PCI host bridge to bus 0000:00
    [    7.696601] pci_bus 0000:00: root bus resource [bus 00-ff]
    [    7.745132] pci_bus 0000:00: root bus resource [io  0x0000-0xffff] (bus address [0x10001000-0x10010fff])
    [    7.754878] pci_bus 0000:00: root bus resource [mem 0x10011000-0x17ffffff]
    [    7.761983] pci 0000:00:00.0: [104c:b00d] type 01 class 0x060400
    [    7.768505] pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
    [    7.769148] Bluetooth: Core ver 2.22
    [    7.778404] pci 0000:00:00.0: supports D1
    [    7.786617] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
    [    7.793322] pci 0000:00:00.0: reg 0x224: [mem 0x00000000-0x003fffff 64bit]
    [    7.797927] NET: Registered PF_BLUETOOTH protocol family
    [    7.800861] pci 0000:00:00.0: VF(n) BAR0 space: [mem 0x00000000-0x00ffffff 64bit] (contains BAR0 for 4 VFs)
    [    7.810678] Bluetooth: HCI device and connection manager initialized
    [    7.818405] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
    [    7.830697] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
    [    7.832778] Bluetooth: HCI socket layer initialized
    [    7.837474] pci 0000:00:00.0: BAR 7: assigned [mem 0x10400000-0x113fffff 64bit]
    [    7.849663] pci 0000:00:00.0: PCI bridge to [bus 01]
    [    7.852840] Bluetooth: L2CAP socket layer initialized
    [    7.856434] pcieport 0000:00:00.0: PME: Signaling with IRQ 820
    [    7.861092] Bluetooth: SCO socket layer initialized
    [    7.867156] pcieport 0000:00:00.0: AER: enabled with IRQ 820
    [    7.877233] j721e-pcie-host 2910000.pcie: host bridge /bus@100000/pcie@2910000 ranges:
    [    7.885306] j721e-pcie-host 2910000.pcie:       IO 0x0018001000..0x0018010fff -> 0x0018001000
    [    7.893926] j721e-pcie-host 2910000.pcie:      MEM 0x0018011000..0x001fffffff -> 0x0018011000
    [    7.902512] j721e-pcie-host 2910000.pcie:   IB MEM 0x0000000000..0xffffffffffff -> 0x0000000000
    [    8.120821] cfg80211: Loading compiled-in X.509 certificates for regulatory database
    [    8.150003] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
    [    8.181097] platform 41000000.r5f: R5F core may have been powered on by a different host, programmed state (0) != actual state (1)
    [    8.207560] platform 41000000.r5f: configured R5F for IPC-only mode
    [    8.217598] platform 41000000.r5f: assigned reserved memory node vision-apps-r5f-dma-memory@a0000000
    [    8.230530] remoteproc remoteproc3: 41000000.r5f is available
    [    8.236435] remoteproc remoteproc3: attaching to 41000000.r5f
    [    8.242697] platform 41000000.r5f: R5F core initialized in IPC-only mode
    [    8.249466] rproc-virtio rproc-virtio.15.auto: assigned reserved memory node vision-apps-r5f-dma-memory@a0000000
    [    8.260160] virtio_rpmsg_bus virtio3: rpmsg host is online
    [    8.265767] rproc-virtio rproc-virtio.15.auto: registered virtio3 (type 7)
    [    8.278022] remoteproc remoteproc3: remote processor 41000000.r5f is now attached
    [    8.278065] virtio_rpmsg_bus virtio3: creating channel ti.ipc4.ping-pong addr 0xd
    [    8.294379] platform 5c00000.r5f: configured R5F for IPC-only mode
    [    8.303130] platform 5c00000.r5f: assigned reserved memory node vision-apps-r5f-dma-memory@a2000000
    [    8.303393] virtio_rpmsg_bus virtio3: creating channel rpmsg_chrdev addr 0xe
    [    8.313659] remoteproc remoteproc4: 5c00000.r5f is available
    [    8.325158] remoteproc remoteproc4: attaching to 5c00000.r5f
    [    8.332202] platform 5c00000.r5f: R5F core initialized in IPC-only mode
    [    8.345635] rproc-virtio rproc-virtio.16.auto: assigned reserved memory node vision-apps-r5f-dma-memory@a2000000
    [    8.351472] am65-cpsw-nuss 46000000.ethernet eth0: PHY [46000f00.mdio:00] driver [TI DP83867] (irq=POLL)
    [    8.379668] am65-cpsw-nuss 46000000.ethernet eth0: configuring for phy/rgmii-rxid link mode
    [    8.384927] virtio_rpmsg_bus virtio4: rpmsg host is online
    [    8.397169] virtio_rpmsg_bus virtio4: creating channel rpmsg_chrdev addr 0xd
    [    8.405646] rproc-virtio rproc-virtio.16.auto: registered virtio4 (type 7)
    [    8.414462] remoteproc remoteproc4: remote processor 5c00000.r5f is now attached
    [    8.426584] platform 5d00000.r5f: configured R5F for IPC-only mode
    [    8.435297] platform 5d00000.r5f: assigned reserved memory node vision-apps-r5f-dma-memory@a4000000
    [    8.446164] remoteproc remoteproc5: 5d00000.r5f is available
    [    8.455252] remoteproc remoteproc5: attaching to 5d00000.r5f
    [    8.461796] platform 5d00000.r5f: R5F core initialized in IPC-only mode
    [    8.468508] rproc-virtio rproc-virtio.17.auto: assigned reserved memory node vision-apps-r5f-dma-memory@a4000000
    [    8.481740] virtio_rpmsg_bus virtio5: rpmsg host is online
    [    8.487517] virtio_rpmsg_bus virtio2: creating channel rpmsg_chrdev addr 0x15
    [    8.495287] rproc-virtio rproc-virtio.17.auto: registered virtio5 (type 7)
    [    8.502323] virtio_rpmsg_bus virtio2: creating channel ti.ipc4.ping-pong addr 0xe
    [    8.510063] virtio_rpmsg_bus virtio4: creating channel rpmsg_chrdev addr 0x15
    [    8.517357] virtio_rpmsg_bus virtio5: creating channel rpmsg_chrdev addr 0xd
    [    8.524566] virtio_rpmsg_bus virtio5: creating channel rpmsg_chrdev addr 0x15
    [    8.532058] virtio_rpmsg_bus virtio5: creating channel ti.ipc4.ping-pong addr 0xe
    [    8.539713] virtio_rpmsg_bus virtio0: creating channel rpmsg_chrdev addr 0x15
    [    8.546955] virtio_rpmsg_bus virtio0: creating channel ti.ipc4.ping-pong addr 0xe
    [    8.554673] virtio_rpmsg_bus virtio1: creating channel rpmsg_chrdev addr 0x15
    [    8.561959] virtio_rpmsg_bus virtio1: creating channel ti.ipc4.ping-pong addr 0xe
    [    8.569615] virtio_rpmsg_bus virtio4: creating channel ti.ipc4.ping-pong addr 0xe
    [    8.578856] remoteproc remoteproc5: remote processor 5d00000.r5f is now attached
    [    8.664556] platform 5e00000.r5f: configured R5F for remoteproc mode
    [    8.676054] platform 5e00000.r5f: assigned reserved memory node vision-apps-r5f-dma-memory@a6000000
    [    8.716796] m_can_platform 40528000.can: m_can device registered (irq=823, version=32)
    [    8.732226] m_can_platform 40568000.can: m_can device registered (irq=824, version=32)
    [    8.755444] m_can_platform 2701000.can: m_can device registered (irq=825, version=32)
    [    8.769168] m_can_platform 2721000.can: m_can device registered (irq=826, version=32)
    [    8.800815] remoteproc remoteproc6: 5e00000.r5f is available
    [    8.820180] remoteproc remoteproc6: Direct firmware load for j7-main-r5f1_0-fw failed with error -2
    [    8.830281] remoteproc remoteproc6: powering up 5e00000.r5f
    [    8.831194] platform 5f00000.r5f: configured R5F for remoteproc mode
    [    8.836002] remoteproc remoteproc6: Direct firmware load for j7-main-r5f1_0-fw failed with error -2
    [    8.851542] remoteproc remoteproc6: request_firmware failed: -2
    [    8.878409] platform 5f00000.r5f: assigned reserved memory node vision-apps-r5f-dma-memory@a7000000
    [    8.914028] remoteproc remoteproc7: 5f00000.r5f is available
    [    8.980419] j721e-pcie-host 2910000.pcie: PCI host bridge to bus 0001:00
    [    9.020550] remoteproc remoteproc7: Direct firmware load for j7-main-r5f1_1-fw failed with error -2
    [    9.027666] pci_bus 0001:00: root bus resource [bus 00-ff]
    [    9.030328] remoteproc remoteproc7: powering up 5f00000.r5f
    [    9.041707] remoteproc remoteproc7: Direct firmware load for j7-main-r5f1_1-fw failed with error -2
    [    9.051204] remoteproc remoteproc7: request_firmware failed: -2
    [    9.182379] pci_bus 0001:00: root bus resource [io  0x10000-0x1ffff] (bus address [0x18001000-0x18010fff])
    [    9.245171] pci_bus 0001:00: root bus resource [mem 0x18011000-0x1fffffff]
    [    9.257235] pci 0001:00:00.0: [104c:b00d] type 01 class 0x060400
    [    9.268810] pci_bus 0001:00: 2-byte config write to 0001:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
    [    9.284077] pci 0001:00:00.0: supports D1
    [    9.315433] audit: type=1334 audit(1651185534.552:6): prog-id=9 op=LOAD
    [    9.323119] audit: type=1334 audit(1651185534.560:7): prog-id=10 op=LOAD
    [    9.388209] pci 0001:00:00.0: PME# supported from D0 D1 D3hot
    [    9.560260] pci 0001:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
    [    9.569782] pci_bus 0001:01: busn_res: [bus 01-ff] end is updated to 01
    [    9.578126] pci 0001:00:00.0: PCI bridge to [bus 01]
    [    9.590501] pcieport 0001:00:00.0: PME: Signaling with IRQ 828
    [    9.598984] pcieport 0001:00:00.0: AER: enabled with IRQ 828
    [    9.608815] j721e-pcie-host 2920000.pcie: host bridge /bus@100000/pcie@2920000 ranges:
    [    9.617088] j721e-pcie-host 2920000.pcie:       IO 0x4400001000..0x4400010fff -> 0x0000001000
    [    9.630453] j721e-pcie-host 2920000.pcie:      MEM 0x4400011000..0x4407ffffff -> 0x0000011000
    [    9.639837] j721e-pcie-host 2920000.pcie:   IB MEM 0x0000000000..0xffffffffffff -> 0x0000000000
    [    9.824430] audit: type=1006 audit(1651185535.060:8): pid=602 uid=0 old-auid=4294967295 auid=1000 tty=(none) old-ses=4294967295 ses=1 res=1
    [    9.847972] cdns-ufshcd 4e84000.ufs: ufshcd_populate_vreg: Unable to find vdd-hba-supply regulator, assuming enabled
    [    9.858621] audit: type=1300 audit(1651185535.060:8): arch=c00000b7 syscall=64 success=yes exit=4 a0=8 a1=ffffd27c1938 a2=4 a3=ffffb9e23020 items=0 ppid=1 pid=602 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="/lib/systemd/systemd" key=(null)
    [    9.886587] cdns-ufshcd 4e84000.ufs: ufshcd_populate_vreg: Unable to find vcc-supply regulator, assuming enabled
    [    9.896824] audit: type=1327 audit(1651185535.060:8): proctitle="(systemd)"
    [    9.896844] cdns-ufshcd 4e84000.ufs: ufshcd_populate_vreg: Unable to find vccq-supply regulator, assuming enabled
    [    9.896848] cdns-ufshcd 4e84000.ufs: ufshcd_populate_vreg: Unable to find vccq2-supply regulator, assuming enabled
    [    9.926407] scsi host0: ufshcd
    [    9.931985] omap_rng 4e10000.rng: Random Number Generator ver. 241b34c
    [    9.932434] remoteproc remoteproc8: b034000.pru is available
    [    9.944861] remoteproc remoteproc9: b004000.rtu is available
    [    9.956939] remoteproc remoteproc10: b00a000.txpru is available
    [    9.963172] remoteproc remoteproc11: b038000.pru is available
    [    9.968681] scsi 0:0:0:49488: Well-known LUN    TOSHIBA  THGAF8G8T23BAILB 0300 PQ: 0 ANSI: 6
    [    9.970386] remoteproc remoteproc12: b006000.rtu is available
    [    9.985665] scsi 0:0:0:49476: Well-known LUN    TOSHIBA  THGAF8G8T23BAILB 0300 PQ: 0 ANSI: 6
    [    9.995865] remoteproc remoteproc13: b00c000.txpru is available
    [   10.003401] remoteproc remoteproc14: b134000.pru is available
    [   10.009637] cdns-ufshcd 4e84000.ufs: ufshcd_scsi_add_wlus: BOOT WLUN not found
    [   10.009784] remoteproc remoteproc15: b104000.rtu is available
    [   10.029444] remoteproc remoteproc16: b10a000.txpru is available
    [   10.037424] remoteproc remoteproc17: b138000.pru is available
    [   10.043574] remoteproc remoteproc18: b106000.rtu is available
    [   10.051470] remoteproc remoteproc19: b10c000.txpru is available
    [   10.622417] audit: type=1006 audit(1651185535.856:9): pid=542 uid=0 old-auid=4294967295 auid=1000 tty=tty7 old-ses=4294967295 ses=2 res=1
    [   10.696516] j721e-pcie-host 2920000.pcie: PCI host bridge to bus 0002:00
    [   10.708553] pci_bus 0002:00: root bus resource [bus 00-ff]
    [   10.715276] pci_bus 0002:00: root bus resource [io  0x20000-0x2ffff] (bus address [0x1000-0x10fff])
    [   10.724954] pci_bus 0002:00: root bus resource [mem 0x4400011000-0x4407ffffff] (bus address [0x00011000-0x07ffffff])
    [   10.735979] pci 0002:00:00.0: [104c:b00d] type 01 class 0x060400
    [   10.742134] pci_bus 0002:00: 2-byte config write to 0002:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
    [   10.752466] pci 0002:00:00.0: supports D1
    [   10.756477] pci 0002:00:00.0: PME# supported from D0 D1 D3hot
    [   10.765755] pci 0002:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
    [   10.774084] pci_bus 0002:01: busn_res: [bus 01-ff] end is updated to 01
    [   10.781583] pci 0002:00:00.0: PCI bridge to [bus 01]
    [   10.787007] pcieport 0002:00:00.0: PME: Signaling with IRQ 857
    [   10.793425] pcieport 0002:00:00.0: AER: enabled with IRQ 857
    [   11.412382] xhci-hcd xhci-hcd.18.auto: xHCI Host Controller
    [   11.418028] xhci-hcd xhci-hcd.18.auto: new USB bus registered, assigned bus number 1
    [   11.426244] xhci-hcd xhci-hcd.18.auto: hcc params 0x200073c9 hci version 0x100 quirks 0x0000002000018010
    [   11.435814] xhci-hcd xhci-hcd.18.auto: irq 832, io mem 0x06010000
    [   11.442175] xhci-hcd xhci-hcd.18.auto: xHCI Host Controller
    [   11.447828] xhci-hcd xhci-hcd.18.auto: new USB bus registered, assigned bus number 2
    [   11.455718] xhci-hcd xhci-hcd.18.auto: Host supports USB 3.0 SuperSpeed
    [   11.462769] hub 1-0:1.0: USB hub found
    [   11.466589] hub 1-0:1.0: 1 port detected
    [   11.472088] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
    [   11.480842] hub 2-0:1.0: USB hub found
    [   11.484665] hub 2-0:1.0: 1 port detected
    [   11.489012] xhci-hcd xhci-hcd.19.auto: xHCI Host Controller
    [   11.494662] xhci-hcd xhci-hcd.19.auto: new USB bus registered, assigned bus number 3
    [   11.502551] xhci-hcd xhci-hcd.19.auto: hcc params 0x200073c9 hci version 0x100 quirks 0x0000002000018010
    [   11.512107] xhci-hcd xhci-hcd.19.auto: irq 858, io mem 0x06410000
    [   11.518349] xhci-hcd xhci-hcd.19.auto: xHCI Host Controller
    [   11.523951] xhci-hcd xhci-hcd.19.auto: new USB bus registered, assigned bus number 4
    [   11.531727] xhci-hcd xhci-hcd.19.auto: Host supports USB 3.0 SuperSpeed
    [   11.538692] hub 3-0:1.0: USB hub found
    [   11.542469] hub 3-0:1.0: 1 port detected
    [   11.546683] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
    [   11.555186] hub 4-0:1.0: USB hub found
    [   11.558980] hub 4-0:1.0: 1 port detected
    [   11.748198] PVR_K:  542: RGX Firmware image 'rgx.fw.22.104.208.318' loaded
    [   11.750786] usb 1-1: new high-speed USB device number 2 using xhci-hcd
    [   11.782562] PVR_K:  542: Shader binary image 'rgx.sh.22.104.208.318' loaded
    [   11.798803] usb 3-1: new high-speed USB device number 2 using xhci-hcd
    [   11.914001] hub 1-1:1.0: USB hub found
    [   11.918222] hub 1-1:1.0: 4 ports detected
    [   11.951625] hub 3-1:1.0: USB hub found
    [   11.955588] hub 3-1:1.0: 4 ports detected
    [   12.038874] usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd
    [   12.066679] hub 2-1:1.0: USB hub found
    [   12.070743] hub 2-1:1.0: 4 ports detected
    [   12.234749] usb 1-1.3: new full-speed USB device number 3 using xhci-hcd
    [   12.474762] usb 1-1.4: new full-speed USB device number 4 using xhci-hcd
    [   12.491882] am65-cpsw-nuss 46000000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
    [   12.500505] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [   12.616624] input: Logitech USB Receiver as /devices/platform/bus@100000/4104000.cdns-usb/6000000.usb/xhci-hcd.18.auto/usb1/1-1/1-1.4/1-1.4:1.0/0003:046D:C534.0001/input/input1
    [   12.691114] hid-generic 0003:046D:C534.0001: input: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-xhci-hcd.18.auto-1.4/input0
    [   12.706505] input: Logitech USB Receiver Mouse as /devices/platform/bus@100000/4104000.cdns-usb/6000000.usb/xhci-hcd.18.auto/usb1/1-1/1-1.4/1-1.4:1.1/0003:046D:C534.0002/input/input2
    [   12.723675] input: Logitech USB Receiver Consumer Control as /devices/platform/bus@100000/4104000.cdns-usb/6000000.usb/xhci-hcd.18.auto/usb1/1-1/1-1.4/1-1.4:1.1/0003:046D:C534.0002/input/input3
    [   12.747839] usb 2-1.1: new SuperSpeed USB device number 3 using xhci-hcd
    [   12.776439] usb-storage 2-1.1:1.0: USB Mass Storage device detected
    [   12.790359] scsi host1: usb-storage 2-1.1:1.0
    [   12.799000] input: Logitech USB Receiver System Control as /devices/platform/bus@100000/4104000.cdns-usb/6000000.usb/xhci-hcd.18.auto/usb1/1-1/1-1.4/1-1.4:1.1/0003:046D:C534.0002/input/input4
    [   12.816328] hid-generic 0003:046D:C534.0002: input: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-xhci-hcd.18.auto-1.4/input1
    [   12.942299] peak_usb 1-1.3:1.0: PEAK-System PCAN-USB adapter hwrev 84 serial FFFFFFFF (1 channel)
    [   12.956134] peak_usb 1-1.3:1.0 can4: attached to PCAN-USB channel 0 (device 255)
    [   12.963978] usbcore: registered new interface driver peak_usb
    [   14.539885] scsi 1:0:0:0: Direct-Access     Samsung  PSSD T7          0    PQ: 0 ANSI: 6
    [   14.548508] sd 1:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
    [   14.557376] sd 1:0:0:0: [sda] Write Protect is off
    [   14.562292] sd 1:0:0:0: [sda] Mode Sense: 43 00 00 00
    [   14.562624] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [   14.575959]  sda: sda1
    [   14.578489] sd 1:0:0:0: [sda] Attached SCSI disk
    [   15.657195] EXT4-fs (sda1): mounted filesystem with ordered data mode. Quota mode: none.
    [   23.147336] platform main-r5fss-cpsw9g-virt-mac0: deferred probe pending
    [   23.154041] platform main-r5fss-cpsw9g-virt-mac1: deferred probe pending
    [  952.772119] kauditd_printk_skb: 2 callbacks suppressed
    [  952.772126] audit: type=1006 audit(1651186478.008:10): pid=1260 uid=0 old-auid=4294967295 auid=0 tty=(none) old-ses=4294967295 ses=3 res=1
    [  952.789847] audit: type=1300 audit(1651186478.008:10): arch=c00000b7 syscall=64 success=yes exit=1 a0=8 a1=ffffd27c1938 a2=1 a3=ffffb9e23020 items=0 ppid=1 pid=1260 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=3 comm="(systemd)" exe="/lib/systemd/systemd" key=(null)
    [  952.816580] audit: type=1327 audit(1651186478.008:10): proctitle="(systemd)"
    [  952.823646] audit: type=1334 audit(1651186478.028:11): prog-id=11 op=LOAD
    [  952.830457] audit: type=1300 audit(1651186478.028:11): arch=c00000b7 syscall=280 success=yes exit=8 a0=5 a1=ffffeba838d0 a2=78 a3=0 items=0 ppid=1 pid=1260 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=3 comm="systemd" exe="/lib/systemd/systemd" key=(null)
    [  952.856012] audit: type=1327 audit(1651186478.028:11): proctitle="(systemd)"
    [  952.863100] audit: type=1334 audit(1651186478.052:12): prog-id=11 op=UNLOAD
    [  952.870112] audit: type=1334 audit(1651186478.052:13): prog-id=12 op=LOAD
    [  952.876987] audit: type=1300 audit(1651186478.052:13): arch=c00000b7 syscall=280 success=yes exit=8 a0=5 a1=ffffeba83970 a2=78 a3=0 items=0 ppid=1 pid=1260 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=3 comm="systemd" exe="/lib/systemd/systemd" key=(null)
    [  952.902458] audit: type=1327 audit(1651186478.052:13): proctitle="(systemd)"
    

    Last, I modified drm_dp_mst_hpd_irq function in drm_dp_mst_topology.c as PSDK linux 9.1.0.8.

    I've modified other codes such as amdgpu_dm.c, intel_dp.c and disp.c which are related to 'drm_dp_mst_hpd_irq' to make same as PSDK9.1.0.8. 

    and then copied new driver files as below.

    • drivers/gpu/drm/bridge/display-connector.ko
    • drivers/gpu/drm/bridge/ite-it66121.ko
    • drivers/gpu/drm/bridge/lontium-lt8912b.ko
    • drivers/gpu/drm/bridge/lontium-lt9611.ko
    • drivers/gpu/drm/bridge/nwl-dsi.ko
    • drivers/gpu/drm/bridge/parade-ps8640.ko
    • drivers/gpu/drm/bridge/sii902x.ko
    • drivers/gpu/drm/bridge/simple-bridge.ko
    • drivers/gpu/drm/bridge/thc63lvd1024.ko
    • drivers/gpu/drm/bridge/ti-sn65dsi86.ko
    • drivers/gpu/drm/bridge/ti-tfp410.ko
    • drivers/gpu/drm/display/drm_display_helper.ko
    • drivers/gpu/drm/i2c/tda998x.ko
    • drivers/gpu/drm/panel/panel-boe-tv101wum-nl6.ko
    • drivers/gpu/drm/panel/panel-edp.ko
    • drivers/gpu/drm/panel/panel-lvds.ko
    • drivers/gpu/drm/panel/panel-mantix-mlaf057we51.ko
    • drivers/gpu/drm/panel/panel-raydium-rm67191.ko
    • drivers/gpu/drm/panel/panel-simple.ko
    • drivers/gpu/drm/panel/panel-sitronix-st7703.ko
    • drivers/gpu/drm/panel/panel-truly-nt35597.ko
    • drivers/gpu/drm/tidss/tidss.ko
    • drivers/gpu/drm/drm_kms_helper.ko
    • drivers/gpu/drm/drm.ko

    But it was failed again.

    Please test by using my dtbs and then if you could recommend a new DP-to-HDMI, I'll test.

    (My DP-to-HDMI is working well in other psdk versions. So I don't think adapter is root cause)

    For more information, I'n using QT libs, so I'm checking the screen with weston.ini

    I copied my weston.ini to /etc/xdg/weston/weston.ini  in sdcard

    [core]
    idle-time=0
    require-input=false
    
    [shell]
    locking=false
    animation=zoom
    panel-position=top
    background-image=/usr/share/demo/j7-evm-oob-wallpaper.jpg
    startup-animation=fade
    binding-modifier=ctrl
    
    [output]
    name=DP-1
    force-on=true
    mode=1920x1080@60
    
    [screensaver]
    # Uncomment path to disable screensaver
    #path=@libexecdir@/weston-screensaver
    
    [launcher]
    

    best regards

    Yongsig

  • Hi Yongsig,

    I ordered the HDMI grabber and obtained a similar DP to HDMI adapter from a co-worker. The grabber should arrive next week Wednesday at the latest.

    As of now, I do not have a good idea as to why this specific combination of device is not working. This looks like a corner case, so I would like to set expectation that debugging this may take some time.

    Regards,

    Takuma

  • Hi Takuma

    I sincerely appreciate you for your help.

    If It's hard to make the same case on your side, please let me know.

    Best regards

    yongsig

  • Hi Yongsig,

    Understood and thank you for your patience.

    Regards,

    Takuma

  • Hi Yongsig,

    I have received the HDMI grabber and doing some initial tests with it. It looks like this issue is very specific with 9.0.0.8 version of the SDK. I tried with the 9.0.1.3 SDK and find that the grabber works fine. You could also test this on your end: https://www.ti.com/tool/download/PROCESSOR-SDK-LINUX-J721E/09.00.01.03.

    Currently looking into what the change was - it will probably take a few days since I will be consulting with some folks in a different timezone.

    Otherwise, a workaround would be to see if you can update your SDK to a newer SDK.

    Regards,

    Takuma

  • Hi, Takuma.

    Thanks for your effort to make the same issue on your side.

    I'll try PSDK Linux 9.0.1.3. I was wondering if I could use PSDK RTOS 9.0.0.8 with PSDK Linux 9.0.1.3.

    Once I tried to run PSDK RTOS 9.0.0.8 with PSDK Linux 9.1.0.6, It failed due to a different memory region.

    And my customer wants to use PSDK RTOS Linux 9.0.0.8 still. If you figure out the root cause, please let me know.

    Best regards

    Yongsig


    [update]

    I tried to run my app in psdk rtos 9.0.0.2 with psdk linux 9.0.1.3 and it runs well.

    Also, I disabled some features in vision_app dts of psdkla 9.0.1.3 not to use r5 display as below.

    /*
    &serdes_wiz4 {
    	status = "disabled";
    };
    
    &mhdp {
    	status = "disabled";
    };
    
    &dss {
    	status = "disabled";
    };
    
    &main_i2c1 {
    	status = "disabled";
    };
    */

    But the displaying issue is the same as before.

    So, I tried to boot using the default psdkla image to see TI wayland on the screen.

    The only things that I modified are vision_app dtbs and uEnv as below.

    # name_overlays_fit=conf-ti_k3-j721e-evm-virt-mac-client.dtbo conf-ti_k3-j721e-vision-apps.dtbo

    Just disabled the last line in the uEnv.txt in BOOT of sdcard.

    I can see the screen from /etc/xdg/weston/weston.ini once I connect to portable monitor via DP-to-HDMI.

    But there is no signal via Grabber.

    Additionally, I can see the Wayland when I use only psdk linux 9.1.0.6.

    How could you see the screen via Grabber in psdk linux 9.0.0.8?

    Best regards

    Yongsig

  • Hi Yongsig,

    Apologies for the confusing wording in my previous post. I was not able to get Grabber to work in PSDK Linux 9.0.0.8. Only on 9.0.1.3 and above, or 8.6 or less versions for PSDK Linux, the Grabber was working -> or, more simply put, I found that only with 9.0.0.8 SDK version the Grabber did not work, and all other versions I have tried so far works.

    Currently trying to understand the differences.

    However, you mention you can get 9.1.0.6 to work. For the customer use case/requirement, would this be a sufficient work around while we root cause the issue for 9.0.0.8?

    Regards,

    Takuma

  • Hi Takuma.

    The customer and our side is already working on PSDK rtos 9.0.0.2 and linux 9.0.0.8. The only problem that we have is on Grabber use case.

    It looks like It's hard to upgrade to 9.1.0.6 now, as you know there are so many updates in TIDL.

    Do we have a test that HPD is working or another physically?

    Best regards

    Yongsig

  • Hi Yongsig,

    Understood that they are working on 9.0.0.8 and it is difficult to upgrade to 9.1.0.6 for TIDL. However, it is also equally difficult to determine which specific patch has made the fix between 9.0.0.8 and 9.1.0.6. I will try to go through and test if there is a specific patch that fixes the issue, but there are a couple thousand changes between 9.0.0.8 and 9.1.0.6 to go through, so please expect that this will take a very long time. It would most likely be faster to port code over to the new SDK version.

    Regards,

    Takuma

  • Hi Yongsig,

    Just as an update, I think I have narrowed down the commits to around 10 commits. Will be testing these commits tomorrow to see if one can fix the HDMI grabber issue.

    Regards,

    Takuma

  • I appreciate your effort.

    I'll wait the update.

    Best regards

    Yongsig

  • Hi Yongsig,

    May take a few more days on this.

    I currently think this commit initially caused the issue: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?h=ti-linux-6.1.y&id=51404b29a0d264d0ccc3bea29ae3df123aa41c28. But, I think there is a possibility that there are other commits that are affecting the display output.

    Regards,

    Takuma

  • Hi Yongsig,

    It looks like reverting this commit fixes the HDMI grabber on my end:

    • git revert 63672bc1fe1

    In your Linux kernel, could you also do the same and confirm?

    The commit message of the commit to revert is: "HACK: arm64: configs: defconfig: Enable OMAP mailbox"

    Regards,

    Takuma

  • Hi Takuma,

    Thanks for your effort.

    Once I tried to revert it, failed.

    usami@usami-HP-ZBook-Fury-15-6-inch-G8-Mobile-Workstation-PC:~/workspace/ti_psdk/default/ti-processor-sdk-linux-adas-j721e-evm-09_00_00_08/board-support/linux-6.1.33+gitAUTOINC+8f7f371be2-g8f7f371be2$ git revert 63672bc1fe1
    error: Your local changes to the following files would be overwritten by merge:
            arch/arm64/configs/defconfig
    Please commit your changes or stash them before you merge.
    Aborting
    fatal: revert failed

    Would you share more details about guidance?

    And If the kernel version is reverted, What driver (ko files) should I update into the Linux file system image?

    Best regards

    Yongsig

  • Hi Yongsig,

    That is probaby due to having some uncommitted changes in the kernel. As the log message says, either commit the changes or stash them. Alternatively, if you are not savvy with git, then you could manually apply below change. It is a one line change, so it should be relatively easy to change.

    0001-Revert-HACK-arm64-configs-defconfig-Enable-OMAP-mail.patch

    The patch changes omap-mailbox.ko.

    Regards,

    Takuma

  • Hi Takuma

    As you know, there is no omap_mailbox.ko in targets basically.

    So I have made a directory and copied omap_mailbox.ko into lib/modules/6.1.33-g8f7f371be2/kernel/drivers/mailbox.

    and then, after booting.

    Loading omap-mailbox.ko failed.

    root@j721e-evm:~# depmod
    root@j721e-evm:~#
    root@j721e-evm:~# modprobe omap-mailbox.ko
    modprobe: FATAL: Module omap-mailbox.ko not found in directory /lib/modules/6.1.33-g8f7f371be2
    root@j721e-evm:~#
    

    Do you know what I missed?

    Best regards

    Yongsig

  • Hi Yongsig,

    The patch removes -CONFIG_OMAP2PLUS_MBOX=y from the kernel config. Since it was "y" instead of "m", this used to be built into the kernel. However, we are removing this config, so we need to update the kernel instead of the kernel module. Please remove this line from <PSDK LInux installation directory>/board-support/linux-*/arch/arm64/configs/defconfig and recompile.

    If you are using the top level makefile as documented here, then to build and install the kernel, running "make linux" and "sudo ROOTFS_PART=/path/to/root/partition/of/sd/card make linux_install" should build and install the kernel, kernel modules, and device tree blobs: https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-jacinto7/09_01_00_06/exports/docs/linux/Overview_Top_Level_Makefile.html

    Regards,

    Takuma

  • Hi Takuma.

    CONFIG_OMAP2PLUS_MBOX=y has been removed.

    After make, make linux-dtbs, make linux.

    The only file which is changed is omap-mailbox.ko. I don't think I need to copy all kernel files from psdkla/targetNFS to sdcard.

    That's why I asked you what I should copy into sdcard and what I should do more.

     

    As your recommendation, I copied all files in targetNFS in psdkla into sdcard/rootfs.

    But any screen from weston file is not displayed now including a portable monitor.

     

    Best regards

    Yongsig

  • Hi Yongsig,

    That is strange... could you do an experiment then?

    Check out the following commit: "git checkout 9ee794b9509"

    This should be 1 commit before the commit I reverted. I tested on my end just now, but this commit seems to have display working.

    Regards,

    Takuma

  • Hi Takuma

    I succeeded "git revert 63672bc1fe1" and then I checked The only thing that is changed is deconfig.

    After booting, omap-mailbox driver loaded well.

    But, any screen is not displayed.

     

    I'll share my rootfs in sdcard. Could you test using mine? You can download the below link. (password is 1234) 

    - http://119.202.38.9:5000/sharing/R1FrEZz6T

     

    and then I'll attach a new dtbo and uEnv.txt not to use r5f display.

    uEnv_qt.txt
    psdk_setup_file=.psdk_setup
    check_psdk_setup=load mmc 1:1 ${loadaddr} ${psdk_setup_file}
    
    # Reset to the default environment
    do_psdk_setup=env default -f -a; saveenv
    
    # If not previously configured, then configure the environment and indicate this by writing a file
    uenvcmd=if test ${boot_fit} -eq 1; then  setenv name_overlays $name_overlays_fit; fi; if run check_psdk_setup; then echo "Already setup."; else run do_psdk_setup; mw.b ${loadaddr} 0 1; fatwrite mmc 1:1 ${loadaddr} .psdk_setup 1; reset; fi
    
    # Setting the right U-Boot environment variables
    dorprocboot=1
    name_overlays=ti/k3-j721e-evm-virt-mac-client.dtbo ti/k3-j721e-vision-apps-no-r5f-display_evm.dtbo
    
    # Name overlays when booting from fit image
    # name_overlays_fit=conf-ti_k3-j721e-evm-virt-mac-client.dtbo conf-ti_k3-j721e-vision-apps.dtbo
    
    k3-j721e-vision-apps-no-r5f-display_evm.zip

    Please copy them into sdcard before test.

    and then Please let me know if qt screen shows up or not.

    I think It'll be good if we have a meeting using teams or zoom.  I can show my problem in real time.

    My time zone is EST. How about you ? and what do you think?

    Best regards

    Yongsig

  • Hi Yongsig,

    I am currently out of office due to US holiday so I do not have access to my work PC until next Tuesday. I can try reviewing your SD card image when I come back to office.

    In the meantime, could you do also do the experiment where you go back to an older commit as mentioned in my previous post? Hardware and software-wise, we should have the exact same set up, since we have obtained the same HDMI grabber, so it is strange that we are seeing different behaviors.

    Regards,

    Takuma

  • Hi Yongsig,

    Unfortunately, it seems like our company proxy blocks the URL as a suspicious link, so I am unable to test out the image from you.

    On the other hand, were you able to test out the older commit by checking it out? I would like to see whether you can reproduce what I am seeing on my setup where HDMI grabber comes up when I check out commit ID 9ee794b9509.

    Regards,

    Takuma

  • Hi Takuma.

    That link have expired. So I'll share the new link. Could you try downloading again?

    - http://119.202.38.9:5000//sharing/tCvwEdOt0

    I'll try it on commit ID 9ee794b9509. But I can share the test result next week.

    Before trying, I would like to make sure if I should add CONFIG_LOCALVERSION="-g8f7f371be2" option in ti_arm64_prune.config file.

     

    Best regards

    Yongsig do

  • Hi Yongsig,

    I do not have CONFIG_LOCALVERSION set in ti_arm64_prune.config when testing on my setup, so it should not be needed.

    Regards,

    Takuma

  • Hi Takuma.

     "git checkout 9ee794b9509" has been succeeded in ./board-support/linux-6.1.33+gitAUTOINC+8f7f371be2-g8f7f371be2  as below.

    usami@usami-HP-ZBook-Fury-15-6-inch-G8-Mobile-Workstation-PC:~/workspace/ti_psdk/default/ti-processor-sdk-linux-adas-j721e-evm-09_00_00_08/board-support/linux-6.1.33+gitAUTOINC+8f7f371be2-g8f7f371be2$ git log -1
    commit 9ee794b9509d2dc88a8239653bbc71ac7c57547f (HEAD)
    Author: Vignesh Raghavendra <vigneshr@ti.com>
    Date:   Mon Jun 26 20:27:57 2023 -0500
    
        arm64: dts: ti: k3-am625-sk: Add support for WL1837 module onboard
        
        WL1837 WLAN card is present on AM625 SK board. It communicates with the SoC
        using 4 bit SDIO through the second instance of MMCSD.
        
        Therefore, add corresponding device tree support for the same.
        
        Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
        Signed-off-by: Aswath Govindraju <a-govindraju@ti.com>
        [sabeeh-khan@ti.com: fwd port from ti-5.10 to ti-6.1]
        Signed-off-by: Sabeeh Khan <sabeeh-khan@ti.com>

    and then once I tried to build "make all", there were some errors.

    In just "make", 

    make[2]: Leaving directory '/home/usami/workspace/ti_psdk/default/ti-processor-sdk-linux-adas-j721e-evm-09_00_00_08/board-support/u-boot-2023.04+gitAUTOINC+756ba776d4-g756ba776d4/build/r5'
    make[1]: Leaving directory '/home/usami/workspace/ti_psdk/default/ti-processor-sdk-linux-adas-j721e-evm-09_00_00_08/board-support/u-boot-2023.04+gitAUTOINC+756ba776d4-g756ba776d4'
    cp /home/usami/workspace/ti_psdk/default/ti-processor-sdk-linux-adas-j721e-evm-09_00_00_08/board-support/prebuilt-images/fitImage.its /home/usami/workspace/ti_psdk/default/ti-processor-sdk-linux-adas-j721e-evm-09_00_00_08/board-support/linux-6.1.33+gitAUTOINC+8f7f371be2-g8f7f371be2
    cd /home/usami/workspace/ti_psdk/default/ti-processor-sdk-linux-adas-j721e-evm-09_00_00_08/board-support/linux-6.1.33+gitAUTOINC+8f7f371be2-g8f7f371be2; \
    mkimage -r -f fitImage.its -k /home/usami/workspace/ti_psdk/default/ti-processor-sdk-linux-adas-j721e-evm-09_00_00_08/board-support/u-boot-2023.04+gitAUTOINC+756ba776d4-g756ba776d4/board/ti/keys -K /home/usami/workspace/ti_psdk/default/ti-processor-sdk-linux-adas-j721e-evm-09_00_00_08/board-support/u-boot-2023.04+gitAUTOINC+756ba776d4-g756ba776d4/build/a72/dts/dt.dtb fitImage
    FATAL ERROR: Couldn't open "arch/arm64/boot/dts/ti/k3-j721e-beagleboneai64.dtb": No such file or directory
    mkimage: Can't open fitImage.tmp: No such file or directory
    make: *** [makerules/Makefile_linux-fitImage:14: linux-fitImage] Error 255

    and In just "make linux-fitImage"

    usami@usami-HP-ZBook-Fury-15-6-inch-G8-Mobile-Workstation-PC:~/workspace/ti_psdk/default/ti-processor-sdk-linux-adas-j721e-evm-09_00_00_08$ make linux-fitImage
    cp /home/usami/workspace/ti_psdk/default/ti-processor-sdk-linux-adas-j721e-evm-09_00_00_08/board-support/prebuilt-images/fitImage.its /home/usami/workspace/ti_psdk/default/ti-processor-sdk-linux-adas-j721e-evm-09_00_00_08/board-support/linux-6.1.33+gitAUTOINC+8f7f371be2-g8f7f371be2
    cd /home/usami/workspace/ti_psdk/default/ti-processor-sdk-linux-adas-j721e-evm-09_00_00_08/board-support/linux-6.1.33+gitAUTOINC+8f7f371be2-g8f7f371be2; \
    mkimage -r -f fitImage.its -k /home/usami/workspace/ti_psdk/default/ti-processor-sdk-linux-adas-j721e-evm-09_00_00_08/board-support/u-boot-2023.04+gitAUTOINC+756ba776d4-g756ba776d4/board/ti/keys -K /home/usami/workspace/ti_psdk/default/ti-processor-sdk-linux-adas-j721e-evm-09_00_00_08/board-support/u-boot-2023.04+gitAUTOINC+756ba776d4-g756ba776d4/build/a72/dts/dt.dtb fitImage
    FATAL ERROR: Couldn't open "arch/arm64/boot/dts/ti/k3-j721e-beagleboneai64.dtb": No such file or directory
    mkimage: Can't open fitImage.tmp: No such file or directory

    Actually, there is no arch/arm64/boot/dts/ti/k3-j721e-beagleboneai64.dtb.

    1. What should I fix to build?

    2. What is your default screen ?

    3. What file should I change to diaply using A72 (not R5f)?

    Best regards

    Yongsig

  • Hi Yongsig,

    Please use the target "make linux" and "sudo ROOTFS_PART=</path/to/root/filesystem/of/sd/card> make linux_install" to build and install.

    While using the Linux SDK, default display should be set to A72 instead of R5F, so no changes should be necessary.

    Regards,

    Takuma

  • Hi Takuma.

    I did as you mentioned.

    1. flash sdcard using defualt psdk image in psdk rtos install path.

    - "sudo ./sdk_builder/scripts/mk-linux_sdcard.sh /dev/sdc"

    - "./sdk_builder/scripts/install_to_sdcard.sh"

    2. make linux and then copy to sdcard in psdk linux install path

    - "./setup.sh"

    - "make linux"

    - "sudo ROOTFS_PART=/media/usami/rootfs make linux_install"

    But there is no signal on the monitor. That's why asked about what the default screen was.

    Was it Just console screen or QT screen?

    I don't think there will be any progress if I do this.

    What do you think about we are having an online meeting?

    Best regards

    Yongsig

  • Hi Yongsig,

    Default screen - what I see is default Weston GUI coming up on the monitor that is connected through HDMI to the HDMI grabber, which is then connected to DP through an active HDMI to DP adapter to DP0 port on the TDA4VM EVM.

    I assumed this is exactly the same setup as your setup... however, it seems that is not the case and we cannot reproduce the issue being seen at your setup on our setup. I think you mentioned 9.1 SDK is working in the past, so please port your code to the latest SDK.

    Regards,

    Takuma

  • Hi Takuma

    Pleas one more check the result of 'lsmod'

    root@j721e-evm:~# lsmod
    Module                  Size  Used by
    pci_endpoint_test      20480  0
    xhci_plat_hcd          16384  0
    rpmsg_ctrl             16384  0
    rpmsg_char             16384  1 rpmsg_ctrl
    ti_am335x_adc          20480  0
    kfifo_buf              16384  1 ti_am335x_adc
    pru_rproc              24576  0
    irq_pruss_intc         16384  0
    omap_rng               16384  0
    cdns3                  45056  0
    cdns_usb_common        20480  1 cdns3
    overlay               122880  0
    display_connector      16384  0
    drm_kms_helper        184320  1 display_connector
    cfbfillrect            16384  1 drm_kms_helper
    syscopyarea            16384  1 drm_kms_helper
    crct10dif_ce           16384  1
    cfbimgblt              16384  1 drm_kms_helper
    ti_j721e_cpsw_virt_mac    32768  0
    snd_soc_j721e_evm      32768  0
    sysfillrect            16384  1 drm_kms_helper
    sysimgblt              16384  1 drm_kms_helper
    fb_sys_fops            16384  1 drm_kms_helper
    cfbcopyarea            16384  1 drm_kms_helper
    phy_can_transceiver    16384  4
    bluetooth             503808  2
    ecdh_generic           16384  1 bluetooth
    ecc                    36864  1 ecdh_generic
    cfg80211              380928  0
    rfkill                 24576  3 bluetooth,cfg80211
    omap_mailbox           20480  6
    ti_k3_r5_remoteproc    28672  0
    vxd_dec               344064  0
    vxe_enc               286720  0
    videobuf2_dma_contig    20480  1 vxd_dec
    videobuf2_dma_sg       20480  2 vxe_enc,vxd_dec
    videobuf2_memops       16384  2 videobuf2_dma_contig,videobuf2_dma_sg
    v4l2_mem2mem           36864  2 vxe_enc,vxd_dec
    videobuf2_v4l2         32768  3 vxe_enc,vxd_dec,v4l2_mem2mem
    videobuf2_common       57344  7 vxe_enc,videobuf2_dma_contig,videobuf2_v4l2,vxd_dec,videobuf2_dma_sg,v4l2_mem2mem,videobuf2_memops
    ti_am335x_tscadc       16384  1 ti_am335x_adc
    pruss                  16384  0
    videodev              245760  5 vxe_enc,videobuf2_v4l2,vxd_dec,videobuf2_common,v4l2_mem2mem
    snd_soc_pcm3168a_i2c    16384  1
    ti_k3_dsp_remoteproc    16384  0
    snd_soc_pcm3168a       32768  1 snd_soc_pcm3168a_i2c
    virtio_rpmsg_bus       20480  0
    rpmsg_ns               16384  1 virtio_rpmsg_bus
    ti_k3_common           16384  1 ti_k3_dsp_remoteproc
    sa2ul                  36864  0
    snd_soc_davinci_mcasp    32768  2
    mc                     57344  4 videodev,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem
    snd_soc_ti_udma        16384  1 snd_soc_davinci_mcasp
    cdns_dphy_rx           16384  0
    m_can_platform         16384  0
    snd_soc_ti_edma        16384  1 snd_soc_davinci_mcasp
    m_can                  24576  1 m_can_platform
    snd_soc_ti_sdma        16384  1 snd_soc_davinci_mcasp
    cdns3_ti               16384  0
    pci_j721e_host         16384  0
    pci_j721e              16384  1 pci_j721e_host
    can_dev                36864  1 m_can
    pcie_cadence_host      16384  1 pci_j721e_host
    pcie_cadence           16384  2 pcie_cadence_host,pci_j721e_host
    optee_rng              16384  0
    rng_core               20480  2 optee_rng,omap_rng
    fuse                  131072  1
    drm                   557056  2 drm_kms_helper,display_connector
    drm_panel_orientation_quirks    28672  1 drm
    

    I think R5 core is used for display.

    mhdp driver is for DP, isn't it?

    Best regards

    Yongsig

  • Hi Yongsig,

    Yes, you are right. It does seem like mhdp driver is not getting probed. Is there a device tree overlay in uEnv.txt on your setup by any chance? If SDK default device tree is being built, that would be the only reason I can think of for why DP is not getting probed.

    Otherwise, attached are my dmesg logs that you can check for comparison. I also printed out the kernel version via uname, kmsprint to verify monitor is being detected (and visually, a gray background shows up on the connected monitor), and lsmod output that can also be used as comparison to identify difference between our setups.

    9_0_logs_for_hdmi_grabber_functional.txt

    Hope this helps with troubleshooting.

    Regards,

    Takuma

  • Hi Takuma

    I found wrong path once I put "sudo ROOTFS_PART=/media/usami/rootfs make linux_install"

      INSTALL /media/usami/rootfs/lib/modules/6.1.33-g8f7f371be2-00009-g9ee794b9509d-dirty/kernel/sound/soc/ti/snd-soc-j721e-evm.ko
      STRIP   /media/usami/rootfs/lib/modules/6.1.33-g8f7f371be2-00009-g9ee794b9509d-dirty/kernel/sound/soc/ti/snd-soc-j721e-evm.ko
      INSTALL /media/usami/rootfs/lib/modules/6.1.33-g8f7f371be2-00009-g9ee794b9509d-dirty/kernel/sound/soc/ti/snd-soc-ti-edma.ko
      STRIP   /media/usami/rootfs/lib/modules/6.1.33-g8f7f371be2-00009-g9ee794b9509d-dirty/kernel/sound/soc/ti/snd-soc-ti-edma.ko
      INSTALL /media/usami/rootfs/lib/modules/6.1.33-g8f7f371be2-00009-g9ee794b9509d-dirty/kernel/sound/soc/ti/snd-soc-ti-sdma.ko
      STRIP   /media/usami/rootfs/lib/modules/6.1.33-g8f7f371be2-00009-g9ee794b9509d-dirty/kernel/sound/soc/ti/snd-soc-ti-sdma.ko
      INSTALL /media/usami/rootfs/lib/modules/6.1.33-g8f7f371be2-00009-g9ee794b9509d-dirty/kernel/sound/soc/ti/snd-soc-ti-udma.ko
      STRIP   /media/usami/rootfs/lib/modules/6.1.33-g8f7f371be2-00009-g9ee794b9509d-dirty/kernel/sound/soc/ti/snd-soc-ti-udma.ko

    These are some parts of logs from "sudo ROOTFS_PART=/media/usami/rootfs make linux_install".

    As you know there is no "/lib/modules/6.1.33-g8f7f371be2-00009-g9ee794b9509d-dirty" folder in sdcard.

    Why '00009-g9ee794b9509d-dirty' of name is following?

    Best regards

    Yongsig

  • Hi Yongsig,

    I found wrong path once I put "sudo ROOTFS_PART=/media/usami/rootfs make linux_install"

    Could I get a clarification of what "wrong path" is? Kernel modules should automatically install under rootfs/lib/modules/<Linux kernel version number>, and kernel should check the correct folder with the kernel modules. "make linux_install" installs dts, kernel, and kernel modules that are all compatible with each other as they are compiled from the same kernel source.

    As you know there is no "/lib/modules/6.1.33-g8f7f371be2-00009-g9ee794b9509d-dirty" folder in sdcard.

    The folder should get created automatically when "make linux_install" is ran.

    Why '00009-g9ee794b9509d-dirty' of name is following?

    "00009-g9ee794b9509d" is the commit ID that we have checked out, "dirty" means there are uncommited changes within your Linux kernel source code.

    Regards,

    Takuma

  • Hi Takuma

    Thanks for your answer.

    As you know, the name of kernel directory in the default SDK image is "6.1.33-g8f7f371be2".

    - default SDK Image link : https://dr-download.ti.com/software-development/software-development-kit-sdk/MD-U6uMjOroyO/09.00.00.08/tisdk-adas-image-j721e-evm.tar.xz

    I though that all kernel files should be overwritten on "sdcard/rootfs/lib/modules/6.1.33-g8f7f371be2"

    Should I remove the original kernel after copying the new kernel ?

    I mean the new kernel is "6.1.33-g8f7f371be2-00009-g9ee794b9509d-dirty".

    And Please check if my sequence is correct or not.

    1. flash the sdcard using default SDK image.(https://dr-download.ti.com/software-development/software-development-kit-sdk/MD-U6uMjOroyO/09.00.00.08/tisdk-adas-image-j721e-evm.tar.xz)

    2. git checkout 9ee794b9509   in <psdk_linux_install_path/board-support/linux-6.1.33+gitAUTOINC+8f7f371be2-g8f7f371be2>

    3. psdk linux install and "setup.sh" and then "make_linux"

    4. "sudo ROOTFS_PART=</path/to/root/filesystem/of/sd/card> make linux_install"

     

    If I use the device trees in the default SDK image, the display will run on R5F not A72.

    If I want to use A72, I think I must use 'mdhp' module in the kernel.

    So that's why I changed some features in k3-j721e-vision-apps.dtso in first trying(not in 9ee794b9509  commit ).

    /* disable below features not to use R5 for display
    &serdes_wiz4 {
    	status = "disabled";
    };
    
    &mhdp {
    	status = "disabled";
    };
    
    &dss {
    	status = "disabled";
    };
    
    &main_i2c1 {
    	status = "disabled";
    };
    */

    I would like to want to make the same environment and kernel image as yours.

     

    Best regards

    Yongsig

  • Hi Yongsig,

    For step 1, it looks like you are downloading just the filesystem which is what would be flashed into the rootfs partition. This leads me to suspect the boot partition is not being modified.

    Please ensure the uEnv.txt in boot partition does not have any overlays set for testing purposes:

    That is, if there is something like name_overlays=k3-j721e-vision-apps.dtso, please delete this line.

    After you can confirm that Linux can detect HDMI grabber, then we should move on to the next step of applying vision-apps overlays and testing with  your application.

    Regards,

    Takuma

  • Hi Takuma

    Of course, I downloaded boot file from this link : https://dr-download.ti.com/software-development/software-development-kit-sdk/MD-U6uMjOroyO/09.00.00.08/boot-adas-j721e-evm.tar.gz

    and then, as you know sdcard have been flashed using ./sdk_builder/scripts/install_to_sdcard.sh.

    These are file list in default boot portion.

    yongsigvb22@yongsigvb22:/media/yongsigvb22/BOOT$ tree
    .
    ├── sysfw.itb
    ├── tiboot3.bin
    ├── tiboot3-j721e-gp-evm.bin
    ├── tiboot3-j721e-gp-evm-j721e-evm-k3r5-2023.04+gitAUTOINC+756ba776d4-r0_psdkla_0_edgeai_2.bin
    ├── tiboot3-j721e_sr1_1-hs-evm.bin
    ├── tiboot3-j721e_sr2-hs-fs-evm.bin
    ├── tispl.bin
    ├── u-boot.img
    ├── uEnv.txt
    └── version
    
    0 directories, 10 files
    

    I removed tiboot3-j721e-*.bin to make same as yours.

    then this is default uEnv.txt

    # 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.
    psdk_setup_file=.psdk_setup
    check_psdk_setup=load mmc 1:1 ${loadaddr} ${psdk_setup_file}
    
    # Reset to the default environment
    do_psdk_setup=env default -f -a; saveenv
    
    # If not done previously, then reset to the default environment and indicate this by writing a file
    # Also update the Linux hostname based on board_name
    uenvcmd=if run check_psdk_setup; then echo "Already setup."; else run do_psdk_setup; mw.b ${loadaddr} 0 1; fatwrite mmc 1:1 ${loadaddr} .psdk_setup 1; reset; fi; if test "$board_name" = "j721e-sk"; then ; setenv args_all $args_all systemd.hostname=tda4vm-sk ; fi; if test ${boot_fit} -eq 1; then  setenv name_overlays $name_overlays_fit; fi;
    
    # Setting the right U-Boot environment variables
    dorprocboot=1
    name_overlays=ti/k3-j721e-evm-virt-mac-client.dtbo ti/k3-j721e-vision-apps.dtbo
    
    # Name overlays when booting from fit image
    name_overlays_fit=conf-ti_k3-j721e-evm-virt-mac-client.dtbo conf-ti_k3-j721e-vision-apps.dtbo
    ~                                                                                                   

    As you mentioned, should I modify like this?

    # Setting the right U-Boot environment variables
    dorprocboot=1
    name_overlays=ti/k3-j721e-evm-virt-mac-client.dtbo
    
    # Name overlays when booting from fit image
    name_overlays_fit=conf-ti_k3-j721e-evm-virt-mac-client.dtbo
    

    2. git checkout 9ee794b9509   in <psdk_linux_install_path/board-support/linux-6.1.33+gitAUTOINC+8f7f371be2-g8f7f371be2>

    3. psdk linux install and "setup.sh" and then "make_linux"

    4. "sudo ROOTFS_PART=</path/to/root/filesystem/of/sd/card> make linux_install"

    and then should I do next step to check detecting HDMI grabber ? 

    or should I check to detect HDMI grabber before doing next steps?

    Best regards

    Yongsig

  • Hi Yongsig,

    Try removing the name_overlays line altogether for testing purposes, including k3-j721e-evm-virt-mac-client.dtbo. Or, in Linux SDK, there is a different install script which flashes the micro SD card with default Linux image with no ties to RTOS SDK: https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-jacinto7/09_02_00_05/exports/docs/linux/Overview/Processor_SDK_Linux_create_SD_card.html#create-sd-card-with-default-images-using-script. Using this to create the image will isolate the issue from any RTOS and vision apps components that could be causing differences in observed behavior between our setup.

    Then do steps 2, 3, and 4. 

    Regards,

    Takuma

  • Hi Takuma

    I did as below sequence.

    1. format sdcard using mk-linux-sdcard.sh

    2. flash sdcard using install-to-sdcard.sh

    3. remove all name_overlays in uEnv.txt

    # Setting the right U-Boot environment variables
    dorprocboot=1
    
    # Name overlays when booting from fit image
    

    4. "make_linux" and "sudo ROOTFS_PART=</path/to/root/filesystem/of/sd/card> make linux_install"

    - copy log

      STRIP   /media/usami/rootfs/lib/modules/6.1.33-00009-g9ee794b9509d/kernel/sound/soc/ti/snd-soc-ti-edma.ko
      INSTALL /media/usami/rootfs/lib/modules/6.1.33-00009-g9ee794b9509d/kernel/sound/soc/ti/snd-soc-ti-sdma.ko
      STRIP   /media/usami/rootfs/lib/modules/6.1.33-00009-g9ee794b9509d/kernel/sound/soc/ti/snd-soc-ti-sdma.ko
      INSTALL /media/usami/rootfs/lib/modules/6.1.33-00009-g9ee794b9509d/kernel/sound/soc/ti/snd-soc-ti-udma.ko
      STRIP   /media/usami/rootfs/lib/modules/6.1.33-00009-g9ee794b9509d/kernel/sound/soc/ti/snd-soc-ti-udma.ko
      INSTALL /media/usami/rootfs/lib/modules/6.1.33-00009-g9ee794b9509d/kernel/sound/usb/snd-usb-audio.ko
      STRIP   /media/usami/rootfs/lib/modules/6.1.33-00009-g9ee794b9509d/kernel/sound/usb/snd-usb-audio.ko
      INSTALL /media/usami/rootfs/lib/modules/6.1.33-00009-g9ee794b9509d/kernel/sound/usb/snd-usbmidi-lib.ko
      STRIP   /media/usami/rootfs/lib/modules/6.1.33-00009-g9ee794b9509d/kernel/sound/usb/snd-usbmidi-lib.ko

    5. remove the old kernel directory.

    usami@usami-HP-ZBook-Fury-15-6-inch-G8-Mobile-Workstation-PC:/media/usami/rootfs/lib/modules$ ls -al
    total 16
    drwxr-xr-x  4 root root 4096  4월 11 15:04 .
    drwxr-xr-x 10 root root 4096  3월  9  2018 ..
    drwxr-xr-x  3 root root 4096  4월 11 15:04 6.1.33-00009-g9ee794b9509d
    drwxr-xr-x  4 root root 4096  3월  9  2018 6.1.33-g8f7f371be2
    
    usami@usami-HP-ZBook-Fury-15-6-inch-G8-Mobile-Workstation-PC:/media/usami/rootfs/lib/modules$ sudo rm -rf 6.1.33-g8f7f371be2/

    6. insert sdcard into EVM board and boot

    --> RESULT

    1. on portable monitor : QT screen displayed.

    2. via HDMI grabber : No signal

    lsmod result

    Module                  Size  Used by
    pci_endpoint_test      20480  0
    xhci_plat_hcd          16384  0
    rpmsg_ctrl             16384  0
    rpmsg_char             16384  1 rpmsg_ctrl
    cdns_csi2rx            20480  0
    v4l2_fwnode            20480  1 cdns_csi2rx
    omap_rng               16384  0
    ti_am335x_adc          20480  0
    kfifo_buf              16384  1 ti_am335x_adc
    irq_pruss_intc         16384  0
    pru_rproc              24576  0
    cdns3                  45056  0
    cdns_usb_common        20480  1 cdns3
    snd_soc_j721e_evm      32768  0
    crct10dif_ce           16384  1
    overlay               122880  0
    display_connector      16384  0
    phy_can_transceiver    16384  4
    omap_mailbox           20480  2
    cfg80211              380928  0
    ti_k3_r5_remoteproc    28672  0
    bluetooth             503808  2
    ecdh_generic           16384  1 bluetooth
    ecc                    36864  1 ecdh_generic
    rfkill                 24576  3 bluetooth,cfg80211
    cdns_mhdp8546          40960  0
    tidss                  53248  1
    drm_dma_helper         20480  1 tidss
    drm_display_helper    147456  1 cdns_mhdp8546
    ti_am335x_tscadc       16384  1 ti_am335x_adc
    drm_kms_helper        184320  7 drm_dma_helper,display_connector,cdns_mhdp8546,drm_display_helper,tidss
    cfbfillrect            16384  1 drm_kms_helper
    syscopyarea            16384  1 drm_kms_helper
    vxd_dec               344064  0
    cfbimgblt              16384  1 drm_kms_helper
    pruss                  16384  0
    sysfillrect            16384  1 drm_kms_helper
    vxe_enc               286720  0
    snd_soc_davinci_mcasp    32768  2
    ti_k3_dsp_remoteproc    16384  0
    snd_soc_ti_udma        16384  1 snd_soc_davinci_mcasp
    j721e_csi2rx           24576  0
    snd_soc_pcm3168a_i2c    16384  1
    snd_soc_ti_edma        16384  1 snd_soc_davinci_mcasp
    virtio_rpmsg_bus       20480  0
    snd_soc_pcm3168a       32768  1 snd_soc_pcm3168a_i2c
    sysimgblt              16384  1 drm_kms_helper
    snd_soc_ti_sdma        16384  1 snd_soc_davinci_mcasp
    sa2ul                  36864  0
    videobuf2_dma_sg       20480  2 vxe_enc,vxd_dec
    fb_sys_fops            16384  1 drm_kms_helper
    pci_j721e_host         16384  0
    videobuf2_dma_contig    20480  2 j721e_csi2rx,vxd_dec
    pci_j721e              16384  1 pci_j721e_host
    cdns_dphy_rx           16384  0
    rpmsg_ns               16384  1 virtio_rpmsg_bus
    videobuf2_memops       16384  2 videobuf2_dma_contig,videobuf2_dma_sg
    v4l2_async             24576  3 v4l2_fwnode,j721e_csi2rx,cdns_csi2rx
    cfbcopyarea            16384  1 drm_kms_helper
    v4l2_mem2mem           36864  2 vxe_enc,vxd_dec
    ti_k3_common           16384  1 ti_k3_dsp_remoteproc
    videobuf2_v4l2         32768  4 j721e_csi2rx,vxe_enc,vxd_dec,v4l2_mem2mem
    videobuf2_common       57344  8 j721e_csi2rx,vxe_enc,videobuf2_dma_contig,videobuf2_v4l2,vxd_dec,videobuf2_dma_sg,v4l2_mem2mem,videobuf2_memops
    videodev              245760  8 v4l2_async,j721e_csi2rx,vxe_enc,videobuf2_v4l2,vxd_dec,cdns_csi2rx,videobuf2_common,v4l2_mem2mem
    pcie_cadence_host      16384  1 pci_j721e_host
    pcie_cadence           16384  2 pcie_cadence_host,pci_j721e_host
    mc                     57344  7 v4l2_async,videodev,j721e_csi2rx,videobuf2_v4l2,cdns_csi2rx,videobuf2_common,v4l2_mem2mem
    cdns3_ti               16384  0
    m_can_platform         16384  0
    m_can                  24576  1 m_can_platform
    can_dev                36864  1 m_can
    optee_rng              16384  0
    rng_core               20480  2 optee_rng,omap_rng
    fuse                  131072  1
    drm                   557056  8 drm_kms_helper,drm_dma_helper,display_connector,cdns_mhdp8546,drm_display_helper,tidss
    drm_panel_orientation_quirks    28672  1 drm
    ipv6                  475136  38
    

    Thanks for your hard effort. I appreciate your effort. 

    I think the root cause is different from your case even though I have the same environment as you.

    If you have another idea of what I can do, please let me know

    Best regards

    Yongsig

  • Hi Takuma,

    I ordered the same one.

    And the test result was FAIL. I don't have any idea what we should do more. 

    Anyway. I appreciate your help with this issue.

    I'll try again as you mentioned. and then I'll close this ticket later. 

    Best regards

    Yongsig

  • Hi Yongsig,

    Ok understood. It is very strange that the setup is failing on your end. It looks to me hardware and software versions are all the same between our setups.

    Apologies for not being able to root cause, and I appreciate your patience with this issue.

    Regards,

    Takuma