'Failure to open USB device' Error When Flashing IMX8 with UUU on Windows 10

[Exbo7]

Good morning,

I have been experiencing some problems when flashing IMX8 recently. I will provide as much information as possible about the system and the issue I have encountered.

Information of the system

• The microcontroller I am trying to flash is an IMX8.
• I am using Windows 10 64-bit as the operating system.
• Version of UUU used v1.5.201.

Analyzing the flash logs, we observed that during the flash_init sequence, UUU produced error 2:2->Fail: 'Failure to open USB device' (1.497e+16 s). However, as can be seen in the log, UUU continued to execute the script. Despite executing the entire script correctly, however, the UUU program returned an error message saying 'USB device not open' and marked the script execution as 'NOK'. (Flash log attached with the name Flash_init.txt)

I am also attaching the script that is run to flash. (Script used attached with the name kostal-mat12003035-02-init.txt)

Does anyone know what might be happening? Could it be a Windows configuration problem? Or could it be that UUU is reporting a 'NOK' when the script has finished running correctly? Alternatively, could it be a configuration issue with the script used?

I would be grateful for any support from those who have experienced a similar problem or know how to mitigate this error.

Thank you in advance.

[Exbo7]

Hello,

Thank you for your reply.

The error reported as Fail: ‘Failure to open USB device’ (1.497e+16 s) occurs after executing the command SDPS: boot -f imx-loader. As shown in the log I attached, the tool first detects the board, then executes the SDPS command successfully. After booting, the board restarts (as expected from the command), and that’s when the tool fails to detect the USB device. The error is logged, but shortly afterwards the board is recognized again, and the sequence continues normally.

The issue is that UUU marks the overall execution as NOK, even though the entire flashing sequence completes successfully.

In my script, I already have a SDPV: delay 1000 command right after the SDPS boot. Would increasing this delay to, say, 5000 milliseconds allow enough time for the USB device to be recognized again after the reboot? Do you think that could solve the issue?

Regarding your question: yes, I can confirm that the board is in Serial Download Mode.

Also worth mentioning — this error does not occur on all boards, but only occasionally.

Best regards,

[JorgeCas]

Hello,

Got it, thank you for the clarification.

In that case if this issues occurs occasionally, increasing the delay could help to improve this behavior in flashing process.

Best regards. 

[Exbo7]

Hello,

I'm going to try increasing the SDPV delay to 5000 to see if that eliminates these errors.
Thank you very much for your support. I'll let it run for a couple of days and see what happens.

I'll keep you posted.

[JorgeCas]

Hello,

The error code you are getting is because the tool is not able to connect with the board.

Please confirm that your board is in serial download mode.

Also, you could use the a command to flash the file directly instead the script.

Best regards.