1: XAVIER NX + JP5.1.2_R35.4.1, after`sudo ./flash.sh p3509-0000+p3668-0001-qspi-emmc mmcblk0p1`command , device can not poweroff
The following file is log about can not poweroff.
minicom.cap (79.1 KB)
2: XAVIER NX + JP5.1.1_R35.3.1, after`sudo ./flash.sh p3509-0000+p3668-0001-qspi-emmc mmcblk0p1`command, device can poweroff.
So, what difference may cause this question between JP5.1.2 and JP5.1.1 ?
Thank you . Best regards.
Is a DevKit (P3509) or a custom board?
Does flashing with SDK Manager make any difference?
It is custom board.
We did not flash by sdkmanager. only flash by driver package(JP5.1.2) without any change.
Besides, I had flash by sdkmanager (JP5.1.2), this device can not poweroff too after flash.
do you have any kind of peripherals connected to the device?
Please remove them and try again to see if the error still persists.
The above file named minicom.cap is the debug file. which is log printed in debug serial.
I mean like Ethernet cables/USB drives/camera connectors, etc.
Leave only the power cable and the UART cable and try again.
Just power cable and the uart cable, execute command
sudo poweroff, the phenomenon is still the same.
Can you capture the log again?
can you check if the design of your carrier board aligns with that of P3509?
Or see if this issue also happens on the official DevKit.
This phenomenon look like caused by software.
And I had move the XAVIER NX som(JP5.1.2) to devkit board, poweroff work normal.
if it caused by hardware design ,could you help me show the point?
WARNING @ [platform/drivers/mailbox/tmo_link_provider/mail_tmo.c]: mail tmo TX timeout
After disable all pcie devices, XAVIER NX can poweroff.
Thank you very much. Best regards.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.