Dear all:
1: jetpack7.2 agx orin 64GB + custom board
2: flash cmd: sudo ./flash.sh jetson-agx-orin-devkit internal, can not flash
flash log: Error: failed to get storage info ;
3: cat /sys/block/mmcblk0/device/name: TY2964
Please tell me: Does agx orin 64GB can flash in Jetpack7.2 ?if can, how to flash it.
Thanks for reporting this issue. To help diagnose the flashing failure on your AGX Orin 64GB with a custom board, we need some additional information:
-
Exact error message or output: What does the flash command print? Does it show an error code, or does it hang/exit silently?
-
Command behavior: Does the command hang indefinitely, exit immediately with an error, or produce no output at all?
-
Log files: Check for logs in /tmp or the flash directory (typically Linux_for_Tegra/). Please share any relevant log files from the flashing process.
-
First-time flash or re-flash: Is this the first time flashing this board, or are you re-flashing an existing installation?
-
Custom board configuration: What is the specific configuration of your custom board? Please provide details about:
- Device tree customizations
- Bootloader configuration
- Any board-specific BSP modifications
Note: The flash.sh script searches for a board configuration file matching your board ID (e.g., jetson-agx-orin-devkit.conf). For custom boards, you may need a custom .conf file with the correct format. If you’re using a vendor-provided custom board, contact the vendor for their customized BSP.
Once you provide these details, we can better identify the root cause.
1: 刷机后是无期限 卡住, 不是首次刷机,这个模组当前已经有系统了JP6.2;
2: 自制底板 +jp6.2是正常的, odmdata的修改同步到 JP7.2上了。
3
Thank you for the additional details. To help diagnose the hanging issue after flashing JetPack 7.2 on your custom AGX Orin 64GB board, we need a few more pieces of information:
-
Complete flashing output and logs: Please share the full console output from the flash.sh command, including any error messages. Also check for log files in /tmp and Linux_for_Tegra/ directories and attach them.
-
Device tree and bootloader configuration: Can you provide details on the custom device tree modifications and bootloader configuration specific to your board? This includes any custom .conf file used with flash.sh.
-
Flashing completion status: Does the board hang during the flashing process or after flashing completes? Does the script report success before the hang?
-
Board-specific BSP modifications: Are there any vendor-provided custom board documentation or BSP modifications that were applied for JP6.2 that may need updating for JP7.2?
-
odmdata verification: You mentioned odmdata changes were synced to JP7.2. Can you confirm the exact odmdata values being used and whether they differ from the JP6.2 configuration?
Once we have these details, we can identify whether this is a device tree issue, bootloader configuration mismatch, or a custom board-specific compatibility problem with JP7.2.
cannot flash JP7.2 with TY2964 eMMC. Please wait for our update.
Okay,when will this update be released roughly?