hi DaveYYY 感谢回复，但是kernel之前的log应该是贵司的bootloader或者cpu自带的引导程序产生的吧？ 这块我们没有代码也无法修改，为什么不能产生log呢
對啊，正常來說只要不是recovery mode，插電開機就應該要有log，所以我也只能建議你們多交叉測試幾次
應該不會是板子接電但是沒有自動開機，你們忘記按電源鍵吧
我是断电后重新上电的，已经试过好几次了，现象一样
請問這條有沒有必要一定要–massflash 8才能複製？
我的意思是比方說–massflash 2能否複製問題？ 還有devkit能不能複製？
Is this still an issue to support? Any result can be shared? Thanks
dear
休假刚回来，今天继续看该问题
安装完cuda后，再刷机就无法刷进去了
串口 log:
[0000.062] I> MB1 (version: 0.32.0.0-t234-54845784-57325615)
[0000.067] I> t234-A01-0-Silicon (0x12347) Prod
[0000.072] I> Boot-mode : Coldboot
[0000.075] I> Emulation:
[0000.077] I> Entry timestamp: 0x00000000
[0000.081] I> last_boot_error: 0x49490003
[0000.085] I> BR-BCT: preprod_dev_sign: 0
[0000.088] I> rst_source: 0x3, rst_level: 0x1
[0000.092] I> Task: Bootchain select WAR set (0x5000ba65)
[0000.098] I> Task: Enable SLCG (0x5000bab1)
[0000.102] I> Task: CRC check (0x5001ea19)
[0000.105] I> Skip FUSE records CRC check as records_integrity fuse is not burned
[0000.113] I> Task: Initialize MB2 params (0x5000cb51)
[0000.118] I> MB2-params @ 0x40060000
[0000.121] I> Task: Crypto init (0x5001d981)
[0000.126] I> Task: Secure debug controls (0x5000c0a9)
[0000.131] I> Task: strap war set (0x5000ba2d)
[0000.135] I> Task: Initialize SOC Therm (0x5001bd35)
[0000.140] I> Task: Program NV master stream id (0x5000c05d)
[0000.145] I> Task: Verify boot mode (0xd4820f1)
[0000.151] 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)
[0000.167] I> FUSE_OPT_CCPLEX_CLUSTER_DISABLE = 0x000001c0
[0000.172] I> FUSE_OPT_GPC_DISABLE = 0x00000000
[0000.176] I> FUSE_OPT_TPC_DISABLE = 0x00000002
[0000.180] I> FUSE_OPT_DLA_DISABLE = 0x00000000
[0000.185] I> FUSE_OPT_PVA_DISABLE = 0x00000000
[0000.189] I> FUSE_OPT_NVENC_DISABLE = 0x00000000
[0000.193] I> FUSE_OPT_NVDEC_DISABLE = 0x00000000
[0000.198] I> FUSE_OPT_FSI_DISABLE = 0x00000000
[0000.202] I> FUSE_OPT_EMC_DISABLE = 0x00000000
[0000.206] I> FUSE_BOOTROM_PATCH_VERSION = 0x7
[0000.211] I> FUSE_PSCROM_PATCH_VERSION = 0x7
[0000.215] I> FUSE_OPT_ADC_CAL_FUSE_REV = 0x2
[0000.219] I> FUSE_SKU_INFO_0 = 0xd2
[0000.222] I> FUSE_OPT_SAMPLE_TYPE_0 = 0x3 PS
[0000.226] I> FUSE_PACKAGE_INFO_0 = 0x2
[0000.230] I> SKU: Prod
[0000.232] I> Task: Boost clocks (0x500148a1)
[0000.236] I> Initializing PLLC2 for AXI_CBB.
[0000.240] I> AXI_CBB : src = 35, divisor = 0
[0000.244] I> Task: Voltage monitor (0x50014b49)
[0000.249] I> VMON: Vmon re-calibration and fine tuning done
[0000.254] I> Task: UPHY init (0x5000d065)
[0000.260] I> HSIO UPHY init done
[0000.263] E> Skipping GBE UPHY config
[0000.267] I> Task: Boot device init (0x50000be9)
[0000.271] I> Boot_device: QSPI_FLASH instance: 0
[0000.276] I> Qspi clock source : pllc_out0
[0000.280] I> QSPI Flash: Macronix 64MB
[0000.284] I> QSPI-0l initialized successfully
[0000.288] I> Task: TSC init (0x50020a4d)
[0000.292] I> Task: Load membct (0x50011fe9)
[0000.296] I> RAM_CODE 0x40000c1
[0000.299] I> Loading MEMBCT
[0000.302] I> Slot: 1
[0000.304] I> Binary[3] block-0 (partition size: 0x40000)
[0000.309] I> get_binary_info: Binary name: MEM-BCT-3
[0000.314] I> Size of crypto header is 8192
[0000.318] I> BCH load address is : 0x40050000
[0000.322] I> Size of crypto header is 8192
[0000.326] I> BCH of MEM-BCT-3 read from storage
[0000.330] I> BCH address is : 0x40050000
[0000.334] I> MEM-BCT-3 header integrity check is success
[0000.339] I> Binary magic in BCH component 3 is MEM3
[0000.344] I> component binary type is 3
[0000.349] I> MEM-BCT-3 binary is read from storage
[0000.353] I> MEM-BCT-3 binary integrity check is success
[0000.359] I> Binary MEM-BCT-3 loaded successfully at 0x40040000 (0xe580)
[0000.365] I> RAM_CODE 0x40000c1
[0000.370] I> RAM_CODE 0x40000c1
[0000.374] I> Task: Load Page retirement list (0x500115b1)
[0000.379] I> Task: SDRAM params override (0x50011fc5)
[0000.384] I> Task: Save mem-bct info (0x50014fa1)
[0000.389] I> Task: Carveout allocate (0x50015005)
[0000.394] I> RCM blob carveout will not be allocated
[0000.398] I> ECC region[0]: Start:0x0, End:0x0
[0000.403] I> ECC region[1]: Start:0x0, End:0x0
[0000.407] I> ECC region[2]: Start:0x0, End:0x0
[0000.411] I> ECC region[3]: Start:0x0, End:0x0
[0000.415] I> ECC region[4]: Start:0x0, End:0x0
[0000.420] I> Non-ECC region[0]: Start:0x80000000, End:0x80000000
[0000.426] I> Non-ECC region[1]: Start:0x0, End:0x0
[0000.430] I> Non-ECC region[2]: Start:0x0, End:0x0
[0000.435] I> Non-ECC region[3]: Start:0x0, End:0x0
[0000.439] I> Non-ECC region[4]: Start:0x0, End:0x0
[0000.450] E> BL_CARVEOUT: Failed to allocate memory of size 0x36800000 for CO:44.
[0000.457] C> Task 0x0 failed (err: 0x49490003)
[0000.461] E> Top caller module: BL_CARVEOUT, error module: BL_CARVEOUT, reason: 0x03, aux_info: 0x00
[0000.470] C> Boot Info Table status dump :
1
[0000.474] I> Busy Spin
刷机log:
flash_3-12_0_20230818-143026.log (5.2 KB)
請問你們有確認過這個嗎？
是只有特定module會這樣，還是每一台都會
只有massflash會出錯，flash.sh不會？
我试了两块模组都是这样
用sudo ./flash.sh jetson-agx-orin-lcfc mmcblk0p1命令刷机也是报一样错误
所以你們是先用flash.sh刷完device A，備份之後再用massflash刷進剩下的B, C, D, E…？
如果flash.sh都不能燒的話就不是massflash的問題了
你可以拿那兩片有問題的module搭配DevKit試試看嗎？
刷不进去的模组装到 devkit上使用sudo ./flash.sh jetson-agx-orin-lcfc mmcblk0p1命令是可以刷进去的，能帮忙看看log是哪个地方报错了的地方都有 ] ERROR: might be timeout in USB write.
这个是因为USB配置导致的吗？
只有這兩塊module會這樣嗎
hi
这个问题找到了，是因为我这段时间没来上班，硬件被其他同事搞坏了。后续继续测试之前的问题
1 Like
hi DaveYYY
刷机失败kernel log如下：
4276.188607] nfs: server fc00:1:1:0::1 not responding, timed out
[ 4286.428787] nfs: server fc00:1:1:0::1 not responding, timed out
[ 4296.156569] nfs: server fc00:1:1:0::1 not responding, timed out
[ 4306.652572] nfs: server fc00:1:1:0::1 not responding, timed out
[ 4316.700785] nfs: server fc00:1:1:0::1 not responding, timed out
[ 4326.684855] nfs: server fc00:1:1:0::1 not responding, timed out
[ 4341.468646] nfs: server fc00:1:1:0::1 not responding, timed out
[ 4410.332793] nfs: server fc00:1:1:0::1 not responding, timed out
bash-5.0#
bash-5.0#
bash-5.0#
bash-5.0#
bash-5.0#
bash-5.0#
bash-5.0#
bash-5.0#
bash-5.0# ls
bin etc initrd_flash.cfg mnt root sbin tmp var
dev init lib proc run sys usr
bash-5.0# [ 4415.452657] nfs: server fc00:1:1:0::1 not responding, timed out
bash-5.0#
bash-5.0#
bash-5.0#
bash-5.0#
bash-5.0# [ 4420.572800] nfs: server fc00:1:1:0::1 not responding, timed out
[ 4425.692798] nfs: server fc00:1:1:0::1 not responding, timed out
[ 4430.812793] nfs: server fc00:1:1:0::1 not responding, timed ou
但是lsusb是有USB的
neil@neil:~/B600/ROM/mfi_jetson-agx-orin-lcfc$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 028: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Bus 003 Device 004: ID 13d3:56fb IMC Networks
Bus 003 Device 003: ID 06cb:00bd Synaptics, Inc.
Bus 003 Device 006: ID 8087:0032 Intel Corp.
Bus 003 Device 068: ID 15d9:0a4e Trust International B.V.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 014: ID 0955:7035 NVidia Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
neil@neil:~/B600/ROM/mfi_jetson-agx-orin-lcfc$
你們可以確認一下嗎
現在這一段log是用什麼command刷的，是不是每一台module都會這樣
還有用DevKit能不能複製？
刷机命令如下：
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --network usb0 --massflash 2 --showlogs
现象是随机发生的
可以把完整的serial console log貼上來嗎？
hi DaveYYY
我换了跟USB线又可以正常刷机了。
目前来看，可能有以下几点影响了刷机：
1、我们之前用的是jetson5.0.2，现在升级到jetson5.1.1,直接使用backup的包刷机会概率性导致无法启动，
串口也不会有任何log输出，解决办法：刷过5.0.2的模组，先试用sudo ./flash.sh xxx mmcblk0p1刷机后即可。
我没看过bootloader的代码，应该是bootloader差异造成的改问题；
2、backup时候需要 添加–no-flash --network usb0，否则也会造成一些异常，例如，插网线不能正常开机等；
3、系统在安装cuda后，会造成backup后的包很大，需要将maxcount=${timeout:-20} 的参数时间加长，否则也会造成timeout。
4、我们自己的板子USB信号有可能眼图不太标准，有时候会出现USB连接的异常，重新刷机，或者换线也能解决，但这块我就不太确定了
此问题我就关闭了，感谢您的支持！
1 Like
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.