Failed to use Easy Installer

Hi Toradex,

I can’t stop the U-boot from booting by pressing any key on the keyboard,then I tried the hardware JP4 shorting, running ‘recovery-windows.bat’ there is an error ‘Cannot open the device. ID=XXX…’

Is there any other way for me to revert this module to factory configuration?

Thanks.

Hi @kane ,
JP4 's Pin1 and Pin2 need to be shortened first, and then turn on the power. Meanwhile, JP2 should be open.

I can’t stop the U-boot from booting by pressing any key on the keyboard,

you may try to enable or disable the HW/SW flow control feature in your console client.

@benjamin.tx
I forgot to share some other information, the imge inside the module is customized, including the u-boot.

What I actually want to do is to restore the module to its original u-boot and imge as if it were a newly purchased module, is there any way to do that?

Because of the customized imge and u-boot, Easy Installer can’t use them anymore.

Hi @kane ,

Loading Toradex Easy Installer doesn’t have to reuse the U-boot or image installed on Apalis iMX6 SoM. Just follow the guide here. We suggest the latest version which is Toradex Easy Installer V5.7.3. Make sure JP2 on Ixora is removed. With Toradex Easy Installer loaded, you can install Toradex reference image or your own customized one.

Hi @benjamin.tx ,

Yes, I did that, but the Easy Installer (version: Apalis-iMX6_ToradexEasyInstaller_5.7.3+build.17) keeps reporting an error.
I can confirm that JP2 has been removed, JP4 has been shorted correctly and I have tried to replace the module, carrier board and cables.
I have not used the USB hub or VM.
But I still get this error (as follows)

Downloading Toradex Easy Installer...
config file <recovery\\\imx_usb.conf>
vid=0x15a2 pid=0x0054 file_name=mx6_usb_rom.conf
-> vid=0x1b67 pid=0x4fff file_name=mx6_usb_sdp_spl.conf
-> vid=0x1b67 pid=0x4000 file_name=mx6_usb_sdp_uboot.conf
vid=0x15a2 pid=0x0061 file_name=mx6_usb_rom.conf
-> vid=0x1b67 pid=0x4fff file_name=mx6_usb_sdp_spl.conf
-> vid=0x1b67 pid=0x4000 file_name=mx6_usb_sdp_uboot.conf
vid=0x15a2 pid=0x0076 file_name=mx7_usb_rom.conf
-> vid=0x1b67 pid=0x4000 file_name=mx7_usb_sdp_uboot.conf
vid=0x15a2 pid=0x0080 file_name=mx6ull_usb_rom.conf
-> vid=0x1b67 pid=0x4000 file_name=mx6ull_usb_sdp_uboot.conf
config file <recovery\\\mx6_usb_rom.conf>
parse recovery\\\mx6_usb_rom.conf
Trying to open device vid=0x15a2 pid=0x0054
Interface 0 claimed
HAB security state: production mode (0x12343412)
== work item
filename SPL
load_size 0 bytes
load_addr 0x13f00000
dcd 0
clear_dcd 0
plug 0
jump_mode 2
jump_addr 0x00000000
== end work item

loading binary file(SPL) to 00907400, skip=0, fsize=bc00 type=aa

<<<48128, 48128 bytes>>>
succeeded (status 0x88888888)
jumping to 0x00907400
j4 in err=0, last_trans=64  33 22 0a 00
config file <recovery\\\mx6_usb_sdp_spl.conf>
parse recovery\\\mx6_usb_sdp_spl.conf
Trying to open device vid=0x1b67 pid=0x4fff.........................
Could not open device vid=0x1b67 pid=0x4fff
ECHO is off.
Downloading Toradex Easy Installer failed...
Press any key to continue . . .

Hi @kane , it could be the environment from the previous custom u-boot stops Tezi running. Do you see any output from the serial console when recovery-windows.bat or recovery-linux.sh is executed? What is the version of your custom u-boot installed?
Our default u-boot can be interrupted by a pressing SPACE key on serial console during booting. Is this feature disabled in your custom u-boot? If not, clear u-boot env by env default -fa;saveenv and then load Toradex Easy Installer again in recovery mode.