Skip to main content

I get error #4 when trying to update my Connect.  I have tried it multiple times, always with the same problem.

Diagnostic is 933993755.  Please advise.

Thanks

 

I get error #4 when trying to update my Connect.  I have tried it multiple times, always with the same problem.

Diagnostic is 933993755.  Please advise.

Thanks

 

Perhaps cable the Connect direct to your router with an Ethernet cable and then try the update again.


I should have mentioned that...it is hard wired to my router.

 


I should have mentioned that...it is hard wired to my router.

 

I would try the other network port on the device and/or another cable, as the error. by all accounts. is a communication error - or perhaps try the update over WiFi if you have your WiFi credentials installed in your Sonos Household.


I tried the other ethernet port and wifi.  Same problem.

I suspect that the flash chip is not writable for some reason.  Hopefully the Sonos team can see something in the diagnostic log.


I took the plunge, and hooked up a serial port monitor.  The flash has a bunch of bad blocks…

U-Boot 1.1.1(1-16-5-zp90-0.8), Build: zp90-0.8

MPC8272 Reset Status: External Soft, External Hard

MPC8272 Clock Configuration
 - Bus-to-Core Mult 3x, VCO Div 4, 60x Bus Freq  16-50 , Core Freq  50-150
 - dfbrg 1, corecnf 0x10, busdf 3, cpmdf 1, plldf 0, pllmf 3
 - vco_out  400000000, scc_clk  100000000, brg_clk   25000000
 - cpu_clk  300000000, cpm_clk  200000000, bus_clk  100000000
 - pci_clk   33333333

CPU:   MPC8272 (HiP7 Rev 14, Mask unknown immr=0x0d10,k=0x00e1]) at 300 MHz
Board: Sonos ZP90
I2C:   ready
Cold boot, starting the codec
DRAM:  32 MB
IMMR: f0000000
DRAM tests running ... done
Using default environment

In:    serial
Out:   serial
Err:   serial
Net:   FCC2 ETHERNET, FCC1 ETHERNET
Hit any key to stop autoboot:  0
NAND ID is 20:75
32M NAND flash (ST NAND256W3A)
Block 1372 is bad
Block 1373 is bad
.

.

Block 1476 is bad
Block 1477 is bad
Block 1504 is bad
Block 1505 is bad
.

.

Block 1976 is bad
Block 1977 is bad
Block 2009 is bad
S0 provisionally good, KP=1, G39
page appears to be blank, page 4294967295
page appears to be blank, page 4294967264
S1 is no good
Boot from partition 1
## Starting application at 0x00400000 ..▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒..............................

 

The skipped “.” lines include every intermediate block.  So there are 581 bad blocks out of 2048… no wonder it’s giving problems.

I recently acquired a flash programmer.  Maybe I’ll try to copy the existing flash contents to a new chip.


Hi @timc995 

It is indeed a bad block problem. I would encourage you to get in touch with our technical support team for replacement options, but it sounds like you have opened the unit in which case we cannot receive it.


Yes it’s opened up.  I wouldn’t expect any assistance from Sonos on a 7 year old device.

If this thread doesn’t get closed, I will report back on any results with respect to replacing the flash chip.

 


Time is the most frequent reason for closing a thread, not content, at least over the last several years. Sonos is pretty forgiving, as long as you stay within the community rules about posting. 

There are just a few threads here about opening up Sonos devices. I think there’s likely another, more welcoming place out there to get advice. For what I suspect are a multitude of reasons, Sonos doesn’t officially support the opening of their hardware. 


Hi @timc995 

Yes it’s opened up.  I wouldn’t expect any assistance from Sonos on a 7 year old device.

We would have offered a 30% discount on a replacement, though your own solution will certainly be cheaper - if it works.