Setup-
Hardware: Jetson AGX Orin on a custom carrier board
SKUs tested: 0008 (Industrial) and 0005 (DevKit)
Software: Jetson Linux r36.3 (same BSP/rootfs image for both), same monitor/cable
Symptom
SKU 0005 (DevKit): gets text during early boot and full graphics after Linux is up.
SKU 0008 (Industrial): no video at all (no early text, no graphics) on the attached monitor, even though the system boots normally over serial.
Notes-
Both units are flashed from the same build; UEFI boot app hashes match.
Have the same GPIO/Pinmux/Pad DTSI
Flash conf files–
0005.conf.txt (3.2 KB)
0008.conf.txt (3.4 KB)
Looking for guidance on what typically prevents early console and DRM/KMS graphics from coming up on Industrial builds vs DevKit when running the same image on a custom carrier.
Questions-
What are the common differences between DevKit vs Industrial SKUs that impact display bring-up (UEFI handoff/simple-framebuffer, GOP/HPD policies, DT display nodes)?
Any specific checks or knobs (UEFI/PCD, efivars, DT status/HPD/DP-AUX) to focus on for Industrial SKU 0008?
Notice that framebuffer is not enabled on the Industrial, 0008. Not sure how it is set
Happy to provide boot logs, running DT dumps, and extlinux/UEFI details if helpful.
bootlog-good-video-0005.txt (72.1 KB)
bootlog-no-video-0008.txt (86.5 KB)
0008.running.dts.txt (673.7 KB)
0005-running-dts.txt (673.4 KB)