The unit described below seems to be unusable and does not “boot” i am able to access the TTY on power up and seems the MCU is active but not the ARM core any ideas on where to look further ?
ATI3
Manufacturer: Sierra Wireless, Incorporated
Model: WP8548
Revision: SWI9X15Y_07.12.14.00 r34472 CARMD-EV-FRMWR1 2017/11/29 18:24:42
IMEI: 359377060030094
IMEI SV: 46
FSN: LL621100290706
+GCAP: +CGSM,+DS,+ES
ATI8
Legato Ver: 18.03.0_c733ac5c03f8a3c9a87e60500d601634
Yocto Ver: SWI9X15Y_07.12.14.00 2018-04-14_20:43:56
OS Ver: Linux version 3.14.29ltsi-36b09ac0d2_1ff719e057 (comb@comb-desktop) (gcc version 4.9.1 (GCC) ) #3 PREEMPT Sat Apr 14 20:41:36 SAST 2018
LK Ver: unknown
RootFS Ver: SWI9X15Y_07.12.14.00 2018-04-14_20:43:56
UserFS Ver: unknown
MCU Ver: 002.004
AT!ENTERCND="A710"
AT!UDINFO?
VID: 0x1199
PID: 0x68C0
Interface: QMI
Manufacturer: Sierra Wireless, Incorporated
Product: WP8548
AT!USBCOMP=?
!USBCOMP:
AT!USBCOMP=<Config Index>,<Config Type>,<Interface bitmask>
<Config Index> - configuration index to which the composition applies, should be 1
<Config Type> - 1:Generic
<Interface bitmask> - DIAG - 0x00000001,
NMEA - 0x00000004,
MODEM - 0x00000008,
AT - 0x00000010,
OSA - 0x00000020,
RAWDATA - 0x00000040,
RMNET0 - 0x00000100,
RMNET1 - 0x00000400,
MBIM - 0x00001000,
RNDIS - 0x00004000,
AUDIO - 0x00010000,
ECM - 0x00080000,
e.g.
10D - diag, nmea, modem, rmnet interfaces enabled
1009 - diag, modem, mbim interfaces enabled
AT!USBCOMP?
Not Set
AT!PRIID?
PRI Part Number: Unknown
Revision: Unknown
Carrier PRI: 9999999_9904559_SWI9X15Y_07.12.14.00_00_GENERIC_001.034_000
AT!CUSTOM?
!CUSTOM:
GPIOSARENABLE 0x01
WAKEHOSTEN 0x01
RMNETREDIALEN 0x01
HSICENABLE 0x01
OK
Yip the default spk from the source page R15 and our own firmware as released we have 200 boards build based on the mangoh this is the first time i have seen this swaping the WP8548 out the board functions fine.
I have R15 / 18.03 working quite well on the WP85’s we have started using WP76’s waiting for production stock and want to use the same version of legato on all platforms. i did load the R15/16.10.4 build as well onto this unit then loaded our build back on.
This is from the same board with a new CPU loaded with R15/18.03
Device: WP8548
IMEI: 359377060030383
IMEISV: 2E
FSN: LL620100110706
Firmware Version: SWI9X15Y_07.12.14.00 r34472 CARMD-EV-FRMWR1 2017/11/29 18:24:42
Bootloader Version: SWI9X15Y_07.12.14.00 r34472 CARMD-EV-FRMWR1 2017/11/29 18:24:42
MCU Version: 002.004
PRI Part Number (PN): 9905383
PRI Revision: 01.02
Carrier PRI Name: GENERIC
Carrier PRI Revision: 001.034_000
SKU: 1102816
Last Reset Cause: Unknown
Resets Count: Expected: 0 Unexpected: 0
Here is the file i loaded on the board 15.0 = 18.02 15.1 = 18.03
No not at all that is the current version we testing and have some in the field already the CPU never turns on at all regardless of version the same board with a new WP85 is working fine on 18.03 see cm info output above and the spk file i loaded onto the new cpu on the board …
IT was running overnight here in the lab and died a miserable death i have put it one side and will send it in to arrow for follow up. i am very interested in understanding it for future purposes