TDA4VM: Display boot file not present

Thomas Agnola

Part Number: TDA4VM

Hello,

I open this thread because another question didn't help me fixing my problem.
For short, I have the same problem and display as him :

https://e2e.ti.com/support/processors/f/791/t/948601?TDA4VM-Jacinto-7-cann-t-run-display

But, I have in my side the uEnv.txt on my boot partition with name_overlays=k3-j721e-vision-apps.dtbo instead of overlay_files=k3-j721e-dp0.dtbo.
I believe the system want k3-j721e-dp0.dtbo for initializing the display but, this file is nowhere in psdkla or psdkrtos.
this are the file that come out when I list them on the system :

root@j7-evm:~# ls /boot/
Image                                         k3-j721e-proc-board-tps65917.dtb
Image-5.4.74-g9574bba32a                      k3-j721e-vision-apps.dtbo
k3-j721e-common-proc-board-infotainment.dtbo  tisdk-tiny-image-j7-evm.cpio
k3-j721e-common-proc-board-jailhouse.dtbo     vmlinux.gz
k3-j721e-common-proc-board.dtb                vmlinux.gz-5.4.74-g9574bba32a
k3-j721e-pcie-backplane.dtbo
root@j7-evm:~#

The uEnv.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 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

dorprocboot=1
name_overlays=k3-j721e-vision-apps.dtbo

Also, I use the last version for both psdk that is : 07_02_00_06

Did I miss something or is it normal ?
How can I fix my display then ?

Thanks in advance,

Thomas Agnola

over 4 years ago

0 Brijesh Jadav over 4 years ago

TI__Guru**** 484275 points

Hi Thomas,

Yes, can you please try commenting out k3-j721e-vision-apps.dtbo in the uEnv.txt file and also set dorprocboot flasg to 0?

Then it should display few text like console on the display.

Regards,

Brijesh

0 Thomas Agnola over 4 years ago in reply to Brijesh Jadav

Prodigy 20 points

Hello Brijesh,

Unfortunately, setting dorprocboot to 0 will stop the board at :

remoteproc remoteproc5: Booting fw image j7-main-r5f0_1-fw, size 1964032

I also tried, just with commenting out k3-j721e-vision-apps.dtbo but it didn't display anyhting.
I even rebuilt both sdk today and my result are given with this fresh installation.
So, I really don't know why, I can't have something on my display.

Also, I was confident, but I re-tried to use the cable with a computer, and no problem with it, the screen displayed my computer display.

Have you any other ideas that I can test ?

Regards,

Thomas Agnola

0 Brijesh Jadav over 4 years ago in reply to Thomas Agnola

TI__Guru**** 484275 points

Hi Thomas,

Can you please run upto step-4 from the link, https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/psdk_rtos/docs/user_guide/out_of_box_j721e.html?

This will create SD card with the PSDKLA filesystem, but will not copy vision apps demos. Can you try booting with this SD card?

Regards,

Brijesh

0 Thomas Agnola over 4 years ago in reply to Brijesh Jadav

Prodigy 20 points

Hello Brijesh,

I followed the steps with ti-processor-sdk-rtos-j721e-evm-07_02_00_06-prebuilt.tar.gz.
The result is the same as always,
no display and no /dev/fb0 which I believe is the device that manage the display.

I can mention that even without the extra data_set, uEnv.txt is still populated with the 'name_overlays' line.

log board prebuilt.txt

Can it be a configuration prior to the psdkla ?
Or can I even try to install this device by any means ?

Regards,

Thomas Agnola

0 Brijesh Jadav over 4 years ago in reply to Thomas Agnola

TI__Guru**** 484275 points

Hi Thomas,

I still dont see dss being initialized in the Linux. I think you are still installing vision apps binaries to SD card. Could you please avoid it?

You could just create the SD card and copy filesystem to it, as explained in the above link. Just run upto step-4. This would essentially mean that vision apps would not copied to SD card, then DSS would be controlled by Linux.

Regards,

Brijesh

0 Thomas Agnola over 4 years ago in reply to Brijesh Jadav

Prodigy 20 points

Hello Brijesh,

So, I looked into the steps and found that my problem wasn't what I did but the first command in step-4.
I opened the install_to_sd_card.sh file and found that it start to install some part of the vision apps files.
Instead of launching this script, I extracted myself the file to my sd card and I have normally just the linux filesystem.

I still have my problem but now, I have the /dev/fb0 driver.
When I try to launch psplash myself I get this error :FBIOPUT_VSCREENINFO failed, double buffering disabled

log board linux.txt

I hope that you will found what you want.

Regards,

Thomas Agnola

0 Brijesh Jadav over 4 years ago in reply to Thomas Agnola

TI__Guru**** 484275 points

Hi Thomas,

But before that, do you see the screen being recognized and some display on the screen?

In the log, i see DSS being initialized by Linux now. So you should see now some display.

Regards,

Brijesh

0 Thomas Agnola over 4 years ago in reply to Brijesh Jadav

Prodigy 20 points

Hi,

Unfortunately not, my screen still shows nothing.
I still have psplash that fail and my screen goes to sleep.
Even after the boot sequence, nothing is displayed.

Regards,

Thomas Agnola

0 Brijesh Jadav over 4 years ago in reply to Thomas Agnola

TI__Guru**** 484275 points

Hi,

I see one error in your log "*ERROR* Failed to read EDID".

But i do see same error on my setup also. Even then i see DSS is turned on at the boot time and i see images getting displays.

What command do you use to start psplash?

Regards,

Brijesh

0 Thomas Agnola over 4 years ago in reply to Brijesh Jadav

Prodigy 20 points

Hi,

I can use two command to start psplash :
/usr/bin/psplash
and
/etc/init.d/psplash.sh

The first was found when I was searching some way to launch it.
The last one is referenced by : systemctl status psplash.service.

both gave me the same error.

Regards,

Thomas Agnola

0 Brijesh Jadav over 4 years ago in reply to Thomas Agnola

TI__Guru**** 484275 points

Hi Thomas,

I also see same error, but this issue is due to unsupported double buffering the driver. I am not sure how to enable it or is ever supported. I will check with the team and get back to you.

But i do see valid image displayed on the screen as soon as Linux kernel boots up.

Regards,

Brijesh

0 Thomas Agnola over 4 years ago in reply to Brijesh Jadav

Prodigy 20 points

Hi Brijesh,

So this error shouldn't cause my problem then.
If, so I don't know what I can do to resolve it.
I re-tried again the steps and had the same result.
If it can be an hint, I can mention that via my manipulation the uEnv.txt is empty.
I attached a photo of my board to be completely sure that I connected the cables to the right spots.

I will continue searching why the display is not displaying anything, and hope that something can be done by your team.

Regards,

Thomas Agnola

0 Brijesh Jadav over 4 years ago in reply to Thomas Agnola

TI__Guru**** 484275 points

Hi Thomas,

I am checking why i get EDID error. That's important one. Without EDID support, it would be difficult to support new display.

I will get back to you as soon as i find some changes.

Regards,

Brijesh

Processors

Processors forum

TDA4VM: Display boot file not present