Hi ALL, I purchased a jetson ORIN AGX 32GB development kit from Seeed studio. After successful flashing the ORIN module with HOST System. Development kit is not Booting.
Third party carrier boards usually require customized firmware (device tree). Does the Seeed Studio web page for this specific carrier board state that you should use the default NVIDIA flash software (BSP)? Or does Seeed provide flash software? It sounds like you might be flashing the wrong device tree.
FYI, almost all debugging on forums will require a serial console boot log. The Seeed Studio documentation probably lists a micro-OTG USB port, and perhaps provides a micro-B USB cable for that purpose (I’ve not worked with a Seeed Studio carrier board so I can’t say for certain what serial console support it has).
Thanks for the update. we followed the Seeed Studio web page for this specific carrier board . we are able to flash the software.
We want to flash ORIN with our custom carrier board, we are following the T234 BCT Deployment Guide]. Could you please support us.Other then the above document, is there any other documents that will help us.
The part which has to change for a custom carrier board is the device tree. This is firmware which tells the module which pins to assign particular functions, and in general, how to find the hardware and associate a driver with that hardware (the non-plug-n-play parts).
The general documents listing for AGX Orin is here:
https://developer.nvidia.com/embedded/downloads#?tx=$product,jetson_agx_orin
Within that you are interested in the “Platform Adaptation and Bring-Up Guides”, or anything on device tree. Looks like the “Platform Adaptation and Bring-Up Guides” are part of the specific L4T release URL, or there is an online version. Just go to that general URL above and type in “adaptation” in the search box.
FYI, you can find your specific L4T release version via “head -n 1 /etc/nv_tegra_release”. You can then find that specific documentation and download URL from here:
https://developer.nvidia.com/linux-tegra
Note that there is a dev kit version or a reference schematic for the Jetson dev kits. The default device trees are for that design. You would essentially start with that, and then edit nodes in the device tree which correspond to any changes in pinout.
You might also want to search on that document download page for “pinmux”:
https://developer.nvidia.com/embedded/downloads#?search=pinmux&tx=$product,jetson_agx_orin
The PINMUX spreadsheet has macros (you have to enable them) with a more general method of generating a device tree. Basically you pick pin functions, and then it can generate a tree. I can’t guarantee it, but I think the defaults are the same as the dev kit, so you might consider using that and then editing based on the spreadsheet.
The most difficult way to edit the device tree is via setting up the kernel configuration correctly, and then building the device tree target (I think it is the “dtbo” target, have not used that in a very long time; you’d have to propagate the configuration prior to doing that). The only time I find this useful is if you are editing or developing a kernel module. Then you can edit the .dtsi content for your custom driver as you change the driver source code.
Also, make generous use of the dtc (“device tree compiler”) program. The kernel source comes with its own version, but it isn’t useful if you are not building trees from correctly configured source. You can run “which dtc” to see if your system already has it. If not, then “sudo apt-get install device-tree-compiler”.
dtc can take an existing binary tree and convert it to source, which is human readable and editable:
dtc -I dtb -O dts -o something.dts original.dtb
On a running system you can extract the device tree from “/proc”:
dtc -I fs -O dts -o extracted.dts /proc/device-tree
(keep in mind that the early boot stages can edit a tree before handing it off to the kernel, so although this is quite useful there are a few cases where it won’t be an exact match)
An edited .dts can be recompiled:
dts -I dts -O dtb -o recompiled.dtb original_source.dts
Mainly, start with the adaptation and bring-up guide.
Dear Team,
After completing the kernel customization, i am able to flash the ORIN module and able to see the bios screen. But not able to boot to OS. the error that i am encountering was: **e requested configuration of display devices is not supported in the gpu jetson agx orin Could you please guide me to solve this issue.
- Can you post a full serial console boot log? Is it correct that the error is somewhere during boot and not during flash?
- Is the monitor purely DisplayPort, or perhaps HDMI with a DP adapter (which is ok)? Or is some other video interface being adapted, e.g., old style VGA or DVI?
- Also, is there anything unusual about the monitor?
error.txt (58.2 KB)
Dear Team,
Please find the attached error Log.
We have ORIN development kit. we used the same monitor and it is working in that case. monitor model DELL P2419H.
That log actually includes some copy and paste from the forums. If you skip that part, and get to the actual log, here are some notes:
- The Linux kernel loads correctly. Boot stages have completed.
- The rootfs is mounted on
/dev/mmcblk0p1, meaning the eMMC rootfs. This system has the possibility of working. - Some of the environment loads correctly.
- Using random self ethernet and host ethernet address makes me wonder if there is an i2c issue with EEPROM, but that’s a very wild guess. Just something to think about, and it might not matter.
- It gets to
nvidia-modeset, which is part of video. It states that the device configurations are not supported. Excerpt:
[ 42.042582] nvidia-modeset: ERROR: GPU:0: The requested configuration of display devices (DELL P2419H (HDMI-1), DELL P2419H (HDMI-0)) is not supported on this GPU.
[ 42.060658] nvidia-modeset: ERROR: GPU:0: The requested configuration of display devices (DELL P2419H (HDMI-1), DELL P2419H (HDMI-0)) is not supported on this GPU.
- You can’t see video, but it is asking for completion of first boot account setup. You just need to do that to set up the login name, and then at least text mode would work. The system is actually booting, and only video is an issue.
Regarding this message, it implies you need to complete first boot account setup via serial console:
[ 44.109332] Please complete system configuration setup on the serial port provided by Jetson's USB device mode connection. e.g. /dev/ttyACMx where x can 0, 1, 2 etc.
If you have the serial console port attached to your Linux host PC (and basically that is what the serial console port is that you are using for the log), then you should be able to interact with the Jetson via the Linux host PC talking to that port (“/dev/ttyACM0” if you have no other serial UARTs on the host PC of that chipset). After you boot this far, can you hit the enter key on the serial console and complete first boot setup?
Once that is done you can deal with the video issue. Having a user you can log in with makes life much easier, although it might simply be the monitor has odd specs. Is there anything unusual about your Dell P2419H? Or the adapter (it says it is using HDMI, so unless your carrier board has HDMI, meaning it isn’t a dev kit, then you are using an adapter from DisplayPort to HDMI…this is generally ok).
If your monitor is not unusual, then consider this error (which might or might not be related):
[ 16.644003] ucsi_ccg 1-0008: i2c_transfer failed -121
[ 16.652000] ucsi_ccg 1-0008: ucsi_ccg_init failed - -121
[ 16.660378] ucsi_ccg: probe of 1-0008 failed with error -121
There is a wire on HDMI and DisplayPort, the DDC wire. That wire transfers EDID data (plug-n-play description of monitor specs). The lower level protocol under this is i2c. If the i2c linked to the HDMI or DisplayPort is not functioning, or if it is corrupt, then the monitor’s true settings will not be valid. This includes issues like hot plug detect being wrong, or power rails to i2c being incorrect (but there is more than one i2c so I don’t know if the error above is related; however, it occurs right before nvidia-modeset, so it probably is related).
The i2c and rails are generally set up on customized carrier boards via the device tree. This is a Seeed Studio carrier board it seems, and I am thinking that perhaps it really does require a customized device tree (at least for the DDC wire of HDMI or DisplayPort).
Hi Team After installing the display drivers we are able to see the display.Thanks for your support.
Need help on RGMII interface signals. we are using 1G ethernet in our carrier board design.We changed the pinmux as per the design guide Table 8-1. Orin Module Gigabit Ethernet Pin Descriptions. After that we replaced the PINMUX and GPIO dtsi files from the traget . we are using DP83867CRRGZR oin our design. After flashing we are not able to see the device.
You’ll need to create a new forum thread specific to that. It is likely that some other device tree modification (e.g., via PINMUX) is required, but I couldn’t tell you the specifics for that.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.