Tezi Installer Trouble Shoot issue in linux host machine - Verdin imx8mp

[Hariprabhu_13]

Hi,

Reference for Linux Tezi Installer: Loading Toradex Easy Installer | Toradex Developer Center

But I need the troubleshoot issue need for the linux host after followed the specific recovery mode and tezi installer download form the docs for the verdin imx8mp, nothing troublehsoot issue is given by the tdx docs for the linux, im still pending for the command response for both “./recovery-linux.sh” and “sudo sh recovery-linux.sh”

For troubleshooting, the Toradex official documentation provides steps only for Windows host machines. We are currently using a Windows host machine, and we do not have a Linux host machine available to check or troubleshoot this issue from the Linux side. Moreover, the troubleshooting options mentioned in the Toradex official documentation are also provided only for Windows host machines.

Troubleshooting documentation for Windows: Loading Toradex Easy Installer | Toradex Developer Center

Any suggestions to resolve this trouble shoot issue in linux host machine what we need to do?

[ToradexAI]

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

---

Troubleshooting Linux Host Issues with Toradex Easy Installer

When the ./recovery-linux.sh script hangs or doesn’t respond on a Linux host, there are several troubleshooting steps you can take based on the Toradex documentation(1).

Common Issues and Solutions

1. USB Enumeration Problems

The Toradex Easy Installer SPL/U-Boot bootloader re-enumerates as different USB devices during recovery mode(1). This can cause issues similar to what you’re experiencing.

If you’re using an Ixora Carrier Board, ensure that X9 is configured in OTG mode by removing JP2(1).

2. USB Cable and Port Issues

Try the following hardware troubleshooting steps(1):

• Use a different USB cable
• Connect to a non-USB3 port on your host machine
• Avoid using USB hubs between the PC and the USB OTG port(2)

3. Check USB Device Recognition

On your Linux host, you can monitor USB device detection using:

dmesg | tail -f

This will show you if the device is being detected and re-enumerating during the recovery process.

You can also check connected USB devices with:

lsusb

4. Network-Related Issues

If the script hangs during download, some firewalls have issues with TCP window scale option(1). You can disable this using:

sysctl -w "net.ipv4.tcp_window_scaling=0"

5. Serial Console Access

There’s a serial console available on UART1/UART_A which you can use to access the Easy Installer’s shell(1). The main UI process outputs debug messages to:

/var/volatile/tezi.log

To view the current log content:

cat /var/volatile/tezi.log

6. Boot Arguments

The Toradex Easy Installer boot scripts start with a fixed set of Linux kernel parameters, but also append any variables defined in teziargs(1). You can add debug parameters such as debug to get full kernel debug output(1).

Additional Recommendations

1. Restart the Recovery Process: If downloading gets stuck or fails, try starting over from the Recovery Mode setup(2)
2. Check Permissions: Ensure you have proper permissions to access USB devices on your Linux system
3. Verify Module is in Recovery Mode: Double-check that your Verdin iMX8M Plus is properly in recovery mode before running the script

If these steps don’t resolve the issue, the problem might be related to your specific Linux distribution’s USB handling or driver configuration.

Best regards, Toradex AI Assistant.

---

Did you like my answer?

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

[Hariprabhu_13]

Hi @ToradexAI,

By default the Ivy carrier doest have the uart console and multiple OTG Support port only single usb otg port verdin ivy carrier board v1.0A, only the way is I have the linux host machine tezi installer failure while the recovery command is executed as both “sudo sh recovery-linux.sh” and “./recovery-linux.sh” are failed and only error is occured. need the trouble shoot issue clearance like the docs already have only for the windows machine.

[ToradexAI]

Linux Host Troubleshooting for Ivy Carrier Board

You’re correct that the Ivy Carrier Board has specific limitations compared to other carrier boards (1). For Linux host troubleshooting when the recovery scripts hang, here are specific steps to diagnose the issue:

Verify Recovery Mode Entry

First, ensure your module is properly in recovery mode. For Verdin modules with Ivy Carrier Board, you need to follow the specific recovery mode procedure (2). The documentation provides direct links for Verdin AM62 and Ivy Carrier Board Recovery Mode, Verdin iMX8M Mini and Ivy Carrier Board Recovery Mode, and Verdin iMX8M Plus and Ivy Carrier Board Recovery Mode (2).

Linux-Specific Diagnostics

Since the documentation notes that you should avoid using Virtual Machines (3), ensure you’re running on a native Linux installation.

Check USB Device Detection:

dmesg | tail -f

Monitor USB devices:

lsusb

Check for USB enumeration issues:
The recovery process involves multiple device re-enumerations (3). During the recovery process, the module connected via USB may re-enumerate several times (3).

Hardware Considerations

The documentation specifically mentions to avoid using a USB Hub between the PC and the USB OTG port (3). Since the Ivy Carrier Board has a single USB OTG port, ensure your connection is direct.

Alternative Approach: External Media

If the USB OTG approach continues to fail, consider using the external media approach (3). You can load TEZI from external media such as a FAT formatted USB stick or SD card (3).

Script Execution Issues

If both ./recovery-linux.sh and sudo sh recovery-linux.sh are hanging, this typically indicates:

1. USB communication failure - The module may not be properly detected in recovery mode
2. Permission issues - Even though you tried with sudo
3. USB driver conflicts on your Linux distribution

Check if the script is executable:

ls -la recovery-linux.sh
chmod +x recovery-linux.sh

Restart Process

If downloading gets stuck or fails with an error, try starting over from the Recovery Mode procedure (3).

Since you mentioned the troubleshooting documentation is primarily for Windows, these Linux-specific diagnostic steps should help identify where the process is failing. The key is ensuring proper USB OTG communication between your Linux host and the module in recovery mode.

Best regards, Toradex AI Assistant.

---

Did you like my answer?

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

[sahil.tx]

Hi @Hariprabhu_13 ,
Is the issue solved?