Hi, We are trying to use the fwupdate on the wp7702 (fx30 catm) and it output an error (after a fwupdate download and the automatic reboot): root@fx30:~# fwupdate checkStatus Connecting to service … Bad status (Unknown), install not possible. With the swiflash from developper studio our .cwe can be installed without problem We are using the latest code available for the fx30-catm (with legato 18.06.1_03c5394b4c271c054ae58a494f160e37) Any idea on what is the problem with fwupdate? Best regards,

We finally found where the problem was the whole time. Our .cwe generated by the Sierra build system was slightly bigger than what the fx30 use. So, the fwupdate just crash when it reboot because it can’t install the .cwe. Now we use squashfs instead of ubifs in our system so all our apps and linux can fit on the image.

Maybe the fw for the fx30 has some difference which can explain why it doesn’t work?

problem is I cannot see whether the fwupdate procedure has been performed in your log. Normally we should see such things like : Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.1.2-00084 S - IMAGE_VARIANT_STRING=LAATANAZA S - OEM_IMAGE_VERSION_STRING=jenkins S - Boot Config, 0x000002e1 B - 1216 - PBL, Start B - 3720 - bootable_media_detect_entry, Start B - 4395 - bootable_media_detect_success, Start B - 4400 - elf_loader_entry, Start B - 7854 - auth_hash_seg_entry, Start B - 31522 - auth_hash_seg_exit, Start B - 82575 - elf_segs_hash_verify_entry, Start B - 129577 - PBL, End B - 138043 - SBL1, Start B - 195810 - pm_device_init, Start B - 215940 - PM_SET_VAL:Skip D - 18452 - pm_device_init, Delta B - 217282 - boot_config_data_table_init, Start D - 0 - boot_config_data_table_init, Delta - (0 Bytes) B - 226035 - CDT version:3,Platform ID:8,Major ID:1,Minor ID:0,Subtype:129 B - 232928 - sbl1_ddr_set_params, Start B - 236771 - Pre_DDR_clock_init, Start D - 213 - Pre_DDR_clock_init, Delta D - 0 - sbl1_ddr_set_params, Delta B - 249459 - pm_driver_init, Start D - 4483 - pm_driver_init, Delta B - 255742 - cpr_init, Start D - 122 - cpr_init, Delta B - 260317 - cpr_cx_mx_apc_vol_update, Start D - 91 - cpr_cx_mx_apc_vol_update, Delta B - 275537 - clock_init, Start D - 152 - clock_init, Delta B - 275781 - boot_flash_init, Start D - 39375 - boot_flash_init, Delta B - 319884 - boot_flash_swi_ddr_init, Start D - 28944 - boot_flash_swi_ddr_init, Delta B - 535244 - hw_family:5, hw_type:22, hw_rev:4 B - 536403 - SSMEM init OK B - 557723 - opening partition 0:SWIFOTA B - 25048460 - smart recovery counter cleared B - 29778614 - ssmem_release: region 20 not exists B - 29778675 - ssmem_get: region 20 not exists B - 29791180 - ssmem_get: region 20 not exists B - 36898747 - ssmem_get: region 20 not exists B - 50711374 - AUTH_SKIPPED=USER,SLOT_WRITE=3,COMP=2,STATUS=PASS B - 50718785

The first lines on the start sequence, show an error about missing partition. Does this partition linked to the fwupdate procedure? [10] Qseecom Init Done in Appsbl [10] secure app region addr=0x87900000 size=0x280000[10] TZ App region notif returned with status:0 addr:87900000 size:2621440 [20] TZ App log region register returned with status:0 addr:82675000 size:4096 [30] Qseecom TZ Init Done in Appsbl [30] ERROR: No devinfo partition found [30] Neither ‘config’ nor ‘frp’ partition found [40] ERROR: No misc partition found [1100] SSMEM init OK [1100] ssmem_get: region 20 not exists

I don’t think so, I have same line when boot up: Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.1.2-00088 S - IMAGE_VARIANT_STRING=LAATANAZA S - OEM_IMAGE_VERSION_STRING=jenkins S - Boot Config, 0x000002e1 B - 1216 - PBL, Start B - 3720 - bootable_media_detect_entry, Start B - 4384 - bootable_media_detect_success, Start B - 4388 - elf_loader_entry, Start B - 7841 - auth_hash_seg_entry, Start B - 31488 - auth_hash_seg_exit, Start B - 82872 - elf_segs_hash_verify_entry, Start B - 129939 - PBL, End B - 118614 - SBL1, Start B - 168177 - pm_device_init, Start B - 185745 - PM_SET_VAL:Skip D - 16287 - pm_device_init, Delta B - 187087 - boot_config_data_table_init, Start D - 0 - boot_config_data_table_init, Delta - (0 Bytes) B - 195810 - CDT version:3,Platform ID:8,Major ID:1,Minor ID:0,Subtype:129 B - 202703 - sbl1_ddr_set_params, Start B - 206546 - Pre_DDR_clock_init, Start D - 213 - Pre_DDR_clock_init, Delta D - 0 - sbl1_ddr_set_params, Delta B - 219234 - pm_driver_init, Start D - 4483 - pm_driver_init, Delta B - 225517 - cpr_init, Start D - 122 - cpr_init, Delta B - 230183 - cpr_cx_mx_apc_vol_update, Start D - 91 - cpr_cx_mx_apc_vol_update, Delta B - 245372 - clock_init, Start D - 152 - clock_init, Delta B - 245586 - boot_flash_init, Start D - 39375 - boot_flash_init, Delta B - 745999 - boot_flash_swi_ddr_init, Start D - 28761 - boot_flash_swi_ddr_init, Delta B - 900146 - hw_family:5, hw_type:22, hw_rev:4 B - 900726 - cannot detect SSMEM base B - 901854 - SSMEM bad, reinit B - 906063 - SSMEM init OK B - 928542 - USB non-zero endpoint requirements: 9 in, 5 out B - 929823 - opening partition 0:SWIFOTA B - 932385 - error for readpage:0 B - 950807 - Failed to read size: /swinv/item_files/CUST_IM_SWITCH_HIDE B - 958005 - Failed to read size: /swinv/item_files/FOTA_PARTITION B - 958584 - Failed to read size: /swinv/item_files/CUST_IM_CONFIG B - 971211 - ssmem_get: region 21 not exists B - 980880 - ssmem_release: region 20 not exists B - 980941 - ssmem_get: region 20 not exists B - 987559 - Image Load, Start D - 94520 - QSEE Image Loaded, Delta - (490996 Bytes) D - 183 - boot_pm_post_tz_device_init, Delta B - 1086471 - sbl1_efs_handle_cookies, Start D - 0 - sbl1_efs_handle_cookies, Delta B - 1094462 - DEVCFG ELF verification failure B - 1098000 - Image Load, Start D - 30 - SEC Image Loaded, Delta - (0 Bytes) B - 1105686 - Image Load, Start D - 55144 - RPM Image Loaded, Delta - (150424 Bytes) B - 1161501 - Image Load, Start B - 1163849 - Auth disabled for image 9 B - 1203042 - ssmem_get: region 20 not exists D - 41602 - APPSBL Image Loaded, Delta - (376144 Bytes) B - 1206305 - QSEE Execution, Start D - 945 - QSEE Execution, Delta B - 1213046 - SBL1, End D - 1096719 - SBL1, Delta S - Throughput, 8000 KB/s (1188316 Bytes, 136023 us) S - DDR Frequency, 240 MHz Android Bootloader - UART_DM Initialized!!! [10] Qseecom Init Done in Appsbl [10] secure app region addr=0x87900000 size=0x280000[10] TZ App region notif returned with status:0 addr:87900000 size:2621440 [20] TZ App log region register returned with status:0 addr:82675000 size:4096 [30] Qseecom TZ Init Done in Appsbl [30] ERROR: No devinfo partition found [30] Neither ‘config’ nor ‘frp’ partition found [40] ERROR: No misc partition found [1100] SSMEM init OK[1100] ssmem_get: region 20 not exists[1190] DEBUG: cmdline has root= [1320] 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.215775] spmi_pmic_arb 200f000.qcom,spmi: PMIC Arb Version-2 0x20010000 [ 0.231281] msm_mpm_dev_probe(): Cannot get clk resource for XO: -517 [ 0.234443] smd_channel_probe_now: allocation table not initialized [ 0.242213] msm_thermal:msm_thermal_dev_probe Failed reading node=/soc/qcom,msm-thermal, key=qcom,online-hotplug-core. err:-517 [ 0.270337] msm_mpm_dev_probe(): Cannot get clk resource for XO: -517 [ 0.273327] msm_thermal:get_kernel_cluster_info CPU0 topology not initialized. [ 0.274254] cpu cpu0: dev_pm_opp_get_opp_count: device OPP not found (-19) [ 0.274271] msm_thermal:get_cpu_freq_plan_len Error reading CPU0 freq table len. error:-19 [ 0.274977] cpu cpu0: dev_pm_opp_get_opp_count: device OPP not found (-19) [ 0.274994] msm_thermal:get_cpu_freq_plan_len Error reading CPU0 freq table len. error:-19 [ 0.275010] cpu cpu0: dev_pm_opp_get_opp_count: device OPP not found (-19) [ 0.275023] msm_thermal:get_cpu_freq_plan_len Error reading CPU0 freq table len. error:-19 [ 0.369869] AXI: msm_bus_scale_register_client(): msm_bus_scale_register_client: Bus driver not ready. [ 0.371761] AXI: msm_bus_scale_register_client(): msm_bus_scale_register_client: Bus driver not ready.[ 0.372054] 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:0x081343c8 OPER:0x00000090 [ 0.420971] swimcu_appl_psm_duration_get: return status 0 [ 0.420998] swimcu_pm_rtc_restore: invalid PSM elapsed time: 0 [ 0.476310] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:2 tx:1) mode:FIFO slv_addr:0x20 MSTR_STS:0x091343c8 OPER:0x00000010 [ 0.476386] pca953x 4-0020: failed reading register [ 0.477331] i2c-msm-v2 78b8000.i2c: NACK: slave not responding, ensure its powered: msgs(n:2 cur:0 tx) bc(rx:3 tx:1) mode:FIFO slv_addr:0x22 MSTR_STS:0x091343c8 OPER:0x00000010 [ 0.477397] pca953x 4-0022: failed reading register

The really strange things is that I don’t have any line before: Android Bootloader - UART_DM Initialized!!!, if I understand correctly it’s the part which is supposed to update the fw. How can I check if this part is properly installed on the FX or repair it, since it seem to be broken…

This is what i mentioned before, i cannot see those message saying about the fwupdate process…

Any idea to repair/reinstall this part?

This part belongs to pbl and sbl (primary and secondary bootloader) where we all don’t have the source code. Not sure if installing a wp77 FW by one click exe in windows can fix the problem. I never try this before, not sure if any potential issue…

Can I install a one click .exe for the wp77 on my fx30 cat-m? I thought that the FX series needed a specific fw.

Never try before, I don’t know and don’t sure if there is potential issue

Fwupdate doesn't work

Legato Application Framework

jyijyi November 13, 2020, 1:50am 49

how did you change to use squashfs instead of ubifs?
Can you write down the procedure to us?

Topic		Replies	Views
Legato not installed using fwupdate Legato Application Framework	34	760	July 21, 2023
Fwupdate / swiflash doesn't seems to be working Legato Application Framework	14	1171	May 26, 2021
Trying to built yocto for fx30 cat1 Legato Linux distribution (Yocto project)	58	1690	December 30, 2022
Cannot perform SOTA updates for Fx30 using Legato-17.09.0 Legato Application Framework	11	1806	December 4, 2017
Software update confusion Legato Application Framework	36	3451	October 16, 2021

Fwupdate doesn't work

Related topics