cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1679
Views
0
Helpful
3
Replies

SPA112: cannot upgrade firmware to 1.4.1 (firmware upgrade failed)

Hi,

I recently upgraded the firmware of a dozen of SPA112 to 1.4.1. All worked fine except one. This one, even after a power cycle, always reports "upgrade failed". It shows the following system information:

Model: SPA112, 2 FXS
Hardware Version: 1.0.0
Boot Version: 1.3.1 (Dec 11 2013 - 11:38:47)
Firmware Version: 1.3.5 (004) Jul 31 2014
Recovery Firmware: 1.0.1 (005)
Serial Number: CBT154009VM

I found that this is my only device with boot version larger than 1.0.x. This one only upgrades to firmware version 1.3.5.

Is there an incompatibility with the 1.4.1 firmware and the boot version 1.3.1?

Thanks for your support.

Christoph

1 Accepted Solution

Accepted Solutions

Dan Lukes
VIP Alumni
VIP Alumni

No issue of such kind known (as far as I know). Make sure the upgrade file is complete and intact (older firmware may not detect some kind of modifications):

Payton_1.4.1_002_102615_1042_pfmwr.bin
SHA256 = 595bb908e9223daafc68e0615c793bf65d3ae393b0ae77fdfe0b9d67b88f5911
SHA1 : c3a3ebb7029e5c41333ee1d6a09ae9a2e732d005
MD5 : 74dd18427f94bc76ae2e08bb0dbddcda
SIZE : 9961864

If unmodified then turn on syslog & debug (highest level) and capture it during upgrade. It may disclose true cause of upgrade fail.

View solution in original post

3 Replies 3

Dan Lukes
VIP Alumni
VIP Alumni

No issue of such kind known (as far as I know). Make sure the upgrade file is complete and intact (older firmware may not detect some kind of modifications):

Payton_1.4.1_002_102615_1042_pfmwr.bin
SHA256 = 595bb908e9223daafc68e0615c793bf65d3ae393b0ae77fdfe0b9d67b88f5911
SHA1 : c3a3ebb7029e5c41333ee1d6a09ae9a2e732d005
MD5 : 74dd18427f94bc76ae2e08bb0dbddcda
SIZE : 9961864

If unmodified then turn on syslog & debug (highest level) and capture it during upgrade. It may disclose true cause of upgrade fail.

Dan, thanks for the hint. I did not believe that this could ever happen, but the file was indeed broken (correct size, but incorrect hash). With the proper file, it works as expected.

Glad to hear you solved it.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: