hi nvidia team
I encountered an error while using tools to scan the machine。
Ongoing processes: 1021
Ongoing processes: 1021
Ongoing processes: 1021
Ongoing processes: 1021
Ongoing processes: 1021
Ongoing processes: 1021
Ongoing processes: 1021
Ongoing processes: 1021
Ongoing processes: 1021
Ongoing processes: 1021
Ongoing processes: 1021
Ongoing processes: 1021
Ongoing processes: 1021
Ongoing processes:
Flash complete (WITH FAILURES)
writing item=3, 1:3:mmcblk0p2,20480,134217728,mmcblk0p2_bak.img,134217728,fixed--2,bbbd3be175c541f62bd2c81a3d1c78bef0327d2f
Writing mmcblk0p2 partition with mmcblk0p2_bak.img
Get size of partition through connection.
…Timeout
[ 299]: l4t_flash_from_kernel: Error flashing emmc
Error flashing non-qspi storage
Cleaning up…
The operation steps are as follows:
Brushing machine:1、sudo ./flash.sh jetson-agx-orin-lcfc mmcblk0p1
2、install cuda: sudo ./flash.sh jetson-agx-orin-lcfc mmcblk0p1
Backup Command:1、sudo ./tools/backup_restore/l4t_backup_restore.sh -b -c jetson-agx-orin-lcfc
2、sudo ./tools/kernel_flash/l4t_initrd_flash.sh --use-backup-image --no-flash --massflash 8 jetson-agx-orin-lcfc mmcblk0p1
Brush command:sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --massflash 8
jetson version:JetPack_5.1.1_Linux_JETSON_AGX_ORIN_TARGETS
Backup log:
back-cuda.log (107.5 KB)
Brush error log:
flash_3-6_0_20230808-112953.log (18.3 KB)
kayccc
August 8, 2023, 6:18am
3
Your topic was posted in the wrong category. I am moving this to the Jetson AGX Orin category for visibility.
Hi,
then can it be restored directly with the backup/restore tool instead of massflash with initrd flash?
Can you also try adding --network usb0
to the flashing command?
Sorry, I don’t understand what you mean?
Why add - network usb0? We use internal EMMC
It’s what we suggest in README_initrd_flash.txt
- Use --network <netargs> if you want the flash process to happen through Ethernet protocol
instead of USB protocol. Ethernet protocol is more reliable than USB protocol
for external devices like USB.
<netargs> can be "usb0" when flashing using ethernet protocol through the usb
flashing cable or "eth0:<target-ip>/<subnet>:<host-ip>" when flashing using
ethernet protocol through the RJ45 cable.
It doesn’t matter whether you are using eMMC or NVMe drives.
hi DaveYYY
We didn’t use Ethernet to flash the machine, we took over USB type-c
That is why you need to add --network usb0
…
hi WayneWWW
现在刷机后,无法正常开机,串口也没任何log产生!
使用如下命令备份刷机的:
备份:
sudo ./tools/backup_restore/l4t_backup_restore.sh -b -c jetson-agx-orin-lcfc
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --use-backup-image --no-flash --network usb0 --massflash 8 jetson-agx-orin-lcfc mmcblk0p1
刷机:
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --network usb0 --massflash 5 --showlogs
刷机log :
flash_3-6_0_20230809-165654.log (22.7 KB)
刷机过程的kernel log:
flash_kernel.log (66.0 KB)
你的不能開機是怎麼樣 serial console完全沒東西?
flashing log看起來蠻正常的
接上mircro USB之後開機,然後host跑sudo picocom -b 115200 /dev/ttyACM0
真的什麼都沒有?
没有的
mfi_jetson-agx-orin-lcfc$ sudo picocom -b 115200 /dev/ttyUSB0
picocom v2.2
port is : /dev/ttyUSB0
flowcontrol : none
baudrate is : 115200
parity is : none
databits are : 8
stopbits are : 1
escape is : C-a
local echo is : no
noinit is : no
noreset is : no
nolock is : no
send_cmd is : sz -vv
receive_cmd is : rz -vv -E
imap is :
omap is :
emap is : crcrlf,delbs,
Type [C-a] [C-h] to see available commands
Terminal ready
hi 此种需要我上传那些文件可以方便您这边分析问题?
你們的板子的serial console device確定是ttyUSB0 嗎?
插螢幕也不會亮?
再重燒一次試試看呢
hi DaveYYY
我有两个模组,
其中一个是通过如下命令刷机:sudo ./flash.sh jetson-agx-orin-lcfc mmcblk0p1
产生log,其中部分如下
[0000.062] I> MB1 (version: 0.32.0.0-t234-54845784-57325615)
[0000.067] I> t234-A01-0-Silicon (0x12347) Prod
[0000.071] I> Boot-mode : Coldboot
[0000.074] I> Emulation:
[0000.077] I> Entry timestamp: 0x00000000
[0000.081] I> last_boot_error: 0x0
[0000.084] I> BR-BCT: preprod_dev_sign: 0
[0000.087] I> rst_source: 0x0, rst_level: 0x0
[0000.092] I> Task: Bootchain select WAR set (0x5000ba65)
[0000.097] I> Task: Enable SLCG (0x5000bab1)
[0000.101] I> Task: CRC check (0x5001ea19)
[0000.105] I> Skip FUSE records CRC check as records_integrity fuse is not burned
[0000.112] I> Task: Initialize MB2 params (0x5000cb51)
[0000.117] I> MB2-params @ 0x40060000
[0000.121] I> Task: Crypto init (0x5001d981)
[0000.125] I> Task: Secure debug controls (0x5000c0a9)
[0000.130] I> Task: strap war set (0x5000ba2d)
[0000.134] I> Task: Initialize SOC Therm (0x5001bd35)
[0000.139] I> Task: Program NV master stream id (0x5000c05d)
[0000.144] I> Task: Verify boot mode (0xd4820f1)
[0000.150] I> Task: Alias fuses (0x5001095d)
[0000.155] W> FUSE_ALIAS: Fuse alias on production fused part is not supported.
[0000.162] I> Task: Print SKU type (0x5000f5f1)
底板不动情况下(串口线未经过插拔):替换另一块经过如上备份再刷机的,就没log
你可以用那兩組不同的command在這兩塊板子上交叉試試看嗎?
開機沒有log我實在不知道怎麼幫你
模组本身是没问题的啊,换别的模组现象也是一样的,这个没有其他办法了吗?
刷机的方法,tools里的脚本,还有我上传的两个conf文件,bootload能否帮忙check下? 另外,其他厂家有遇到过类似问题吗?
就是用原本的flash.sh和Massflash都試一遍
sudo ./flash.sh jetson-agx-orin-lcfc mmcblk0p1
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --network usb0 --massflash 5 --showlogs
config file是vendor給的話我們也沒辦法驗證正確性,但是正常來說flash可以正常結束config file(包含device tree)應該就沒問題
我也說了,連log都印不出來實在很難幫你…