Struggling to Load Easy Installer on AM62/Mallow

I have an AM62 1GB WB IT V1.0A and a Mallow board V1.1A. I have been struggling to connect to it and have been trying to reinstall Torizon and start from scratch. I am very familiar with the process for the Colibri boards, but this has been a struggle for me to say the least.

I believe I am able to get into recovery mode as I see AM62x DFU on my device manager. I had used the Zadig tool to install the WinUSB driver. When I then try to run the recovery script (Verdin-AM62_ToradexEasyInstaller_6.6.0+build.6) I get the output that I have pasted below.

Downloading Toradex Easy Installer…
dfu-util 0.11

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Waiting for device, exit with ctrl-C
More than one DFU capable USB device found! Try `–list’ and specify the serial number or disconnect all but one device

recovery\dd: opening `SocId.bin’: No such file or directory
FC: cannot open SOCTYPE.BIN - No such file or folder

Could Not Find C:\Users\dleberfinger\Desktop\Toradex\Verdin-AM62_ToradexEasyInstaller_6.6.0+build.6\SocId.bin
dfu-util 0.11

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Warning: Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release
Waiting for device, exit with ctrl-C
Opening DFU capable USB device…
Device ID 0451:6165
Device DFU version 0110
Claiming USB DFU Interface…
Setting Alternate Interface #0
Determining device status…
DFU state(2) = dfuIDLE, status(0) = No error condition is present
DFU mode device DFU version 0110
Device returned transfer size 512
Copying data from PC to DFU device
Download [=========================] 100% 300570 bytes
Download done.
DFU state(6) = dfuMANIFEST-SYNC, status(0) = No error condition is present
DFU state(2) = dfuIDLE, status(0) = No error condition is present
Done!
Resetting USB to switch back to Run-Time mode
dfu-util 0.11

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Warning: Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release
Waiting for device, exit with ctrl-C
Failed to retrieve language identifiers
Failed to retrieve language identifiers

The failed to review language identifiers just continues to repeat seemingly forever.

Any help would be greatly appreciated.

Hi, I’m the Toradex AI Assistant. I’m in early beta, and I would appreciate your feedback.
The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:


Hello,

It seems you’re encountering a few issues while trying to load the Toradex Easy Installer on your AM62 1GB WB IT V1.0A module using a Mallow board V1.1A. Let’s address these step by step.

  1. Multiple DFU Devices Detected: The message “More than one DFU capable USB device found!” suggests that there are multiple devices in DFU mode connected to your PC. Ensure that only the target device (in this case, the AM62 module) is connected in DFU mode. Disconnect any other devices that may be in DFU mode to avoid confusion for the dfu-util.

  2. Missing SocId.bin and SOCTYPE.BIN Files: The errors related to missing SocId.bin and SOCTYPE.BIN files indicate that the script is unable to find necessary files in the expected directory. This could be due to an incomplete download or extraction of the Toradex Easy Installer package. Verify that the package is fully and correctly extracted. It might be helpful to re-download and extract the package to ensure all files are present.

  3. Invalid DFU Suffix Signature: The warning about an invalid DFU suffix signature, while not immediately critical (as it’s a warning that a future release of dfu-util will require a valid suffix), suggests that the firmware being loaded might not be correctly packaged or is missing some metadata. This is not necessarily the cause of the failure but is something to be aware of for future troubleshooting.

  4. Continuous “Failed to retrieve language identifiers” Messages: This issue typically indicates a problem with the USB communication post the firmware download phase. It could be related to the device not correctly resetting or not being properly recognized by the host after the download completes.

Given the issues you’re facing, here are some steps to troubleshoot:

  • Ensure Only One DFU Device is Connected: Before running the recovery script, ensure that no other DFU-capable devices are connected to your system.
  • Check the Integrity of the Downloaded Package: Re-download the Toradex Easy Installer package for the AM62 and ensure it’s fully extracted without any corruption.
  • Use a Different USB Port: Preferably, use a USB 2.0 port instead of a USB 3.0 port, as USB 3.0 can sometimes cause issues with DFU mode operations.
  • Check the USB Cable: Ensure the USB cable is in good condition and supports data

Please, also check if these links can help you solve your problem:

Troubleshoot | Toradex Developer Center.

I am working from my laptop and have all cables disconnected except the USB-A to USB-C cable that is being used to connect to the Mallow board.

I redownloaded the Toradex Easy Installer packager for the AM62 and still get the same missing SocId.bin and SOCTYPE.BIN file errors.

Greetings @dleberfinger,

I just tried this on my own Windows system and I didn’t see any of the issues you described.

have all cables disconnected except the USB-A to USB-C cable that is being used to connect to the Mallow board.

After you did this are the logs still complaining about More than one DFU capable USB device found!?

On the Mallow how did you put the device into recovery mode? Did you short the required pin or did you add a recovery switch?

Best Regards,
Jeremias

Jeremias,

I am shorting the two pins as shown in the recovery documentation for my setup. In looking through my device manager, I see a Camera DFU device, I’m guessing this is the web camera built into my laptop. I have uninstalled that driver and I still get the error that multiple DFU devices are detected. Is there a way to specify the DFU device instead of it throwing the error for multiple devices?

Can you provide any insight on the recovery\dd: opening `SocId.bin’: No such file or directory
FC: cannot open SOCTYPE.BIN - No such file or folder errors?

Edit::
I was able to get rid of the multiple DFU device warning. Even when disabling or uninstalling my Camera DFU device, it will reappear very quickly after so there is a very short window of time to run the installer. I am now stuck at the point where I need to install the ADB driver. I have tried to download it from Google and follow the instructions for updating the Unknown USB Device, however when selecting the .inf file from Google, it is not being recognized by Windows as a device driver. Are you aware of any issue with this on Windows 11?

Can you provide any insight on the recovery\dd: opening `SocId.bin’: No such file or directory
FC: cannot open SOCTYPE.BIN - No such file or folder errors?

I don’t seem to have these files either in the Easy Installer I downloaded just now. That at least tells me you’re not suppose to have these in the download.

it is not being recognized by Windows as a device driver. Are you aware of any issue with this on Windows 11?

When I did this a while ago on my Windows machine I don’t recall any such difficulties. Though my laptop is still on Windows 10. So if the issue you’re experiencing is Windows 11 specific I wouldn’t know for sure.

Best Regards,
Jeremias

Jeremias,

I was able to successfully disable my other DFU device and the first step of the recovery script is running successfully. At this point, I updated the device driver to Android ADB Interface per the readme instructions in the Easy Installer. Now I am getting further, but it seems like the script is failing to recognize the device when it attempts to install Tezi.

Briefly I get the message “Waiting for known USB Device” then a failure to open usb device as shown below.

Warning: Invalid DFU suffix signature
A valid DFU suffix will be required in a future dfu-util release
Waiting for device, exit with ctrl-C
Opening DFU capable USB device…
Device ID 1b67:4000
Device DFU version 0110
Claiming USB DFU Interface…
Setting Alternate Interface #1
Determining device status…
DFU state(2) = dfuIDLE, status(0) = No error condition is present
DFU mode device DFU version 0110
Device returned transfer size 4096
Copying data from PC to DFU device
Download [=========================] 100% 984531 bytes
Download done.
DFU state(7) = dfuMANIFEST, status(0) = No error condition is present
DFU state(2) = dfuIDLE, status(0) = No error condition is present
Done!
Resetting USB to switch back to Run-Time mode
uuu (Universal Update Utility) for nxp imx chips – libuuu_1.4.127-0-g08c58c9

Success 0 Failure 1

2:7 1/ 0 [Failure open usb device ]

ECHO is off.
Downloading Toradex Easy Installer failed…
Press any key to continue . . .

Following the readme instructions, it states to install the device as an Android ADB Interface, but I was only able to successfully install Tezi by utilizing the Android Bootloader Interface.

Thank you for the help through this.

Interesting, I wonder if the difficulties you were having were due to Windows 11 or something else. In any case I’m glad to see you were able to resolve things and share your solution. This could be helpful for others in your position.

Best Regards,
Jeremias