Error occured when we are flashing the T5000 module. Below are the log. Please help to figure out what is wrong for this situation.
烧录失败的日志.txt (34.7 KB)
Hi,
Please record the serial console log and provide the txt file for us to review.
Thanks
Hi David，
We have tried two methods to flash the QSPI flash of T5000 and NVME.
Below are the steps:
- Flash qspi only
Command: sudo SKIP_EEPROM_CHECK=1 ./l4t_initrd_flash.sh --no-flash --qspi-only jetson-agx-thor-devkit internal
Result: Success
Log in flashing PC:
qspi-only.txt (289.1 KB)
T5000 serial console: No output
- Flash qspi and NVME
Command: sudo SKIP_EEPROM_CHECK=1 ./l4t_initrd_flash.sh jetson-agx-thor-devkit internal
Result: Failed
Log in flashing PC:
新单板完整烧录过程的失败记录.txt (403.1 KB)
T5000 serial console: No output
Quoting nvidia documents “ EEPROM is an optional component for a customized carrier board. If the carrier board is designed without an EEPROM, the following modifications are needed on the MB2 BCT file, Linux_for_Tegra/bootloader/generic/BCT/tegra264-mb2-bct-common.dtsi:
- cvb_eeprom_read_size = <0x100>
+ cvb_eeprom_read_size = <0x0>
# In the board configuration file, add the following line:
+ SKIP_EEPROM_CHECK=1
“
And the error from the log “Getting ramcode failed” might be remedied by adding RAMCODE=0 as shown below.
“Typically, NVIDIA-provided board configurations rely on values retrieved from EEPROM and the chip to define these bash variables.”
sudo SKIP_EEPROM_CHECK=1 BOARDSKU=0008 FAB= BOARDREV= CHIP_SKU=00 RAMCODE=0 FUSELEVEL=fuselevel_production ./l4t_initrd_flash.sh --no-flash jetson-agx-thor-devkit internal
Hi Scott,
We are doing the flahsing work as your guide. There are still some isuess on our custom carrier board.
Flash module and SSD on custom board：
- Flash qspi only
Command: sudo SKIP_EEPROM_CHECK=1 BOARDSKU=0008 FAB= BOARDREV= CHIP_SKU=00 RAMCODE=0 FUSELEVEL=fuselevel_production ./l4t_initrd_flash.sh --no-flash jetson-agx-thor-devkit internal
Result: Success
Log in flashing PC:
no-flash-烧录.txt (381.1 KB)
T5000 serial console when flashing:
no-flash-串口.txt (42.3 KB)
- Flash qspi and NVME
Command: sudo SKIP_EEPROM_CHECK=1 BOARDSKU=0008 FAB= BOARDREV= CHIP_SKU=00 RAMCODE=0 FUSELEVEL=fuselevel_production ./l4t_initrd_flash.sh jetson-agx-thor-devkit internal
Result: Failed
Log in flashing PC:
T5000 serial console when flashing:
sudo SKIP_EEPROM_CHECK=1 串口日志.txt (55.3 KB)
Flash module and SSD on devkit：
- Flash qspi and NVME
Command: sudo SKIP_EEPROM_CHECK=1 BOARDSKU=0008 FAB= BOARDREV= CHIP_SKU=00 RAMCODE=0 FUSELEVEL=fuselevel_production ./l4t_initrd_flash.sh jetson-agx-thor-devkit internal
Result: Success
But when we put the T5000 module and SSD onto custom carrier board. The carrier_power_on signal from T5000 will be high for a while and then pulled low!
Did you follow all these steps for your custom board? Thor Adaptation and Bring Up
“Before you use the T5000 with a carrier board other than developer kit P4071, change the kernel device tree, the MB1 configuration, the MB2 configuration, the ODM data, and the flashing configuration to correspond to the new carrier board instead of the P4071. The next section provides more information about the changes.”
You will need to use your custom board.conf file created with above methods jetson-thor-adaptation-and-bring-up-flash-build-image
Hi Scott,
Can you help to check what is happened in below logs?
Flash module and SSD on devkit：
- Flash qspi and NVME
Command: sudo SKIP_EEPROM_CHECK=1 BOARDSKU=0008 FAB= BOARDREV= CHIP_SKU=00 RAMCODE=0 FUSELEVEL=fuselevel_production ./l4t_initrd_flash.sh jetson-agx-thor-devkit internal
Result: Success
But when we put the T5000 module and SSD onto custom carrier board. The carrier_power_on signal from T5000 will be high for a while and then pulled low!
devkit烧录后安装到自研载板上电串口打印信息.txt (6.4 KB)
