ZP100 not booting

Got the Silicon Lab CP210x USB to UART bridge. Supposedly work the same as Bus Pirate.
got the pin to map as below:
1:3V3
2:RX
3:TX
4:GND

Driver install and COM4 is enable in my PC.

Launch Hyper Terminal and set COM4 to as follow 38400/8/None/1/Hardware

Then connect. Hyper Terminal show sucessful connection status.
The ZP100 is on. Can access via default http://169.254.1.1:1400/status.

But I'm staring at blank screen on Hyper Terminal.
What should I see if everything work? Is there some command to send/received between Hyper Terminal and ZP100?

Also tried telnet. Got Rincon login screen. But obviously can't get in since no root passwd.

My experience with the console has been through Linux, so I can't speak to any windows specific issues. First things first, just try hitting enter in the hyperterm window, IIRC the ZP doesn't send anything automatically when you plug in the UART. If you still don't get a command prompt power cycle the ZP100 while the UART is connected. When the ZP powers on it should send a bunch of stuff to the terminal about the bootloader, if you see that (and it doesn't look like gibberish) your connection setting are are correct, otherwise check to make sure you have a good connection to the UART header.

I picked up a bus pirate but this is my first experience with it and I'm having trouble getting anything out of it. I'm not sure if the connections and settings are correct. Can someone confirm the steps and connections from the bus pirate?

Thank you for all the help so far...

@tbearrows: PMed

At the OS level, the UART device is detect and enable. But nothing show up when connecting through either cu on linux or Hyper Terminal on Window.

Its hard to get the pin to snuggly fit onto the port. Seem like the port a bit bigger than the standard IC chip pin, like this one: https://c1.staticflickr.com/3/2774/4149942841_209b609977.jpg

What kind of connector are you using?

had to get my post up to 5

Thanks

I used to be able to get to the default http://169.254.1.1:1400/status. But that appears to be broken as well. Can't ping it either.
Probably as result of twiddling with UART hearder/ports that may short something else. Now the ZP100 is a brick.

@Andres,
Firstly might be worth checking the upgrade log files, this should tell you what version of firmware is loaded. Others on this forum have commented its only diag software that will allow you to access via the uart port to enable you to upgrade the software.

@soyuppy, I'd be suprised if you managed to brick it from the UART connector. I know the one I learned on took waay more abuse (including hooking the UART up to RS232 voltage) without dying. Have you tried unplugging the UART and rebooting the device? It's possible that your UART connection is shorting something. When you reboot the device, take a look at the lights on the ethernet ports. If they flash when you plug in the power the board is (probably) not fried.

I'm just using this sort of cable http://amzn.com/B00A6SOGC4 .

My exprience has been on linux: use minicom to attach to your ttyUSB device and setting up the speed and flow control settings there (check out http://www.wiki.xilinx.com/Setup+a+Serial+Console for a rough explanation).

Success!

I connected my ZP100 (with white blinking led) to a bus pirate (v2, SparkFun with cable) as follows:

On the ZP100 there is a J1000 port with pins 1 to 4 numbered. Connect:
Pin 1: white
Pin 2: brown
Pin 3: orange
Pin 4: black

Then use PuTTY (windows) and connect to Serial COM3 with speed 115200.
Use the following options
m (switch mode)
3 (UART)
7 (38400 speed)
1 (8, NONE bits/parity)
1 (stop bits)
1 (idle 1 receive polarity)
2 (3.3V)
(1) (UART bridge)

I then got:
Rincon boot loader version 0.16-11080(ZP) (32M SDRAM). Press 'h' for help.
SDRAM test...
Memory test iteration 0
Memory test fail @ 8C4F25D4 - D90A7081 != D91A7081
SDRAM test complete
SDRAM test failed, autoboot aborted
>

After pressing 'h':
> 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

After pressing 'b':
> NAND ID is EC:75
32M NAND flash (Samsung K9F5608U0C) detected
Section 0 is provisionally good, kernel on partition 1, generation 7
Section 1 is provisionally good, kernel on partition 4, generation 6
Attempting to boot kernel from partition 1

And hurray! The zoneplayer booted and showed up the Sonos controller! I then could update the firmware.

I'm now going to attempt to replace the memory chip.