Custom carrier board kernel modyfication - RGMII, HDMI

Hi
I am trying to run my own hardware board where I mount the module: NVIDIA 900-13701-0040-000
I am not an expert in software however I need to do this to test the hardware. Unfortunately the instructions are not clear enough for me to do this.

I am using JetPack version 6.0 rev2 Release Tag: jetson_36.3

I have installed the SDKManager software. I can do a flash of the software.

I was able to make the following modifications:
Remove MGBE > ODMDATA=“gbe-uphy-config-0,hsstp-lane-map-3,nvhs-uphy-config-0,hsio-uphy-config-0”;

delete EEPROM > cvb_eeprom_read_size = <0x0>.

After these procedures, the module starts up. However, the image via HDMI does not work - this is similar to the one from the Jetson AGX Xavier schematic and Design Guide for Orin AGX.
Design Guide:

our:

I also wanted to point out that the development board on which I am performing the upload has HDMI and not DP as it is in the schematic. It is a Leetop 900-44805-0000 and I have an image on the original board, but I don’t have a complete schematic for it and I don’t know where the differences are.

I found a lot of information, however, I am lost in what AND how:
https://docs.nvidia.com/jetson/archives/r36.3/DeveloperGuide/SD/Kernel/DisplayConfigurationAndBringUp/OrinDisplayconfig.html

I downloaded:

tegra234-dcb-p3701-0000-a02-p3737-0000-a01_hdmi.dtsi (from: Jetson Linux 34.1.1 | NVIDIA Developer)
Instead of:
tegra234-dcb-p3701-0000-a02-p3737-0000-a01.dtsi (since it does not appear here! Jetson Linux | NVIDIA Developer)

I ran the tool with my downloaded from the internet file
./dcb_tool -m tegra234-dcb-p3701-0000-a02-p3737-0000-a01_hdmi.dtsi

And I see something like this. I understand that this is the configuration in the file I got from the internet and not mine. Mine might be different? However, I have HDMI working on this development board, so how to determine the difference?

I use 88E1512 as the ETH PHY chip via RGMII. A solution according to the Design Guide and scaled to Jetson Xavier (P2822_B03_OrCAD_schematics).

What is the easiest way to run both?
Please do not refer me to the Design Guide or PinMux documents because in this case it is unclear to me and I cannot use it

Hi, did you measure the HDMI_5V and HDMI_3V3 output?

Do you have any software guys on your side that can help you and communicate with us? It would be a painful one if you don’t have the knowledge to check these software things here.

Hi. Thank you for your reply.

Hi, did you measure the HDMI_5V and HDMI_3V3 output?

Yes, I have these voltages.

Do you have any software guys on your side that can help you and communicate with us? It would be a painful one if you don’t have the knowledge to check these software things here.

I misspoke earlier. I will follow all instructions if only the instructions are detailed enough. As you can see some small steps I have already done, the description was good.
I need to get the equipment up and running before passing it on. Otherwise, making modifications to the equipment will be very difficult.

I analyzed the schematic again and found a problem with the SCL and SDA lines swapped. I fixed the connection but still no picture.
On the socket I have HDMI_CEC 3.3V regardless of plugging in. The HDMI_HPD signal going to the SOM responds to plugging in the connector. I tried disconnecting this circuit to verify that it is not active in the opposite state. No change.

Is there a command in Ubuntu that forces the monitor data to be sent or read via this IIC? it would help me with testing.

Is it possible that even though I have the HDMI image on the original development board, I need to make other changes in my software?

I hope we just discuss one issue in one topic each time. For another issue, please open new topic.

Do you want to discuss HDMI here or the RGMII?

Okay, there is more information about HDMI here so let’s focus on that topic.

I checked IIC communications more thoroughly. Disconnecting and connecting HDMI has this effect - On the right side of the values that have been decoded.


zoom:

Hi,

I don’t check things from hardware but only software.

Please share me the dmesg/xrandr and /var/log/Xorg.0.log here.

agx_27_08.txt (14.2 KB)

In addition, I analyzed several similar topics. I checked only “sudo dmesg” and “xrandr”:
agx_27_08_dmesg.txt (55.0 KB)

dmesg after hotplug:
agx_27_08_dmesg_hotplug.txt (60.7 KB)

lsmod part/full:
image

agx_27_08_dmesg_lsmod.txt (5.5 KB)

I would like to add that if with this software I translate the AGX to the original devboard then I get the image. I do the tests on two different monitors.

Hi,

Your xorg log indicates

  1. Your dcb change didn’t take effect.

  2. GPIO hotplug pin is not added.

Hi,
thank you for your reply.
Where can I find instructions to do the compilation with my dtb file for version 36.3? Do I need to swap any specific files or where to upload it to make it work? We reviewed the instructions for older versions but they seem to be outdated.
Is the tegra234-dcb-p3701-0000-a02-p3737-0000-a01_hdmi.dtsi file downloaded from your site and instuctions for 34.1.1 correct?

Unfortunately, we did not get additional information so we are trying to continue on our own.

We did it according to the instructions given in the link (Jetson AGX Orin Platform Adaptation and Bring-Up — NVIDIA Jetson Linux Developer Guide 1 documentation) , more specifically:

  1. we copied the new .dtb to the Linux_for_tegra/kernel/dtb folder

  2. we replaced the name of the DTB_FILE variable with the correct one in the devkit confuiguration file (jetson-agx-orin-devkit.conf);

  3. just in case, we also modified extlinux.conf, adding the FDT field with the name to the correct .dtb file;

  4. we performed a flashing using: sudo ./flash.sh jetson-agx-orin-devkit mmcblk0p1

  5. still no image after booting. You can see the changes in the Extlinux file (FDT field), but our .dtb file is not included

Do you have any tips for us?

Please refer to p3509+p3767 board config file. That one has all the setting for HDMI.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.