I am using the product 900-82888-0080-000 (Jetson AGX Xavier Industrial) and flashing the image directly from the SDK manager. The used linux version is Jetson_Linux_R35.1.0_aarch64. In this version USB is detected but I am not getting HDMI output. I have routed HDMI/DP0 port for the display signal. Cable and carrier board working is confirmed with the older version module (Jetson AGX Xavier). Kindly suggest what are the changes need to be done in the source file to get the HDMI output in port0. Any changes need to be done in PINMUX file. Kindly suggest.
What is port0 here? Could you give a hardware pin name?
And why HDMI is related to USB?
I mean it is HDMI_DP0 _TXDP/NX.
No not any USB comes into picture, i have given the clarity that Jetson is booting properly and we are facing issue in HDMI output.
Hi,
Does any engineer on your side have experience with linux kernel and device tree?
No. I am from hardware side. myself only have to do the changes. guide me the steps to update.
Actually we have application support team they have experience in linux kernal.
JETSON MODULE 1.txt (83.8 KB)
tegra194-p2822-disp (1) (1) NEW.dtsi (3.0 KB)
tegra194-p2822-disp (1) OLD.dtsi (3.4 KB)
Attached log of the Jetson AGX Xavier with the file name Jetson Module 1
and also dtsi files attached wrt the changes done with old jetson Agx Xavier module which is having linux kernel 32.5.2 but the same changes tried to implement in the new Jetson AGX xavier industrial, it is not possible to build the kernel getting kernel build error.
Hi,
Could you let your application support team directly reply on this forum topic?
It would be more efficient to both of us.
Also, one question before I check your dts file, are you directly using a file on rel-32 to rel-35 to build? Or you are modifying from rel-35 source code?
And, your error log does not look like anything related to the dtsi files here. I guess you couldn’t even build the default NV kernel source code, right?
I will add that instead of screenshots there is something which is both easier and better information for creating logs. This is just an example, so it isn’t your specific build command, but you can append “2>&1 | log_something.txt” to any command and get a complete log. Example:
uname -r 2>&1 | tee log_uname.txt
Or another example:
sudo make mrproper
make O=$KERNEL_OUT ARCH=arm64 tegra_defconfig 2>&1 | tee defconfig.txt
# Maybe run a customization now in menuconfig or nconfig, and simply say what was altered.
make O=$KERNEL_OUT ARCH=arm64 modules_prepare 2>&1 | tee prepare.txt
# Just assuming you are using 12 cores here:
make O=$KERNEL_OUT ARCH=arm64 -j 12 modules 2>&1 | tee modules.txt
make O=$KERNEL_OUT ARCH=arm64 INSTALL_MOD_PATH=$KERNEL_MODULES_OUT modules_install 2>&1 | tee module_install.txt
I also want to suggest that for any kernel build error it is very important to know (A) what the configuration was, and (B) if the configuration was correctly propagated before building. Building the Image target will propagate the configuration, but if this step is not used, then you might want to build the “modules_depend” target before building other targets. We can assume this was all correct, but if one little part is missing, then debugging kernel build is difficult. I see setting LOCALVERSION, so I’m guessing the rest of it is correct, but I did not see any “tegra_defconfig” or previous configuration (I can’t be certain, and the order of steps matters).
It might also be useful (assuming cross compile) to include the output of:
${CROSS_COMPILE}gcc --version
Hi Wayne,
We are modifying in the rel-35 source code and trying to build.
Please try to answer all the questions I asked…
Sorry for that…
yes we couldn’t able to build default NV kernel source code.
Ok. Please check the page here to make sure you are using correct tool and also follow the page here to build kernel.
https://docs.nvidia.com/jetson/archives/r35.4.1/DeveloperGuide/text/SD/Kernel.html
Rel-32 and rel35 use different tool.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.