ZP100 not booting

It does the same thing even without speakers plugged into the device.

First - thanks to everyone for leading the way and helping others figure out how to revive these zp100's.

I have a few of these with the diag firmware and will be receiving a bus pirate tomorrow. My confidence level coming into this is mildly enthusiastic 😮 but I want to clear some things up if possible.

Firmware files - do I need to download a new fw for each individual box, or can I just rename the file to the appropriate s/n per box?

UART - any specific tips or things to watch out for when using the bus pirate? I haven't used anything like this for at least 10yrs, and even then it was a prebuilt JTAG device which was idiot proof. Don't be shy - the clearer and easier to follow the better :D

Box cleaning - I've seen some have had good luck cleaning up the boards and internals, and reconnecting the cables. Are you taking everything possible apart? Concentrating on the main board/network area? Specific things I should be looking for? Any thoughts on pulling the main board and attempting to reflow the solder with a heatgun or oven (some hardware faulty devices do well with this like video game consoles)?

Once again great thread and thanks to those pioneering the way! I'll be sure to update how things go, and try to snap a pic or screenshot along the way to help those in the future.

Looks like I have an empty NAND flash... anybody know the password for programming?

Guys thanks for all your help! Through the aide of this thread I was able to get 7.5 out of 10 of the Sonos zp100 I purchased on eBay working. I say 7.5 because I was able to get the logic board fixed on one that still have a problem with the amp 😉.

I used a Raspberry Pi to host the web server and perform all the UART commands. If someone would put together an image it could save people hours of messing with that part of the repair.

Thanks again!

Hi all.

I've been following this thread for awhile in hopes of getting this one ZP90 I have back to life. To make the long story short, I've managed to get the UART interface connected and visibly witnessed the Sonos going through the whole bootloader process until it hands off to the OS. I also took some ideas from this thread and through a direct Ethernet connection to my PC using the 169.254.xxx.xxx IP address, was able to connect to the diagnostic pages of the Sonos. For fun, at that point I enabled Wifi on my PC and to my amazement the ZP90 grabbed an IP address in my local network range and I could add the ZP90 to my existing Sonos system and update the firmware.

That's where the good news ends. For whatever reason, port one on the back of this Sonos is the only one I can connect to and it's acting very odd at best. With nothing connected it acts as if there is something there and happily blinks away. Port two seems to emulate port one (although there's no connection lights until something is actually connected to it), which doesn't surprise me, although I can't access any of the HTTP diagnostic pages through this port. If I connect the Sonos directly to my network, everything freaks out and looking at Wireshark, there seems to be a ton of traffic and a whole lot of STP errors. At the same time, my Sonos system basically crumbles and my WiFi goes to hell. Sounds to me like I have a unique firmware looking for something that doesn't exist, because as soon as I connect it back up to my PC directly using the 169.254.xxx.xxx IP and use the WiFi, the unit is completely happy. Unfortunately none of the diagnostic screens offer any indication of an out of the ordinary configuration on the eth0 ports, so I'm at a loss.

Anybody have any ideas?

Thanks

@diw4321 It sounds like there is something wrong with the ethernet controller. If I had to take a guess I'd suspect that the two ethernet ports have become bridged internally somehow, causing a STP cascade when it connects to the Sonosnet, and tries to determine the correct topology.

My wild guess would be that the unit got hit by a surge through one of the ethernet ports. If you've already got the thing open, I'd check to see if there is any visible evidence of electrical damage (charred component, melty smell, etc). If correct, you might be able to restore functionality to one of the ports by figuring out where they are shorted, and repairing the connection.

@ecsherwo: The "program" option in the bootloader is misleading at best, what it does is wipe the flash and then try to load an image from RAM, as far as I know, no-one outside of Sonos knows how to load an image to RAM, so the most you are gonna do is wipe the chip again. If you are really adventurous and know some JTAG you can hook up a highspeed JTAG board to the unit and dump/load an image dumped off a working unit.

@poshul thanks for the advice. If there's something wrong with the controller it's not obvious, there's nothing to indicate a surge (smell or visual) and nothing looks modified. It really seems like a software thing to me, like someone has programmed it to act this way.

Weird. You mention that you updated the firmware, what is the current version as displayed in ZP-IP-ADDR:1400/status/jffs/upgrade.log and what was the previous version from :1400/status/jffs/upgrade_prev.log ? Also is there anything at :1400/SLASH/ ? Also also, can you post the contents of :1400/status/enetports ?

With the way that firmware updates work I'd be suprised if this sort of diagnostic software setting survived. Can you try factory resetting the unit to see if the behaviour persists?

Thanks again for looking into this. Here's the three files. I couldn't even find :1400/SLASH/ ?

contents of /jffs/upgrade.log
Upgrade url is-c --sonosid xxx --householdid HHID_xxx http://update-firmware.sonos.com/firmware/Gold/28.1-86173-v5.3.2-tshhkh-SP2/^28.1-86173
URL is http://update-firmware.sonos.com/firmware/Gold/28.1-86173-v5.3.2-tshhkh-SP2/28.1-86173-1-1.upd?cmaj=14&cmin=5&cbld=40190&subm=16&rev=4®=2&serial=xxx&sonosid=xxx&householdid=HHID_xxx
client-server mode: listening on port 4444
waiting for connection from HH...
accepted connection from 10.5.2.127
readCommand() - read HELLO?version=28.1-86140
readCommand() - read DOWNLOAD
starting op DOWNLOAD
upgrade version 28.1-86173
compatible with Sonos Zone Player submodels 0-16 revisions 0-4294967294 (any region)
compatible with hardware feature set 1d
My hardware feature set is c
Upgrade supports all my features
Upgrade file is good
readCommand() - read FLASHWRITE
starting op FLASHWRITE
Using new partition format mode
Destination section 1 generation 6
Operating in redundant partition mode (not changing partition table)
Executing upgrade script...Checking to see if (hh.)anacapad is running...Stopping ancillary processes...
Killing udhcpc
Killing smbscand
Killing inetd
kill: 100: Usage: kill [-s sigspec | -signum | -sigspec] [pid | job]... or
kill -l [exitstatus]
Killing netstartd
ok
Merged partition table flags 00000001:
0 1:0:16
1 16:16:48
2 17:64:256
3 64:320:1389
4 16:1709:48
5 17:1757:256
6 0:0:0
Writing kernel to partition 4
Writing / to partition 5
sections M16 len check 0
Executing upgrade script to do any final work...Doing post-install steps...

contents of /jffs/upgrade_prev.log
Upgrade url is-c --sonosid xxx --householdid HHID_xxx http://update.sonos.com/firmware/Gold/v3.4-Crosby/^14.5-40190
URL is http://update.sonos.com/firmware/Gold/v3.4-Crosby/14.5-40190-1-1.upd?cmaj=14&cmin=4&cbld=33290&subm=16&rev=4®=2&serial=xxx&sonosid=xxx&householdid=HHID_xxx
client-server mode: listening on port 4444
waiting for connection from HH...
accepted connection from 192.168.1.91
readCommand() - read HELLO?version=14.5-40190
readCommand() - read DOWNLOAD
starting op DOWNLOAD
upgrade version 14.5-40190
compatible with Sonos Zone Player submodels 0-4294967294 revisions 0-4294967294 (any region)
compatible with hardware feature set 1d
My hardware feature set is c
Upgrade supports all my features
Upgrade file is good
readCommand() - read FLASHWRITE
starting op FLASHWRITE
Using new partition format mode
Destination section 0 generation 5
Operating in redundant partition mode (not changing partition table)
Executing upgrade script...Checking to see if (hh.)anacapad is running...Stopping ancillary processes...
kill: 96: Usage: kill [-s sigspec | -signum | -sigspec] [pid | job]... or
kill -l [exitstatus]
kill: 96: Usage: kill [-s sigspec | -signum | -sigspec] [pid | job]... or
kill -l [exitstatus]
ok
Merged partition table flags 00000001:
0 1:0:16
1 16:16:48
2 17:64:256
3 64:320:1389
4 16:1709:48
5 17:1757:256
6 0:0:0
Writing kernel to partition 1
Writing / to partition 2
sections M16 len check 0
Executing upgrade script to do any final work...Doing post-install steps...

Port Link Speed
0 1 100FD
1 0 0

I tried a factory reset and it changed nothing. One other interesting point to note:
Once I get the Sonos added to the system, if I unplug the Ethernet cable from the Sonos, the lights turn off, but about 1 second later they turn back on without any cable connected. At this point if I reconnect my Ethernet cable to the Sonos, I can't get to it at all without a full restart.

Thanks for your help

So has anyone had any luck reviving a no audio out zp100? I've had a couple of these I've tried with no luck. They both originally had the amps blown (literally burnt the VCC legs off the IC's). I've replaced the amps and the audio controller IC but no luck. They appear to play but get no sound. Tried to use the line in also but that didn't work either. If no one has any other ideas it appears the TI DSP IC is my next try.