ZP100 not booting

Thanks poshul.
Is there anything I could do/check with the power supply?

andresmorago,

Measure the output voltages, and the ripple voltage. Visually inspect the traces and components. I also like to "thump" the board with an insulated tool while monitoring the voltage. An oscilloscope is very handy as a monitor. In any case, a healthy board will not respond to the thumps.

andresmorago,

Measure the output voltages, and the ripple voltage. Visually inspect the traces and components. I also like to "thump" the board with an insulated tool while monitoring the voltage. An oscilloscope is very handy as a monitor. In any case, a healthy board will not respond to the thumps.

hello
im starting to think that indeed there is a voltage issue. i noticed today that the white led is kinda flickering a little bit. very weak but its there.
i monkeyd around with cables a little bit, re-powered up the unit and seems to be better.
i will clean electronic parts with a cleaner and see what happens.

24 hours and still running ok with 5.3 version.
i cleaned up electronic boards and cotacts. also i moved cables around and toggled the voltage switch several times in order to make sure that the contact was ok.
will report any news.

reporting back. so far so good. revived unit has been stable for 2 days already and have playing music without any hiccups.
apparently, moving the cables and doing some cleaning, did the trick.
im still afraing of moving to 5.4 version...

I tried to connect to the serial port using a buspirate and was pretty unsuccessful. Mostly because the bootloader and machine name were too difficult to locate without access to the :1400 interface.

Are there ways to bring the ZPT28 CPU board back from an non-pingable state? Got my IP address on my PC in the same range as default on ZP100 so my :1400/status is visible.


Here is my workaround using hardware. With a unit that I was able to ping as the donor, I swapped the top CPU board with a unit that had no IP or ping ability. Once the board was swapped the unit powered, recognized and updated itself. I successfully did this 2 times, yielding 2 working ZP100s. I sliced off the working MAC address sticker on the rear and attached it to the transplant machine so I could keep my MAC addresses tidy on my network. I am VERY interested in swapping or trading 2 non IP devices for 1 working IP/ethernet/cpu ZPT28 card.

My screwdriver and assembly skills are better than my linux.

*moderators please move this to a new topic if you feel this is too far from initial BusPirate/serial port discussion

So I too am having these issues. I have downloaded the latest firmware and currently my system shows
Software Version 3.2-29243-diag
I am willing to purchase the buspirate but need some guidance as to where to hook it up. I have the unit mostly apart at this time and am fairly confident in being able to get this working again. Thanks in advance.

John

So, I am now a pro at opening a buspirate connection in bridge, setting my computer IP to 169.254.1.x to use the same range as the default ZP100, and then pulling out my hair.

I have got bootloader on my local PC, kill ancapa and I can get it to upgrade, but then it just doesn't seem to take. I get command prompt # with no reboot or indication that it wants to stay upgraded.

Also are the http upgrade values after the upd?blahblah=xx&yadda=xxxx&var=x. . .etc specific to the machine or the upgrade? or is it just the serial, sonosid, and householdid that are machine specific?

For some reason my wife doesn't want to discuss sonos with me anymore.

Connected to UART console and was able to see the boot loader message..but it seem to be stuck there. no other message show up.

"Rincon boot loader version 0.16-11080(ZP) (32M SDRAM). Press 'h' for help."
tried pressing h repeated. no luck

This is the only line of text appearing via Putty Console thru Bus Pirate

Anyone seen or know how to get pass this?

Because of this, I cannot get thru the http://169.254.1.1:1400/status either.

I wonder if all the units have the same root password for accessing via telnet.

Seems the hash is stored in /etc/passwd as you'd expect. The hash on the unit I have is hSmFHLbnzeXIA.

Its probably salted and then hashed, so I dont know if we'll be able to recover it this way.

Regardless, I got 2 ZP100s from ebay which were both non-functional when I got them.

Thanks to the advice in this thread, learned that the one is failing the SDRAM check, and giving up on autoboot. Manually booting it via the bootloader console is enough to get it alive, updated to current firmware, and it links to my Sonosnet and plays music. I suspect replacing the ISSI IS42S16800B-7TI SDRAM chip on the board will make it autoboot once more.

The other was a 3.2.whatever-diag firmwared unit, coming up on 169.254.1.1, with telnet open. Breaking in as root via the UART console let me set its IP to a routable one on my network and get it updated and playing music too. Its dmesg is still showing a bunch of "Empty flash at..." and "Data CRC failed..." messages. It was having issues where after a couple hours of runtime on the diag firmware, it wouldn't boot anymore. Few hours of cooldown would get it running again. I'm currently running it for a few hours to see if the fail to boot comes back.