Hi, I have built a SPK for WP76 using swi-fx30-cat1_2.0.0 from leaf.
It flashed fine to the EMEA FX30(WP7607-1) , but not to the NAM FX30S(WP7611-1) .
I get “Bad status (Bootloader failed), install not possible.” in response to fwupdate checkStatus
My understanding is that these should run off the same FW? I have used the generic modem image…
Any thoughts?
The same error occurs with full spk supplied in leaf and even with just the modem image
fwupdate …/modem/9999999_9907152_SWI9X07Y_02.37.03.00_00_GENERIC_002.095_000.spk
Connecting to service …
Download started …
Download successful
Installing & Reboot …
Timeout, server 192.168.2.2 not responding.
fwupdate checkStatus
Connecting to service …
Bad status (Bootloader failed), install not possible.
what is the return of the following for the two modules?
AT!ENTERCND="A710"
AT!BSINFO
Not sure if it relates to this:
For the NAM FX30S(WP7611-1) LTE-CAT-1 that does NOT accept the SPK
AT!ENTERCND=“A710”
OKAT!BSINFO
Product: FX30S(WP7611-1)
Revision: 40
Main: MDM9207 (000)
Radio: WTR2965
Power: PMD9607 (002)
Flash: H27S4G8F2EKPB4 512MB x8 (173/0/0) (2048 blocks of 64 pages/block 4096B page size)OK
and for the EMEA FX30(WP7607-1) that accepts the SPK
AT!ENTERCND=“A710”
OK
AT!BSINFO
Product: FX30(WP7607-1)
Revision: 40
Main: MDM9207 (000)
Radio: WTR2965
Power: PMD9607 (002)
Flash: MT29F4G08ABBEA3W 512MB x8 (44/0/0) (2048 blocks of 64 pages/block 4096B page size)
What are you looking for…
In your linux PC, can you also post the following of your yocto.cwe for checking?
hexdump -C -s0 -n400 yocto_wp76xx.4k.cwe
Probably you need to check yoctocwetool.sh
hmmm I don’t have a yocto*.cwe file… are you referring to the legato.cwe file?
These are the cwe files available as well as some reset.cwe files.
/home/legato/.leaf/fx30-cat1-legato_19.11.5/build/wp76xx/legato_rw.cwe
/home/legato/.leaf/fx30-cat1-legato_19.11.5/build/wp76xx/legato-squashfs.ubi.cwe
/home/legato/.leaf/fx30-cat1-legato_19.11.5/build/wp76xx/legatoimg/squashfs.ubi/temp.mbn.cwe
/home/legato/.leaf/fx30-cat1-legato_19.11.5/build/wp76xx/legato.cwe
/home/legato/.leaf/fx30-cat1-legato_19.11.5/platformAdaptor/fwupdate/apps/test/fwupdateSinglesysUnitTest/ls_ubi.cwe
/home/legato/.leaf/fx30-cat1-legato_19.11.5/platformAdaptor/fwupdate/apps/test/fwupdateSinglesysUnitTest/ls2cp.cwe
/home/legato/.leaf/fx30-cat1-legato_19.11.5/platformAdaptor/fwupdate/apps/test/fwupdateSinglesysUnitTest/cp.cwe
/home/legato/.leaf/fx30-cat1-legato_19.11.5/platformAdaptor/fwupdate/apps/test/fwupdateSinglesysUnitTest/ls.cwe
/home/legato/.leaf/fx30-cat1-legato_19.11.5/platformAdaptor/fwupdate/apps/test/fwupdateSinglesysUnitTest/keystore.cwe
/home/legato/.leaf/fx30-cat1-legato_19.11.5/platformAdaptor/fwupdate/apps/test/fwupdateSinglesysUnitTest/cp2ls.cwe
/home/legato/.leaf/fx30-cat1-legato_19.11.5/platformAdaptor/fwupdate/apps/test/fwupdateSinglesysUnitTest/cp_ubi.cwe
/home/legato/.leaf/fx30-cat1-legato_19.11.5/platformAdaptor/fwupdate/apps/test/fwupdateSinglesysUnitTest/ls2cp_ubi.cwe
/home/legato/.leaf/fx30-cat1-legato_19.11.5/platformAdaptor/fwupdate/apps/test/fwupdateSinglesysUnitTest/cp2ls_ubi.cwe
/home/legato/.leaf/fx30-cat1-legato-image_19.11.5/legato.cwe
/home/legato/.leaf/fx30-catm-legato_19.11.5/build/wp77xx/legato_rw.cwe
/home/legato/.leaf/fx30-catm-legato_19.11.5/build/wp77xx/legato-squashfs.ubi.cwe
/home/legato/.leaf/fx30-catm-legato_19.11.5/build/wp77xx/legatoimg/squashfs.ubi/temp.mbn.cwe
/home/legato/.leaf/fx30-catm-legato_19.11.5/build/wp77xx/legato.cwe
/home/legato/.leaf/fx30-catm-legato_19.11.5/platformAdaptor/fwupdate/apps/test/fwupdateSinglesysUnitTest/ls_ubi.cwe
/home/legato/.leaf/fx30-catm-legato_19.11.5/platformAdaptor/fwupdate/apps/test/fwupdateSinglesysUnitTest/ls2cp.cwe
/home/legato/.leaf/fx30-catm-legato_19.11.5/platformAdaptor/fwupdate/apps/test/fwupdateSinglesysUnitTest/cp.cwe
/home/legato/.leaf/fx30-catm-legato_19.11.5/platformAdaptor/fwupdate/apps/test/fwupdateSinglesysUnitTest/ls.cwe
/home/legato/.leaf/fx30-catm-legato_19.11.5/platformAdaptor/fwupdate/apps/test/fwupdateSinglesysUnitTest/keystore.cwe
/home/legato/.leaf/fx30-catm-legato_19.11.5/platformAdaptor/fwupdate/apps/test/fwupdateSinglesysUnitTest/cp2ls.cwe
/home/legato/.leaf/fx30-catm-legato_19.11.5/platformAdaptor/fwupdate/apps/test/fwupdateSinglesysUnitTest/cp_ubi.cwe
/home/legato/.leaf/fx30-catm-legato_19.11.5/platformAdaptor/fwupdate/apps/test/fwupdateSinglesysUnitTest/ls2cp_ubi.cwe
/home/legato/.leaf/fx30-catm-legato_19.11.5/platformAdaptor/fwupdate/apps/test/fwupdateSinglesysUnitTest/cp2ls_ubi.cwe
you said that you have built a SPK for WP76 using swi-fx30-cat1_2.0.0, what spk are you building?
just legato.cwe?
Can you list how this spk is generated?
the following file /home/legato/.leaf/wp76-toolchain_SWI9X07Y_02.37.07.00-linux64/sysroots/x86_64-pokysdk-linux/usr/bin/yoctocwetool.sh
already has the relevant line set to
COMPAT_BYTE=00000001
i am not saying the toolchain, did you build yocto.cwe?
If not, then it is not relevant.
sure…
I update the wifi.sdef file to include my app
I then run the below from within the leaf shell.
make wp76xx prod=fx30 -C $LEGATO_ROOT
I then pull this together into an SPK using
swicwe -c ${MODEM_IMAGE} ${!LINUX_IMAGES}/linux.cwe legato.${BUILDTARGET}.cwe -o FULL.${BUILDTARGET}.spk;
Where the environmental variables are set accordingly…
That said though the pre-built spk files from leaf do not download successfully either. So I don’t think this is to do with my build of legato.cwe files… see SPK that flashes to a FX30(WP7607-1) does not flash to FX30S(WP7611-1) - #2 by karlkuhn
can you post the following?
hexdump -C -s0 -n400 9999999_9907152_SWI9X07Y_02.37.03.00_00_GENERIC_002.095_000.spk
00000000 01 01 00 00 00 00 01 90 00 06 6d 90 46 55 4c 4c |..........m.FULL|
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000020 01 02 00 00 00 06 6f 20 01 ae 8c dc 46 55 4c 4c |......o ....FULL|
00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000040 01 03 00 00 01 b4 fb fc 00 00 70 c6 46 55 4c 4c |..........p.FULL|
00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000100 99 ea 2b 4e 00 00 00 03 ff ff ff ff 53 50 4b 47 |..+N........SPKG|
00000110 59 39 32 31 01 b5 6b 32 19 7c 86 4f 39 39 39 39 |Y921..k2.|.O9999|
00000120 39 39 39 5f 39 39 30 37 31 35 32 5f 53 57 49 39 |999_9907152_SWI9|
00000130 58 30 37 59 5f 30 32 2e 33 37 2e 30 33 2e 30 30 |X07Y_02.37.03.00|
00000140 5f 30 30 5f 47 45 4e 45 52 49 43 5f 30 30 32 2e |_00_GENERIC_002.|
00000150 30 39 35 5f 30 30 30 00 00 00 00 00 00 00 00 00 |095_000.........|
00000160 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000170 30 34 2f 30 38 2f 32 30 00 00 00 00 00 00 00 00 |04/08/20........|
00000180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 |................|
00000190
AND
hexdump -C -s0 -n400 ./linux/linux.cwe
00000000 01 03 00 00 00 00 01 90 00 08 a3 50 46 55 4c 4c |...........PFULL|
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000020 01 03 00 00 00 08 a4 e0 02 09 9a 20 46 55 4c 4c |........... FULL|
00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000100 bf 80 0a 98 00 00 00 03 ff ff ff ff 53 50 4b 47 |............SPKG|
00000110 59 39 32 31 02 12 3d 70 f2 66 38 af 39 39 39 39 |Y921..=p.f8.9999|
00000120 39 39 39 5f 39 39 39 39 39 39 39 5f 3f 5f 3f 5f |999_9999999_?_?_|
00000130 3f 5f 3f 5f 3f 00 00 00 00 00 00 00 00 00 00 00 |?_?_?...........|
00000140 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000170 30 37 2f 30 31 2f 32 31 00 00 00 01 00 00 00 00 |07/01/21........|
00000180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 |................|
00000190
and incase it is useful… the full SPK
hexdump -C -s0 -n400 9999999_9907152_SWI9X07Y_02.37.03.00_00_GENERIC_002.095_000-full.spk
00000000 01 01 00 00 00 00 01 90 00 06 6d 90 46 55 4c 4c |..........m.FULL|
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000020 01 02 00 00 00 06 6f 20 01 ae 8c dc 46 55 4c 4c |......o ....FULL|
00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000040 01 03 00 00 01 b4 fb fc 00 00 70 c6 46 55 4c 4c |..........p.FULL|
00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000060 01 03 00 00 01 b5 6c c2 00 08 a3 50 46 55 4c 4c |......l....PFULL|
00000070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000080 01 03 00 00 01 be 10 12 02 09 9a 20 46 55 4c 4c |........... FULL|
00000090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000000a0 01 03 00 00 03 c7 aa 32 00 64 03 20 46 55 4c 4c |.......2.d. FULL|
000000b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000100 be 63 87 4a 00 00 00 03 ff ff ff ff 53 50 4b 47 |.c.J........SPKG|
00000110 59 39 32 31 04 2b ab c2 f9 db 4f 01 39 39 39 39 |Y921.+....O.9999|
00000120 39 39 39 5f 39 39 30 37 31 35 32 5f 53 57 49 39 |999_9907152_SWI9|
00000130 58 30 37 59 5f 30 32 2e 33 37 2e 30 33 2e 30 30 |X07Y_02.37.03.00|
00000140 5f 30 30 5f 47 45 4e 45 52 49 43 5f 30 30 32 2e |_00_GENERIC_002.|
00000150 30 39 35 5f 30 30 30 00 00 00 00 00 00 00 00 00 |095_000.........|
00000160 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000170 30 32 2f 31 30 2f 32 33 00 00 00 01 00 00 00 00 |02/10/23........|
00000180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 |................|
00000190
if you just build the legato.cwe, why don’t you just download it instead of building a spk file?
because we have modems that are possibly out of date with there base FW. I thought it best practice to ensure everything is the latest and correct version… i.e. SWI occasionaly upversion there releases… requirement the modem/linux FW to be update as well as the legato image…
Can you see any issues above?
seems the linux.cwe image is not for new memory module.
From your test, even the official image cannot be downloaded to new memory module. ( you can double confirm with the image here)
https://source.sierrawireless.com/resources/airlink/software_downloads/fx30-firmware/fx30-firmware-cat1/#sthash.wDBFkHQD.dpbs
probably you need to download the yocto source of swi-fx30-cat1_2.0.0
And then change yocto/meta-swi/common/recipes-core/cwetool/cwetool/yoctocwetool.sh
Finally rebuild the yocto image.
Hmmm. So the image provided in leaf does not support the latest HW? Am I understanding that correctly?
Would that be the same problem with the FW from source I wonder? Are they the same pre-built images?
Can we get an official view on this from SWI? What are they putting on the devices? Can that be available in leaf?
Would that be the same problem with the FW from source I wonder? Are they the same pre-built images?
I guess so, but you can double confirm by downloading that image to your module with WP7611
BTW, did you contact distiributor on this?
I will give the official FW a go…
Yes I have contacted my distributor… with not response yet…
I can confirm that the offical FW also fails… same error…
then probably you need to get support from distributor
(Or you need to rebuild the yocto.cwe)