Pogoplug Mobile V4-A1-01 troubles

Hello,
I just bought my first pogoplug, and decided to play around with it. I follow the directions at archlinux for the Pogoplug Series 4. After I was done, I was left with a flashing green light. I spent a few hours reading on how to fix it and I think I'm at the point where I could use some assistance.

I was able to search around and found the pin layout and setting used for serial connection. I was also able to install ubuntu 64 in virtualbox and got kwboot to work. I think I need to use "uboot.uartpogoMobile-MMC-mtdparts-NoUSB.kwb.tar.gz"
found here http://forum.doozan.com/read.php?3,7477,7670#msg-7670 but I'm not sure if I can correct what arch already did.

At this point, I'm sort of lost on how to proceed. I was looking to try Arch but have no problems with Debian since my Pi also runs that. I'm very new to linux so this process has been a major journey. Can someone point me in the right direction from here.
Thanks

jeepster,

You have connected serial console, but no need to do UART booting yet. Perhaps the problem is quite simple to see on serial console.

- First connect the serial console from your Ubuntu/Windows/Mac box using whatever program you are confortable with.
- At serial console, get the entire log of what's going on and post here.

Only if the installed u-boot is all messed up, then you need to boot with UART and go from there.

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



Edited 1 time(s). Last edit at 07/20/2014 04:32PM by bodhi.

Here is what I got

U-Boot 1.1.4 (Oct  1 2011 - 12:21:35) Cloud Engines 1.1.2 (3.4.27) PHYADDR=0

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006918B4

Soc: 88F6192 A1 (DDR2)
CPU running @ 800Mhz L2 running @ 400Mhz
SysClock = 200Mhz , TClock = 166Mhz

DRAM CAS Latency = 3 tRP = 3 tRAS = 8 tRCD=3
DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:128 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)
CLOUD ENGINES BOARD: PPV4A1

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0
Unknown command 'usb' - try 'help'

NAND read: device 0 offset 0x100000, size 0x73d0c
 474380 bytes read: OK
## Starting application at 0x00800000 ...


U-Boot 1.1.4 (Jan 13 2012 - 22:33:21) Arch Linux ARM (PPV4 r1) PHYADDR=0

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFD60

Soc: 88F6192 A1 (DDR2)
CPU running @ 800Mhz L2 running @ 400Mhz
SysClock = 200Mhz , TClock = 166Mhz

DRAM CAS Latency = 3 tRP = 3 tRAS = 8 tRCD=3
DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:128 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)
CLOUD ENGINES BOARD: PPV4A1

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
T Device NOT ready
   Request Sense returned 00 00 00
1 Storage Device(s) found

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found

Device NOT ready
   Request Sense returned 00 00 00
** Can't read from device 0 **

** Unable to use usb 0:1 for fatls **

IDE device 0 not available
** Bad partition 1 **
ALARM>>


ALARM>> printenv


baudrate=115200


loads_echo=0


rootpath=/mnt/ARM_FS/


netmask=255.255.0.0


run_diag=yes


CASset=min


MALLOC_len=1


ethprime=egiga0


load_nand=nboot 0x800000 0 0x200000


load_nand2=nboot 0x800000 0 0x500000


boot=bootm 0x800000


boot_nand=run load_nand boot || run load_nand2 boot


ethmtu=1500


usb0Mode=host


nandEcc=1bit


ethact=egiga0


#ethaddr=00:24:71:04:a4:f3


#cesvcid=2FDEVMHQK25Y4DWY6QXZVVBCX


ceboardver=PPV4A1


ipaddr=192.168.58.233


serverip=192.168.58.188


bootargs=console=ttyS0,115200 root=ubi0:rootfs ubi.mtd=4,2048 rootfstype=ubifs


arcNumber=3960


bootcmd=if usb start; then run alarm_boot; else nand read 0x800000 0x100000 0x73d0c; go 0x800000; fi


alarm_boot=ide reset; run alarm_revert; if ide part 0; then run alarm_ide; else setenv isDisk no; fi; run alarm_usb


alarm_revert=if fatls usb 0:1 /revert; then setenv mainlineLinux no; setenv arcNumber; setenv bootcmd run boot_nand; saveenv; reset; fi


alarm_args=setenv bootargs console=ttyS0,115200 root=$device rootwait rootfstype=ext3


alarm_which=if test $isDisk = yes; then setenv device /dev/sdb1; else setenv device /dev/sda1; fi


alarm_ide=if ext2load ide 0:1 0x800000 /boot/uImage; then setenv device /dev/sda1; run alarm_args; bootm 0x800000; else setenv isDisk yes; fi


alarm_usb=if ext2load usb 0:1 0x800000 /boot/uImage; then run alarm_which; run alarm_args; bootm 0x800000; fi


stdin=serial


stdout=serial


stderr=serial


mainlineLinux=yes


enaMonExt=no


enaCpuStream=no


enaWrAllo=no


pexMode=RC


disL2Cache=no


setL2CacheWT=yes


disL2Prefetch=yes


enaICPref=yes


enaDCPref=yes


sata_dma_mode=yes


netbsd_en=no


vxworks_en=no


bootdelay=1


disaMvPnp=no


hddPowerCtrl=no


pcieTune=no


isDisk=no





Environment size: 1627/131068 bytes


ALARM>>

# I added the # and changed that info as I pasted here, not sure if that info needs to be kept private.
Thanks for the help!!

jeepster,

USB:   scanning bus for devices... 2 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
T Device NOT ready
   Request Sense returned 00 00 00
1 Storage Device(s) found

The problem is the USB was not properly initialized. This problem usually can be solved just by switching to a better brand (such as Sandisk). But first, you can do this:

- At serial console u-boot prompt, start USB a few times to see it if is eventually initialized properly.

ALARM>> usb start

If it did, go ahead and boot:

ALARM>> boot

Also, remember to use the USB 2.0 port on top of the Pogo V4, the two USB 3.0 ports in the rear cannot be used for booting.

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

Ok, I'll give it a try although I do question one thing....... I have the mobile verison not the V4 with the sata and usb3 ports. Mine is the stripped down version with just one USB2.0 port on the back. I followed this tutorial that left me with a flashing green light. http://archlinuxarm.org/platforms/armv5/pogoplug-series-4

I'll give usb start a few shots and i have a bunch of different usb sticks to try in the mean time



Edited 1 time(s). Last edit at 07/20/2014 06:32PM by jeepster.

Ah. That's made it simpler with only one USB port. And that link currently the only way to install with a script.

Later when you have booted into Arch succesfully, you can come back and install the new U-boot which I will upload today or tomorrow in this thread.

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



Edited 1 time(s). Last edit at 07/20/2014 06:51PM by bodhi.

Thank you bodhi! You're the best!

Yesterday when I followed the instructions on the arch site for version 4 I was pretty sure it worked unitl I powered down, I did the /sbin/reboot and I think it was running at that time I never proceded further. I then moved it to another PC and all that would happen is a flashing green light. So I've been copying the files over but I think maybe my problem was the USB label?
I guess I'll leave this here, in hopes it helps someone else out in the future.
Format the flash drive as ext3, label it as "rootfs"
sudo su
cd /media/rootfs
wget http://archlinuxarm.org/os/ArchLinuxARM-armv5te-latest.tar.gz
tar xvzf ArchLinuxARM-armv5te-latest.tar.gz
sync #may take a while
cd /
umount /media/rootfs

Now that "we" got this unit up and running, I need to figure out its purpose LOL Man I put in a good 8hrs of fustration into this 7 dollar device, but in the end I do have a virtual box running with ubuntu that goes full screen and not a 3x3 window (damn guest addons) The journey was rough one ...........

bodhi Wrote:

> Later when you have booted into Arch succesfully,
> you can come back and install the new U-boot which
> I will upload today or tomorrow in
> this
> thread.

@bodhi,

Can I get a early release of the uboot for the PPv4? Would like to test it tonight.

@jeepster,

Hang in there. I've picked up a few PP Mobile for $6 but definitely spent way more time on messing with it than I'm comfortable to admit.

@grayman4hire,

Sorry gray, I need to write some extra flashing instruction for PogoV4/Mobile (same as for iConnect and Netgear Stora). It won't work without it.

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

No problem @bodhi.

grayman4hire Wrote:
-------------------------------------------------------
> bodhi Wrote:
>
> > Later when you have booted into Arch
> succesfully,
> > you can come back and install the new U-boot
> which
> > I will upload today or tomorrow in
> >
> this
>
> > thread.
>
> @bodhi,
>
> Can I get a early release of the uboot for the
> PPv4? Would like to test it tonight.
>
> @jeepster,
>
> Hang in there. I've picked up a few PP Mobile for
> $6 but definitely spent way more time on messing
> with it than I'm comfortable to admit.

grayman4hire, When I thought I bricked the unit I sort of laughed a little, I got a wallwart and cat cable for 7 bucks and the mobile was free. Now that unit works its the other way around. I was just searching the web, one search took me to slickdeals (my fav place) and saw a post by grayman with a collection of what appears to be e02's
http://slickdeals.net/forums/showpost.php?p=61167472&postcount=5 I've seen that photo before, I saw the pogo family photo on http://blog.qnology.com :) Yeah I spent a few hours on that blog trying to get a new e02 to take the uboot - bad blocks, ended up using arch uboot script which worked.

I ordered another P22 - hoping it comes as an e02 from amazon, - which is the best set of instructions to use to get debian on the e02?

Oh which procedure should I follow to make a backup of the stock unit? I would like to dump everything and have a backup for the other unit, just incase something happens in the future. Thanks



Edited 1 time(s). Last edit at 07/21/2014 05:48PM by jeepster.

That's my Pogoplug family photo :)

I got a few more blog/tutorials lined up but haven't had time to publish them yet. One of them will be on Debian on the E02. I got most of the ArchLinuxARM tutorial ported over to Debian.

@bodhi's rootfs makes it very simple to get Debian running on the E02 - http://forum.doozan.com/read.php?2,12096

Regarding backups, if you're talking about the internal flash, I wouldn't bother. If you need it, I'm sure someone on this formal can provide it.



Edited 1 time(s). Last edit at 07/21/2014 08:49PM by grayman4hire.