jetson tx2 nx developer kit board suddenly doesn’t run after reboot.
In addition, the following errors occur, and the screen turns off periodically.
Hi,
have you tried to re-flash it using SDK Manager or scripts provided in our BSP?
If it still does not boot up properly, please put the UART log here.
I tried to connect using SDK manager but it didn’t boot.
[ 1.048541] tegradc 15210000.nvdisplay: dp: aux write got error (0x10000100)
[ 1.055617] tegradc 15210000.nvdisplay: dp: Failed for I2C write addr:80, size:1, stat:0x10000100
[ 1.072903] tegradc 15210000.nvdisplay: dp: aux write got error (0x10000100)
[ 1.079966] tegradc 15210000.nvdisplay: dp: Failed to write DPCD data. CMD 0x600, Status 0x10000100
[ 1.093994] tegradc 15210000.nvdisplay: dp: aux write got error (0x10000100)
[ 1.101049] tegradc 15210000.nvdisplay: dp: Failed to write DPCD data. CMD 0x600, Status 0x10000100
[ 1.115152] tegrade 15210000.nvdisplay: dp: aux write got error (0x10000100)
[ 1.122208] tegradc 15210000.nvdisplay: dp: Failed to write DPCD data. CMD Ox600, Status 0x10000100
[ 1.136353] tegradc 15210000.nvdisplay: dp: aux write got error (0x10000100)
[ 1.143432] tegradc 15210000.nvdisplay: dp: Failed to write DPCD data. CMD 0x600, Status 0x10000100
[ 1.152510] tegradc 15210000.nvdisplay: dp: failed to exit panel power save mode (Oxfffffff2)
[ 1.277396] tegradc 15210000.nvdisplay: dp: aux write got error (0x10000100)
[ 1.277400] tegradc 15210000.nvdisplay: dp: Failed to write DPCD data. CMD 0x600, Status 0x10000100
[ 1.282439] tegradc 15210000.nvdisplay: dp: aux write got error (0x10000100)
[ 1.282442] tegradc 15210000.nvdisplay: dp: Failed to write DPCD data. CMD 0x600, Status 0x10000100
[ 1.287482] tegradc 15210000.nvdisplay: dp: aux write got error (0x10000100)
[ 1.287485] tegradc 15210000.nvdisplay: dp: Failed to write DPCD data. CMD 0x600, Status 0x10000100
[ 1.292517] tegradc 15210000.nvdisplay: dp: aux write got error (0x10000100)
[ 1.292520] tegradc 15210000.nvdisplay: dp: Failed to write DPCD data. CMD 0x600, Status 0x10000100
[ 1.292523] tegrade 15210000.nvdisplay: dp: failed to exit panel power save mode (Oxfffffff2)
[ 1.292526] hpd: edid read prepare failed
[ 1.372740] imx219 9-0010: imx219_board_setup: error during 12c read probe (-121)
[ 1.372804] imx219 9-0010: board setup failed
[ 1.396379] imx219 10-0010: imx219_board_setup: error during 12c read probe (-121)
[ 1.396428] imx219 10-0010: board setup failed
cp: not writing through dangling symlink ‘etc/resolv.conf’
[ 1.883691] cgroup: cgroup2: unknoun option “nsdelegate”
[ 3.103117] using random self ethernet address
[ 3.146374] using random host ethernet address
[ 3.589762] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8265-26.ucode failed with error -2
[ 3.600615] iwlwifi 0000:02:00.0: Falling back to user helper
[ 3.669464] using random self ethernet address
[ 3.674109] using random host ethernet address
[ 4.040259] CPU1: shutdown
[ 4.091010] CPU2: shutdoun
[ 4.935133] Bridge firewalling registered
[ 6.953228] iwlwifi 0000:02:00.0: Direct firmuare load for iwlwifi-8265-25.ucode failed with error -2
[ 6.964057] iwlwifi 0000:02:00.0: Falling back to user helper
[ 7.103923] uvcvideo 2-2.4:1.0: Entity type for entity Intel(R) RealSense™ Depth Ca was not initialized!
[ 7.116349] uvcvideo 2-2.4:1.0: Entity type far entity Processing 2 was not initialized!
[ 7.142813] uvcvideo 2-2.4:1.0: Entity type for entity Camera 1 was not initialized!
[ 7.760516] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-8265-24.ucode failed with error -2
[ 7.770828] iwlwif1 0000:02:00.0: Falling back to user helper
[ 7.901293] iwlwifi 0000:02:00.0: Direct firmuare load for iwlwifi-8265-23.ucode failed with error -2
[ 7.911097] iwlwifi 0000:02:00.0: Falling back to user helper
What do you mean with:
I tried to connect using SDK manager but it didn’t boot.
You flash it again but the result is still the same?
Is it the full log shown in UART console?
Also want to know what JetPack/L4T version is in use.
Mostly this is just an extension of what @WayneWWW just mentioned, but I want to also mention that the EDID error is from the monitor’s automatic configuration wire. It is quite possible that serial console still works (but if you’ve tried to flash that doesn’t much matter until flash succeeds). Regardless, it is quite useful if you can create a serial console boot log since serial console has no dependence on the drivers a monitor would use, and it allows you to log the whole boot process (even before Linux ever starts). I strongly suggest a serial console boot log…perhaps the flash did succeed? Plus, if you flashed with JetPack/SDK Manager, and there is some indication of failure, then SDKM has an “export logs” button and you could attach those logs to the forum.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.