Mangoh Red Rev6 - WP8548 issue


#1

Dear All,

We have received new Mangoh Red wp85 - revision 6 boards Is there any info what have been changed to rev 5 HW? Also, the wp85 processors seem to be in strange USB mode so usb ethernet interface was not working so we will try to use swiflash later to recover the modules.

Thanks,
Tom


#2

The changes are: The Battery Fuel Gauge is replaced with the TI part (BQ27426) and also added 8-bit Buffer chip to support the HL78 module.


#3

Hi Habib, Thanks for the informaiton.
We have a serious problem, none of the new batch of Mangoh Reds Rev6 seems to be working. The “old” WP85 processors are working in Rev6 board so it is the processor that is causing us a problem. On mangoh Green we could refresh the firmware with swiflash but after that still does not work normally neither on Mangoh Green and Red. We are running out of ideas…

Ids from two of not working wp85 processors:
1.
IMEI: 354282090118304
S/N: LL841301590810
2.
IMEI: 354282090117843
S/N: LL841302511010

Does anybody have any idea what to try?
Has somebody else received recently new Mangoh Red rev6 WP85 boards?

Thanks
tom


#4

Hi Tom,
. So the problem is not red but the Wp85 shipped with red DV6. Correct?

@Habib let’s order one today and check


#5

Hello Asyal,

Yes, it is the WP85 module. It seems to be the USB interface, but swiflash should flash that settings too, or am I wrong?

Thanks
tom


#6

Is the console ok ? What do you read ?


#7

Also, did you do complete firmware update?


#8

Hi Asyal,
I’m working with tomalex.
The firmware download to the chip seemed to have worked, but looks like it got stuck in reboot.
It tried to reboot for over 10 minutes. But after that nothing changed.

No, also the console doesn’t work.
The development system recognizes the FTDI device and I can even open a screen session,
but the device is not responding.

We have no response from the board in any way.

Thanks
G.


#9

And eveything works well with the older modules ?

@dfrey can you send them the swiflash erase command. I think it is
swiflash -m WP85 -r
I am not next to a comp so can’t verify . They might want to try with boot pin (sw401-7) up


#10

Yes, the chips of the older boards work completely fine. ssh and uart work as intended.

I also tried the -r command. The same result as the firmware update. Download worked fine, it got stuck in reboot and afterwards nothing changed.

Bootloader mode was the only way that swiflash even recognized the device.


#11

Is there any log messages for bad modules? At this point @habib can you please order Wp85 mangoh red and test?


#12

Hi Asyal,
dmesg log iooks diffent, “Aircard TRU-Install” ?

[ 5854.390921] usb 1-1: new high-speed USB device number 37 using xhci_hcd
[ 5854.542020] usb 1-1: config 1 has an invalid interface number: 10 but max is 8
[ 5854.542026] usb 1-1: config 1 has an invalid interface number: 11 but max is 8
[ 5854.542030] usb 1-1: config 1 has an invalid interface number: 16 but max is 8
[ 5854.542033] usb 1-1: config 1 has an invalid interface number: 17 but max is 8
[ 5854.542037] usb 1-1: config 1 has an invalid interface number: 17 but max is 8
[ 5854.542041] usb 1-1: config 1 has an invalid interface number: 18 but max is 8
[ 5854.542045] usb 1-1: config 1 has an invalid interface number: 18 but max is 8
[ 5854.542049] usb 1-1: config 1 has an invalid interface number: 9 but max is 8
[ 5854.542053] usb 1-1: config 1 has no interface number 1
[ 5854.542056] usb 1-1: config 1 has no interface number 2
[ 5854.542060] usb 1-1: config 1 has no interface number 4
[ 5854.542063] usb 1-1: config 1 has no interface number 5
[ 5854.542066] usb 1-1: config 1 has no interface number 6
[ 5854.542070] usb 1-1: config 1 has no interface number 7
[ 5854.543093] usb 1-1: New USB device found, idVendor=1199, idProduct=68c0
[ 5854.543099] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5854.543103] usb 1-1: Product: WP8548
[ 5854.543107] usb 1-1: Manufacturer: Sierra Wireless, Incorporated
[ 5854.543113] usb 1-1: SerialNumber: 0123456789ABCDEF
[ 5854.548031] qcserial 1-1:1.0: Qualcomm USB modem converter detected
[ 5854.548243] usb 1-1: Qualcomm USB modem converter now attached to ttyUSB0
[ 5854.549157] qcserial 1-1:1.3: Qualcomm USB modem converter detected
[ 5854.549275] usb 1-1: Qualcomm USB modem converter now attached to ttyUSB1
[ 5854.549936] GobiNet 1-1:1.8 eth0: register ‘GobiNet’ at usb-0000:00:14.0-1, GobiNet Ethernet Device, fe:5f:d0:19:d8:6b
[ 5854.550097] USB Speed : USB 2.0
[ 5854.550750] GobiNet 1-1:1.10 eth1: register ‘GobiNet’ at usb-0000:00:14.0-1, GobiNet Ethernet Device, fe:5f:d0:19:d8:6b
[ 5854.551431] USB Speed : USB 2.0
[ 5854.558040] usb-storage 1-1:1.9: USB Mass Storage device detected
[ 5854.558273] scsi host5: usb-storage 1-1:1.9
[ 5855.094413] GobiNet 1-1:1.10 enp0s20f0u1i10: renamed from eth1
[ 5855.111074] GobiNet 1-1:1.8 enp0s20f0u1i8: renamed from eth0
[ 5855.127193] IPv6: ADDRCONF(NETDEV_UP): enp0s20f0u1i10: link is not ready
[ 5855.127263] IPv6: ADDRCONF(NETDEV_UP): enp0s20f0u1i10: link is not ready
[ 5855.127616] IPv6: ADDRCONF(NETDEV_UP): enp0s20f0u1i10: link is not ready
[ 5855.134594] IPv6: ADDRCONF(NETDEV_UP): enp0s20f0u1i8: link is not ready
[ 5855.134742] IPv6: ADDRCONF(NETDEV_UP): enp0s20f0u1i8: link is not ready
[ 5855.135092] IPv6: ADDRCONF(NETDEV_UP): enp0s20f0u1i8: link is not ready
[ 5855.572229] scsi 5:0:0:0: Direct-Access Aircard TRU-Install 2.31 PQ: 0 ANSI: 2
[ 5855.572995] sd 5:0:0:0: Attached scsi generic sg3 type 0
[ 5855.573377] sd 5:0:0:0: Power-on or device reset occurred
[ 5855.575313] sd 5:0:0:0: [sdc] Attached SCSI removable disk


#13

All of the processors that we have received with dev6 boards seems to be the SKU 1103133, and the working old ones are SKU 1103113.
I don’t even see this SKU 1103133 anywhere:
https://octopart.com/search?q=WP8548&start=0


#14

Hi Tom,

Send me a message with your address. We will look at shipping you the right SKU 8548. Can you ship me back those modules btw?

Regards,
Ashish


unlisted #15