We upgraded from version 6.2.2 to 7.2.0. The tegra234-dcb-p3737-0000-p3701-0000.dtsi file was modified. However, the system failed to boot and only the log could be accessed. But when the 6.2.2 version was burned in, it could function normally. Why is this?
SaveWindows2026_7_17_11-46-02.TXT (72.7 KB)
Pease check if your issue is similar as JetPack 7.2 - Flashing fails for module 699-13701-0005-502, works for module 699-13701-0005-501,
I feel this is duplciated.
Did you use Jetpack 7.2 Linux_for_Tegra/ version of dcb_tool to make your change? OrinDisplayconfig
On x86_64/amd64 Ubuntu host
/Linux_for_Tegra$ ls tools/dcb_tool/
dcb_tool readme.txt
You should also get and post a serial log of an attempted boot.
7.2.0 This file, tegra234-dcb-p3737-0000-p3701-0000.dtsi, will function normally if not modified. However, it does not support 4K. We have debugged it on 6.2.2 and it can start normally and support 4K resolution. However, when ported to 7.2.0, it fails to start.
Is it necessary to re-create the DCB file?
I think so and you probably need to make all edits you applied to 6.2.2 Linux_for_Tegra files and device tree source, to the Jetpack7.2 files. That is why you may see custom carrier boards staying on the older Jetpack version they originally built their board with.
However, I re-created the DCB file and burned it in, but it still wouldn’t boot. The binary in the newly created DCB is the same as the previous 6.2.2 version.
Could you please tell me if there has been any progress? Unlike the issue you reported, the current problem is mainly focused on this file: tegra234-dcb-p3737-0000-p3701-0000.dtsi. Even after re-making it, it still fails to start.
Is this s a custom board or NV devkit?
I am not sure why a display DCB is under discussion here. I don’t see anything related to display.
Will issue be gone if you use default DCB setting? My point here is, why do you think dcb is leading to the problem?
The log is not full complete log. You should provide full log first.
We are providing a custom service. This is the complete log from the burning process to the startup, including the situation where the system failed to start and the hardware was reset once.
log.txt (275.0 KB)
Could it be determined the cause from the log?
If the default settings are used, the dcb problem will disappear.
Hi,
這邊用中文跟您詢問一下
你這裡要說的應該是你改了dcb內容之後 boot error就消失了對吧?
前面已經提過了, 你現在碰到的error log完全沒有任何display相關的錯誤.
(我只是要澄清一下, 因為你的英文寫的是"dcb 問題沒了" . 但我完全不知道你所謂的dcb問題是什麼)
那現在的狀況是你的螢幕沒辦法使用了是嗎?
已经解决了，就是dcb的问题，重新配置了dcb就没有问题了
請問你之前的問題是因為直接拿jp6的DCB到jp7使用嗎?
是的，我是用jp6的dcb在jp7.2上面使用的