I bought some jetson tx2 board, and one of them can not into recovery mode. the UART output is:
[0003.114] [TegraBoot] (version 00.00.2014.50-mobile-6987b70e)
[0003.120] Processing in cold boot mode Bootloader 2
[0003.124] A02 Bootrom Patch rev = 255
[0003.128] Power-up reason: on button
[0003.131] No Battery Present
[0003.134] RamCode = 2
[0003.136] Platform has Ddr4 type ram
[0003.139] max77620 disabling SD1 Remote Sense
[0003.144] Setting Ddr voltage to 1125mv
[0003.148] Serial Number of Pmic Max77663: 0x1307a5
[0003.155] Entering ramdump check
[0003.158] Get RamDumpCarveOut = 0xff23f000
[0003.162] RamDumpCarveOut=0xff23f000, RamDumperFlag=0xffffffff
[0003.168] Last reboot was clean, booting normally!
[0003.173] Sdram initialization is successful
[0003.177] SecureOs Carveout Base=0xff800000 Size=0x00800000
[0003.182] GSC1 Carveout Base=0xff700000 Size=0x00100000
[0003.187] GSC2 Carveout Base=0xff600000 Size=0x00100000
[0003.193] GSC3 Carveout Base=0xff500000 Size=0x00100000
[0003.198] GSC4 Carveout Base=0xff400000 Size=0x00100000
[0003.203] GSC5 Carveout Base=0xff300000 Size=0x00100000
[0003.208] BpmpFw Carveout Base=0xff2c0000 Size=0x00040000
[0003.213] Lp0 Carveout Base=0xff2bf000 Size=0x00001000
[0003.229] RamDump Carveout Base=0xff23f000 Size=0x00080000
[0003.234] Platform-DebugCarveout: 0
[0003.237] Nck Carveout Base=0xff03f000 Size=0x00200000
[0003.242] Non secure mode, and RB not enabled.
[0003.296] Using GPT Primary to query partitions
[0003.301] Loading Tboot-CPU binary
[0003.395] Verifying TBC in OdmNonSecureSBK mode
[0003.405] Bootloader load address is 0xa0000000, entry address is 0xa0000258
[0003.412] Bootloader downloaded successfully.
[0003.416] Downloaded Tboot-CPU binary to 0xa0000258
[0003.421] MAX77620_GPIO1 Configured.
[0003.424] MAX77620_GPIO5 Configured.
[0003.428] CPU power rail is up
[0003.431] CPU clock enabled
[0003.435] Performing RAM repair
[0003.438] Updating A64 Warmreset Address to 0xa00002e9
[0003.443] Loading NvTbootBootloaderDTB
[0003.537] NvTbootBootloaderDTB is not valid
[0003.541] Error in NvTbootLoadBinary: 0x14 !
[0003.545] Bootloader DTB Load Address: 0x83000000
[0003.550] Loading NvTbootKernelDTB
[0003.644] NvTbootKernelDTB is not valid
[0003.648] Error in NvTbootLoadBinary: 0x14 !
[0003.652] Error is 14
It seems the boot loader is damaged. so I can not flash system by using recovery mode. Is there any way to fix it?
How did you dump this log? I mean under what kind of situation?
This looks like a boot log but not flash log. Recovery mode is to put device into a status that can get flashed.
And it has nothing to do with the software running on it. This process is totally a hardware triggered case.
I mean even the emmc is totally formatted, it should still be able to get flashed.
I got this log by connect the UART pin of the 40-pin exp header on the carrier board to my computer and use minicom software to read the output on Linux. right now, I can not force into recovery mode by pressing the switchs on the carrier board. I think to force into recovery mode, the bootloader must be running first, but from the log, it seems my bootloader is broken and it can not run. maybe i am wrong. I think I have to fix the boot software so I can get into recovery mode and then flash os, but I have no idea what to do
I guess you just didn’t use the correct to steps to let the board enter recovery mode.
As I said, even a empty emmc can let the board gets flashed, which means the sw running on the board does not matter.
but I have another four tx2, all of them can get into recovery mode with my steps, and every day i would flash os into the board several times, and they all succeed. Why only this board can not work? Or did my board have hardware damage ?
Can we do some cross check by switch the carrier board and module here?
For example, you have 4 normal TX2 and 1 NG TX2, how many carrier board do you have? Is it possible to take the NG TX2 to the carrier board of other normal TX2 and then try to flash?
Also, can you describe how you put device into recovery mode?
thanks, I have 4 third-party carrier board and 4 original nvidia carrier board and I have already tried to switch the carrier board, and it did not work.
my steps is, press the power switch then press the recovery switch and hold it, and wait for about 5s~7s, then press the reset switch and wait for 3s ~ 5s then release the recovery switch
Actually, you only need to hold rec button along with “either” power key or reset key.
There is no “hold them both” case.
The logic here is simple, if the board is not yet powered up, then you have to use power key since the reset key has no function under such situation.
Thus, the steps in such case are press/hold rec → press/hold power key → release power key → release rec.
And if the board is already in power on state, then what you should is using the reset key.
Thus, steps become: press/hold rec → press/hold reset key → release reset key → release rec.
Please try them, if the module still cannot get into recovery mode, then please file RMA request.
thank you very much, but the module still cannot get into recovery mode, but still thanks
Then please RMA that module.
Recovery mode is triggered by hardware. It is not possible to fix that from the software.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.