novaforme, Your bootcmd is messed up! > bootcmd=nand read.e 0x800000 0x100000 0x300000; setenv bootargs $(console)\ > $(bootargs_root); bootm 0x800000 Should be bootcmd=run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; reset Update: And this is wrong too: mainlineLinux=no should be mainlineLinux=yesby bodhi - uBoot
Peacemaker, For some info about GPIO and U-Boot take a look at 2013.10 U-Boot for Pogoplug V3 (OXNAS). I've added some code to control the LED during booting. And I've updated the SPL to 850MHz: http://forum.doozan.com/read.php?3,16017,page=3by bodhi - Debian
herb Wrote: ------------------------------------------------------- > bodhi consider the 4TB a full success! > I pulled the drive from my NSA320 and stuffed it > in the NSA325 and it simoly came up no > problems;-) > > Herb Cool! thanks for testing. That's the last checkmark. I am adding the uEnv loading capability, and we'll be done.by bodhi - Debian
Paging gnexus !!! http://linuxgizmos.com/hackable-39-allwinner-a20-sbc-packs-hdmi-and-gbe/by bodhi - Allwinner A10
@jfharper, Before you flash the orignal u-boot to the bad GFH, try booting it with my uploaded Debian rootfs: http://forum.doozan.com/read.php?2,12096 I looked over u-boot envs listed in serial console for the bad GFH, and did not see anything wrong. So perhaps something wrong with your Arch rootfs? best to try booting with Debian rootfs that we know working.by bodhi - uBoot
jfharper, I will respond in detail when I got home. Pls see below for short answers. Wrote: ------------------------------------------------------- > So the way I understand it, the NAND is my Flash > memory on the GFH board. It contains some > partitions, and each partition has some stuff > written on each partition. The stuff are > utilities know as MTD utilitiesby bodhi - uBoot
herb Wrote: ------------------------------------------------------- > command line: > time ./kwboot -t -B 115200 /dev/ttyUSB0 -b > ./uboot.2013.10-tld-1.nsa325.uart.kwb -p > > result: > real 0m32.111s > user 0m0.076s > sys 0m0.270s > > bodhi, you say you've been using the nand version. > Are there any problems??? > I'll flash it to nanby bodhi - Debian
jfharper, Your dmesg shows: Creating 3 MTD partitions on "nand_mtd": 0x00000000-0x00100000 : "u-boot" 0x00100000-0x00700000 : "uImage" 0x00700000-0x10000000 : "root" So you should go with this actual layout as the original MTD parts.by bodhi - uBoot
Hi Herb, Did you time the UART loading? on mine it's 30 seconds. The test we need is internal SATA, GPT larger than 2 TB.by bodhi - Debian
@Jharper, Can't hurt using kwboot. Instruction to download in my u-boot thread: QuoteImportant Note: If possible, try to test this boot image with UART booting before flashing to NAND. See davygravy's UART booting using kwboot instruction: here in this thread. To download ARM kwboot binary for UART booting at Dropbox: kwboot md5: 0efd011bdb244436e432a8de33e639a1by bodhi - uBoot
@ jfharper, Great! but be careful about the mtd parts definition, they are different. Stock has 3 mtds, your current u-boot has 4 mtds, and the locations are different too, except for mtd0.by bodhi - uBoot
Ian, This is the problem with mounting rootfs. The kernel was loaded ok. Try these possible remedies, in order: - take the USB drive to another Linux box and check for file system error with fsck. Plug it back in and power up. - make sure the USB file system format is Ext2 or Ext3 (because your rootfstype is Ext2). - if the above did not help, download the latest Kirkwood rootfs tarball (by bodhi - Debian
Ian, Usually netcosole output stops there. LED green solid is good. So look for the plug on the network (your router web page, or use nmap tool to scan the network). Btw, your u-boot and kernel versions are a lttle old. See the latest u-boot and kernel in my signature.by bodhi - Debian
jfharper, > > GoFlexNet> nand bad > > Device 0 bad blocks: > GoFlexNet> nand info > > Device 0: nand0, sector size 128 KiB > Page size 2048 b > OOB size 64 b > Erase size 131072 b > GoFlexNet> > You are on the right track. The above shown that the bad blocks that we saw in Debian were not really bad blocks afby bodhi - uBoot
@Kevin, You are going in reversed :) usually we install customized version of u-boot to get more capability, instead of using the mainline u-boot. What you had before was either Jeff or Davygravy u-boot (2011, 2012). And you have installed the mainline version on top of it. If you're looking for a newer u-boot to take advantage of modern features, see this thread for my builds of 2014 u-by bodhi - uBoot
Juan C. Galvez, In serial console, get the output of printenv and the boot log from begining until the above rootfs mounting error, and post here.by bodhi - uBoot
Twinclouds, It's in the kernel tarball in the kernel and rootfs thread. QuoteUpdated 04 April 2014: Kernel 3.14.0-kirkwood-tld-1 package was uploaded. This kernel 3.14 release has lots of new features: LinuxChanges log I have also incorporated the following requests: pbg4's patch for dvb-usb-dw2102, tt-s2-4600 and some other dvb-usb S2 devices Request for more USB HIby bodhi - Debian
@WarheadsSE, Yeah. It's kind of a pain to revisit the default envs for other boxes :) Some are OK, but a majority need to be rewritten. Perhaps now is the time to do it. I've looked at what Kevin did for Arch mainline U-boot, and I think it is really nice and flexible. I've tempted to cut and paste those in, but decided otherwise. I'd like to keep the envs as simple andby bodhi - uBoot
@shv, Yes, the root=LABEL=rootfs argument only works with initrd. So if you boot either stock, or Arch kernel, you would have to create this ramdisk file separately and use it for booting. There is just no generic way to boot correctly on Pogo V3 to boot with several USB and SATA drives attached. However, in a specific case, you can set u-boot env to boot correctly. For example, booting USBby bodhi - uBoot
@herb, The new u-boot kills the watchdog at the moment u-boot starts. To download the latest pre-release nsa325 u-boot: http://forum.doozan.com/read.php?3,12381,17420#msg-17420 What you saw were the watchdog behaviour and have been discussed and analyzed thoroughly in this thread: http://forum.doozan.com/read.php?2,14351 QuoteHas anyone else seen the power led come on, then off and thby bodhi - uBoot
@WarheadsSE, So do you want to do the rebase first, and then merge. Or, do you expect we will stay with 2013.10 branch for the NSAxxx for a long while?by bodhi - uBoot
sunfire, There is no way for me to tell what's wrong without the entire serial boot log :)by bodhi - uBoot
Understood. But uEnv.txt loading will work only if the load command is available in U-boot. It was not enabled in u-boot-kirkwood 2013.10 branch. There was a conflict between the generic FS load/ls with the jffs2 flsload/ls and I did not try to resolve it in 2013.10 branch. I've fixed it in my local 2014.07 build to enable load command, and will push a new version to the 2014.07 branch.by bodhi - uBoot
@shv, Your set_bootargs_usb looks OK. 3. Incomplete because these are possibe variations of bootm command: bootm command for booting with the uInitrd and DTB: bootm 0x60500000 0x60e00000 0x62c00000 booting command for booting without the uInitrd and DTB: bootm 0x60500000 - 0x62c00000 booting command for booting with the uInitrd and embedded DTB: bootm 0x60500000 0x60e00000by bodhi - uBoot
WarheadsSE Wrote: ------------------------------------------------------- > Now if we could get it to support uEnv.txt . It is already in my latest local build for 2014.07 (have not realeased or pushed to GitHub yet). The load command is common to all boxes, so I've been holding off on that and it wil be automatically picked up when we rebase this to 2014.07.by bodhi - uBoot
@shv, Possible improvements: 1. When you try to boot either the FDT kernel or non-FDT kernel, it is best to have 2 separate set of boot envs. It'll make it easier to code and debug. 2. To ensure booting the correct rootfs when multiple drives connected, the USB rootfs should have partition label rootfs, and: usb_root=LABEL=rootfs 3. And this is not completed: usb_boot=ext2loby bodhi - uBoot
@WarheadsSE, Here is the patch for ./include/configs/nsa325.h. The evns will boot USB and then SATA. It's been tested for booting the USB rootfs when the envs location 0xC0000 has not been written before.by bodhi - uBoot
@ theliquid, So are we good with the wireless and 3G config additions? is there anything unresolved?by bodhi - Debian
Ah! that I did not try. I always flash a default env image from here: Quotea. Download the default u-boot envs at Dropbox: uboot.2014.07-tld-1.environment.img.bodhi.tar md5 c5921e3ea0a07a859878339ffb771088 So I forgot :) But yes, we do need this in case of bad blocks. I'll will incorporate a default set to boot USB.by bodhi - uBoot
@WarheadsSE, It's time for NSA325 GitHub? I think we've done testing out the functionalities. The only thing we have not tried is booting SATA >2TB rootfs.by bodhi - uBoot