vaidyasr, Quote# ls -l > total 844 > -rwxr-xr-x 1 root root 12819 Jul 22 17:23 > flash_erase > -rwxr-xr-x 1 root root 329 Jul 22 17:23 > fw_env.config > -rwxr-xr-x 1 root root 668497 Jul 22 17:23 > fw_printenv > -rwxr-xr-x 1 root root 21286 Jul 22 17:23 > nanddump > -rwxr-xr-x 1 root root 11500 Jul 22 17:23 > nandwrite > -rw-r--r-- 1 root rby bodhi - uBoot
Hi vaidyasr, > Thanks bodhi. But when I use the instructions on > page 1 on step 2, I can't use fw_printenv. It says > error, which I have already posted. I'm quoting what I wrote in the 1st post: QuoteAlso, if you are running stock kernel, which usually does not provide NAND tools, you can download it here in this thread. Because Arch rootfs (like stock kernel) doesby bodhi - uBoot
absintos, The new kernel has more modules compiled in so it's quite a bit larger than before. > ext2load ide 0:1 0x00800000 /uImage; ext2load ide > 0:1 0x01100000 /uInitrd This should boot fine with uncompressed 6.9MB kernel (0x01100000 = 17MB, 0x00800000 = 8MB).by bodhi - Debian
Hi restamp, The L2 cache is re-enabled by the kernel during boot, we can see this in dmesg: root@tldDebian:~# dmesg | grep -i l2 [ 16.769392] Feroceon L2: Enabling L2 [ 16.769431] Feroceon L2: Cache support initialised.by bodhi - Debian
vaidyasr, You're confused 2 different instructions (the 1st were written long ago for a different purpose). 1. Using new kernel with stock u-boot (blparam is needed) QuoteI believe the link above you have shared should be http://forum.doozan.com/read.php?3,11538,11706 2. Installing new-uboot (this thread) (blparam does not come in to play at all). Ignore every thread that you havby bodhi - uBoot
OK. Got rid of this error after refetch every thing. git fetch --allby bodhi - uBoot
Tinkerer, It does not sound there was any hanshake occured. It occurs when the spinning | changes speed. So I think it could be either: - Your kwboot binary is not working. or - Your GoFlexHome does not have correct Boot ROM. or - Your serial console does not work (can you test it somehow?). If you have the dmesg log after you SSH in, and before you installed Arch, please post here.by bodhi - uBoot
@WarheadsSE, I'm rebasing u-boot-kirwood and got this error: # git checkout -b 2014.07-kirkwood 524123a70761110c5cf3ccc5f52f6d4da071b959 fatal: reference is not a tree: 524123a70761110c5cf3ccc5f52f6d4da071b959 Any idea why? I've used this same command before to rebase 2014.01. In the second attempt, I've created the branch 2014.07-kirkwood first and then got the sameby bodhi - uBoot
vaidyasr, Please reread the first post. The link I've included above is only for information. The 1st post in this thread is what you need to follow. Take your time.by bodhi - uBoot
@vaidyasr, Here is the thread that shows similar instruction about how to install new U-Boot manually. The starting point is from the Arch Linux installation of Pogo V4/Mobile: Install uBoot/Debian From this post, you can see the NAND tools set is needed to do the installation, if you are installing from a system that does not provide it (stock Pogo OS, Pogo V4 Arch Linux). And as theby bodhi - uBoot
vaidyasr Wrote: ------------------------------------------------------- > Ok, thank you. One more question. I found the > script in arch linux installation called > ppv4-install.sh. which contains similar steps on > page 1, but dealt with bldparm, so can I just use > the same script by making appropriate changes (not > to download uboot from web) and use your uboot?. Nby bodhi - uBoot
See this post: http://forum.doozan.com/read.php?3,8044,8152#msg-8152by bodhi - Debian
@gray It is more complicated than just adding the file. @vaidyasr, When you boot with Arch installation on Pogo V4/Mobile, you're not using the uboot-env-tools that newer systems are using. You are using blparam (cloudengines tool to deal with NAND). So let me get you the links to different threads here, and once you've read them, I'll write more explanation.by bodhi - uBoot
FYI, I've re-upload uboot.2014.07-tld-1.environment.img.bodhi.tar to fix typos in bootcmd which was reported in this post.by bodhi - uBoot
vaidyasr, If your question is about the Pogo V4 or Mobile with Arch installed, then 3TB is not supported and netconsole is not supported either. This is because current ALARM Pogo V4 U-boot is a variant of stock U-Boot. So you can install the latest U-Boot in this thread and boot the same Arch rootfs. But with your current U-Boot and Arch installation, you will need to download NAND tools (by bodhi - uBoot
shv, Have you tried this instruction ? also in the working thread at ALARM site, I recall some have succesfully prepared and booted with SATA.by bodhi - Debian
agiorgio, I would recommend to recreate the partitions after booting into your current rootfs on USB (to take advantage of the latest Debian packages). Live CD is usually old and only good for emergency usage. And I think the latest U-Boot code does GPT detection properly, perhaps something is not quite right in your drive partitions? it's best to start from scratch in Debian.by bodhi - Debian
OK. It might be that your GoFlex Home has the earlier Boot ROM, therefore UART booting does not work. However, because if u-boot is all messed up, we can't see the Boot ROM to tell for sure. So you might as well try this: - Start kwboot on the other Linux box: ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07.tld-1.goflexhome.mtd0.kwb -p - Power up the GoFlex Home - Watch theby bodhi - uBoot
Tinkerer, I'm looking at the GoFlex Home board picture, inside from the battery looking outward. There are 2 rows of 5 pins. The top row left most 3 pins are: GND TX RX Is that how you determine the pins?by bodhi - uBoot
Tinkrer Wrote: ------------------------------------------------------- > I have two terminal windows open. > > In terminal 1 > kwboot shows spinning. > > In terminal 2 > screen /dev/ttyUSB0 115200 shows garbled > characters. I would check Tx and Rx lines to see they were reversed. Because kwboot handshakes with Boot ROM only, u-boot is not involved. And itby bodhi - uBoot
Tinkrer Wrote: ------------------------------------------------------- > Appreciate your quick reply. > > Yes. I did try with the binary that you posted. > > ./kwboot -t -B 115200 /dev/ttyUSB0 -b > uboot.2014.07.tld-1.goflexhome.mtd0.kwb -p > > I do not have another ARM plug. > > The | character continues to spin :-( > > - Tinkrer Does theby bodhi - uBoot
Hi Looker, Did you install the same u-boot using Arch installation on the other Pogo E02 that still work with Pogo OS?by bodhi - uBoot
Thanks Gray! LouisV did report the typos: http://forum.doozan.com/read.php?2,11663,16696#msg-16696 I've updated the post to indicate that. QuoteAs feedback, I would like to see the "mmc_bootcmd" and "sata_bootcmd" (<devicetype>_bootcmd) as the standard. The reason I use bootcmd_xxx postfix was to follow the same convention that Jeff used originally. It iby bodhi - uBoot
LouisV, Quote> As per my potentially flawed interpretation of > your directions I changed > > mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage) > ,32M(rootfs),-(data) > > back to > > mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage) > ,3M(uImage2),8M(failsafe),112M(root) > This is correct interpretation. Each box potentially has different mtdpaby bodhi - Debian
LouisV, Cool! just what I've suspected, the older MMC driver in davygravy's version might have problem with some SD cards. The kirkwood MMC driver used by ebbes is working much better.by bodhi - Debian
Darn! :) Thanks for testing it! I might have an editing error in that bootcmd.by bodhi - Debian
Tinkrer, Did you download the u-boot I posted? if you did, the command is: ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07.tld-1.goflexhome.mtd0.kwb -p And if you have another ARM plug, then you can use the kwboot binary I uploaded in that same thread.by bodhi - uBoot
@LouisV, Quote> Pogov4> ext2ls mmc 0:1 /boot > ext2ls mmc 0:1 /boot > > > I'm not sure, but shouldn't I see the boot files > listed? > > Pogov4> ext2ls mmc 0:1 / > ext2ls mmc 0:1 / > <DIR> 4096 . > <DIR> 4096 .. > <DIR> 16384 lost+found > <DIR> 98306 proc > <DIR>by bodhi - Debian
agiorgio, Ignore the UBIFS errors, they are expected.by bodhi - Debian
LouisV, > I have been using gparted (which worked fine with > the USB stick). Is the SD card MBR or GPT?by bodhi - Debian