ZP100 not booting

Show first post
This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

197 replies

P
Userlevel 2
Badge
Yeah, there are two headers close to each other. The UART is the 4 pin one. The frequency is 38400 (all of the other serial settings are their defaults, which I do not recall off the top of my head). For what it's worth the bootloader is super minimal. You can't load new firmware off of it (as far as I can tell), but it should give you information if the NAND flash has bad blocks, or if the RAM is bad. As for where the firmware is, if you have another zone player check out http://ZP'S_IP_ADDRESS:1400/status/jffs/upgrade.log for information on its last update
S
Userlevel 2
@LogicIsHard would you mind sharing where to find the firmware?

@poshul Where can I find the UART header on the board? Is it the header near the front of the device?
P
Userlevel 2
Badge
There is a 4 pin UART connector on the logic board of the ZP100 (1:vcc 2:rx 3:tx 4:gnd). If you have some way to connect to it (I used a buspirate), you can see any info that the bootloader is printing out (and test the flash memory and RAM). My guess, given your description of the failure mode, is that the OS crashes sometime after boot. The serial console isn't gonna be real useful if that is the case, it stops printing stuff out after booting. There is a JTAG port on the logic board, but connecting to it is a major pain, and unless you have a lot of time (and money) to burn I wouldn't recommend messing with it.

Keep in mind that Sonos can replace the unit (for a cost) until you open it. Once it's opened they won't replace it. It might be more worth your while to check with them first, before taking the leap.

If you are going to open up the device you can go ahead and check for any obvious issues (blown caps, dry solder joints, etc.). Bgelb0 reported similar issues here.
K
Userlevel 2
Any more progress here? I bought an old ZP100 at a garage sale recently with the hope of adding it to my existing system. It blinks about 5-10 times at startup the the LED goes solid white but can't seem to connect to my existing system. I've tried a factory reset but not luck. It doesn't stay in linking mode very long (only 6-7 flashes of green white). Assume it's some kind of firmware issue. I don't have a lot of money in the unit so I'm not too worries about competely messing it us. Any thoughts? I'd love to play with it a bit to see if I can get it running.
L
Userlevel 2
I'm very interested in this fix... will test and let you know what I find out. Also, would someone please give me a link to the firmware, also on where to find the jtag.

EDIT: OK. I found where to get the firmware... but I still haven't found the serial port. Do you just use the same procedure as if flashing DD-WRT with ethernet port directly connected to computer?
A
Userlevel 2
Hi Zacharias,
jsut read in your port that you connected to the serial port of the zp100.
Can you share any information how you did find the serial port and how you conencted to it?

Working on something but wasn`t able to msg you since i have < 5 posts.

Thanks,
Rolf


Any help ?
R
Userlevel 2
Hi Zacharias,
jsut read in your port that you connected to the serial port of the zp100.
Can you share any information how you did find the serial port and how you conencted to it?

Working on something but wasn`t able to msg you since i have < 5 posts.

Thanks,
Rolf
K
Userlevel 2
After moving to my new house I wanted to reconnect my ZP100 today again. But what a bad surpise: I am facing now same issues as posted here. For me it looks like that backup battery gets weak in this device (if any) and firmware is gone! If a battery is causing this problem a lot more ZP100 users will have the same issue soon (after unplugging power for a while).

Mentioned trick to ping the device also did not helped (it is not longer recognized by my router).

If anybody has an idea to reanimate this device then please let me know.

Katte
R
Userlevel 2
Hi, I have the same issue now with my ZP100. Flashing white light, any help would be fantastic
S
If the technique works to bring the device back alive, I would be rather curious to see what/where/how you got it back.....
H
Badge
Check your PM.
Z
Userlevel 2
Here's the update:

Found the serial port, and can interact with the bootloader via terminal:

Still need some firmware!

Rincon boot loader version 0.16-11080(ZP) (32M SDRAM). Press 'h' for help.
SDRAM test...
Memory test iteration 0
SDRAM test complete
Attempting to autoboot from NAND device
NAND ID is EC:75
32M NAND flash (Samsung K9F5608U0C) detected
NAND flash block 321 is bad
NAND flash block 323 is bad
NAND flash block 325 is bad
NAND flash block 327 is bad
NAND flash block 331 is bad
NAND flash block 333 is bad
NAND flash block 335 is bad
NAND flash block 337 is bad
NAND flash block 339 is bad
NAND flash block 341 is bad
NAND flash block 343 is bad
NAND flash block 345 is bad
NAND flash block 347 is bad
NAND flash block 349 is bad
NAND flash block 353 is bad
NAND flash block 355 is bad
NAND flash block 359 is bad
NAND flash block 361 is bad
NAND flash block 363 is bad
NAND flash block 365 is bad
NAND flash block 369 is bad
NAND flash block 371 is bad
NAND flash block 373 is bad
NAND flash block 375 is bad
NAND flash block 377 is bad
NAND flash block 379 is bad
NAND flash block 381 is bad
NAND flash block 385 is bad
NAND flash block 387 is bad
NAND flash block 389 is bad
NAND flash block 391 is bad
NAND flash block 393 is bad
NAND flash block 395 is bad
NAND flash block 399 is bad
NAND flash block 405 is bad
NAND flash block 407 is bad
No valid partition table, defaulting to old boot mechanism
nand_load: page appears to be blank, page 512
Sorry, autoboot failed
>
Rincon boot loader version 0.16-11080(ZP) (32M SDRAM). Press 'h' for help.
SDRAM test...
Memory test iteration 0
SDRAM test complete
Attempting to autoboot from NAND device
NAND ID is EC:75
32M NAND flash (Samsung K9F5608U0C) detected
NAND flash block 321 is bad
NAND flash block 323 is bad
NAND flash block 325 is bad
NAND flash block 327 is bad
NAND flash block 331 is bad
NAND flash block 333 is bad
NAND flash block 335 is bad
NAND flash block 337 is bad
NAND flash block 339 is bad
NAND flash block 341 is bad
NAND flash block 343 is bad
NAND flash block 345 is bad
NAND flash block 347 is bad
NAND flash block 349 is bad
NAND flash block 353 is bad
NAND flash block 355 is bad
NAND flash block 359 is bad
NAND flash block 361 is bad
NAND flash block 363 is bad
NAND flash block 365 is bad
NAND flash block 369 is bad
NAND flash block 371 is bad
NAND flash block 373 is bad
NAND flash block 375 is bad
NAND flash block 377 is bad
NAND flash block 379 is bad
NAND flash block 381 is bad
NAND flash block 385 is bad
NAND flash block 387 is bad
NAND flash block 389 is bad
NAND flash block 391 is bad
NAND flash block 393 is bad
NAND flash block 395 is bad
NAND flash block 399 is bad
NAND flash block 405 is bad
NAND flash block 407 is bad
No valid partition table, defaulting to old boot mechanism
nand_load: page appears to be blank, page 512
Sorry, autoboot failed
> h
Rincon boot loader version 0.16-11080(ZP) (32M SDRAM). Press 'h' for help.
h - help
m - SDRAM test
i - print NAND device ID
n - NAND device scan
x - NAND device destructive test
y - NAND device dump first page
p - Program NAND device
b - Boot the Linux kernel from NAND device
d - Boot diagnostics from NAND device
Z
Userlevel 2
Upon further inspection, whilst the warranty seal etc was in place this unit has been repaired before, I am assuming by Sonos. It has had several components replaced near the ethernet ports and in the power supply section.

It tests with a healthy 1.5v from the regulator for the Renasas cpu supply voltage.

Is there some kind of serial monitor pinout or jtag diagram available for this board? I really need some way of finding out what has gone wrong.

Buzz you mentioned on the forum having a sometimes functional ZP100, can you post the firmware download link from your update.log file please?
Z
Userlevel 2
Will have a poke around to see what I can find re. flash chip etc.
I see on these forums someone had a ZP100 that would become unresponsive after a certain period of time. Also somebody else who had flash problems that would disappear and reappear with firmware updates.

"Worse, the two dmesg reports on the bad box showed multiple flash memory errors. First were several "Empty flash at xxxxxx ends at xxxxx" at different memory locations, followed later by bad file checks (Data CRC failed on node at xxxx) corresponding to the locations in the previous warnings. "

So looks like I've got a starting point.

Would really appreciate if somebody else with a working ZP100 could email me their

http://Sonos's IP address:1400/status/jffs/upgrade.log

or the firmware download link from within that file.

cheers!
buzz
Zacharias,

If there is some sort of boot trick, it has not been published.
Z
Userlevel 2
bummer. i'm stuck with the unit.

i had a wireless router that refused to boot after a failed firmware update. it was possible to update the firmware via one of the network ports and a linux box to bring it back. i'm sure the zp100 would have a similar tool. at this point i guess i'm completely reliant on the kindness of sonos support or somebody with inside knowledge of how the boot process works, or in this case doesn't.
buzz
Zacharias,

First post! Welcome to the forums.

If the unit will not boot or reset you are stuck and a stop payment would be your best bet.

If the ZP100 has been sitting for a while, it will not recognize any of the newer components. First, you'll need to update the ZP100's firmware with the ZP100 isolated from any current units (remove power from them). Once updated, a healthy ZP100 can be added to your system and it will be fine. Be sure to factory reset the ZP100 before adding it to your system.
Terms & ConditionsCookie settings