Target SoM is Orin Nano, BSP is Jetson 36.4.3(JetPack 6.2)
Our custom carry board schematic for reference, part of M2 M KEY (Same Jetson OrinNX P3768 carrier board)
Tested PCIe 2-lane (H/W team re-work to disconnected 3rd/4th lane as green square @ schematic) and flash successful.
We heard the problematic NVMe controller MAXIO MAP1202-I of the SSD have compatibility issues.
If it is true, we need any either suggestion or possible solution before discard it.
*** Please note that this reply is generated by LLM automatically ***
Based on the provided context, I’ll provide a comprehensive answer to the question.
The issue is with flashing a Jetson Orin Nano module on a custom carrier board using a third-party NVMe SSD, specifically the TEAM GROUP N845M42 with a MAXIO MAP1202I controller. The flash process fails, and the log files are provided.
To address this issue, let’s break down the key points:
Hardware compatibility: The custom carrier board is based on the Jetson Orin NX P3768 carrier board schematic, which is a good starting point. However, the introduction of a third-party NVMe SSD might be causing compatibility issues.
NVMe SSD compatibility: The TEAM GROUP N845M42 with a MAXIO MAP1202I controller is not explicitly mentioned in the provided context as a supported or compatible NVMe SSD for the Jetson Orin Nano module. This might be the root cause of the issue.
Flash command and process: The flash command used is not explicitly mentioned, but it’s likely that the flash.sh script is being used. The log files provided might give more insight into the flash process and the error messages.
Previous successful flashing: The same Jetson Orin Nano module was successfully flashed with an Apacer PV250M280 NVMe SSD, which suggests that the issue is specific to the TEAM GROUP N845M42 NVMe SSD.
To resolve this issue, I recommend the following steps:
Verify NVMe SSD compatibility: Check the NVIDIA documentation and supported hardware list to confirm whether the TEAM GROUP N845M42 with a MAXIO MAP1202I controller is a supported or compatible NVMe SSD for the Jetson Orin Nano module.
Update the flash command and process: If the NVMe SSD is compatible, try updating the flash command and process to ensure that it’s correctly configured for the TEAM GROUP N845M42 NVMe SSD.
Check the log files: Analyze the provided log files (Flashlog and DebugUARTlog) to identify any specific error messages or issues that might be causing the flash process to fail.
Test with a different NVMe SSD: If the issue persists, try testing with a different NVMe SSD that is known to be compatible with the Jetson Orin Nano module to isolate the issue.
In comparison to other similar issues mentioned in the provided context, such as “Timeout when flashing Jetson Orin Nano 8G module” and “Flash Orin image to NVME”, the root cause of this issue seems to be related to the specific NVMe SSD used. Therefore, verifying the compatibility of the NVMe SSD and updating the flash command and process should be the primary focus.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
Our H/W leader have a idea and let me to asking in forum to explore the feasibility as follows
1.Is possible take PCIe either 1 or 2 lane(s) mode or lower clock speed during flashing time, and take PCIe either 4 lanes mode or full clock speed in normal running time?
Because based on above mentioned “Flash successful @ PCIe 2-lane H/W” case.
The NVMe SSD moved to normal (PCIe 4-lanes) carry board and working after boot in short-term observation.
2.Orin Nano set PCIe3.0*4 mode?
(Search result max-link-speed=<3>, but not idea it correct or not here)
