HL8548-G downgrade firmware

Hi,
I’m trying to downgrade the firmware of one HL8548-G module from the version 5.5.24 to the version 5.5.22.
I’m using the exe file provided by Sierra but when I run it, I have an error:
“Library Error: IMCDownload.cpp:508 - SPH_state_await_tra (1)”.
How can I downgrade the firmware?
Best regards,
Fabrice

No problem is found on my side.
Is this only happen to one module only?


Log file is “C:\Users\jyi\AppData\Local\Temp\HL8FW_r4251.log”
Use Port: USB1

Intel Command Line FlashTool v.1.37 1.3-r33 (Download Library v.4.140,0.0 )

psi.fls (PSI) (NAND)
slb.fls (SLB) (NAND)
AENEAS_FW.fls (Code) (NAND)
SAM_6260.fls (Code) (NAND)
SAM_6260-MSY.fls (Code) (NAND)
SAM_6260-CDS.fls (Code) (NAND)
Booting ‘C:\Users\jyi\AppData\Local\Temp\7zSEE02.tmp\temp\psi.fls’, memclass: PSI
→ Please reboot your phone device ←

Device synchronized.
Details> Injecting RPSI
Details> Injecting EBL
Details> Boot-loader is active
Details> EBL version: XMM6260_1327.100_M1S1 1327…100
Details> Boot mode is: BB
Using: Faster CRC, Writing all blocks , Skip data CRC , Skip protocol CRC
Details> Package length is 16384 - protocol: 3.32
Details> Baud rate set to 921600
Details> Get flash id.
Details> Flash ID is: 00A100C8
Details> Boot process finished

Downloading files (6)…
Downloading PSI…

Start downloading item ‘BOOT CORE PSI:psi.fls’’ from file ‘C:\Users\jyi\AppData\Local\Temp\7zSEE02.tmp\temp\psi.fls’'.
Details> Sending sec-pack.
Details> Load region 0
Details> - Erasing. (Pre-erase, Used-length)
Progress: 100%
Details> - Sending data. (USB RAW mode)
Progress: 100%
Details> Sending end-pack.
Checksum OK (0x2909)
Details> Verify OK
Process time was 141 msec.

Downloading SLB…

Start downloading item ‘BOOT CORE SLB:slb.fls’’ from file ‘C:\Users\jyi\AppData\Local\Temp\7zSEE02.tmp\temp\slb.fls’'.
Details> Sending sec-pack.
Details> Load region 0
Details> - Erasing. (Pre-erase, Used-length)
Progress: 100%
Details> - Sending data. (USB RAW mode)
Progress: 100%
Details> Sending end-pack.
Checksum OK (0x7A84)
Details> Verify OK
Process time was 672 msec.

Downloading Code…

Start downloading item ‘CODE:AENEAS_FW.fls’’ from file ‘C:\Users\jyi\AppData\Local\Temp\7zSEE02.tmp\temp\AENEAS_FW.fls’'.
Details> Sending sec-pack.
Details> Load region 0
Details> - Erasing. (Pre-erase, Used-length)
Progress: 100%
Details> - Sending data. (USB RAW mode)
Progress: 100%(7.4 Mb/s)
Details> Sending end-pack.
Checksum OK (0x4D4D)
Details> Verify OK
Process time was 812 msec.

Downloading Code…

Start downloading item ‘CODE:SAM_6260.fls’’ from file ‘C:\Users\jyi\AppData\Local\Temp\7zSEE02.tmp\temp\SAM_6260.fls’'.
Details> Sending sec-pack.
Details> Load region 0
Details> - Erasing. (Pre-erase, Used-length)
Progress: 100%
Details> - Sending data. (USB RAW mode)
Progress: 100%(11 Mb/s))
Details> Sending end-pack.
Checksum OK (0xB452)
Details> Verify OK
Process time was 8.0 sec.

Downloading Code…

Start downloading item ‘CODE:SAM_6260-MSY.fls’’ from file ‘C:\Users\jyi\AppData\Local\Temp\7zSEE02.tmp\temp\SAM_6260-MSY.fls’'.
Details> Sending sec-pack.
Details> Load region 0
Details> - Erasing. (Pre-erase, Used-length)
Progress: 100%
Details> - Sending data. (USB RAW mode)
Progress: 100%(11 Mb/s)
Details> Sending end-pack.
Checksum OK (0xBBD1)
Details> Verify OK
Process time was 625 msec.

Downloading Code…

Start downloading item ‘CODE:SAM_6260-CDS.fls’’ from file ‘C:\Users\jyi\AppData\Local\Temp\7zSEE02.tmp\temp\SAM_6260-CDS.fls’'.
Details> Sending sec-pack.
Details> Load region 0
Details> - Erasing. (Pre-erase, Used-length)
Progress: 100%
Details> - Sending data. (USB RAW mode)
Progress: 100%(11 Mb/s)
Details> Sending end-pack.
Checksum OK (0x617E)
Details> Verify OK
Process time was 625 msec.

Success!

Force Target Reset!

Total time was 12.0 sec.

This prompt will be closed in 5 seconds

Hi Jyijyi,

Thank you for your reply.
I tried on 3 modules and the result was exatly the same.
I made other tests. When I downgrade from 5.5.25 to 5.5.24, there is no problem. When I tried from 5.5.25 (or 5.5.24) to 5.5.23 or an anterior version, I have the error.

Best regards,
Fabrice

I’ve same problem any new about this?

@befaoim

So it might depend on the age of your module, the unit was initially designed with two qualified memories as you would expect for good design practice to cater for EOL’s. Unfortunately a couple of years ago the manufacturers EOL’ed both memories within a couple of months of each other. We then had to update the unit PCB to cope with newly qualified memory, this also meant we had to update the firmware with the new memory drivers which the older firmware did not have in it meaning that the new units cannot run old (pre 5.5.24.2) firmware, whereas old hardware can run all of the firmware releases (as the new firmware obviously has the drivers for the old memory as well as the new).

We could not retrospectively add the new drivers into the old firmware as it was no longer capable of passing all of the newer 3GPP tests which we would hgave had to go through as it would have been new firmware.

Anyway thats what I think might be the problem with your unit.

Regards

Matt

Dear Matt,

Thank you for the reply and for the clear explanation.

Best regards,
Fabrice

Dear Matt,

Thank you for the reply and for the clear explanation.
Is there a way to know which hardware version a module is using?

Best regards,
Fabrice

I think you can identify it from the serial number but I am not sure.

Regards

Matt

Hi Matt,

Thanks.
So you mean the serial number is coded with hardware information inside? It will be interesting to know how to decode the serial number if it is the case.

By the way, I have another question with fota firmware upgrade/downgrade.
I have a recent HL8548-G modules (2019) and it is impossible to downgrade the firmware to an old version (<5.5.24.2) through FOTA. Your previous explanation explains that. Old firmware cannot handle new hardware.
But at the meantime, I have an old module with version 5.5.22 and this one doesn’t want to upgrade to the version 5.5.25. When I used the same Fota method, the old one displays “+WDSI: 18” and always reboots alone. I’m able to upgrade it through USB.

Here is my log for the old version:

Best regards,
Fabrice