Hi guys,
having problems with the SDK flashing the Jetson AGX. Running Ubuntu 20.04, SDK Manager 1.8.0.10363. Logs are attached.
I tried the obvious solutions, including:
- formated SD-Card to ext4 (128GB)
- re-installed SDK
- ran the SDK in automated and manual mode multiple times
- switched USB-C cable.
- switched Host Computer
Latest Log-Messages are
15:23:00 ERROR: Flash Jetson AGX Xavier - flash: while count is not 0:
15:23:00 INFO: Flash Jetson AGX Xavier - flash: Failed flashing t186ref.
15:23:00 ERROR: Flash Jetson AGX Xavier - flash: *** ERROR: flashing failed.
15:23:00 INFO: Flash Jetson AGX Xavier - flash: [ NV_L4T_FLASH_XAVIER_WITH_OS_IMAGE_COMP Install took 2m16s ]
15:23:00 ERROR: Flash Jetson AGX Xavier - flash: command terminated with error
15:23:00 SUMMARY: DateTime Target Setup - target: Depends on failed component
Any suggestions? Greetings Eric
logs.zip (85.1 KB)
Hi,
When flash problem comes, I always ask this first. Is this your first time flashing sdkmanager with this jetson AGX?
Hi.
Thanks for the quick response. That’s also a hard to answer question. The AGX was in the hands of some Master’s Student before, who probably used it, but I cannot tell for sure. Given that situation, I formated the SD-card to ext4.
I guess that means yes, I am flashing it for the first time.
SDcard does not really matter here. I am not sure why you mentioned it. This is not Xavier NX.
Xavier AGX is not using sdcard to boot.
Are you able to dump the serial console log when this flash error happened?
Hi
I had hoped it was contained in the attached .log-files in the original question. This is the latest full Console Log.
currentlog.log (7.3 KB)
No, this is not what I need. I won’t ask you dump a log which is already shared before. Please do read the page I shared and share the log.
Let me make it easier to understand. Flash requires two parts, the host and the device (AGX).
What you shared were the host side log. I need the device side log to see what is going on.
Hi
I hope this is correct
Welcome to minicom 2.7.1
OPTIONS: I18n
Compiled on Dec 23 2019, 02:06:26.
Port /dev/ttyUSB3, 16:08:16
Press CTRL-A Z for help on special keys
��
[1071.259] W> RATCHET: MB1 binary ratchet value 4 is larger than ratchet level 2 from HW fuses.
[1071.267] I> MB1 (prd-version: 2.2.0.0-t194-41334769-3540ffaa)
[1071.272] I> Boot-mode: Platform RCM
[1071.276] I> Platform: Silicon
[1071.278] I> Chip revision : A02P
[1071.281] I> Bootrom patch version : 15 (correctly patched)
[1071.287] I> ATE fuse revision : 0x200
[1071.290] I> Ram repair fuse : 0x0
[1071.293] I> Ram Code : 0x2
[1071.296] I> rst_source: 0xb, rst_level: 0x1
[1071.301] I> USB configuration success
[1073.518] I> mb2 image downloaded
[1073.555] I> Recovery boot mode 0
[1073.560] I> UPHY full init done
[1073.567] I> MB1 done
[1073.572] I> Welcome to MB2(TBoot-BPMP) Applet (version: default.t194-mobile-a1105112)
[1073.580] I> DMA Heap @ [0x40020000 - 0x40065800]
[1073.584] I> Default Heap @ [0xd486400 - 0xd48a400]
[1073.589] W> Profiler not initialized
[1073.613] I> sdmmc DDR50 mode
[1073.618] E> SPI_FLASH: Invalid value device id: 7.
[1073.622] I> QSPI Flash is not present.
[1073.629] E> CLK_RST: instance 6 not found in module 44.
[1073.634] E> MPhy CAR configuration failed error = 1747992077
[1073.639] E> UFS initialization failed
[1073.643] I> UFS is not present
[1073.650] I> Found 17 partitions in SDMMC_BOOT (instance 3)
[1073.659] I> Found 42 partitions in SDMMC_USER (instance 3)
[1073.665] W> Profiler not initialized
[1073.668] I> Entering 3p server
[1073.671] I> USB configuration success
[1074.901] I> Populate chip info
[1074.985] I> Populate eeprom info
[1074.989] I> Populate eeprom info for module cvm
[1074.994] > DEVICE_PROD: device prod is not initialized.
[1081.545] I> Populate chip info
[1081.585] I> Populate eeprom info
[1081.588] I> Populate eeprom info for module cvb
[1081.796] I> Rebooting : reboot-recovery
[1081.801] I> Reset to recovery mode
��
[0002.286] W> RATCHET: MB1 binary ratchet value 4 is larger than ratchet level 2 from HW fuses.
[0002.294] I> MB1 (prd-version: 2.2.0.0-t194-41334769-3540ffaa)
[0002.299] I> Boot-mode: Platform RCM
[0002.302] I> Platform: Silicon
[0002.305] I> Chip revision : A02P
[0002.308] I> Bootrom patch version : 15 (correctly patched)
[0002.313] I> ATE fuse revision : 0x200
[0002.317] I> Ram repair fuse : 0x0
[0002.320] I> Ram Code : 0x2
[0002.323] I> rst_source: 0xb, rst_level: 0x1
[0002.328] I> USB configuration success
[0004.492] I> mb2 image downloaded
[0004.533] I> Recovery boot mode 0
[0004.538] I> UPHY full init done
[0004.545] I> MB1 done
[0004.550] I> Welcome to MB2(TBoot-BPMP) Applet (version: default.t194-mobile-a1105112)
[0004.557] I> DMA Heap @ [0x40020000 - 0x40065800]
[0004.562] I> Default Heap @ [0xd486400 - 0xd48a400]
[0004.566] W> Profiler not initialized
[0004.591] I> sdmmc DDR50 mode
[0004.595] E> SPI_FLASH: Invalid value device id: 7.
[0004.599] I> QSPI Flash is not present.
[0004.606] E> CLK_RST: instance 6 not found in module 44.
[0004.611] E> MPhy CAR configuration failed error = 1747992077
[0004.616] E> UFS initialization failed
[0004.619] I> UFS is not present
[0004.627] I> Found 17 partitions in SDMMC_BOOT (instance 3)
[0004.636] I> Found 42 partitions in SDMMC_USER (instance 3)
[0004.641] W> Profiler not initialized
[0004.645] I> Entering 3p server
[0004.648] I> USB configuration success
[0005.779] I> Populate chip info
[0005.835] I> Populate eeprom info
[0005.839] I> Populate eeprom info for module cvm
[0005.844] > DEVICE_PROD: device prod is not initialized.
[0006.007] I> Rebooting : reboot-recovery
[0006.012] I> Reset to recovery mode
��
[0114.971] W> RATCHET: MB1 binary ratchet value 4 is larger than ratchet level 2 from HW fuses.
[0114.980] I> MB1 (prd-version: 2.2.0.0-t194-41334769-3540ffaa)
[0114.985] I> Boot-mode: RCM
[0114.988] I> Platform: Silicon
[0114.990] I> Chip revision : A02P
[0114.993] I> Bootrom patch version : 15 (correctly patched)
[0114.999] I> ATE fuse revision : 0x200
[0115.002] I> Ram repair fuse : 0x0
[0115.005] I> Ram Code : 0x2
[0115.008] I> rst_source: 0xb, rst_level: 0x1
[0115.013] I> USB configuration success
[0117.100] I> bct_bootrom image downloaded
[0117.109] W> PROD_CONFIG: device prod data is empty in MB1 BCT.
[0117.114] I> Temperature = 44500
[0117.117] W> Skipping boost for clk: BPMP_CPU_NIC
[0117.122] W> Skipping boost for clk: BPMP_APB
[0117.126] W> Skipping boost for clk: AXI_CBB
[0117.130] W> Skipping boost for clk: AON_CPU_NIC
[0117.134] W> Skipping boost for clk: CAN1
[0117.138] W> Skipping boost for clk: CAN2
[0117.142] I> Boot-device: SDMMC (instance: 3)
[0117.146] I> bct_mb1 image downloaded
[0117.156] I> Non-ECC region[0]: Start:0x80000000, End:0x100000000
[0117.164] W> Thermal config not found in BCT
[0117.172] W> MEMIO rail config not found in BCT
[0117.188] C> Task 0x42 failed (err: 0x8c8c011c)
[0117.192] E> Top caller module: MB1_MSS, error module: MB1_MSS, reason: 0x1c, aux_info: 0x01
[0117.200] C> Error: 0x8c8c011c
[0117.203] C> MB1(2.2.0.0-t194-41334769-3540ffaa) BIT boot status dump :
00111111111100000000000111101111110000001111111111111001110001111100000000000000000000000000000000000000000000000000000000000000101000000000010100000000000001010000000000101000000000000000000000000000000
[0117.233] I> Reset to recovery mode
Hi,
Are these logs coming out after you start to run sdkmanager on your host?
[0117.156] I> Non-ECC region[0]: Start:0x80000000, End:0x100000000
[0117.164] W> Thermal config not found in BCT
[0117.172] W> MEMIO rail config not found in BCT
[0117.188] C> Task 0x42 failed (err: 0x8c8c011c)
[0117.192] E> Top caller module: MB1_MSS, error module: MB1_MSS, reason: 0x1c, aux_info: 0x01
[0117.200] C> Error: 0x8c8c011c
[0117.203] C> MB1(2.2.0.0-t194-41334769-3540ffaa) BIT boot status dump :
00111111111100000000000111101111110000001111111111111001110001111100000000000000000000000000000000000000000000000000000000000000101000000000010100000000000001010000000000101000000000000000000000000000000
[0117.233] I> Reset to recovery mode
Hi
In Step 3 I
- turn off the AGX, connect to host using USB-C
- turn on the AGX in Recovery Mode (Press Middle Button, then Power On Button, then release both)
- start the SDK setup in “Manual” Mode
What you can see is the entire log on the device, from the moment I start running the SDK Step 3 (Setup) on the host to the point the SDK fails.
Minicom does not record any messages BEFORE I start the SDK Step 3 (Setup).
Sorry that do you have any ubuntu 18.04 x86 host that can test jetpack4?
1 Like
I can setup an Ubuntu18 host. Will have to get back to you tomorrow then, though. Currently I only dual-boot Ubuntu20 and 22.
VMs apparently make trouble forwarding USB when setting up the AGX. So I will have to generate another partition and install Ubuntu18.
If it helps (probably will not :D) I am trying to run the “Automatic” mode right now. It gets stuck at 36.36% without me being able to interact, including seeing the console. I can read the Device log using Minicom, but there are simply no messages, not in /dev/ttyUSB2 or 3. Minicom tells me /dev/ttyUSB1 is “locked”.
Just in case you don’t know, actually you don’t need to select sdk(cuda/tensorRT) in sdkm. Those software are not related to flash. (You can click the GUI to remove them from list)
The “flash” is only for the OS. But sdkmanager will not treat them separately. It means your “36.36%” may not definitely indicate the flash got stuck. Maybe it is just something wrong when preparing those cuda software and it is not related to jetson OS.
I mean that is maybe why UART didn’t give you any device side log when you got stuck.
1 Like
Hi,
I installed Ubuntu18.04 and tried flashing Jetpack 4.6.2. Flashing failed yet again, see .log-file. Will try again and
log the minicom-logs as well.
This is done doing Manual Mode.
Ubuntu18_Jetpack4.zip (209.6 KB)
I don’t see minicom log in the zip file you shared. What file name is it?
It’s not in there yet. As said, I will try again and this time log the minicom as well.
1 Like
Hi,
here we go. Both .log files. Again: Manual Mode, Jetpack 4.6.2. Both .log-files from Host and Device are attached.
Device (Minicom)
minicomLog.log (10.8 KB)
Host (Ubuntu18)
Ubuntu18_Jetpack4_6_2.zip (272.9 KB)
Hi,
The log of this line seems gone, could you share full line?
[0084.193] E> Top caller module: ALIASCHECKER, error module: ALIASCHECKER, reas6
BTW, is this board still able to boot up? Could you boot up (not flash) and share me the log from minicom?
Hi
[0084.175] E> FAILED: MEMIO rail config
[0084.189] E> Task 50 failed (err: 0x7979061c)
[0084.193] E> Top caller module: ALIASCHECKER, error module: ALIASCHECKER, reas6
[0084.202] I> MB1(1.5.1.9-t194-41334769-73a9b7ef) BIT boot status dump :
00000000000111111111100001111111111111100110001111100000000000000000000000000000
[0084.232] I> Reset to recovery mode
this IS the full message. I guess it’s supposed to be “Reason 6”? The board does not boot up. Attached you will find the minicom-log from when attempting to boot.
bootlog_minicom.log (3.1 KB)
Hi,
Are you sure this is boot up log? I mean this looks like a log trying to enter recovery mode.
