How to enable DP port in xavier AGX L4T32.4.3

Still let me say this again.

Disable all the ports and leave only one you want to debug.
DP log from all the ports are coming out together and it is hard to read.

1 Like

btw, sharing some posts that are related to the DP.

Hi,
Attaching dmsg log file with HDMI_DP0 only enabled, also here are some debug data:

nvidia@localhost:~$ sudo cat /sys/kernel/debug/tegradc.1/mode
[sudo] password for nvidia:
cat: /sys/kernel/debug/tegradc.1/mode: No such file or directory
nvidia@localhost:~$ sudo cat /sys/kernel/debug/tegradc.0/mode
pclk: 74250000
h_ref_to_sync: 0
v_ref_to_sync: 0
h_sync_width: 40
v_sync_width: 5
h_back_porch: 220
v_back_porch: 20
h_active: 1280
v_active: 720
h_front_porch: 110
v_front_porch: 5
flags: 0x0
stereo_mode: 0
avi_m: 0x2
vmode: 0x10600000
nvidia@localhost:~$ sudo cat /sys/kernel/debug/tegradc.2/mode
cat: /sys/kernel/debug/tegradc.2/mode: No such file or directory
nvidia@localhost:~$ sudo cat /sys/class/graphics/fb0/mode
U:1280x720p-60
nvidia@localhost:~$ sudo cat /sys/class/graphics/fb1/mode
cat: /sys/class/graphics/fb1/mode: No such file or directory
nvidia@localhost:~$ sudo cat /sys/class/graphics/fb2/mode
cat: /sys/class/graphics/fb2/mode: No such file or directory
nvidia@localhost:~$ sudo cat /sys/kernel/debug/tegradc.0/edid
00 ff ff ff ff ff ff 00 3a c4 01 00 00 00 00 00
05 1b 01 03 80 59 32 8c 0a e2 bd a1 5b 4a 98 24
15 47 4a 20 00 00 01 01 01 01 01 01 01 01 01 01
01 01 01 01 01 01 01 1d 00 72 51 d0 1e 20 6e 28
55 00 75 f2 31 00 00 1e 01 1d 00 bc 52 d0 1e 20
b8 28 55 40 75 f2 31 00 00 1e 00 00 00 fd 00 32
3d 0f 2e 08 00 0a 20 20 20 20 20 20 00 00 00 fc
00 4e 56 49 44 49 41 00 0a 20 20 20 20 20 01 f9
02 03 19 71 46 84 13 05 14 03 12 23 09 07 07 83
01 00 00 65 03 0c 00 10 00 01 1d 80 18 71 1c 16
20 58 2c 25 00 75 f2 31 00 00 9e 01 1d 80 d0 72
1c 16 20 10 2c 25 80 75 f2 31 00 00 9e 8c 0a d0
8a 20 e0 2d 10 10 3e 96 00 75 f2 31 00 00 18 8c
0a d0 90 20 40 31 20 0c 40 55 00 75 f2 31 00 00
18 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ca
nvidia@localhost:~$ sudo cat /sys/kernel/debug/tegradc.1/edid
cat: /sys/kernel/debug/tegradc.1/edid: No such file or directory
nvidia@localhost:~$ sudo cat /sys/kernel/debug/tegradc.2/edid
cat: /sys/kernel/debug/tegradc.2/edid: No such file or directory
nvidia@localhost:~$ sudo cat /sys/kernel/debug/tegradc.0/stats
underflows: 0
underflow_frames: 0

fb1_Head1_SOR0_HDMI_DP0_Enabled_Dmesg_02182021.txt (74.3 KB)

Is this edid from your monitor or from the fallback mode?

Looks like it has taken from Fallback. not matching with my display EDID.

I have made below changes:
dp.c (90.5 KB) edid.c (26.5 KB) tegra194-p2822-disp.dtsi (3.1 KB) tegra194-p2888-0001-p2822-0000-common.dtsi (7.4 KB)
in edid.c made use_fallback = true
int tegra_edid_get_monspecs(struct tegra_edid *edid, struct fb_monspecs *specs)
{
int i;
int j;
int ret;
int extension_blocks;
struct tegra_edid_pvt *new_data, *old_data;
u8 checksum = 0;
u8 *data;
bool use_fallback = true;

in dp.c removed below
if (dc->edid->errors) {
return (mode->xres == 640 && mode->yres == 480)
? true : false;
}

in tegra194-p2888-0001-p2822-0000-common.dtsi

removed ā€œnvidia,typec-port = /bits/ 8 <0>;ā€

in tegra194-p2822-disp.dtsi changed as below

  • fb0: Head0->SOR2->HDMI ā€“ disabled
  • fb1: Head1->SOR0->DP0
  • fb2: Head2->SOR1->DP1 ā€“ disabled

Why do you have to enable fallback edid and remove that line from dp.c in the beginning?

Does your hardware design really match the design guide?

I have not enabled fallback earlier, just to have a try if it works with fallback I have tried this option, My HW team confirmed that it matches with the design guide.

Please restore it back and see if it can read your edid or not.

Hi,

Now I have restored the fallback to false,
Current Combination is fb1: Head1->SOR0->DP0 to use as DP,
disabled other HDMI_DP1 and HDMI_DP2.
Connected to an AOC display.

Attached Kernel log and debug logs fb1_Head1_SOR0_HDMI_DP0_Enabled_Fallback_false_Dmesg_02192021.txt (83.0 KB) with EDID. can you check?

Actually the log looks fine and I donā€™t see any error.

If there is still no signal, maybe you can try to do the tuning.

https://developer.nvidia.com/embedded/downloads#?search=tuning

Hi,
Right now we do not have setup for tuning.

But meanwhile we have observed the display comes for a while, during boot we can se some boot messages and nvidia logo and then boots to desktop as well and goes off. this is a short time period, Looks like it is not on during all these time we miss to see some log messages in between.

We suspected the DP connector side and looking into it, do you have any suggestion on this behavior?
Currently I am working with these configurations -
use_fallback=false,
default EDID,
only one DP enabled,
type C option removed.

Do you have uart console on your side to dump the log from cboot?

The boot logo is from bootloader but not kernel so the dmesg will not print info about it.

Also, what kind of ā€œboot messageā€ do you see on the screen? Could you make a video to show us what is on your screen?

Why do you suspect connector side? How about posting your board and connector schematic here?

Hi,

I could not make a video, but here is the boot log from serial console fb1_Head1_SOR0_HDMI_DP0_Enabled_Fallback_false_bootlog_02192021.txt (28.5 KB)
This is the one you are asking for?

It appears to be the same message which I see on serial console while booting, flashes on the display for fraction of seconds.

I think the monitor is already okā€¦ just the desktop fails to launch.

Since our cboot does not initialize dp monitor, if you see something on the display, it must be from kernel.

Share me the xorg.0.log please.

Yes, we can also see the ubuntu desktop I mean it shows user login screen, standard ā€œubuntu/gnomeā€ desktop screen sometime.
Here is the xorg.O.log,

Xorg.0.log_02222021.txt (5.5 KB)

I am not sure why you didnā€™t mention that until nowā€¦

If you can see the desktop, it means the software side is done and no more problemā€¦

Ah, I have missed to make it in detail. Sorry for that, Will look into HW things now. May be as I told earlier we are looking into connector side

1 Like

Hi, Here is the video for reference. We can see some boot logs, then mouse curser and then log in screen, then it goes off

According to the video, I think software side does not have any problem.

1 Like