well, I'm not really interested on pogoplug services.. I can boot into nand with your rootfs but I just need it (hopefully not) for some future rescue purpose.. I'm planning to boot my system straight from SATA hard drive as I'm doing with my dockstar from USB hard drive. indeed, if there are any configurations specific of your device (device id or else), that you may want to usby skakz - uBoot
actually I'm going to install gentoo on it! I've already gentoo on my dockstar and I'm happy with it. Yes, I compile every single package and no, it does not take too much time :) I want to see if with the SATA of the Pogov4 I can overcome the barrier of 10MB of the USB hard drive on the dockstar. Then one device will serve music and video to the raspberry connected to my TV, anby skakz - uBoot
bodhi... THANKS!!!! it worked!!!!! I owe you a beer!! U-Boot 1.1.4 (Oct 1 2011 - 12:06:06) 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 Tby skakz - uBoot
ok, I'm goind to restore Davy's uboot and env.. take your time! I have no hurryby skakz - uBoot
Ok, I managed to boot from UART with the Davy's uboot. I changed the mdparts and booted into debian. I've flashed your mtd0 backup, this is the output: root@debian:~# ./flash_erase /dev/mtd0 0 16 Erase Total 16 Units Performing Flash Erase of length 131072 at offset 0x1e0000 done root@debian:~# root@debian:~# root@debian:~# ./nandwrite /dev/mtd0 mtd0 Image 2162688 bytes,by skakz - uBoot
actually I think I screwed up the rootfs too (I don't know how.. I tought that it was read-only..) maybe the kernel is ok (maybe). well. dmseg is not reporting any bad blocks. I've done the flash_erase command but: root@debian:~# ./flash_erase /dev/mtd0 0 16 Erase Total 16 Units Performing Flash Erase of length 131072 at offset 0x100000 MTD Erase failure: Invalid argument roby skakz - uBoot
bodhi!! thanks! It worked!! I managed to send and boot "uboot.nandpogoV4-MMC-mtdparts-noSATA.kwb". However I can't boot from ALARM uboot (downloaded from http://archlinuxarm.org/os/ppv4/uboot.bin.gz ). I'm using kwboot without the -p option but I got everytime the "Bad message" error. thanks edit: ok i'll try with your mtd0! edit2: clearly Iby skakz - uBoot
Don't worry bodhi. Take your time! I don't want to rush things. thank you!!by skakz - uBoot
yes I've, but the hard drive doesn't even turn on. (The hard drive works fine on other computers). let's flash the original fw. Don't worry, I'll take full responsibility. Then I still have my trusty indistruttibile dockstar!!by skakz - uBoot
yeah! sorry about that! I forgot I changed the kernel: here it is dmsg for the debian kernel: root@debian:~# dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.10.4-kirkwood-tld-1 (root@tldDebian) (gcc versby skakz - uBoot
why is that? label under the device says: Model Pogo-V4-A3-A1 Product Pogoplug Series 4 root@debian:~# cat /proc/cpuinfo Processor : Feroceon 88FR131 rev 1 (v5l) BogoMIPS : 795.44 Features : swp half thumb fastmult edsp CPU implementer : 0x56 CPU architecture: 5TE CPU variant : 0x2 CPU part : 0x131 CPU revision : 1 Hardware : Marvell Oby skakz - uBoot
Hi bodhi, here it is: root@debian:~# dmesg [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 3.1.10-22-ARCH (nobody@) (gcc version 4.7.2 (GCC) ) #1 PREEMPT Fri Jun 28 21:43:02 CDT 2013 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 [ 0.000000] CPU: VIVT data cache, VIVT instrby skakz - uBoot
thank you bodhi yeah I didn't know :( I bought a sata hard drive just for it! so I see that is a very complicated subject! mayabe the simpliest solution is to find a way to restore those backups..by skakz - uBoot
Thanks bodhi, I don't want disturb too much =) you have been far too kind thanks again edit: checked with armlinux kernel and sata is still not working, so it is not a kernel problem. mayabe something in uboot?? my envs are now: Pogov4> printenv arcNumber=3960 baudrate=115200 bootcmd=mmc init; run mmc_bootcmd; reset console=ttyS0,115200 ethact=egiga0 ethaddr=02:50:43by skakz - uBoot
thanks bodhi, finally with debian works fine. Now let's forget about nand and restoring original fw. Llet's say I want boot from sata. the easyst way is to put the kernel on the usb and the rootfs on sata hard drive. the hardest way would be to install the alarm uboot that may screw up forever my pogo. can I install the ALARM uBoot somewhere else in the nand and load it fromby skakz - uBoot
hi bodhi, I think your example is for the command shell once booted in linux. I need something directly from uboot (nand erase/write) where I have to specify adresses and offsets. I wold do this steps (tell me if I'm wrong): 1) tftpboot 0x800000 mtd0 (uboot backup) 0x800000 is an external memory address check transferred bytes and convert to hex 2) nand erase 0x0 0x80000 3) nby skakz - uBoot
Hi all, I need some help restoring the original firmware on my Pogoplug V4 (A3-01). My actual situation is that I can only boot into uBoot. I don't have a working o.s. on the nand and I can't manage to boot any other o.s from usb or mmc. Luckily I have both access to the serial console and mtds backups. Now my question is: how do I use these backups to restore my device? How I know wheby skakz - uBoot
Hi everyone, here it is my situation: I've installed openwrt on NAND following this guide with this configuration: mtd0 uboot 1Mb mtd1 second stage uboot 1Mb mtd2 kernel 3Mb mtd3 rootfs 251Mb Now, I've also a full working gentoo installation on a usb hard disk with: sda1 /boot ext2 partion sda2 / ext4 partiotion sda3by skakz - uBoot
Hi all, first of all.. thank you so much for your work and for sharing this with everyone.. I've installed this rescue system to fs.check my partitions before start the system, exsplecially the /dev/sda1 ext2 partition which is not checked at boot-time because it is already mounted. My /dev/sda2 partition is XFS, and I've this error when I try to check the partition: rescue:~#by skakz - Rescue System