My EM7565 is installed in an omnia turris router (based on openwrt).
I installed all the packages required. I could create the interface using qmi protocol, and stating using AT commands. At some point I issued a AT!usbcomp=1,1,1001 command. Since then, all ttyUSB devices have disappeared.
I tried the " echo 1199 9091 > /sys/bus/usb-serial/drivers/qcserial/new_id " command. It did recreate a ttyUSB0 device, but I can’t send and AT! command to it, and it seems unusable.
Any idea to help me?
Ouch. Don’t do that…
You might have more luck with the option driver. The qcserial driver has a strict layout built-in. But success will depend on the AT function still being enabled by firmware. And I’m not sure it is… Anyway, the option driver is worth a try. See the hints here: EM7565 wrong USBCOMP Command sent - did i brick it?
Don’t panic. Collect and post more information if you can’t figure out a way to get to a working AT command function.
Thank you for your message… I also tried the command with option driver… with the same result 
What gives me hopeis that I get the folowing result with lsusb command :
root@turris:~# lsusb -t
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=orion-ehci/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Communications, Driver=, 480M
|__ Port 1: Dev 2, If 1, Class=CDC Data, Driver=, 480M
|__ Port 1: Dev 2, If 4, Class=Vendor Specific Class, Driver=, 480M
Or when I browse the /sys/dev/char folder I find these devices :
lrwxrwxrwx 1 root root 0 Jan 5 18:24 189:0 -> …/…/devices/platform/soc/soc:internal-regs/f1058000.usb/usb1
lrwxrwxrwx 1 root root 0 Jan 5 18:24 189:1 -> …/…/devices/platform/soc/soc:internal-regs/f1058000.usb/usb1/1-1
lrwxrwxrwx 1 root root 0 Jan 5 20:21 189:128 -> …/…/devices/platform/soc/soc:internal-regs/f10f0000.usb3/usb2
lrwxrwxrwx 1 root root 0 Jan 5 20:21 189:256 -> …/…/devices/platform/soc/soc:internal-regs/f10f0000.usb3/usb3
lrwxrwxrwx 1 root root 0 Jan 5 20:21 189:384 -> …/…/devices/platform/soc/soc:internal-regs/f10f8000.usb3/usb4
lrwxrwxrwx 1 root root 0 Jan 5 20:21 189:512 -> …/…/devices/platform/soc/soc:internal-regs/f10f8000.usb3/usb5
Obviously the modem is device 2 on bus 1. But I have no clue of what I could do at this point…
lsusb -v tells a bt more, like the number of endpoints for each interface.
But I’m afraid the info you already posted along matches what I feared: You have only an MBIM function (interfaces 0 and 1) and a QCDM function (interface 4). The AT command function is disabled. Unfortunately I don’t think the method we previously used to change this setting via QMI/MBIM works on the EM7565.
Let’s hope someone else knows a way to change this variable using either the bootloader, QCDM or MBIM.
Thank you for yrou help.
the result of lsusb -v is below
root@turris:/sys/dev/char# lsusb -s 01:2 -v
Bus 001 Device 002: ID 1199:9091 Sierra Wireless, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2 ?
bDeviceProtocol 1 Interface Association
bMaxPacketSize0 64
idVendor 0x1199 Sierra Wireless, Inc.
idProduct 0x9091
bcdDevice 0.06
iManufacturer 1 Sierra Wireless, Incorporated
iProduct 2 Sierra Wireless EM7565 Qualcomm® Snapdragon™ X16 LTE-A
iSerial 3 UF81859331030635
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 118
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 500mA
Interface Association:
bLength 8
bDescriptorType 11
bFirstInterface 0
bInterfaceCount 2
bFunctionClass 2 Communications
bFunctionSubClass 14
bFunctionProtocol 0
iFunction 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 14
bInterfaceProtocol 0
iInterface 0
CDC Header:
bcdCDC 1.10
CDC Union:
bMasterInterface 0
bSlaveInterface 1
CDC MBIM:
bcdMBIMVersion 1.00
wMaxControlMessage 4096
bNumberFilters 32
bMaxFilterSize 128
wMaxSegmentSize 2048
bmNetworkCapabilities 0x20
8-byte ntb input size
UNRECOGNIZED CDC: 08 24 1c 00 01 40 dc 05
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 9
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 2
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 2
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8e EP 14 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x0f EP 15 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 4
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2 ?
bDeviceProtocol 1 Interface Association
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
We had a Windows one click updater for the 74 series that could be used in cases like this where people had set the USB to a state where it could not easily be recovered, the tool set it back to the default USB config. We don’t have one for the EM75 yet but it has been requested internally, if you raise this with your distributor then they will be able to get hold of it when it is created.
Regards
Matt
Thank you Matt,
Looking forward to this one click updater…
Alain
Matt,
the modem was purchased on ebay, and after some emails, I have no more news from the reseller, with of course no one click updater received. Does that mean that the modem is lost?
is there any possibility to have some help from sierra wireless?
Thank you