ZP100 not booting | Sonos Community

Zacharias · 2013-04-06T08:26:02+00:00

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?

if you hardwire the unit to your router, what do you get when running arp -a in any network device?

connecting ZP directly to my computer. And computer is set to static ip address of 169.254.1.2/24 default gateway of 169.254.1.1

Here's the output from arp -a

arp -a

Interface: 169.254.1.2 --- 0xb

Internet Address Physical Address Type

169.254.255.255 ff-ff-ff-ff-ff-ff static

224.0.0.2 01-00-5e-00-00-02 static

224.0.0.22 01-00-5e-00-00-16 static

224.0.0.252 01-00-5e-00-00-fc static

239.255.255.250 01-00-5e-7f-ff-fa static

255.255.255.255 ff-ff-ff-ff-ff-ff static

apparently, there is no ethernet traffic at all from the unit.

what happens when you try to factory reset it?

also, when you connect it to your network, are there any dhcp requests?

On a working unit, when I hold mute button and plug in the power, the LED eventually flash in amber/orange. After release the mute button, LED eventually shows constant white.

On this problematic unit, LED continue to flash white immediate after plug in AC. event with me pressing and holding the mute button, LED never change to amber...it continue to flash white.

I'll take a look at my router log to see if DHCP request is made from the device.

nothing on router DHCP log. Consistent with no ethernet activity analysis from arp -a

I press h to get into boot loader menu

Rincon boot loader version 1.0-27270(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

> nand_load: bad page magic, page 0

There's Boot diagnostics, but press d only result in the bad page magic.

Does anyone know what this mean? Has anyone try this option with success?

Never seen that before.

But as I can see, maybe the nand is fried? 😞

None of the production units (or indeed the diagnostic unit) that I have worked on have a diagnostic partition. A quick look at the bootloader assembly indicates that it refers to a different type of partition that I've never seen before. My guess is that it is a remnant from the development process (remember that the bootloader wasn't designed for us), that's been left in.

I have a RAM chip (ISSI IS42S16800A-7TL) ordered on ebay to replace the one that wont boot on its own. I guess I should order another one for the temperature failing one.

Did you ever get the RAM chip replace? was it easy to do?

Haven't received the chip from China yet. Replacement, well, there's certainly a technique to replacing a 54 pin SMT chip.

Would love to see some pic.

Unless you have previous experience reworking SMT boards, this is not the place to start learning. Practice on some discarded electronics first. You'll have a bunch of failed attempts until you hone your technique.

Ok. I have a zp100 and a bus pirate. I have issues getting connected. The four ports I see are on the network pcb correct? What is the pinout for them vs the bus pirate?

I get connected and see UART> that is all.

@johnbcw

go back a little bit in this thread and youll get more info about it

http://forums.sonos.com/showpost.php?p=249346&postcount=62

I am closer but now the system says read-only file system. That appears to be keeping me from connecting to get the 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

Section 0 is provisionally good, kernel on partition 1, generation 15

Section 1 is provisionally good, kernel on partition 4, generation 14

Attempting to boot kernel from partition 1

(946756120)VFS: Mounted root (cramfs filesystem) readonly.

(946756120)Mounted devfs on /dev

(946756120)Freeing unused kernel memory: 36k freed

(946756120)ttsc/0: 1 input overrun(s)

h(946756121)Empty flash at 0x0061c268 ends at 0x0061c400

(946756121)Empty flash at 0x0061d740 ends at 0x0061d800

(946756121)Empty flash at 0x0061e144 ends at 0x0061e200

(946756121)jffs2_scan_dirent_node(): Node CRC failed on node at 0x0061ebe4: Read 0xffffffff, calculated 0xfe67f4a0

(946756121)Empty flash at 0x0078c6cc ends at 0x0078c800

(946756121)Empty flash at 0x0078d144 ends at 0x0078d200

(946756121)Empty flash at 0x0078e344 ends at 0x0078e400

(946756121)Empty flash at 0x0078edb0 ends at 0x0078ee00

(946756121)Empty flash at 0x0078f630 ends at 0x0078f800

(946756122)jffs2_scan_inode_node(): CRC failed on node at 0x00a5dbe4: Read 0xfff fffff, calculated 0x00cac3a6

(946756122)Empty flash at 0x00a5dd7c ends at 0x00a5de00

(946756122)Empty flash at 0x00a5eb38 ends at 0x00a5ec00

(946756122)jffs2_scan_eraseblock(): Node at 0x00a5f3f8 {0x1985, 0xe002, 0x000000 44) has invalid CRC 0xe0021985 (calculated 0x98f7fb1d)

(946756122)jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00a5f3fc : 0x0044 instead

(946756122)Empty flash at 0x00a5fd44 ends at 0x00a5fe00

(946756122)Empty flash at 0x011a482c ends at 0x011a4a00

(946756122)Empty flash at 0x011a53fc ends at 0x011a5400

(946756122)jffs2_scan_dirent_node(): Name CRC failed on node at 0x011a59d0: Read 0xee69547a, calculated 0xa871cd3d

(946756122)Empty flash at 0x011a5a10 ends at 0x011a5c00

(946756122)Empty flash at 0x011a6f40 ends at 0x011a7000

(946756122)Empty flash at 0x012c05a4 ends at 0x012c0600

(946756122)Empty flash at 0x012c08cc ends at 0x012c0a00

(946756122)Empty flash at 0x012c265c ends at 0x012c2800

(946756122)Empty flash at 0x012c3aa8 ends at 0x012c3c00

(946756123)jffs2_get_inode_nodes(): Data CRC failed on node at 0x012c0688: Read 0x2c55f3e3, calculated 0xd2a2f536

Initializing random number generator...

Using /modules/cifs.o

Using /modules/audiodev.o

(946756123)SCIF-Based Audio Control Interface Initialized

(946756123) at 0xffe80000

(946756123)audioctl: registered.

(946756123)dsp: Initializing DSP ... Complete

(946756123)dsp: registered.

(946756123)jffs2_get_inode_nodes(): Data CRC failed on node at 0x012c02b8: Read 0x376ec35f, calculated 0xe768257c

(946756123)jffs2_get_inode_nodes(): Data CRC failed on node at 0x011a50b4: Read 0xed2df1cc, calculated 0x43e32b19

Using /wifi/ath_hal.o

Warning: loading ath_hal wil(946756124)ath_hal: 0.9.14.4 (AR5212, RF5112, RF2413 )

l taint the kernel: non-GPL license - Proprietary

See http://www.tux.org/lkml/#export-tainted for information about tainted modu les

Using /wifi/ath_driver.o

Warning: loading ath_driver (946756124)PCI: Enabling device PCI device 168c:0013 (0000 -> 0002)

will taint the kernel: no license

See http://www.tux.org/lkml/#export-tainted for information about tainted modu les

(946756124)ath0: registered with power management

(946756124)ath0: Atheros 5212: mem=0xfd000000, irq=8

/usr/sbin/setmac: started

Using MDP s(946756124)ath0: set MAC address to 00:0E:58:10:3D:73

erial number 000E58103D727

Successfully opened socket: 3

Successfully got interface index for if ath0: 3

Current wifi address: 00:02:78:FD:E2:2A

Successfully got i(946756124)eth0: link up, 100Mbps, full-duplex, lpa 0x05E1

nterface index for if eth0: 2

Current ethernet MAC address: 00:E0:4C:00:00:0F

Setting interface eth0 MAC address to 00:0E:58:10:3D:72

Starting internet superserver: inetd(946756125)jffs2_get_inode_nodes(): Data CRC failed on node at 0x00a5fa58: Read 0xc95dbcf1, calculated 0x95178f96

.

PING 169.254.2.2 (169.254.2.2): 56 data bytes

(946756125)jffs2_get_inode_nodes(): Data CRC failed on node at 0x00a5e84c: Read 0xc95dbcf1, calculated 0x072fbe16

Please press Enter to activate this console. (946756125)jffs2_get_inode_nodes(): Data CRC failed on node at 0x0078ea58: Read 0x15dfa329, calculated 0xe434b54e

(946756125)jffs2_get_inode_nodes(): Data CRC failed on node at 0x0078e058: Read 0xc95dbcf1, calculated 0x95178f96

(946756126)jffs2_get_inode_nodes(): Data CRC failed on node at 0x0078ce58: Read 0xc95dbcf1, calculated 0x95178f96

(946756126)jffs2_get_inode_nodes(): Data CRC failed on node at 0x0061de58: Read 0x376ec35f, calculated 0x9c0093c0

(946756126)jffs2_get_inode_nodes(): CRC failed on node at 0x0061cfdc: Read 0xfff fffff, calculated 0xb97835b2

(946756126)jffs2_get_inode_nodes(): Data CRC failed on node at 0x0061c000: Read 0x581d4522, calculated 0x32691c16

(946756126)jffs2_get_inode_nodes(): CRC failed on node at 0x012c25c4: Read 0xfff fffff, calculated 0xd2d4d182

(946756126)jffs2_get_inode_nodes(): Data CRC failed on node at 0x012c3944: Read 0x33f02626, calculated 0x2d022b39

(946756126)jffs2_get_inode_nodes(): Data CRC failed on node at 0x011a4664: Read 0xa31bb5ff, calculated 0x7dcac85f

(946756126)jffs2_get_inode_nodes(): Data CRC failed on node at 0x0078c458: Read 0x20fce934, calculated 0x85098c7e

(946756126)jffs2_get_inode_nodes(): CRC failed on node at 0x0078f5ec: Read 0xfff fffff, calculated 0x81756b8b

(946756127)jffs2_get_inode_nodes(): Data CRC failed on node at 0x0061d4cc: Read 0x20fce934, calculated 0x95044465

BusyBox v1.00-pre3 (2007.03.30-22:08+0000) Built-in shell (ash)

Enter 'help' for a list of built-in commands.

The system says read-only file system when I attempt and upgrade or wget. Also is see the Rincon boot loader but then it gets to a busybox v1.00-pre3. Don't know if that is expected. It shows to be running the diag firmware.

Got it connected and recognized now in Sonos Software. Was able to update the firmware. The device I think though is dead....as it doesn't play any audio when speakers are attached. Any idea's where to start?

could you please tell us, for reference, how did you revive it? just to keep records in the forum for future people who might need it.

regarding your other issue, check the circuit boards. do a complete cleanup and make sure the audio amplifiers arent fried.

Sure.

I used a bus pirate connected to the zp100 which was booting in diag firmware. Setup the bus pirate to run uart mode. Setup Apache on my local workstion windows 8 and downloaded the 28.1-83040-1-1.upd file. Ran update http://169.254.1.2/28.1-83040-1-1.upd. Found that you had to kill anacapa service. Once that was killed the system updated. It booted with local ip address. I had to reboot holding the mute to reset the system then Sonos software would see it. Right now I get no audio and the box appears to freeze often........the timer will begin and then the box goes unresponsive. Where are the audio amplifies on the boards?

John

My revived used to freeze a lot. I ended up cleaning everthing with contact cleaner and marking sure every wire was connected tight. After doing that, it came back from death and is been running for almost a month now.

Apms are located on the right side of the unit.

andresmorago: I got it working 100%. So after the unit was freezing I took it apart and completely cleaned the inside. Everything now working 100%. Doing a little burn in on the system. Hopefully it all holds. Thanks for all of the help.

The device I think though is dead....as it doesn't play any audio when speakers are attached.

n/m...

andresmorago: I got it working 100%. So after the unit was freezing I took it apart and completely cleaned the inside. Everything now working 100%. Doing a little burn in on the system. Hopefully it all holds. Thanks for all of the help.

great to hear that. indeed, cleaning the house helps! it did for me too 🙂

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

Section 0 is provisionally good, kernel on partition 1, generation 15

Section 1 is provisionally good, kernel on partition 4, generation 14

Attempting to boot kernel from partition 1

(946756120)VFS: Mounted root (cramfs filesystem) readonly.

(946756120)Mounted devfs on /dev

I don't remember ever seeing above BOLD message before.

Do these messages appear after it booted with the updated firmware?

great to hear that. indeed, cleaning the house helps! it did for me too :)

What kind of cleaning are talking about hear? is just a matter of blowing compress air to rid of all the dust behind all the crevices?

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded