TDA4VM: network and screen and mutualy exclusive in sdk 9

Hi,

Can you please clarify the following;

• For the display, are you talking about the Vision apps?
• Is the vision app currently running on EVM?

The display phy and network(QSGMII) link uses different serdes. Maybe you want to run vision apps binary on mcu2_0, but you are running ethfw binary.

Can you share the output of 'ls -al /lib/firmware' and the kernel boot logs here.

Can you also please point me to the older thread you were talking about.

Regards,
Tanmay

I have the sdk08, i connect the display port to a monitor, and a newtork cable to the quad phy.

The thing boots, i stop at the u-boot:

setenv dorprocboot 1

saveenv,

boot

I have a working display ( screen, monitor, why do you asume vision apps means the same as display?)

I have a working network.

On SDK9, seems the network is not running at all, on the QUAD PHY, only on the other one( the litle one on the other side of the common board)

Br, Mircea

Hello,

I did that already, on another board it works, on this one it does not. I think we received another broken board. The previous broken boards had issues in both 08 and 09, no network what so ever. This one seems to not work in 09 only.

If I put the vision dtbo only in uEnv, this thing does not boot at all...it keeps saying waiting to negotiate things.

I was hopping to run a vision app.

Is there anyway to diagnose it?

Br, Mircea

Hi Mircea,

Please put both vision and virt-mac client dtbo as the overlays.

Tanmay Patil said:

Can you share the output of 'ls -al /lib/firmware' and the kernel boot logs here.

Can you please also do the above.

Regards,
Tanmay

If I had both virt-mac and vision-dtbo I do not have a screen :(

root@j721e-evm:~# ls /lib/firmware/ -l
total 28188
-rw-r--r-- 1 root root    2040 Mar  9  2018 LICENCE.ibt_firmware
-rw-r--r-- 1 root root    2046 Mar  9  2018 LICENCE.iwlwifi_firmware
-rw-r--r-- 1 root root  478552 Mar  9  2018 bl32.bin
-rw-r--r-- 1 root root 4295512 Mar  9  2018 bl32.elf
drwxr-xr-x 2 root root    4096 Mar  9  2018 cadence
drwxr-xr-x 2 root root    4096 Mar  9  2018 intel
-rw-r--r-- 1 root root  918268 Mar  9  2018 iwlwifi-3160-17.ucode
-rw-r--r-- 1 root root 2448976 Mar  9  2018 iwlwifi-8000C-34.ucode
-rw-r--r-- 1 root root 2428004 Mar  9  2018 iwlwifi-8000C-36.ucode
-rw-r--r-- 1 root root 2440780 Mar  9  2018 iwlwifi-8265-34.ucode
-rw-r--r-- 1 root root 2436632 Mar  9  2018 iwlwifi-8265-36.ucode
-rw-r--r-- 1 root root 2678092 Mar  9  2018 iwlwifi-9260-th-b0-jf-b0-34.ucode
-rw-r--r-- 1 root root 2521412 Mar  9  2018 iwlwifi-9260-th-b0-jf-b0-38.ucode
-rw-r--r-- 1 root root 1489652 Mar  9  2018 iwlwifi-9260-th-b0-jf-b0-46.ucode
lrwxrwxrwx 1 root root      57 Mar  9  2018 j7-c66_0-fw -> /lib/firmware/vision_apps_evm/vx_app_rtos_linux_c6x_1.out
lrwxrwxrwx 1 root root      64 Mar  9  2018 j7-c66_0-fw-sec -> /lib/firmware/vision_apps_evm/vx_app_rtos_linux_c6x_1.out.signed
lrwxrwxrwx 1 root root      57 Mar  9  2018 j7-c66_1-fw -> /lib/firmware/vision_apps_evm/vx_app_rtos_linux_c6x_2.out
lrwxrwxrwx 1 root root      64 Mar  9  2018 j7-c66_1-fw-sec -> /lib/firmware/vision_apps_evm/vx_app_rtos_linux_c6x_2.out.signed
lrwxrwxrwx 1 root root      57 Mar  9  2018 j7-c71_0-fw -> /lib/firmware/vision_apps_evm/vx_app_rtos_linux_c7x_1.out
lrwxrwxrwx 1 root root      64 Mar  9  2018 j7-c71_0-fw-sec -> /lib/firmware/vision_apps_evm/vx_app_rtos_linux_c7x_1.out.signed
lrwxrwxrwx 1 root root      51 Apr 28 17:45 j7-main-r5f0_0-fw -> ti-eth/j721e/app_remoteswitchcfg_server_strip.xer5f
lrwxrwxrwx 1 root root      65 Mar  9  2018 j7-main-r5f0_0-fw-sec -> /lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu2_0.out.signed
lrwxrwxrwx 1 root root      58 Mar  9  2018 j7-main-r5f0_1-fw -> /lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu2_1.out
lrwxrwxrwx 1 root root      65 Mar  9  2018 j7-main-r5f0_1-fw-sec -> /lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu2_1.out.signed
lrwxrwxrwx 1 root root      58 Mar  9  2018 j7-main-r5f1_0-fw -> /lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu3_0.out
lrwxrwxrwx 1 root root      65 Mar  9  2018 j7-main-r5f1_0-fw-sec -> /lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu3_0.out.signed
lrwxrwxrwx 1 root root      58 Mar  9  2018 j7-main-r5f1_1-fw -> /lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu3_1.out
lrwxrwxrwx 1 root root      65 Mar  9  2018 j7-main-r5f1_1-fw-sec -> /lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu3_1.out.signed
lrwxrwxrwx 1 root root      58 Mar  9  2018 j7-mcu-r5f0_1-fw -> /lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu1_1.out
lrwxrwxrwx 1 root root      74 Mar  9  2018 j7-mcu-r5f0_1-fw-sec -> /lib/firmware/ti-ipc/j721e/ipc_echo_test_mcu1_1_release_strip.xer5f.signed
lrwxrwxrwx 1 root root      49 Mar  9  2018 j7-pru0_0-fw -> /lib/firmware/pru/PRU_RPMsg_Echo_Interrupt0_0.out
lrwxrwxrwx 1 root root      49 Mar  9  2018 j7-pru0_1-fw -> /lib/firmware/pru/PRU_RPMsg_Echo_Interrupt0_1.out
lrwxrwxrwx 1 root root      49 Mar  9  2018 j7-pru1_0-fw -> /lib/firmware/pru/PRU_RPMsg_Echo_Interrupt1_0.out
lrwxrwxrwx 1 root root      49 Mar  9  2018 j7-pru1_1-fw -> /lib/firmware/pru/PRU_RPMsg_Echo_Interrupt1_1.out
lrwxrwxrwx 1 root root      49 Mar  9  2018 j7-rtu0_0-fw -> /lib/firmware/pru/RTU_RPMsg_Echo_Interrupt0_0.out
lrwxrwxrwx 1 root root      49 Mar  9  2018 j7-rtu0_1-fw -> /lib/firmware/pru/RTU_RPMsg_Echo_Interrupt0_1.out
lrwxrwxrwx 1 root root      49 Mar  9  2018 j7-rtu1_0-fw -> /lib/firmware/pru/RTU_RPMsg_Echo_Interrupt1_0.out
lrwxrwxrwx 1 root root      49 Mar  9  2018 j7-rtu1_1-fw -> /lib/firmware/pru/RTU_RPMsg_Echo_Interrupt1_1.out
lrwxrwxrwx 1 root root      35 Mar  9  2018 j7-txpru0_0-fw -> /lib/firmware/pru/TX_PRU_Halt_0.out
lrwxrwxrwx 1 root root      35 Mar  9  2018 j7-txpru0_1-fw -> /lib/firmware/pru/TX_PRU_Halt_1.out
lrwxrwxrwx 1 root root      35 Mar  9  2018 j7-txpru1_0-fw -> /lib/firmware/pru/TX_PRU_Halt_0.out
lrwxrwxrwx 1 root root      35 Mar  9  2018 j7-txpru1_1-fw -> /lib/firmware/pru/TX_PRU_Halt_1.out
drwxr-xr-x 2 root root    4096 Mar  9  2018 pru
-rw-r--r-- 1 root root  247469 Mar  9  2018 pvdec_full_bin.fw
-rw-r--r-- 1 root root    4728 Mar  9  2018 regulatory.db
-rw-r--r-- 1 root root    1182 Mar  9  2018 regulatory.db.p7s
-rw-r--r-- 1 root root  131072 Mar  9  2018 rgx.fw.22.104.208.318
-rw-r--r-- 1 root root  131072 Mar  9  2018 rgx.fw.22.104.208.318.64k
-rw-r--r-- 1 root root  382744 Mar  9  2018 rgx.sh.22.104.208.318
-rw-r--r-- 1 root root      28 Mar  9  2018 tee-header_v2.bin
-rw-r--r-- 1 root root       0 Mar  9  2018 tee-pageable_v2.bin
-rw-r--r-- 1 root root  478552 Mar  9  2018 tee-pager_v2.bin
-rw-r--r-- 1 root root  478552 Mar  9  2018 tee-raw.bin
-rw-r--r-- 1 root root  478580 Mar  9  2018 tee.bin
-rw-r--r-- 1 root root 4295512 Mar  9  2018 tee.elf
drwxr-xr-x 2 root root    4096 Mar  9  2018 ti-connectivity
drwxr-xr-x 3 root root    4096 Mar  9  2018 ti-eth
drwxr-xr-x 3 root root    4096 Mar  9  2018 ti-ipc
drwxr-xr-x 2 root root    4096 Mar  9  2018 vision_apps_evm
root@j721e-evm:~#

Display Port 0, is what I mean by screen.

Hi Mircea,

Let me check with our vision apps expert if this is a known issue or some configuration issue.

I will respond back here tomorrow with updates.

Regards,

Tanmay

Hi Mircea,

A couple of suggestions:

• link the vision app binary to the "j7-main-r5f0_0-fw". It has the ethfw server in it.
• For including the dtbo, please keep the order as virtual-mac dtbo first and vision apps dtbo later.
  • As both of them carve out a memory region for R5, we want to use the one carved out by vision apps

This should work.

One more thing, according to my understanding with vision apps the Display is blank if you do not have a display app running. just pointing this out.

Regards,
Tanmay

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.

# Update the Linux hostname based on board_name
uenvcmd=if test "$board_name" = "j721e-sk"; then ; setenv args_all $args_all systemd.hostname=tda4vm-sk ; fi

# Setting the right U-Boot environment variables
dorprocboot=1
name_overlays=k3-j721e-evm-virt-mac-client.dtbo k3-j721e-vision-apps.dtbo
name_overlays_fit=ti/k3-j721e-evm-virt-mac-client.dtbo ti/k3-j721e-vision-apps.dtbo

Starting weston client:

root@j721e-evm:~# weston
Date: 2024-02-06 UTC
[12:27:56.502] weston 10.0.2
               wayland.freedesktop.org
               Bug reports to: gitlab.freedesktop.org/.../
               Build: 10.0.2
[12:27:56.502] Command line: weston
[12:27:56.502] OS: Linux, 6.1.46-g5892b80d6b, #1 SMP PREEMPT Mon Nov 27 16:11:04 UTC 2023, aarch64
[12:27:56.502] Flight recorder: enabled
[12:27:56.503] Using config file '/etc/xdg/weston/weston.ini'
[12:27:56.503] Output repaint window is 7 ms maximum.
[12:27:56.504] Loading module '/usr/lib/libweston-10/wayland-backend.so'
[   49.569071] audit: type=1006 audit(1707222476.695:19): pid=792 uid=0 old-auid=4294967295 auid=1000 tty=(none) old-ses=4294967295 ses=4 res=1
[   49.581904] audit: type=1300 audit(1707222476.695:19): arch=c00000b7 syscall=64 success=yes exit=4 a0=8 a1=ffffe1707278 a2=4 a3=0 items=0 ppid=1 pid=792 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4 comm="(systemd)" exe="/lib/systemd/systemd" key=(null)
[   49.607652] audit: type=1327 audit(1707222476.695:19): proctitle="(systemd)"
[   49.857551] audit: type=1006 audit(1707222476.983:20): pid=790 uid=0 old-auid=4294967295 auid=1000 tty=tty7 old-ses=4294967295 ses=5 res=1
[   49.870046] audit: type=1300 audit(1707222476.983:20): arch=c00000b7 syscall=64 success=yes exit=4 a0=8 a1=ffffe1707278 a2=4 a3=0 items=0 ppid=1 pid=790 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=tty7 ses=5 comm="(weston)" exe="/lib/systemd/systemd" key=(null)
[   49.895429] audit: type=1327 audit(1707222476.983:20): proctitle="(weston)"
[   49.947227] audit: type=1006 audit(1707222477.075:21): pid=799 uid=0 old-auid=4294967295 auid=1000 tty=tty7 old-ses=4294967295 ses=6 res=1
[   49.960072] audit: type=1300 audit(1707222477.075:21): arch=c00000b7 syscall=64 success=yes exit=4 a0=8 a1=ffffe1707278 a2=4 a3=0 items=0 ppid=1 pid=799 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=tty7 ses=6 comm="(weston)" exe="/lib/systemd/systemd" key=(null)
[   49.985910] audit: type=1327 audit(1707222477.075:21): proctitle="(weston)"
[   50.031864] audit: type=1006 audit(1707222477.159:22): pid=801 uid=0 old-auid=4294967295 auid=1000 tty=tty7 old-ses=4294967295 ses=7 res=1
[12:27:57.365] Error: Failed to retrieve wl_shm from parent Wayland compositor
[12:27:57.365] BUG: layer_list is not empty after shutdown. Calls to weston_layer_fini() are missing somwhere.
[12:27:57.365] fatal: failed to create compositor backend
root@j721e-evm:~#

YES, I do not have a display.