Recover the (mangOH_red)wp7608 to factory state


#1

Hi,

I had updated the yocto-4k.cwe image on the mangoh using the swicwe tool.
How ever, due to some problem with the loaded image the modem is not booting and resetting all the time.

ndroid Bootloader - UART_DM Initialized!!!
[10] ERROR: No devinfo partition found
[10] Neither ‘config’ nor ‘frp’ partition found
[10] ERROR: No misc partition found
[1080] SSMEM init OK[1080] ssmem_get: region 20 not exists[1170] DEBUG: cmdline has root=
[1290] Channel alloc freed
[ 0.000000] GIC CPU mask not found - kernel will fail to boot.
[ 0.000000] GIC CPU mask not found - kernel will fail to boot.
[ 0.000000] MPM 1 irq mapping errored -517
[ 0.077707] SWI ssmem_framework_init: SSMEM init OK
[ 0.216071] spmi_pmic_arb 200f000.qcom,spmi: PMIC Arb Version-2 0x20010000
[ 0.231402] msm_mpm_dev_probe(): Cannot get clk resource for XO: -517
[ 0.234585] smd_channel_probe_now: allocation table not initialized
[ 0.242347] msm_thermal:msm_thermal_dev_probe Failed reading node=/soc/qcom,msm-thermal, key=qcom,online-hotplug-core. err:-517
[ 0.270875] msm_mpm_dev_probe(): Cannot get clk resource for XO: -517
[ 0.273783] msm_thermal:get_kernel_cluster_info CPU0 topology not initialized.
[ 0.274713] cpu cpu0: dev_pm_opp_get_opp_count: device OPP not found (-19)
[ 0.274732] msm_thermal:get_cpu_freq_plan_len Error reading CPU0 freq table len. error:-19
[ 0.275447] cpu cpu0: dev_pm_opp_get_opp_count: device OPP not found (-19)
[ 0.275463] msm_thermal:get_cpu_freq_plan_len Error reading CPU0 freq table len. error:-19
[ 0.275479] cpu cpu0: dev_pm_opp_get_opp_count: device OPP not found (-19)
[ 0.275492] msm_thermal:get_cpu_freq_plan_len Error reading CPU0 freq table len. error:-19
[ 0.371485] AXI: msm_bus_scale_register_client(): msm_bus_scale_register_client: Bus driver not ready.
[ 0.374561] AXI: msm_bus_scale_register_client(): msm_bus_scale_register_client: Bus driver not ready.[ 0.374855] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:2) mode:FIFO slv_addr:0x3a MSTR_STS:0x0c1343c8 OPER:0x00000090
[ 0.416884] swimcu_appl_psm_duration_get: return status 0
[ 0.416898] swimcu_pm_rtc_restore: MCUFW elapsed PSM tme: 0
[ 0.416911] swimcu_pm_rtc_restore: invalid PSM elapsed time: 0
[ 0.435688] msm_bus_fabric_init_driver
[ 0.655524] uart_tx_gpio is not available
[ 0.655545] uart_rx_gpio is not available
[ 0.655565] uart_cts_gpio is not available
[ 0.655583] uart_rfr_gpio is not available
[ 0.656253] sps: BAM device 0x07884000 is not registered yet.
[ 0.661730] AXI: get_pdata(): Error: Client name not found
[ 0.661740] AXI: msm_bus_cl_get_pdata(): client has to provide missing entry for successful registration
[ 0.661749] msm_serial_hsl_probe: Bus scaling is disabled
[ 0.868964] mdm9607-pinctrl 1000000.pinctrl: pin GPIO_4 already requested by 78b0000.uart; cannot claim for 78b0000.serial
[ 0.879472] mdm9607-pinctrl 1000000.pinctrl: pin-4 (78b0000.serial) status -22
[ 0.886654] mdm9607-pinctrl 1000000.pinctrl: could not request pin 4 (GPIO_4) from group gpio4 on device 1000000.pinctrl
[ 0.897586] msm_serial_hsl 78b0000.serial: Error applying setting, reverse things back
[ 0.956467] sps: BAM device 0x07984000 is not registered yet.
[ 1.041458] unable to find DT imem DLOAD mode node
[ 1.045506] unable to find DT imem EDLOAD mode node
[ 1.050509] unable to find DT imem dload-type node
[ 1.055014] Failed to disable secure wdog debug: -4
[ 1.086380] devfreq soc:qcom,cpubw: Couldn’t update frequency transition information.
[ 1.094453] sdhci_msm 7864900.sdhci: sdhci_msm_pm_qos_parse_irq: error -22 reading irq cpu
[ 1.104737] coresight-tmc 6025000.tmc: failed to get flush cti
[ 1.109533] coresight-tmc 6025000.tmc: failed to get reset cti
[ 1.119943] NIDnT disabled, only sd mode supported.
[ 1.180700] mdm9607-asoc-snd soc:sound-wm8944: Defering mdm_asoc_machine_probe, q6_state 0
[ 1.201745] mdm9607-asoc-snd soc:sound-wm8944: Defering mdm_asoc_machine_probe, q6_state 0
[ 1.209574] wl12xx GPIO: 131
[ 1.231553] mdm9607-asoc-snd soc:sound-wm8944: Defering mdm_asoc_machine_probe, q6_state 0
[ 1.246286] calculate_residency: residency < 0 for LPM
[ 1.250821] mdm9607-asoc-snd soc:sound-wm8944: Defering mdm_asoc_machine_probe, q6_state 0
[ 1.270150] parse_cpu_levels: idx 1 420
[ 1.272954] calculate_residency: residency < 0 for LPM
[ 1.278071] parse_cpu_levels: idx 2 500
[ 1.290351] parse_cpu_levels: idx 2 3040
[ 1.294212] mdm9607-asoc-snd soc:sound-wm8944: Defering mdm_asoc_machine_probe, q6_state 0
[ 1.311526] mdm9607-asoc-snd soc:sound-wm8944: Defering mdm_asoc_machine_probe, q6_state 0
Setting up IMA subsystem…
IMA is not supported.
The proc node does not exist
mount root fs from partition (rootfs|system)
Non-secure.
[ 1.503662] mdm9607-asoc-snd soc:sound-wm8944: Defering mdm_asoc_machine_probe, q6_state 0
UBI device number 0, total 120 LEBs (30474240 bytes, 29.1 MiB), available 6 LEBs (1523712 bytes, 1.5 MiB), LEB size 253952 bytes (248.0 KiB)
[ 1.894429] mdm9607-asoc-snd soc:sound-wm8944: Defering mdm_asoc_machine_probe, q6_state 0
rootfs roothash: 62f61058c7c823244ba95ead377ac4aec28d0f01ed23a611fe5a84b489fca678
rootfs: dev ‘/dev/ubiblock0_0’ ‘squashfs’
mount /dev/mapper/rt
[ 3.391253] device-mapper: verity: 252:0: metadata block 1 is corrupted
[ 3.397084] SQUASHFS error: squashfs_read_data failed to read block 0x0
[ 3.416484] squashfs: SQUASHFS error: unable to read squashfs_super_block
mount: mounting /dev/mapper/rt on /mnt/rootfs failed: Input/output error
rootfs: mount failed
It is not dual system logic
System error!
[ 3.450409] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[ 3.450409]
[ 3.458546] CPU: 0 PID: 1 Comm: init Not tainted 3.18.44 #60
[ 3.464176] [] (unwind_backtrace) from [] (show_stack+0x10/0x14)
[ 3.471887] [] (show_stack) from [] (panic+0x108/0x2ec)
[ 3.478831] [] (panic) from [] (do_exit+0x480/0x924)
[ 3.485511] [] (do_exit) from [] (SyS_exit_group+0x0/0x10)
[ 3.492715] [] (SyS_exit_group) from [<00000004>] (0x4)
[ 4.504741] cpr_panic_callback: apc_corner: [corner:7, fuse_corner:3] = 1212500 uV
[ 4.511390] Rebooting in 5 seconds…

Looks like, I had corrupted the mangoH rootfs.
I tried to flash the release9 image WP76xx_Release9_GENERIC_EXE.exe using the windows setup. Unfortunately, the flasing procedure gives the below output with NO success

Device error code: 0x0 - Unknown device error code.

Preexisting images information:
Current:
Firmware:
ImageId:
BuildId:
Configuration:
ImageId:
BuildId:
Final images information:
Current:
Firmware:
ImageId:
BuildId:
Configuration:
ImageId:
BuildId:

OEM PRI:
IMEI:
Total time elapsed: 125 ms.
Images downloaded:
Press Enter to continue …

Could some one help me in getting back the modem alive to default state.

Thanks,
Siva


#2

Hi Siva,
As you are using MangOH Red, please try set SW401 DIP 7 (TP1_BOOT) to ON position then power on, it should enter download mode and the downloader should work.

Refer to MangOH red user guide for more info.

Thx


#3

Hi lotam,

Yes, I am using the mango_red. I changed the DIP7 position. But no luck

From windows,
when I connect usb cf3 ==> the device only shows the dm port
when I connect usb console connector ==> the device shows the $ symbol in the console window

In both the cases, the relase software 9 with single click not worked.
Am I missing something ?

Thanks,
Siva


#4

Hi Siva,

The oneclick tool should able to run upgrade for first case when enumerate as “DM” port.
Maybe you can try with different PC or different version of oneclick?

Thx


#5

Hi lotam,

I tried with different PC. Unfortunately, in both cases the error shows as below

FDT version: 1.0.1803.1
Awaiting adapter …
Enabling selective suspend …
Firmware download failed.
Primary error code: 82 - Failed in checking modem mode.
Secondary error code: 0 - Not applicable.
Device error code: 0x0 - Unknown device error code.

Preexisting images information:
Current:
Firmware:
ImageId:
BuildId:
Configuration:
ImageId:
BuildId:
Final images information:

I have no Idea what’s the error means. Does it make any sense to you ?

Best Regards,
Siva


#6

Hi @stirulaka, for the original rootfs issue, you might want to take a look at the following thread: https://forum.legato.io/t/failed-to-flash-yocto-on-wp7607/3752/8.

I’m not sure that will be the issue, but worth a look.

Regarding recovery, the Sierra one-clicks are going to be attempting to set the carrier (GENERIC, in your case) via the network adapter interface, at the beginning of the execution. Since your device is stuck in boot mode, that’s going to fail. To solve your specific problem with the rootfs, you could use the Linux swiflash or fwupdate tool, and program the Linux Distribution component from the Release page (latest: https://source.sierrawireless.com/resources/airprime/software/wp76xx/wp76xx-firmware-latest-release-components/)

Let me know if that doesn’t help
Ryan


#7

Hi Ryan,

fwiupdate works only with the target ipaddress . In my case, like you said the device is stuck in the boot mode. So, this approach will not help me in firmware update. Correct me if I am wrong

swiflash ==> However, I didn’t find this tool in the linux machine. I will try to explore from my end.

After few searches, there is a web page https://source.sierrawireless.com/resources/legato/wpxxxxrecoveryprocedure/

which outlines the recovery procedure. I was looking for the inputs like this webpage from the supprot team. I will try this now.

Best Regards,
Siva