# SPK that flashes to a FX30(WP7607-1) does not flash to FX30S(WP7611-1)

**URL:** <https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139>\
**Category:** FX30\
**Created:** [March 1, 2023, 1:59pm UTC](https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139 "2023-03-01T13:59:13Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![karlkuhn](https://avatars.discourse-cdn.com/v4/letter/k/977dab/32.png) [@karlkuhn](https://forum.sierrawireless.com/u/karlkuhn)\
**Post date:** [March 1, 2023, 1:59pm UTC](https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139/1 "2023-03-01T13:59:13Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![karlkuhn](https://avatars.discourse-cdn.com/v4/letter/k/977dab/32.png) [@karlkuhn](https://forum.sierrawireless.com/u/karlkuhn)\
**Post date:** [March 1, 2023, 2:07pm UTC](https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139/2 "2023-03-01T14:07:45Z")

</div>

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.**

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [March 1, 2023, 2:55pm UTC](https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139/3 "2023-03-01T14:55:20Z")

</div>

what is the return of the following for the two modules?

```auto
AT!ENTERCND="A710"
AT!BSINFO

```

Not sure if it relates to this:

> **[Flashing custom image to new WP7607-1 Modules don't work](https://forum.legato.io/t/flashing-custom-image-to-new-wp7607-1-modules-dont-work/6086/18)**
>
> try the following: open yocto/meta-swi/common/recipes-core/cwetool/cwetool/yoctocwetool.sh in line 59 , change it to COMPAT\_BYTE=00000101 rebuild the yocto image by “make clean” and “make” command download the yocto.cwe image to module

---

<div class="post-metadata">

**Author:** ![karlkuhn](https://avatars.discourse-cdn.com/v4/letter/k/977dab/32.png) [@karlkuhn](https://forum.sierrawireless.com/u/karlkuhn)\
**Post date:** [March 1, 2023, 3:16pm UTC](https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139/4 "2023-03-01T15:16:44Z")

</div>

For the NAM FX30S(WP7611-1) LTE-CAT-1 that does NOT accept the SPK

> AT!ENTERCND=“A710”  
> OK
> 
> AT!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…

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [March 1, 2023, 3:19pm UTC](https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139/5 "2023-03-01T15:19:44Z")

</div>

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

> **[Flashing custom image to new WP7607-1 Modules don't work](https://forum.legato.io/t/flashing-custom-image-to-new-wp7607-1-modules-dont-work/6086/18)**
>
> try the following: open yocto/meta-swi/common/recipes-core/cwetool/cwetool/yoctocwetool.sh in line 59 , change it to COMPAT\_BYTE=00000101 rebuild the yocto image by “make clean” and “make” command download the yocto.cwe image to module

---

<div class="post-metadata">

**Author:** ![karlkuhn](https://avatars.discourse-cdn.com/v4/letter/k/977dab/32.png) [@karlkuhn](https://forum.sierrawireless.com/u/karlkuhn)\
**Post date:** [March 1, 2023, 3:31pm UTC](https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139/6 "2023-03-01T15:31:54Z")

</div>

> [@jyijyi](#):
>
> hexdump -C -s0 -n400 yocto\_wp76xx.4k.cwe

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

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [March 1, 2023, 3:34pm UTC](https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139/7 "2023-03-01T15:34:02Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![karlkuhn](https://avatars.discourse-cdn.com/v4/letter/k/977dab/32.png) [@karlkuhn](https://forum.sierrawireless.com/u/karlkuhn)\
**Post date:** [March 1, 2023, 3:34pm UTC](https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139/8 "2023-03-01T15:34:10Z")

</div>

> [@jyijyi](#):
>
> Probably you need to check yoctocwetool.sh

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

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [March 1, 2023, 3:35pm UTC](https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139/9 "2023-03-01T15:35:18Z")

</div>

i am not saying the toolchain, did you build yocto.cwe?  
If not, then it is not relevant.

---

<div class="post-metadata">

**Author:** ![karlkuhn](https://avatars.discourse-cdn.com/v4/letter/k/977dab/32.png) [@karlkuhn](https://forum.sierrawireless.com/u/karlkuhn)\
**Post date:** [March 1, 2023, 3:37pm UTC](https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139/10 "2023-03-01T15:37:40Z")

</div>

> [@jyijyi](#):
>
> Can you list how this spk is generated?

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](https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139/2)

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [March 1, 2023, 3:42pm UTC](https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139/11 "2023-03-01T15:42:06Z")

</div>

can you post the following?

1. hexdump -C -s0 -n400 9999999\_9907152\_SWI9X07Y\_02.37.03.00\_00\_GENERIC\_002.095\_000.spk
2. hexdump -C -s0 -n400 ${MODEM\_IMAGE} ${!LINUX\_IMAGES}/linux.cwe

---

<div class="post-metadata">

**Author:** ![karlkuhn](https://avatars.discourse-cdn.com/v4/letter/k/977dab/32.png) [@karlkuhn](https://forum.sierrawireless.com/u/karlkuhn)\
**Post date:** [March 1, 2023, 3:48pm UTC](https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139/12 "2023-03-01T15:48:19Z")

</div>

hexdump -C -s0 -n400 9999999\_9907152\_SWI9X07Y\_02.37.03.00\_00\_GENERIC\_002.095\_000.spk

```auto
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

```auto
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

```auto
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

```

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [March 1, 2023, 3:52pm UTC](https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139/13 "2023-03-01T15:52:04Z")

</div>

if you just build the legato.cwe, why don’t you just download it instead of building a spk file?

---

<div class="post-metadata">

**Author:** ![karlkuhn](https://avatars.discourse-cdn.com/v4/letter/k/977dab/32.png) [@karlkuhn](https://forum.sierrawireless.com/u/karlkuhn)\
**Post date:** [March 1, 2023, 3:55pm UTC](https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139/14 "2023-03-01T15:55:51Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [March 1, 2023, 4:04pm UTC](https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139/15 "2023-03-01T16:04:26Z")

</div>

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](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

> **[Trying to built yocto for fx30 cat1](https://forum.legato.io/t/trying-to-built-yocto-for-fx30-cat1/6208/2)**
>
> I did this for FX30-cat-M in ubuntu16, maybe you can follow: $\> leaf setup fx30-catm -p swi-fx30-catm\_3.0.0 $\> leaf getsrc legato $\> leaf getsrc swi-linux $\> cd swi-linux $\> make MACH=mdm9x28 PROD=fx30

And then change yocto/meta-swi/common/recipes-core/cwetool/cwetool/yoctocwetool.sh

> **[Flashing custom image to new WP7607-1 Modules don't work](https://forum.legato.io/t/flashing-custom-image-to-new-wp7607-1-modules-dont-work/6086/18)**
>
> try the following: open yocto/meta-swi/common/recipes-core/cwetool/cwetool/yoctocwetool.sh in line 59 , change it to COMPAT\_BYTE=00000101 rebuild the yocto image by “make clean” and “make” command download the yocto.cwe image to module

Finally rebuild the yocto image.

---

<div class="post-metadata">

**Author:** ![karlkuhn](https://avatars.discourse-cdn.com/v4/letter/k/977dab/32.png) [@karlkuhn](https://forum.sierrawireless.com/u/karlkuhn)\
**Post date:** [March 1, 2023, 4:09pm UTC](https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139/16 "2023-03-01T16:09:49Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [March 1, 2023, 4:11pm UTC](https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139/17 "2023-03-01T16:11:01Z")

</div>

> > > 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?

---

<div class="post-metadata">

**Author:** ![karlkuhn](https://avatars.discourse-cdn.com/v4/letter/k/977dab/32.png) [@karlkuhn](https://forum.sierrawireless.com/u/karlkuhn)\
**Post date:** [March 1, 2023, 4:14pm UTC](https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139/18 "2023-03-01T16:14:22Z")

</div>

I will give the official FW a go…

Yes I have contacted my distributor… with not response yet…

---

<div class="post-metadata">

**Author:** ![karlkuhn](https://avatars.discourse-cdn.com/v4/letter/k/977dab/32.png) [@karlkuhn](https://forum.sierrawireless.com/u/karlkuhn)\
**Post date:** [March 1, 2023, 4:20pm UTC](https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139/19 "2023-03-01T16:20:20Z")

</div>

> [@jyijyi](#):
>
> ( you can double confirm with the image here)  
> [https://source.sierrawireless.com/resources/airlink/software\_downloads/fx30-firmware/fx30-firmware-cat1/#sthash.wDBFkHQD.dpbs](https://source.sierrawireless.com/resources/airlink/software_downloads/fx30-firmware/fx30-firmware-cat1/#sthash.wDBFkHQD.dpbs)

I can confirm that the offical FW also fails… same error…

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [March 1, 2023, 4:27pm UTC](https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139/20 "2023-03-01T16:27:36Z")

</div>

then probably you need to get support from distributor  
(Or you need to rebuild the yocto.cwe)

[Next page](https://forum.sierrawireless.com/t/spk-that-flashes-to-a-fx30-wp7607-1-does-not-flash-to-fx30s-wp7611-1/29139.md?page=2)
