Hi,
I change the boot dtb file ,now xavier can not work normally,I want to enter recovery mode to fix the dtb file ,How to enter recovery mode ?
Hi xubin4952,
Are you using the devkit or custom board for AGX Xavier?
What’s your Jetpack version in use?
Please press REC button → power up the board(plug power cable and press power button) → release REC button to enter into force recovery state.
Hi Kevin，
I am using xavier agx devkit,jetpack version is R35.21.
I have try press ESC but It seems not into boot mode.The programmer will stop here . Now I can not do anything. What should I do now ?
Hi Kevin,
I’m in urgent need of using this board right now. Could you please provide some suggestions to get this board back to working condition? Thank you.
Have you tried this and run lsusb from your host to confirm the board is recognized?
Hi Kevin，
I have try to press ESC .It seems enter recovery mode,But I can not conrol the xavier by console,
This is lsusb command.
This is log.
You don’t need to press ESC to enter forced-recovery state.
Please just follow the steps I shared and check the result of lsusb.
It should be 7e19 rather than 7019.
My device is xavier AGX not NX ,I think it is right .
But what should I do to make the xavier work normal.
Okay, it’s 7019 for AGX Xavier.
Please use SDK Manager to flash the devkit or you can setup BSP package and run flash.sh to flash your board to recover
Hi Kevin,
Thank you for your reply!
What is the problem with this board?I just change the dtb file why I need to flash the board?
I don’t know what you modify the dtb to cause it booting failed in MB1 so that suggesting you to flash the board to recover. Since you are using the dekvit, you can simply use SDK Manager to reflash it.
FYI, you could clone first to save the rootfs content.
Regarding device trees, think of them as arguments passed to drivers. Many hardware devices are at some physical address on a bus, and they are not “plug-n-play”, so they cannot self-report their address nor even what they are. This is normally set up via device tree.
Jetsons do not have a BIOS which would make it possible to reach an initial boot state without any flashed software. However, Jetsons do require the equivalent of the BIOS function, which is performed in software. This occurs very early on in boot, and if the device tree is missing or incorrect, then this early boot stage won’t be able to find the hardware (the boot software won’t know how to associate a driver to that address, long before Linux ever starts; Linux inherits this environment).
If your device tree breaks something critical to boot, then this will cause boot failure. There are other places where a device tree can fail and there will be no issue booting, but some subset of Linux will no longer function.
The backup and restore is for everything. Clone will give you the rootfs (APP) partition. The “everything else” includes your bad device tree. A raw partition clone will allow you to loopback mount it, edit files (including any device tree), and reflash with that exact fixed clone (presumably with the correct device tree). This is for the eMMC partition though; there is a lot that changes if booting to external media. Clone does take a lot of time and large amount of disk space on the host PC.
Hi Kevin ，
I flash the Image.The system seems to have been restored, the previous Settings are gone, and the first Settings after re-burning need to be reset again
Yes, it is the expected result since it will re-partition/flash the board.
Please just follow the instruction to configure them.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.