Originally used normally… Unknown reason suddenly unable to update
./flash.sh jetson-agx-orin-devkit mmcblk0p1
…
[ 0.2121 ] Boot Rom communication
[ 0.2126 ] tegrarcm_v2 --new_session --chip 0x23 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader.bin.encrypt --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
[ 0.2131 ] BR_CID: 0x80012344705DD1895C00000016018080
[ 0.2139 ] Sending bct_br
[ 0.2140 ] ERROR: might be timeout in USB write.
[ 5.4103 ]
Error: Return value 3
Command tegrarcm_v2 --new_session --chip 0x23 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader.bin.encrypt --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
Reading board information failed.
20220715_flash_orin_err.log (8.4 KB)
run sdkmanager error …
Are you sure this flash issue is happening “suddenly” but not due to you change to new module?
The flash log seems incdicating you are flashing 32GB Orin module…
Originally can use “./flash.sh jetson-agx-orin-devkit mmcblk0p1” command to burn successfully
But yesterday it suddenly failed to burn…
Changing to use the sdkmanager to burn also fails
Please always share log as text file… honestly, those picture you shared didn’t help.
Please also dump the UART log when flash error happened.
Also, please let sdkmanager download the BSP folder again in case the old BSP has some corruption.
-
No UART messages using sdkmanager when flash error happened.
2.
Download the BSP folder again and still the error
Do you have other Orin devices that can validate your host can really see UART log during flash?
Then could you see any uart log from that Orin device if you boot it instead of flash it?
The machine can be started normally but cannot be updated
20220715_orin_boot.log (108.8 KB)
Could you use sudo reboot forced-recovery in your uart console to put the board into recovery mode, monitor the log and start the flash process again.
If there is still no uart log coming out, please also try to change host and usb cable.
So there is no log coming out after these even you run flash.sh on your host?
./flash.sh jetson-agx-orin-devkit mmcblk0p1
UART still no message
Then please change to another host and usb cable.
Can it be verified that this is not a VM?
This is not executed on the VM
If even changing usb cable and host cannot resolve it, then please RMA this device.
I change to another host and usb cable.
Re-download the SDK to compile and burn
Can be burned successfully
but
I copied the file that failed to be burned in the original HOST
Burning in the new HOST will also fail
I compare the flash log and find the difference
/home/iei/NV/tegra186/Linux_for_Tegra/bootloader/tegraflash_internal.py:2598: SyntaxWarning: “is not” with a literal. Did you mean “!=”?
while count is not 0 and not check_ismb2():
/home/iei/NV/tegra186/Linux_for_Tegra/bootloader/tegraflash_internal.py:2598: SyntaxWarning: “is not” with a literal. Did you mean “!=”?
while count is not 0 and not check_ismb2():
/home/iei/NV/tegra186/Linux_for_Tegra/bootloader/tegraflash_internal.py:2607: SyntaxWarning: “is not” with a literal. Did you mean “!=”?
while count is not 0:
/home/iei/NV/tegra186/Linux_for_Tegra/bootloader/tegraflash_internal.py:2607: SyntaxWarning: “is not” with a literal. Did you mean “!=”?
while count is not 0:
/home/iei/NV/tegra186/Linux_for_Tegra/bootloader/tegraflash_impl_t234.py:858: SyntaxWarning: “is not” with a literal. Did you mean “!=”?
while count is not 0 and not self.check_is_mb2applet():
/home/iei/NV/tegra186/Linux_for_Tegra/bootloader/tegraflash_impl_t234.py:858: SyntaxWarning: “is not” with a literal. Did you mean “!=”?
while count is not 0 and not self.check_is_mb2applet():
/home/iei/NV/tegra186/Linux_for_Tegra/bootloader/tegraflash_impl_t234.py:865: SyntaxWarning: “is not” with a literal. Did you mean “!=”?
while count is not 0:
/home/iei/NV/tegra186/Linux_for_Tegra/bootloader/tegraflash_impl_t234.py:865: SyntaxWarning: “is not” with a literal. Did you mean “!=”?
while count is not 0:
…
ERROR: might be timeout in USB write.
Error: Return value 3
Command tegrarcm_v2 --new_session --chip 0x23 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader.bin.encrypt --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
Reading board information failed.
The performance of my original host is much higher than the other one… so I want to know why the original host failed to burn
