Broken PLS8-e units | Thales IoT Developer Community
November 22, 2019 - 1:19pm, 3119 views
We have some products with PLS8-e modules which started to fail. The units will enumerate on the USB bus als Cinterion LTE Modem (1e2d:0061) in the linux kernel messages all subdevices seem to return error -22 and "zero lenght decriptor references) after exactly 60 seconds the device disconnects and start over again.
The following messages are logged in the kernel logging:
usb 1-1.3: USB disconnect, device number 19
usb 1-1.3: new high-speed USB device number 20 using ehci_hcd
cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device
cdc_acm 1-1.3:1.2: ttyACM1: USB ACM device
cdc_acm 1-1.3:1.4: ttyACM2: USB ACM device
cdc_acm 1-1.3:1.6: ttyACM3: USB ACM device
cdc_acm 1-1.3:1.8: ttyACM4: USB ACM device
cdc_ether: probe of 1-1.3:1.10 failed with error -32
cdc_acm: probe of 1-1.3:1.10 failed with error -22
cdc_acm 1-1.3:1.11: Zero length descriptor references
cdc_acm: probe of 1-1.3:1.11 failed with error -22
cdc_ether: probe of 1-1.3:1.12 failed with error -32
cdc_acm: probe of 1-1.3:1.12 failed with error -22
cdc_acm 1-1.3:1.13: Zero length descriptor references
cdc_acm: probe of 1-1.3:1.13 failed with error -22
These modules worked when produced but stopped working over time. It looks to me only some piece of bootrom is working but the firmware in the device is corrupted or something like that.
All ttyACM interfaces just give zero reads and no SYSSTART or AT responses are seen.
Are there more customers seeing this kind of problems? Do we just have some faulty units?