WP7611-1 new SKU 1105146 is not working on same hardware than SKU 1104796

I got samples of WP7611_1_1105146 since the previos module WP7611_1_1104796 is no longer available, when I use the 1105146 module on the custom harware we developed, several USB errors show up without programming anything in the module.

The application uses several USB devices such as USB to Serial adapters, once the program is flashed, more erros happened and all the ttyACMx disappear after several minutes.

The firmware used is R16.0.1 GENERIC, however I’ve tryed with R16.1 and R16.3 with the same result.

The new module info is:

root@swi-mdm9x28-wp:~# cm info
Device: WP7611-1
IMEI: 355883100927961
IMEISV: E
FSN: EC329175201610
Firmware Version: SWI9X07Y_02.37.03.00 73df45 jenkins 2020/04/08 10:59:14
Bootloader Version: SWI9X07Y_02.37.03.00 73df45 jenkins 2020/04/08 10:59:14
MCU Version:
PRI Part Number (PN): 9911510
PRI Revision: 001.000
Carrier PRI Name: GENERIC
Carrier PRI Revision: 002.095_003
SKU: 1105146
Last Reset Cause: Power Down
Resets Count: Expected: 3 Unexpected: 0

The info of the previous and properly working module is:
root@swi-mdm9x28-wp:~# cm info
Device: WP7611-1
IMEI: 355883100551423
IMEISV: E
FSN: ZW230130541510
Firmware Version: SWI9X07Y_02.37.03.00 73df45 jenkins 2020/04/08 10:59:14
Bootloader Version: SWI9X07Y_02.37.03.00 73df45 jenkins 2020/04/08 10:59:14
MCU Version:
PRI Part Number (PN): 9910286
PRI Revision: 001.002
Carrier PRI Name: GENERIC
Carrier PRI Revision: 002.095_003
SKU: 1104796
Last Reset Cause: Crash
Resets Count: Expected: 1 Unexpected: 1

USB Errors that new module shows without programming:

[ 26.130497] usb 1-1.2: clear tt 3 (0080) error -71
[ 26.144470] usb 1-1.2-port3: cannot reset (err = -71)
[ 27.182476] usb 1-1.2-port3: cannot reset (err = -110)
[ 28.202697] usb 1-1.2-port3: cannot reset (err = -110)
[ 29.222333] usb 1-1.2-port3: cannot reset (err = -110)
[ 30.242347] usb 1-1.2-port3: cannot reset (err = -110)
[ 30.246455] usb 1-1.2-port3: Cannot enable. Maybe the USB cable is bad?
[ 31.332390] usb 1-1.2-port3: cannot disable (err = -110)
[ 32.354558] usb 1-1.2-port3: cannot reset (err = -110)
[ 33.375366] usb 1-1.2-port3: cannot reset (err = -110)
[ 34.395332] usb 1-1.2-port3: cannot reset (err = -110)
[ 35.425319] usb 1-1.2-port3: cannot reset (err = -110)
[ 36.444049] usb 1-1.2-port3: cannot reset (err = -110)
[ 36.448177] usb 1-1.2-port3: Cannot enable. Maybe the USB cable is bad?
[ 37.495378] usb 1-1.2-port3: cannot disable (err = -110)
[ 38.514890] usb 1-1.2-port3: cannot reset (err = -110)
[ 39.535351] usb 1-1.2-port3: cannot reset (err = -110)
[ 40.554732] usb 1-1.2-port3: cannot reset (err = -110)
[ 41.574676] usb 1-1.2-port3: cannot reset (err = -110)
[ 42.595373] usb 1-1.2-port3: cannot reset (err = -110)
[ 42.599502] usb 1-1.2-port3: Cannot enable. Maybe the USB cable is bad?
[ 43.625329] usb 1-1.2-port3: cannot disable (err = -110)
[ 44.645342] usb 1-1.2-port3: cannot reset (err = -110)
[ 45.665345] usb 1-1.2-port3: cannot reset (err = -110)
[ 46.685654] usb 1-1.2-port3: cannot reset (err = -110)
[ 47.704959] usb 1-1.2-port3: cannot reset (err = -110)
[ 48.725475] usb 1-1.2-port3: cannot reset (err = -110)
[ 48.729601] usb 1-1.2-port3: Cannot enable. Maybe the USB cable is bad?
[ 49.752616] usb 1-1.2-port3: cannot disable (err = -110)
[ 50.772397] usb 1-1.2-port3: cannot disable (err = -110)
root@swi-mdm9x28-wp:~#

Any idea on how to fix it would be appreciated.

Could it be some soldering issue on USB pins?

how did you flash program if the USB is not working?

Did you check the UART2 for the console log?

Hello jyijyi, we use Snap-in Socket, so literally I used the same custom harware to test the new module. I made sure the hardware is full working with the previous module.

For flashing we have dedicated the USB port, for the application, we use the HSIC port, a HSIC USB Hub is used, then USB-Serial adapters are connected to the hub.

And yes, for the console log, I used the UART2 port, in fact, the erros and the cm info command were captured from the UART2 port.

so the USB error message is about HSIC port instead of physical USB pins, right?

Have you checked HSICENABLE flag in AT!CUSTOM?

Yes, USB error messages are related to HSIC port.

I haven’t checked HSICENABLE flag, thanks for the tip, I’ll check.

I checked the HSICENABLE flag, the flag is already set to 1:
imagen

About 9 months ago I tried with WP7610_1104125, and this behaviour was observed, I did not pay much attention to it, because the WP7610 is obsolete.

I’m also trying with a sample of WP7611_1105148, same issues, so far I’ve identified 3 models with the issue.

Have you compared the pin related to the hsic chipset or hub?
Wondering if there is some gpio pin to power on the peripherals hardware

Furthemore, do you have mangoh board to verify?

Unfortunately I don’t have a mangoh board available, since this custom hardware was developed 2 years ago, we considere it as stable, more than 3000 units produced so far, no special treatment, nor configuration was requiered, just flashing the program to each module.

The IC used for HSIC is the same than mangoh green uses USB3503T-I/ML, mangoh green was used as a reference.

since you are using Snap-in Socket like mangoh board, could it be the metal case not completed closed?
Do you see any signal on the HSIC pin?

You might really need to get a mangoh board to compare

I found my mangoh green, as suggested, and tested both WP7611-1_1105146 and WP7611_1105148, I connected one of the devices (a scanner) we use in our application to USB port CN327, which is related to HSIC, the result is the described issue is present.

So far we have used 3 different SKU WP7603-1_1104250, WP7611-1_1104796 and WP7611_1104795, aready tested using mangoh green, and the issue is no present.

The log of the mangoh green with wp7611_1_1105146 is:
wp7611_1_1105146(Green_log).txt (27.3 KB)

Do you connect two devices to the HSIC bus?

[    1.998240] usb 1-1.1: Manufacturer: FTDI
[    1.998251] usb 1-1.1: SerialNumber: DJ00QLMA
[    2.090155] usb 1-1.3: new high-speed USB device number 4 using msm_hsic_host
[    2.200798] usb 1-1.3: New USB device found, idVendor=0424, idProduct=9514
[    2.200815] usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.480127] usb 1-1.3.1: new high-speed USB device number 5 using msm_hsic_host
[    2.590802] usb 1-1.3.1: New USB device found, idVendor=0424, idProduct=ec00
[    2.590820] usb 1-1.3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.655060] smsc95xx 1-1.3.1:1.0 eth0: register 'smsc95xx' at usb-7c00000.hsic_host-1.3.1, smsc95xx USB 2.0 Ethernet, cda803c8
[    3.400150] usb 1-1.3.2: new full-speed USB device number 6 using msm_hsic_host
[    3.511912] usb 1-1.3.2: New USB device found, idVendor=060e, idProduct=16c7
[    3.511928] usb 1-1.3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=8
[    3.511940] usb 1-1.3.2: Product: 7733XP
[    3.511951] usb 1-1.3.2: Manufacturer: Newtologic
[    3.511961] usb 1-1.3.2: SerialNumber: XXXXXX

And it seems problem is only happening on 7733XP:


[   26.096496] usb 1-1.3: clear tt 2 (0060) error -71
[   27.132370] usb 1-1.3-port2: cannot reset (err = -110)
[   28.152383] usb 1-1.3-port2: cannot reset (err = -110)
[   29.172379] usb 1-1.3-port2: cannot reset (err = -110)
[   30.192416] usb 1-1.3-port2: cannot reset (err = -110)
[   31.212415] usb 1-1.3-port2: cannot reset (err = -110)
[   31.216525] usb 1-1.3-port2: Cannot enable. Maybe the USB cable is bad?
[   32.262857] usb 1-1.3-port2: cannot disable (err = -110)
[   33.282411] usb 1-1.3-port2: cannot reset (err = -110)
[   34.302399] usb 1-1.3-port2: cannot reset (err = -110)
[   35.322398] usb 1-1.3-port2: cannot reset (err = -110)
[   36.342361] usb 1-1.3-port2: cannot reset (err = -110)
[   37.362409] usb 1-1.3-port2: cannot reset (err = -110)
[   37.366535] usb 1-1.3-port2: Cannot enable. Maybe the USB cable is bad?

Have you tried if a USB thumb drive is working on the HSIC USB port?

Can you check if there is any difference between those two SKU with AT+WIOCFG? setting?

Lastly, if you downgrade wp7611_1_1105146 to FW R13.x , does the problem still exist?

https://source.sierrawireless.com/resources/airprime/software/wp76xx/wp76xx-firmware-release-13,-d-,1,-d-,1/#sthash.mu1ldr0f.hKPO0yPG.dpbs

Hi @jyijyi , Thanks a lot for your time and support, the question about the AT+WIOCFG gave me the clue, the problem was that the EXTUIMSWITCHEN flag was enabled, so the reset signal was not working.