No dice for me at 0x800000 either! U-Boot 2012.04.01 (Nov 20 2012 - 06:47:34) Iomega iConnect Wireless SoC: Kirkwood 88F6281_A0 DRAM: 256 MiB WARNING: Caches not enabled NAND: 512 MiB In: serial Out: serial Err: serial Net: egiga0 Hit any key to stop autoboot: 0 iconnect => usb start (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanninby bodhi - Debian
Kurlon, I thought that's how we boot uBoot image with kirkwood header in the first 0x200 bytes. I believe these uBoot images all built that way. But it strange because I'm running the old iConnect Open-WRT uBoot, and load uBoot image that people have tried running in RAM successfully before (I've also tried Davy's uBoot for Pogo E02, same hang after starting). Weird!by bodhi - Debian
What's the output of your USB /boot directory? ls -latr /bootby bodhi - Debian
Sorry, that was a typo! but just tried it again and got same result: U-Boot 2012.04.01 (Nov 20 2012 - 06:47:34) Iomega iConnect Wireless SoC: Kirkwood 88F6281_A0 DRAM: 256 MiB WARNING: Caches not enabled NAND: 512 MiB In: serial Out: serial Err: serial Net: egiga0 Hit any key to stop autoboot: 0 iconnect => usb start (Re)start USB... USB: Register 10011 Nbrby bodhi - Debian
@rpress, It does not seem I can run it from RAM. U-Boot 2012.04.01 (Nov 20 2012 - 06:47:34) Iomega iConnect Wireless SoC: Kirkwood 88F6281_A0 DRAM: 256 MiB WARNING: Caches not enabled NAND: 512 MiB In: serial Out: serial Err: serial Net: egiga0 Hit any key to stop autoboot: 0 iconnect => usb start (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHby bodhi - Debian
Thanks rpress, I've read your post, already downloaded your tarball :) when I started to look at the kirkwood code for the latest uBoot (u-boot-2013.01), I realized that the board files for iconnect, goflex net, dockstar ... were already in there! and they all have env addr set to 0x600000. So I was a little unsure and wanted to gather more info. I will try and post back. Thanks agaby bodhi - Debian
Hi syong, Thanks! did you flash davy's e02 new version right away to NAND, or did you try running it from RAM first this way: Interrupt uBoot at the cound down, and at the prompt: mw 0x600000 0 1 usb start ext2load usb 0:1 0x600000 /uboot.pogoplugE02-L2Coff-arcNumFixed.kwb go 0x600200 or mw 0x800000 0 1 usb start ext2load usb 0:1 0x800000 /uboot.pogoplugE02-L2Coff-arcNuby bodhi - uBoot
syong Wrote: ------------------------------------------------------- > @davygravy, > > Could you please help bodhi by posting your patch > for uboot? I think we do need the patch. Eventhough I found that davy's pogo e02 board file is in the mainline u-boot, the envs address is at a different address so it won't work right away as drop-in for the current set up.by bodhi - Debian
Try this: http://forum.doozan.com/read.php?2,11601 or this: http://forum.doozan.com/read.php?2,12096by bodhi - Debian
Thanks restamp, That was awesome! The problem was just exactly what you've diagnosed :) I have netconsole and serial console connected from the same server! Unset preboot env and got the uBoot prompt again. Now I can go on to testing uBoot. - bodhiby bodhi - uBoot
I'm running davy's uBoot on my Pogo E02: Netconsole: U-Boot 2011.12 (Feb 20 2012 - 21:21:59) Pogoplug E02 arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1 GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709 Hit any key to stop autoboot: 10 I have serial console connected to this E02 and it is strange that I don't see the count down. U-Boot 2011.12 (Feby bodhi - uBoot
Are you running squeeze or wheezy? what is your output of uname -a apt-cache show nfs-commonby bodhi - Debian
Gapp, It should work. The Mobile and E02 processors are in the same family.by bodhi - Debian
I've attached here the config file I used to build this DT kernel.by bodhi - Debian
I've also tried with Davy's uBoot on a GoFlex Net. U-Boot 2011.12 (Apr 18 2012 - 23:08:20) Seagate GoFlexNetby bodhi - Debian
zAM Wrote: ------------------------------------------------------- > Hi, > my deabian installation crashed recently. > my usb stick is broken and all data on it is > lost. > i am stuck with an POGO-E02(black) looping arround > without an usb stick. > > i have no idear on gettin it runnig again, > i tested a ARCHLINUX usb boot stick which worked, > but theby bodhi - uBoot
I should also mention that I've created a GoFlex Home Dt board file. But do not have a way to test it yet until I can boot either the iConnect or the GoFlex Net using this method.by bodhi - Debian
Kurlon Wrote: ------------------------------------------------------- > I was just about to start a new thread about the > impeding DTopcalypse, but then remembered this > one. > > So, short story: I have my GoFlex Net booting 3.5 > via Device Tree. It's including in linux-next now > and should be showing up formally in 3.6. > Kirkwood DT support has gottby bodhi - Debian
@t3ch42, You're probably looking for this: http://forum.doozan.com/read.php?3,8044,8152#msg-8152by bodhi - uBoot
Gapp, You should do everything from /tmp directory. So download and execute commands there. When the commands is in /usr/bin, then it was installed before. If you start with Pogo OS, they are not installed, after downloaded and did chmod +x, you need to execute them from /tmp. One friendly warning: you will need serial console to recover from any problem that might happen while doing this.by bodhi - Debian
Gapp, Currently, this installation is condensed, and does not have step-by-step instruction (it meant for users who are already familiar with installing uBoot and Debian for these plug computers). For example, if you have run Jeff's script to install a Dockstar, or a Pogoplug E02, and kind of familiar with his script, then it is OK to proceed. When I have time I will make it a detailedby bodhi - Debian
I've found if you add silicon feets to the Dockstar's bottom, it will not get too hot. Or you could mount it sideway.by bodhi - Debian
Carlos, I suspect this problem is with loading /dev/root during the time the initrd is trying to load the rootfs on the HDD. This can be observed if you have serial console. I had run into this problem from time to time when I use a rootfs that has been heavily used in installing new kernels. If you have a fresh rootfs on a USB stick, e.g. created with davy's NSA320 rootfs or other meby bodhi - Debian
Ok. Instead of trying to make the Pogo OS work, you could use Davy's rootfs to run the GoFlex Home temporarily. I don't remmeber it has samba already installed. If not, it should be simple to install it. This could serve as temporary file server for the family until you get your own Debian rootfs set up. http://forum.doozan.com/read.php?2,7806by bodhi - uBoot
I don't have a detail instruction written up. But the idea is: - Boot into Debian. - check the mtd partitions #fw_printenv mtdparts - The original uBoot image uboot-original-mtd0.kwb should have been copied to the top directory of rootfs mtd partition (mtd2). So you can mount this while in Debian and make sure the file is there, and not corrupted (looks like this file is there, accby bodhi - uBoot
Cool! You can check your LEDs: ls /sys/class/leds If the Dockstar LED triggers are defined then you should see green and orange LED triggers. ArchNumber should be 2998. # turn on green LED echo default-on > /sys/class/leds/dockstar:green:health/trigger # turn off orange LED echo none > /sys/class/leds/dockstar:orange:misc/trigger You can put these in your /etc/rc.local toby bodhi - Debian
- Most of Seagate drives work with hdparm - Try hdparm first, if it does not work, try sdparm.by bodhi - Debian
The patch was updated and reattached.by bodhi - Debian
@restamp, I use a 2.5" HDD as the boot drive for my kernel building Goflex Net. I was aware of this problem with the "green" drives, so I used the manufacturer's tool to set the sleep period to "never". Mine is a Hitachi drive, and I used the tool from their website to do that on Win 7. As long as you use the OEM tool to set the sleep period either to never or a rby bodhi - Debian
syong, Cool! glad it works. Looks like yours took the same time as my build did on the Goflex Net. There are quite a few modules that we don't really need, but I did not take them out. I figure somebody will need them someday. Also, what I found regarding the security policy files was that it somehow got into the build and the patch was created with those changes. I've updated thby bodhi - Debian