No, this is not correct… there is a board config jetson-agx-orin-devkit-industrial.conf for industrial board.
Then what you’re saying is
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -p “-c ./bootloader/generic/cfg/flash_t234_qspi.xml” -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --network usb0 jetson-agx-orin-devkit-industrial nvme0n1p1
Is this the right command?
Yes, and jetson-agx-orin-devkit-industrial.conf is the config file you should start to modify.
But I have a question here. What I’m curious about is the process of applying build images, that is, enabling HDMI ports instead of DP ports on custom boards. Isn’t this process done before the Flash process?
I am not talking about anything related to build or enable HDMI yet.
The point here is you didn’t even know how to flash the correct config for your board or which file to modify…
Hi,
If so, how should I modify the jeston-agx-orin-devkit-industrial.conf file?
Now, you know which file you are using to flash a industrial.
p3509-a02-p3767-0000.conf has 4 field for enabling HDMI.
As my previous comment here, I hope you could understand it now. You need to refer to p3509-a02-p3767-0000.conf and add missing things to your industrial config.
And if you don’t know where to find something like the source code, then this website has it for every version.
And the developer guide doc in each version provides the method for how to rebuild the kernel.
Hi,
I checked this part of Changing the Display Function Between DP and HDMI in Software Features in Depth/Kernel/Display Configuration and Bring-Up. Is it correct to create and apply dtsi files according to the carrier board design made by the user from the provided pinmux sheet?
Hi,
The reason why I told you to refer to p3509-a02-p3767-0000.conf is because they are already doing this thing for you.
The “Changing the Display Function Between DP and HDMI” is already 100% covered in p3509-a02-p3767-0000.conf.
What I am talking about is the “dtsi” you are talking about here is already part of the software included in the dtbo of p3509-a02-p3767-0000.conf.
The pinmux is partially covered. Actually you just need to update one pin state (your HPD pin) in the default industrial pinmux file is sufficient.
You don’t even need to download the pinmux spreadsheet and do everything from the beginning.
Jetson Orin display software is basically not able to be changed much. The method to configure between DP and HDMI is a fixed pattern. There is no difference when it is on your board or other user’s hardware board. It is just a very fixed software. That is why using p3509-a02-p3767-0000.conf would be a quicker solution than digging those documentation from scratch.
Hi,
readme.txt (13.6 KB)
I read the file attached above and modified the tegra234-dcb-p37-0000-p3701-0000.dtsi file using dcb_tools and changed it from DP type to HDMI type. I flushed jetson-agx-orin-devkit-independent.conf using the above, but there was a problem that the screen was output normally but USB was not recognized. What is the way to solve this?
Hi,
If this becomes a USB issue then it is not related to original problem. Please file a new topic.
It is normal that USB would not work directly on a custom board. You didn’t change anything for the usb, so of course it is still default setting for Devkit, not your board.
Hi,
Is it the right way to change DP to HDMI by modifying the dtsi file the way I said above?
I don’t know if you ever understand things here because I already mentioned that multiple times.
Basically, this file in p3509-a02-p3767-0000.conf already has the correct content for HDMI setting.
OVERLAY_DTB_FILE+=“,tegra234-dcb-p3767-0000-hdmi.dtbo”;
So if you want to know whether your configuration is correct, you could just compare your result with above dtbo source code.
But actually this is kind of duplicated work that you could just use tegra234-dcb-p3767-0000-hdmi.dtbo…
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.