Help with bricked GoFlex Home pin numbers

I have all the supplies to rescue my GFH with a serial cable. However, my pin locations appear to be different than what I have been able to find on various forums. Can anyone help me identify the Tx, Rx and Ground for my particular board? The board itself is stamped with:
EHDUL4 7D28UL44001R1
REV. 01

and the pins are arranged:

54321
678910

Thanks much for any help!

http://archlinuxarm.org/forum/viewtopic.php?f=18&t=3397

Thanks for the quick reply. I'd seen that post before but was worried it wouldn't work since the pin numbers on my board appear to be arranged differently. I tried using the pins based on location in relation to the board (pins 8, 9 and 10 I think) and it seems to get a connection but now I am stuck. I've tried using the picocom method here: http://wiki.scottn.us/goflex:uartboot but it hangs at "Waiting NAK... Press 'x' to escape."

When I connect via minicom I get the following - any help is much appreciated!:

U-Boot 2010.09 (Feb 16 2011 - 18:44:23)
UBIT v0.6 by Jeff Doozan and Peter Carmichael

SoC: Kirkwood 88F6281_A0
DRAM: 128 MiB
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
Creating 1 MTD partitions on "nand0":
0x000000700000-0x000010000000 : "mtd=2"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI error: validate_ec_hdr: bad VID header offset 2048, expected 512
UBI error: validate_ec_hdr: bad EC header
UBI error: ubi_io_read_ec_hdr: validation failed for PEB 0
UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error -22
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:silent", error -19
Error reading superblock on volume 'ubi:silent'!
UBIFS not mounted, use ubifs mount to mount volume first!
Using egiga0 device
ping failed; host 10.10.10.5 is not alive
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 1 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 3  2  1  0
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:fast", error -19
Error reading superblock on volume 'ubi:fast'!
UBIFS not mounted, use ubifs mount to mount volume first!
** Block device usb 0 not supported
** Block device usb 0 not supported

** Invalid boot device **

** Invalid boot device **
** Block device usb 1 not supported
** Block device usb 1 not supported

** Invalid boot device **

** Invalid boot device **
** Block device usb 2 not supported
** Block device usb 2 not supported

** Invalid boot device **

** Invalid boot device **
** Block device usb 3 not supported
** Block device usb 3 not supported

** Invalid boot device **

** Invalid boot device **

Reset IDE: Bus 0: not available Bus 1: not available
** Bad partition 1 **
** Bad partition 1 **
No Powersaving mode 7F
Error (no IRQ) dev 0 blk 0: status 0x7f
** Can't read from device 0 **

** Unable to use ide 0:1 for fatload **
No Powersaving mode 7F
Error (no IRQ) dev 0 blk 0: status 0x7f
** Can't read from device 0 **

** Unable to use ide 0:1 for fatload **
** Bad partition 1 **
** Bad partition 1 **
No Powersaving mode 7F
Error (no IRQ) dev 1 blk 0: status 0x7f
** Can't read from device 1 **

** Unable to use ide 1:1 for fatload **
No Powersaving mode 7F
Error (no IRQ) dev 1 blk 0: status 0x7f
** Can't read from device 1 **

** Unable to use ide 1:1 for fatload **
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:ramdisk", error -19
Error reading superblock on volume 'ubi:ramdisk'!
UBIFS not mounted, use ubifs mount to mount volume first!
Marvell>>

Art Freeman Wrote:
-------------------------------------------------------

> scanning bus for devices... 1 USB Device(s) found
> scanning bus for storage devices... 0
> Storage Device(s) found
> Hit any key to stop autoboot: 3  2  1  0
>

It seems either you don't have USB drive attached, or if attached it can not be used. What was the state of your GF Home? it seems UBIT was installed. Was it installed using Arch Linux ARM procedure using USB drive?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

For future reference (or googlers) the pin assignments for UART using the silkscreen reference on a GoFlex Home:

1: +3.3V (use if you need to power a TTL-RS232 level converter - do not try to apply power to this pin from USB)
10: GND
9: TTL Transmit (Tx)
8: TTL Recieve (Rx)

majic79 - thanks for confirmation on the pin numbers. This should help future users with the same issue.

bodhi - Yes, I originally followed the Arch ARM directions to a successful install. Tried getting a SAMBA server running and, due to excessive tinkering, ended up hosing up the whole thing. At this point I am thinking a complete reinstall is in order but am open to suggestions.

Hit a key to prevent auto-boot and do a "printenv" and post the contents here - looks like either a hosed UBI File System (UBIFS) or incorrect parameters for UBI boot (don't know the ArchArm instructions well, but have become very familiar with GoFlex Home memory layout over the past six weeks!)

Art Freeman Wrote:
-------------------------------------------------------
> majic79 - thanks for confirmation on the pin
> numbers. This should help future users with the
> same issue.
>
> bodhi - Yes, I originally followed the Arch ARM
> directions to a successful install. Tried getting
> a SAMBA server running and, due to excessive
> tinkering, ended up hosing up the whole thing. At
> this point I am thinking a complete reinstall is
> in order but am open to suggestions.

Hi Art,

If you're happy with Arch, and just want it to work, then you should do this:

1. Get a new Arch rootfs from the site. And reformat a new USB stick, put that rootfs on it, try booting with it. See step 12:
http://archlinuxarm.org/platforms/armv5/seagate-goflex-home

2. If that new rootfs did not work then rerun the Arch installation using the same new stick.

I would not tinker too much with UBIT. You could end up spending a lot time. Also, UBIFS error should not matter, since you're running USB.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 08/23/2013 03:52AM by bodhi.