orin nx开发板无法开机，jp6.2.1
客户用一段时间之后，无法开机，寄过来之后，orin nx 8G无法刷机
刷机报错
串口log如下：
接上串口log之后UEFIlog，没有kernel部分log
备注：
相同开发套件底板，用其他orin nx刷完之后能正常开会
Please share the full flash log from host and uart. I need the full one but not just these screenshots.
Hi Wayne,
This is the full flash log from host, I didn’t get uart log. Can you help me analyze the reasons why flash failed? Thank you.
host_flash.log (306.4 KB)
Need your UART log to check what is going on.
Hi Wayne,
These are the UART logs and Host logs generated when the device is being flashed. However, they may not be complete. At the final stage, the Host log got stuck and stopped updating entirely, while the UART log kept looping repeatedly. Therefore, I manually terminated the process and saved the logs.I used BSP version 36.4.4, with the hardware being an Orin Nano DevKit carrier board and an Orin Nano 8G Module. The flashing command was referenced from the online documentation.
UART.log (11.1 MB)
host_flash.log (301.3 KB)
I have no idea why the result this time is actually different from that of the previous attempt. In the last flash, the process completed normally but returned a flash failure prompt, as shown in the attached log file above.
Hi @Holden-W
Could you help test other NVMe SSD too and see if all SSD has this issue?
OK, I will replace it with another NVMe SSD for testing tomorrow and upload the results afterwards. Thank you for your assistance in the analysis.
I saw the PCIe error spew from the log on PCIe C4, so changing NVMe might help clarify the issue first.
Hi Wayne，
These are the flash logs after I replaced the NVMe SSD. Again, the host-side log stopped updating entirely, while the UART log kept looping continuously.
host_netac.log (314.9 KB)
UART_netac.log (1.8 MB)
I then replaced this module with the one that came with the DevKit, and it successfully completed the flashing process and booted up normally. I have also uploaded the corresponding logs for this successful attempt.
UART_DK.log (199.4 KB)
host_DK.log (349.2 KB)
These two sets of logs were generated only by swapping different modules (with all other conditions unchanged). Therefore, I believe this specific module is defective. I plan to submit an RMA request for it. However, it would be much better if we could determine the exact root cause of the failure.
Please RMA this module.
Are you testing both modules on Devkit? I hope no custom board is in use here for this test.
Yes, all these tests were completed on the NV DevKit.
ok. please go ahead with RMA.