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


#8

Hi,

I have given a try to recover back the mangOH evaluation with the developer studio in windows following this link https://source.sierrawireless.com/resources/legato/firmwarerecoveryinstructionswithdeveloperstudio/

Unfortunately, Still I have a problems with booting the board .

Below is the snapshot during the recovery procedure. The process is struck and there is no progress in the update process.


In the device manager, I can only see the DM port and not the modem interfaces.

After some time, the output is like below and recovery procedure fails

How can I bring back the mangOH evalution to any of the working state ?


#9

Hi

Which version USB driver you using?
Please try to change previous version again.

BR


#10

hi ,

Thanks for the input. I have changed to previous windows driver. But the process stops at the Awaiting adapter and after few minutes the update procedure fails with the image as shown in my previous post.

Please take a look at the below snpshot where the process struck for so long

I see the network interface as disabled as shown below.
image

Serial console status is as shown below
image

Below is the device manager details

THe background of this device was that , the init scripts were modified to add an infinite loop on wp7608. since then threre is no access to the console. hence we would like to revert the module to the default state by erasing the rootfile system.

How can I acheive to bring back the modem to the known working state.
Any help is much appreciated.


#11

Hi @stirulaka, it looks like the Service Pin (TP1) is asserted, which is holding the system in the Bootloader, awaiting programming (“SVC PIN detected” in the console log). When you use the update tools like swiflash, or Windows one-clicks, to program the device in that mode, you just need to be aware that the confirmation will fail unless you de-assert the Service Pin before the flash routine is complete. The process I use, when recovering a module from a “bad” custom image:

  1. Assert TP1
  2. Power cycle device.
  3. De-assert TP1
  4. Run recovery tool (swiflash, one-click, etc).

The Service pin is not an interrupt input - it’s only read on power-up. So once the device is in Bootloader awaiting a recovery image, you can immediately deassert the pin, so that the device will boot up normally following the recovery image (hopefully :slight_smile: ).

Hope that helps,
Ryan


#12

@stirulaka

From your screen dump of FDT2, the FW image has download to module. However it seem be rejected by your module.

In device manager, modem, DM & NMEA ports are mounted. Did you check the FW version is what you download? You could try to download one old version. It can clear your FWDL process success or not.

Also, modem, DM & NMEA ports still available, your module is operating normal mode(not download mode.

What kind of FW in your module? Is it locked for some ISP such AT&T?
If yes, your module will reject ALL other FW.

BR


#13

Hi Ryan,

Thanks for your inputs. I am glad to get the suggestions on this topic.

I tried your suggestions. Unfortunately at the step 4 . The recovery tool is not able to succeed in flashing. Below is the fdt window after few minutes . It ends up with the failure messages.

Attached the console log for your reference.
console.txt (31.4 KB)

Could you please provide your inputs how can I complete re flash the rootfs of the board.


#14

2.14.4.00 generic is the FW version I tried. Infact I tried all other options in the drop down list. I also tried to load the old Release8.spk file . But No success.


#15

I see below ouput in the console window during he update process.

  • sleep 1
    [ 109.370994] wait_for_irsc_completion: waiting for IPC Security Conf.
    [ 109.390991] wait_for_irsc_completion: waiting for IPC Security Conf.
  • true
  • echo Press [CTRL+C] to stop…
    Press [CTRL+C] to stop…
  • sleep 1
  • true
  • echo Press [CTRL+C] to stop…
    Press [CTRL+C] to stop…
  • sleep 1
  • true
  • echo Press [CTRL+C] to stop…
    Press [CTRL+C] to stop…
  • sleep 1
  • true
  • echo Press [CTRL+C] to stop…
    Press [CTRL+C] to stop…
  • sleep 1
  • true
  • echo Press [CTRL+C] to stop…
    Press [CTRL+C] to stop…
  • sleep 1
  • true
  • echo Press [CTRL+C] to stop…
    Press [CTRL+C] to stop…
  • sleep 1
    [ 114.561000] wait_for_irsc_completion: waiting for IPC Security Conf.
  • true
  • echo Press [CTRL+C] to stop…
    Press [CTRL+C] to stop…
  • sleep 1
    [ 116.010999] wait_for_irsc_completion: waiting for IPC Security Conf.
    [ 116.060982] wait_for_irsc_completion: waiting for IPC Security Conf.
    [ 116.070572] wait_for_irsc_completion: waiting for IPC Security Conf.
    [ 116.130974] wait_for_irsc_completion: waiting for IPC Security Conf.
    [ 116.300972] wait_for_irsc_completion: waiting for IPC Security Conf.
  • true
  • echo Press [CTRL+C] to stop…
    Press [CTRL+C] to stop…
  • sleep 1
  • true
  • echo Press [CTRL+C] to stop…
    Press [CTRL+C] to stop…
  • sleep 1
  • true
  • echo Press [CTRL+C] to stop…
    Press [CTRL+C] to stop…
  • sleep 1
  • true
  • echo Press [CTRL+C] to stop…
    Press [CTRL+C] to stop…
  • sleep 1
  • true
  • echo Press [CTRL+C] to stop…
    Press [CTRL+C] to stop…
  • sleep 1
    [ 120.820619] wait_for_irsc_completion: waiting for IPC Security Conf.
  • true
  • echo Press [CTRL+C] to stop…
    Press [CTRL+C] to stop…
  • sleep 1
  • true
  • echo Press [CTRL+C] to stop…
    Press [CTRL+C] to stop…
  • sleep 1
  • true
  • echo Press [CTRL+C] to stop…
    Press [CTRL+C] to stop…
  • sleep 1
  • true
  • echo Press [CTRL+C] to stop…
    Press [CTRL+C] to stop…
  • sleep 1
  • true
  • echo Press [CTRL+C] to stop…
    Press [CTRL+C] to stop…
  • sleep 1
  • true
  • echo Press [CTRL+C] to stop…
    Press [CTRL+C] to stop…
  • sleep 1
  • true
  • echo Press [CTRL+C] to stop…
    Press [CTRL+C] to stop…
  • sleep 1
  • true
  • echo Press [CTRL+C] to stop…
    Press [CTRL+C] to stop…
  • sleep 1
  • true
  • echo Press [CTRL+C] to stop…
    Press [CTRL+C] to stop…
  • sleep 1
  • true
  • echo Press [CTRL+C] to stop…
    Press [CTRL+C] to stop…
  • sleep 1
  • true
  • echo Press [CTRL+C] to stop…
    Press [CTRL+C] to stop…
  • sleep 1
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 19.842527] msm-pcm-routing soc:qcom,msm-pcm-routing: ASoC: Failed to add route AUDIO_REF_EC_UL29 MUX -> direct -> MM_UL29
    Jan 6 00:05:14 swi-mdm9x28 user.warn kernel: [ 19.860950] msm-pcm-routing soc:qcom,msm-pcm-routing: ASoC: no dapm match for SEC_MI2S_TX --> SEC_MI2S_TX --> SLIMBUS_0_RX Port Mixer
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 19.860972] msm-pcm-routing soc:qcom,msm-pcm-routing: ASoC: Failed to add route SEC_MI2S_TX -> SEC_MI2S_TX -> SLIMBUS_0_RX Port Mixer
    Jan 6 00:05:14 swi-mdm9x28 user.warn kernel: [ 19.873075] msm-pcm-routing soc:qcom,msm-pcm-routing: ASoC: no dapm match for VOICE2_STUB_DL --> Voice2 Stub --> INTERNAL_BT_SCO_RX_Voice Mixer
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 19.873095] msm-pcm-routing soc:qcom,msm-pcm-routing: ASoC: Failed to add route VOICE2_STUB_DL -> Voice2 Stub -> INTERNAL_BT_SCO_RX_Voice Mixer
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 19.886878] msm-pcm-routing soc:qcom,msm-pcm-routing: ASoC: no sink widget found for SENARY_MI2S_TX
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 19.895537] msm-pcm-routing soc:qcom,msm-pcm-routing: ASoC: Failed to add route BE_IN -> direct -> SENARY_MI2S_TX
    Jan 6 00:05:14 swi-mdm9x28 user.warn kernel: [ 20.032831] msm-pcm-routing soc:qcom,msm-pcm-routing: ASoC: Failed to create SEC_MI2S_RX Port Mixer debugfs file
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 20.068756] msm-pcm-routing soc:qcom,msm-pcm-routing: ASoC: mux SLIM_0_RX AANC MUX has no paths
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 20.093839] msm-dai-stub-dev soc:qcom,msm-dai-stub:qcom,msm-dai-stub-dtmf-tx: ASoC: no sink widget found for STUB_DTMF_TX
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 20.103892] msm-dai-stub-dev soc:qcom,msm-dai-stub:qcom,msm-dai-stub-dtmf-tx: ASoC: Failed to add route DTMF TX -> direct -> STUB_DTMF_TX
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 20.116765] msm-dai-stub-dev soc:qcom,msm-dai-stub:qcom,msm-dai-stub-host-rx-capture-tx: ASoC: no sink widget found for STUB_HOST_RX_CAPTURE_TX
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 20.129065] msm-dai-stub-dev soc:qcom,msm-dai-stub:qcom,msm-dai-stub-host-rx-capture-tx: ASoC: Failed to add route CS-VOICE HOST RX CAPTURE -> direct -> STUB_HOST_RX_CAPTURE_TX
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 20.145253] msm-dai-stub-dev soc:qcom,msm-dai-stub:qcom,msm-dai-stub-host-rx-playback-rx: ASoC: no source widget found for STUB_HOST_RX_PLAYBACK_RX
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 20.159146] msm-dai-stub-dev soc:qcom,msm-dai-stub:qcom,msm-dai-stub-host-rx-playback-rx: ASoC: Failed to add route STUB_HOST_RX_PLAYBACK_RX -> direct -> CS-VOICE HOST RX PLAYBACK
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 20.177003] msm-dai-stub-dev soc:qcom,msm-dai-stub:qcom,msm-dai-stub-host-tx-capture-tx: ASoC: no sink widget found for STUB_HOST_TX_CAPTURE_TX
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 20.189504] msm-dai-stub-dev soc:qcom,msm-dai-stub:qcom,msm-dai-stub-host-tx-capture-tx: ASoC: Failed to add route CS-VOICE HOST TX CAPTURE -> direct -> STUB_HOST_TX_CAPTURE_TX
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 20.205221] msm-dai-stub-dev soc:qcom,msm-dai-stub:qcom,msm-dai-stub-host-tx-playback-rx: ASoC: no source widget found for STUB_HOST_TX_PLAYBACK_RX
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 20.218033] msm-dai-stub-dev soc:qcom,msm-dai-stub:qcom,msm-dai-stub-host-tx-playback-rx: ASoC: Failed to add route STUB_HOST_TX_PLAYBACK_RX -> direct -> CS-VOICE HOST TX PLAYBACK
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 20.254268] mdm9607-asoc-snd soc:sound-wm8944: ASoC: no source widget found for SPKOUTP
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 20.262349] mdm9607-asoc-snd soc:sound-wm8944: ASoC: Failed to add route SPKOUTP -> direct -> Lineout_1 amp
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 20.271914] mdm9607-asoc-snd soc:sound-wm8944: ASoC: no source widget found for SPKOUTN
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 20.279625] mdm9607-asoc-snd soc:sound-wm8944: ASoC: Failed to add route SPKOUTN -> direct -> Lineout_3 amp
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 20.289259] mdm9607-asoc-snd soc:sound-wm8944: ASoC: no source widget found for Mic Bias
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 20.297805] mdm9607-asoc-snd soc:sound-wm8944: ASoC: Failed to add route Mic Bias -> direct -> IN1
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 20.306564] mdm9607-asoc-snd soc:sound-wm8944: ASoC: no source widget found for Headset Mic
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 20.314631] mdm9607-asoc-snd soc:sound-wm8944: ASoC: Failed to add route Headset Mic -> direct -> Mic Bias
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 20.324716] mdm9607-asoc-snd soc:sound-wm8944: ASoC: no source widget found for MCLK
    Jan 6 00:05:14 swi-mdm9x28 user.err kernel: [ 20.331642] mdm9607-asoc-snd soc:sound-wm8944: ASoC: Failed to add route MCLK -> direct -> Mic Bias
    Jan 6 00:05:16 swi-mdm9x28 user.err kernel: [ 22.187613] 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:0x0c1300c8 OPER:0x00000090
    Jan 6 00:05:19 swi-mdm9x28 user.info kernel: [ 25.523564] gpio_check_and_wake: wake-n_gpio26 STATE=WAKEUP
    Jan 6 00:05:19 swi-mdm9x28 user.info kernel: [ 25.533295] swimcu_calibrate_event_handle: MCU calibrate completed with remaining time 0
    Jan 6 00:05:19 swi-mdm9x28 user.info kernel: [ 25.533320] swimcu_lpo_calibrate_calc: MCU time=25000 vs MDM time=25113
    Jan 6 00:05:19 swi-mdm9x28 user.info kernel: [ 25.533339] gpio_check_and_wake: wake-n_gpio26 STATE=SLEEP
    Jan 6 00:05:20 swi-mdm9x28 user.err Legato: =ERR= | posDaemon[672]/swiQmi T=main | swiQmi.c InitService() 464 | Service type not recognized: QMI_SERVICE_SWI_LOC (15)
    Jan 6 00:05:24 swi-mdm9x28 user.info swiapp: Out of sleep…
    Jan 6 00:05:24 swi-mdm9x28 user.info swiapp:
    Jan 6 00:05:24 swi-mdm9x28 user.info swiapp: TrtyInit: retryCnt: 3
    Jan 6 00:05:25 swi-mdm9x28 user.info swiapp: qmi_client_init_instance status retry : 3
    Jan 6 00:05:25 swi-mdm9x28 user.info swiapp: qmi_client_init_instance…
    Jan 6 00:05:25 swi-mdm9x28 user.info swiapp: qmi_client_init_instance status: 0, num_retries: 4, retryCnt: 3
    Jan 6 00:05:25 swi-mdm9x28 user.info swiapp: qmi_client_register_error_cb status: 0
    Jan 6 00:05:25 swi-mdm9x28 user.info swiapp: qmi_client_notifier_init status: 0
    Jan 6 00:05:25 swi-mdm9x28 user.info swiapp: qmi_client_notifier_init status: -19
    Jan 6 00:05:25 swi-mdm9x28 user.info swiapp: result : 0 ,Init step :1 ,qmiErrorCode: 0
    Jan 6 00:05:25 swi-mdm9x28 user.info swiapp: Back to main.
    Jan 6 00:05:25 swi-mdm9x28 user.info swiapp: tryinit complete with connectresult: 0
    Jan 6 00:05:25 swi-mdm9x28 user.info swiapp:
    Jan 6 00:05:25 swi-mdm9x28 user.info swiapp: TrtyInit: retryCnt: 1
    Jan 6 00:05:25 swi-mdm9x28 user.info swiapp: type - 2 do nothing
    Jan 6 00:05:25 swi-mdm9x28 user.info swiapp: result : 0 ,Init step :2 ,qmiErrorCode: 0
    Jan 6 00:05:25 swi-mdm9x28 user.info swiapp: Back to main.
    Jan 6 00:05:25 swi-mdm9x28 user.info swiapp: tryinit complete with connectresult: 0
    Jan 6 00:05:25 swi-mdm9x28 user.info swiapp: Trying to register 5 commands:
    Jan 6 00:05:25 swi-mdm9x28 user.info swiapp: cmd0: +CFUN
    Jan 6 00:05:25 swi-mdm9x28 user.info swiapp: sending QMI_AT_REG_AT_CMD_FWD_REQ_V01 message
    Jan 6 00:05:43 swi-mdm9x28 user.err kernel: [ 49.371017] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:05:43 swi-mdm9x28 user.err kernel: [ 49.390965] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:05:48 swi-mdm9x28 user.err kernel: [ 54.560982] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:05:50 swi-mdm9x28 user.err kernel: [ 56.011012] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:05:50 swi-mdm9x28 user.err kernel: [ 56.061008] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:05:50 swi-mdm9x28 user.err kernel: [ 56.066355] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:05:50 swi-mdm9x28 user.err kernel: [ 56.130986] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:05:50 swi-mdm9x28 user.err kernel: [ 56.300997] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:05:55 swi-mdm9x28 user.err kernel: [ 60.820992] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:05:55 swi-mdm9x28 user.info kernel: [ 61.281011] sierra_startup_monitor
    Jan 6 00:06:13 swi-mdm9x28 user.err kernel: [ 79.370951] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:06:13 swi-mdm9x28 user.err kernel: [ 79.391005] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:06:18 swi-mdm9x28 user.err kernel: [ 84.560982] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:06:20 swi-mdm9x28 user.err kernel: [ 86.011003] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:06:20 swi-mdm9x28 user.err kernel: [ 86.060997] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:06:20 swi-mdm9x28 user.err kernel: [ 86.070555] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:06:20 swi-mdm9x28 user.err kernel: [ 86.130975] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:06:20 swi-mdm9x28 user.err kernel: [ 86.301021] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:06:25 swi-mdm9x28 user.err kernel: [ 90.820991] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:06:43 swi-mdm9x28 user.err kernel: [ 109.370994] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:06:43 swi-mdm9x28 user.err kernel: [ 109.390991] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:06:48 swi-mdm9x28 user.err kernel: [ 114.561000] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:06:50 swi-mdm9x28 user.err kernel: [ 116.010999] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:06:50 swi-mdm9x28 user.err kernel: [ 116.060982] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:06:50 swi-mdm9x28 user.err kernel: [ 116.070572] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:06:50 swi-mdm9x28 user.err kernel: [ 116.130974] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:06:50 swi-mdm9x28 user.err kernel: [ 116.300972] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:06:55 swi-mdm9x28 user.err kernel: [ 120.820619] wait_for_irsc_completion: waiting for IPC Security Conf.
    Jan 6 00:07:05 swi-mdm9x28 user.crit Legato: CRT | watchdog[656]/watchdogDaemon T=main | watchdog.c WatchdogHandleExpiry() 488 | Mandatory watchdog double fault on process [audioService][audioDaemon]
    Jan 6 00:07:05 swi-mdm9x28 user.emerg Legato: EMR | watchdog[656]/le_pa_wdog T=main | pa_wdog.c pa_wdog_Shutdown() 72 | Watchdog expired. Restart device.
    Jan 6 00:07:05 swi-mdm9x28 user.emerg Legato: EMR | supervisor[641]/supervisor T=main | frameworkDaemons.c fwDaemons_SigChildHandler() 448 | Framework daemon ‘watchdog’ has exited with code 1.
    Jan 6 00:07:05 swi-mdm9x28 user.emerg Legato: EMR | powerManagerService[673]/framework T=main | LE_FILENAME ClientSocketHangUp() 852 | Session closed by server (powerManagerService.watchdogChain.le_wdog:572ba176b790548eed89b7ba6f9f4b14).
    Jan 6 00:07:05 swi-mdm9x28 user.emerg Legato: EMR | rSimDaemon[670]/framework T=main | LE_FILENAME ClientSocketHangUp() 852 | Session closed by server (rSimDaemon.watchdogChain.le_wdog:572ba176b790548eed89b7ba6f9f4b14).
    Jan 6 00:07:05 swi-mdm9x28 user.emerg Legato: EMR | atClientDaemon[660]/framework T=main | LE_FILENAME ClientSocketHangUp() 852 | Session closed by server (atClientDaemon.watchdogChain.le_wdog:572ba176b790548eed89b7ba6f9f4b14).
    Jan 6 00:07:05 swi-mdm9x28 user.emerg Legato: EMR | portDaemon[671]/framework T=main | LE_FILENAME ClientSocketHangUp() 852 | Session closed by server (portDaemon.watchdogChain.le_wdog:572ba176b790548eed89b7ba6f9f4b14).
    Jan 6 00:07:05 swi-mdm9x28 user.emerg Legato: EMR | gpioService[668]/framework T=main | LE_FILENAME ClientSocketHangUp() 852 | Session closed by server (gpioService.watchdogChain.le_wdog:572ba176b790548eed89b7ba6f9f4b14).
    Jan 6 00:07:05 swi-mdm9x28 user.emerg Legato: EMR | fwupdateDaemon[667]/framework T=main | LE_FILENAME ClientSocketHangUp() 852 | Session closed by server (fwupdateDaemon.watchdogChain.le_wdog:572ba176b790548eed89b7ba6f9f4b14).
    Jan 6 00:07:05 swi-mdm9x28 user.emerg Legato: EMR | atServerDaemon[661]/framework T=main | LE_FILENAME ClientSocketHangUp() 852 | Session closed by server (atServerDaemon.watchdogChain.le_wdog:572ba176b790548eed89b7ba6f9f4b14).
    Jan 6 00:07:06 swi-mdm9x28 user.emerg Legato: EMR | supervisor[641]/supervisor T=main | supervisor.c framework_Reboot() 690 | Supervisor going down to trigger reboot.
    Jan 6 00:07:06 swi-mdm9x28 user.emerg Legato: EMR | _appStopClient[1183]/appStopClient_exe T=main | appStopClient.c _appStopClient_exe_COMPONENT_INIT() 53 | Error sending app name to the AppStop server socket. Connection refused
    Jan 6 00:07:06 swi-mdm9x28 user.emerg Legato: EMR | _appStopClient[1179]/appStopClient_exe T=main | appStopClient.c _appStopClient_exe_COMPONENT_INIT() 53 | Error sending app name to the AppStop server socket. Connection refused
    Jan 6 00:07:06 swi-mdm9x28 user.emerg Legato: EMR | _appStopClient[1184]/appStopClient_exe T=main | appStopClient.c _appStopClient_exe_COMPONENT_INIT() 53 | Error sending app name to the AppStop server socket. Connection refused
    Jan 6 00:07:06 swi-mdm9x28 user.emerg Legato: EMR | _appStopClient[1177]/appStopClient_exe T=main | appStopClient.c _appStopClient_exe_COMPONENT_INIT() 53 | Error sending app name to the AppStop server socket. Connection refused
    Jan 6 00:07:06 swi-mdm9x28 user.emerg Legato: EMR | _appStopClient[1174]/appStopClient_exe T=main | appStopClient.c _appStopClient_exe_COMPONENT_INIT() 53 | Error sending app name to the AppStop server socket. Connection refused

#16

2.14.4.00 generic is the FW version I tried. Infact I tried all other options in the drop down list. I also tried to load the Release9.spk file . But No success.

Any help in reprogramming the board with new rootfs ?


#17

I think the modem programming is actually working, but it’s just not resolving your underlying issue. The module is still not getting to the point where it can confirm the download, though based on the console log it appears to have succeeded.

The most common problem I see is that something added to the overlayfs is causing your problem. Can you run the swiflash recovery process to erase the data from the overlay, which will restore the original rootfs?
“swiflash -m wp76xx -r”

Unfortunately that’s not described in https://source.sierrawireless.com/resources/legato/wpxxxxrecoveryprocedure/. I will open an internal discussion on getting that updated.

Ryan


#18

Hi Ryan,

Thanks for the input.
unfortunately, I am not able to find the swiflash utility on my linux box. where can I download this tool on linux ?
Is this can be done from windows also ?
Looking for your response.

Thanks,
Siva


#19

I have downloaded swiflash from

https://source.sierrawireless.com/resources/airprime/software/swiflash/

With the tool, I am successfully able to recover my board.