WP8548 Filesystem

Hello guys,
I have a module WP8548 and the file system was corrupted.

I’m having a several problems with update.

Can someone help me?


Hi @Allyson,

as provided on your other thread:
As for the bricked WP85, if you are using a mangOH Green, you should be able to put it back into recovery mode through TP1_BOOT on switch 7 @ SW401, cf http://mangoh.io/uploaded-documents/Reference/mangOH%20Green/Discover/Hardware%20User%20Guide/mangOH%20Dev%20Kit%20User%20Guide%20-%20HTML5-Responsive%20HTML5/#t=mangOH_Dev_Kit_User_Guide_-_HTML5%2FHardware%2FHardware.htm&rhsearch=switch&rhhlterm=switch&rhsyns=%20#XREF_26954_SW401_Module

Upon reboot it should be in some kind of ‘recovery mode’ which should allow you to use fdt or swiflash (https://source.sierrawireless.com/resources/airprime/software/swiflash/) to flash a .cwe or .spk that overrides the faulty rootfs.

Note that it would be useful if you can provide some logs as we are trying our best to prevent this kind of situation.
In case of problem the idea is that it should rollback to the previous system.
Did you rebuild/modify the rootfs?
Also you can wipe the ‘user’ partition through swiflash using swiflash -r.

Hi @CoRfr,

Thanks to your help.

SW401 switches are (ON, OFF, OFF, OFF, OFF, OFF, OFF, OFF)

See that boot error

[ 3.740668] hub 1-1.3:1.0: USB hub found
[ 3.744025] hub 1-1.3:1.0: 5 ports detected
[ 3.827010] random: nonblocking pool is initialized
[ 3.838303] ubi0: scanning is finished
[ 3.851365] ubi0: attached mtd2 (name “rootfs”, size 49 MiB)
[ 3.856035] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 3.862994] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 3.869647] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[ 3.876606] ubi0: good PEBs: 394, bad PEBs: 0, corrupted PEBs: 0
[ 3.882588] ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
[ 3.889790] ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 1562874273
[ 3.898916] ubi0: available PEBs: 290, total reserved PEBs: 104, PEBs reserved for bad PEB handling: 80
[ 3.908316] ubi0: background thread “ubi_bgt0d” started, PID 77
UBI device number 0, total 394 LEBs (50028544 bytes, 47.7 MiB), available 290 LEBs (36823040 bytes, 35.1 MiB), LEB size 126976 bytes (124.0 KiB)
[ 3.945673] block ubiblock0_0: created from ubi0:0(legato)
rootfs: dev ‘/dev/ubiblock0_0’ 'squashfs’
rootfs: mount failed
System error!
[ 4.018464] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[ 4.018464]
[ 4.026583] CPU: 0 PID: 1 Comm: init Not tainted 3.14.29ltsi-961ca71325_ab5094eade #2
[ 4.034457] [] (unwind_backtrace) from [] (show_stack+0x20/0x24)
[ 4.042148] [] (show_stack) from [] (dump_stack+0x20/0x28)
[ 4.049351] [] (dump_stack) from [] (panic+0x9c/0x1dc)
[ 4.056188] [] (panic) from [] (do_exit+0x4b0/0x90c)
[ 4.062871] [] (do_exit) from [] (do_group_exit+0x5c/0xdc)
[ 4.070074] [] (do_group_exit) from [] (__wake_up_parent+0x0/0x30)
[ 4.077979] [] (__wake_up_parent) from [] (ret_fast_syscall+0x0/0x30)
[ 4.186021] Rebooting in 5 seconds…

Hi @Allyson,

oh so it’s the ‘legato’ partition that is causing some issue.
I mean, I don’t think it should do a kernel panic for that though.

Can you try to replace the Legato image by flashing legatoz.cwe 16.10.3 from https://source.sierrawireless.com/resources/legato/wpfirmwarerelease/ ?

You should be able to flash from the ‘recovery mode’.

By any chance, did you try the recovery method above?

From a normal boot sequence, it should be:

[    3.885426] block ubiblock0_0: created from ubi0:0(rootfs)
DM verity is not enabled.
rootfs: dev '/dev/ubiblock0_0' 'squashfs'
[    3.938654] random: nonblocking pool is initialized
rootfs: mounting took 20ms

Note the “ubi0:0(rootfs)” while you have “ubi0:0(legato)”, which makes me think that you have a legato image flashed on mtd2, instead of a rootfs.

Hi @CoRfr

The link https://gerrit-legato/#/c/9141/8/modem_proc/qmimsgs/swiaudio/api/swiqmi_audio_v01.h returned “gerrit-legato’s server DNS address could not be found”.

You sure that is a valid URL?

My apologies, I meant https://source.sierrawireless.com/resources/legato/wpfirmwarerelease/