MTSMC-H5: GSM module is not responing

[Mykyta Dorokhin]

Hello,

I think I’ve sent some AT commands to the HE910 GSM module which broke it.

I’ve been playing with some demo application which send AT command sequences. I think the sequence I’ve sent was:

AT#TEMPMON=1
AT#TXMONMODE=0
AT#GPIO=5,0,2
AT#V24CFG=0,1;#V24=0,1
AT#V24=0,0
AT#V24=0,1
AT#V24CFG=0,0

I understand this was stupid but I didn’t expect that it is possible to brake it with AT commands. Maybe something else went wrong and AT commands have nothing to do with this.

Anyway, the module is not responding anymore. MTSMC-H5 reboot doesn’t help.

Is there any way to bring it back to live? Any kind of reset jumper or something?

Here is my dmesg:

usb 1-1: new full speed USB device using at91_ohci and address 2^M
usb 1-1: New USB device found, idVendor=1bc7, idProduct=0021^M
usb 1-1: New USB device strings: Mfr=18, Product=19, SerialNumber=20^M
usb 1-1: Product: Telit Wireless Module^M
usb 1-1: Manufacturer: Telit wireless solutions^M
usb 1-1: SerialNumber: 351579050053105^M
cdc_acm 1-1:1.0: This device cannot do calls on its own. It is not a modem.^M
cdc_acm 1-1:1.0: ttyACM0: USB ACM device^M
cdc_acm 1-1:1.2: This device cannot do calls on its own. It is not a modem.^M
cdc_acm 1-1:1.2: ttyACM1: USB ACM device^M
cdc_acm 1-1:1.4: This device cannot do calls on its own. It is not a modem.^M
cdc_acm 1-1:1.4: ttyACM2: USB ACM device^M
cdc_acm 1-1:1.6: This device cannot do calls on its own. It is not a modem.^M
cdc_acm 1-1:1.6: ttyACM3: USB ACM device^M
cdc_acm 1-1:1.8: This device cannot do calls on its own. It is not a modem.^M
cdc_acm 1-1:1.8: ttyACM4: USB ACM device^M
cdc_acm 1-1:1.10: This device cannot do calls on its own. It is not a modem.^M
cdc_acm 1-1:1.10: ttyACM5: USB ACM device^M
cdc_acm 1-1:1.12: This device cannot do calls on its own. It is not a modem.^M
cdc_acm 1-1:1.12: ttyACM6: USB ACM device^M
usbcore: registered new interface driver cdc_acm^M
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters^M
JFFS2 notice: (256) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.^M
[INFO] mts-io:mts_io_init:2438: init: v0.5.1^M
[INFO] mts-io:mts_id_eeprom_load:403: sizeof: 512^M
[INFO] mts-io:mts_id_eeprom_load:404: vendor-id: Multi-Tech Systems^M
[INFO] mts-io:mts_id_eeprom_load:405: product-id: MTCDP-E1-DK^M
[INFO] mts-io:mts_id_eeprom_load:406: device-id:^M
[INFO] mts-io:mts_id_eeprom_load:407: hw-version: MTCDP-0.0^M
[INFO] mts-io:mts_id_eeprom_load:414: mac-addr: 00:00:00:00:00:00^M
[INFO] mts-io:mts_id_eeprom_load:415: imei:^M
[INFO] mts-io:mts_id_eeprom_load:416: capa-gps: yes^M
[INFO] mts-io:mts_id_eeprom_load:417: capa-din: no^M
[INFO] mts-io:mts_id_eeprom_load:418: capa-dout: no^M
[INFO] mts-io:mts_id_eeprom_load:419: capa-adc: no^M

Thanks,
Mykyta

[Bryan Tran]

Hi Mykyta,

It looks like the unit is booting up with a wrong model number, no mac address and no imei number..etc. (I am assuming you have a MTCDP-H5).

You may want to create a new support ticket at https://support.multitech.com/support/ and include the serial number of the unit you have.

Thanks,

BT

[Author]

Posts