Is my EHS6T definitely ****? | Thales IoT Developer Community
October 25, 2022 - 3:46pm, 380 views
My EHS6T could not load OpenWrt anymore and I did hadn't any other choice to try a Hard Reset.
The process didn't succeed because I didn't have te rescue page to upload Firmware but now modem boot normally now.
So after that reset attempt OpenWrt is available and I can login through Web and SSH.
Unfortunately I'm no more able to access Modem through serial. When I connect I can't input any command and even when I reboot modem nothing is shown on console port but modem boot and I can still access OpenWRT. In OpenWRT the USB interface is missing... I tried factory reset from Web page but still the same.
Please, could you advise if Modem module had **** definitely or there is a way to fix.
OpenWrt and EHS6 module are the separate systems. OpenWrt system communicates with the module over USB interface and used it as a modem. OpenWrt also manages the LAN interface. EHS6 is directly accessible over RS232 interface on the casing.
So theoretically it is possible that OpenWrt runs while the module does not or vice versa.
Did you reconfigure EHS6 module anyhow? It is possible to disable the RS232 interfaces with AT command - please see AT^SPOW command in the AT commands specification. It is also possible that you might have reconfigured some serial communication parameters like baudrate etc. Can you find any USB enumeration in the system log? Please check what you can find. If you can't see any USB enumeration from OpenWrt nor you can't communicate via the serial interface, this suggests that something might have happened to the module. Or maybe you have changed some other configuration like response codes format etc. Can you see anything on serial when you power up the device?
Unfortunately I'm no more able to access Modem through serial. When I connect I can't input any command and even when I reboot modem nothing is shown on console port but modem boot and I can still access OpenWRT. In OpenWRT the USB interface is missing...
Could Hard reset change something ?
How do you reboot the terminal - do you power cycle it or do a software reboot of OpenWrt? Please check the power cycle.
Please check dmesg or logread outputs if there is any information about USB or cdc_acm.
For now it looks like there is a problem with the module. So, hard-resetting the OpenWrt system would not help.
How about the LED?
I have USB and cdc_acm information in dmesg:
[ 0.519788] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
[ 0.526010] ar933x-uart: ttyATH0 at MMIO 0x18020000 (irq = 11, base_baud = 2500000) is a AR933X UART
[ 0.534776] console [ttyATH0] enabled
[ 0.541447] bootconsole [early0] disabled
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 10.154890] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN
[ 3.801784] usbcore: registered new device driver usb
But lsusb doesn't show the USB interface.
Hope there is a chance for rescue.
Looks for me like nothing have been enumerated.
Here's my lsusb output on a similar terminal:
Bus 001 Device 002: ID 1e2d:005b
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
So, there's a module and usb hub. If you can't see the module at all it most probably mean that it does not start. Especially if you can't communicate over serial port (which is directly connected to the module) and you was able to do it before.