Skip to main content
Zacharias
Contributor III
April 6, 2013

ZP100 not booting

Hi,

I've recently acquired a ZP100 however it looks to be stuck in the boot process with a single white light flashing endlessly.

It doesn't appear responsive to holding the mute button on bootup. On powerup all of the network port light flash briefly and the connection lights are solid if wired to bridge via ethernet.

I know this is an old product and I know it is my fault for purchasing it, but is there any other reset tricks or way to update the firmware to get out of this loop?
    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.

    192 replies

    buzz
    buzz
    Grand Maestro
    April 6, 2013
    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.
    ZachariasAuthor
    Contributor III
    April 6, 2013
    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
    buzz
    Grand Maestro
    April 6, 2013
    Zacharias,

    If there is some sort of boot trick, it has not been published.
    ZachariasAuthor
    Contributor III
    April 6, 2013
    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!
    ZachariasAuthor
    Contributor III
    April 10, 2013
    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?
    ZachariasAuthor
    Contributor III
    April 18, 2013
    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
    henkelis
    Trending Lyricist I
    April 18, 2013
    Check your PM.
    steelrat
    Trending Lyricist I
    April 18, 2013
    If the technique works to bring the device back alive, I would be rather curious to see what/where/how you got it back.....
    robertsst
    Contributor I
    May 23, 2013
    Hi, I have the same issue now with my ZP100. Flashing white light, any help would be fantastic
    Katte65
    Lyricist I
    July 14, 2013
    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
    Show more replies
    Terms & ConditionsAccessibility statement