@jochar, Unfortunately, it is a little complicated to do this, using stock u-boot. 1. Plug in the USB and power up 2. Interrupt serial console,check if your stock u-boot can boot USB: usb start If the usb command is available in u-boot, you should see the drive started. And then can try to boot USB with a few changes in envs (basically the same as normal usb booting in other u-boot iby bodhi - uBoot
rickgtx Wrote: ------------------------------------------------------- > I have a Pogoplug E02 that has beed updated with > Jeff's U-Boot and like to install Bodhi's U-Boot. > The Pogo E02 will not boot from a 3T Drive. It > just goes to the rescue system: > > U-Boot 2011.12 (Feb 20 2012 - 21:21:59) > Pogoplug E02 > arm-none-linux-gnueabi-gcc (Sourceby bodhi - uBoot
Peter, It's quite easy. Because what you've installed was Arch kernel in NAND. And you can leave that untouched if you install new u-boot and kernel and boot with USB or SATA. u-boot: http://forum.doozan.com/read.php?3,16017 debian kernel & rootfs (this thread): http://forum.doozan.com/read.php?2,16044 Note: if you want to run Arch then you need to compile the kernel.by bodhi - Debian
Eddie, > I've got UART booting to work with the test image > as a failsafe and have got as far as checking for > bad blocks on the NAND chip. I've received the > following message: "Bad eraseblock 599 at > 0x000004ae0000" > > Am I right in thinking this is fine when it comes > to flashing uboot? Yes. It is fine to flash. BTW, it's gooby bodhi - Debian
zweik, > (there is a undefined symbol at the end, what i > can't post here.) > Do you mean this. If not, where i can found the > log? Yes, this log was what I meant. If nothing happened after this (u-boot image did not start running) then the new u-boot did not work. See what I recommended here: http://forum.doozan.com/read.php?3,12381,18996,page=15#msg-18996by bodhi - Debian
jochar, Try running the rootfs for NSA320 first as an experiment. Memory capacity is not the same, but if everything else works the same way then it's not hard to make the DTS file for NS320S. Download this 3.17 rootfs and put it on USB stick, boot with it and please post serial boot log and dmesg if successful. http://forum.doozan.com/read.php?2,12096by bodhi - uBoot
Jörg, > Finally one question... My ubuntu server do I > update with following command: > apt-get update && apt-get dist-upgrade && apt-get > autoremove > Can I use this also for the rootfs Pogoplug? Yes, the similar commands. However, don't do dist-upgrade. Upgrade is enough to get the latest version of all packages. OTOH, dist-upgrade will replace tby bodhi - uBoot
Robert, You u-boot setting is set to boot the kernel 3.17 with DTB embedded inside uImage. Did you do that? The error seems to point to that problem. Method 4b. Boot with DTB file embedded in the kernel image (no U-Boot envs change needed) in the kernel thread.by bodhi - uBoot
zweik Wrote: ------------------------------------------------------- > Hello bodhi, > > thank you for the hint. I try to make a UART > booting with kwboot. But after the line "" i only get one undefined > symbol. Do this mean that the u-boot do not work? > > > Greeds Please post the entire serial boot log.by bodhi - Debian
Eddie, If you have serial console, and can boot with UART, then risk of bricking is minimal. New u-boot has no problem with SATA using the same Kirkwood driver as other boxes do.by bodhi - Debian
Eddie87 Wrote: ------------------------------------------------------- > Sorry if this has been asked before, are there > issues with activating both SATA ports? I've read > this thread and several others but can't seem to > work out if this is an actual issue with Bodhi's > 3.16 or 3.17 Debian packages, or whether it's just > me. > > I know pby bodhi - Debian
fatal Wrote: ------------------------------------------------------- > Please bodhi or dannyboy2322 send me a full > procedure to recover my goflex home as I have > ended the step of flash install and my goflex led > shows steady green light. After that I can't see > any webUI it is even not shows mac address of the > goflex in arp table. > Thanks in advance.by bodhi - uBoot
dinjo Wrote: ------------------------------------------------------- > Any help here on wget im getting 20% of my > download speed. No idea. It could be the site that you wget from is slow, have you tried wget with different sites?by bodhi - Debian
Awesome! Next question: which DTB you have used to append to the uImage? the link you posted above could not be translated to English!by bodhi - Debian
There is a newer u-boot for NSA320: http://forum.doozan.com/read.php?3,12381,16787#msg-16787 But you need to try with UART booting first to make sure it works before flashing to NAND. It has not been tried on NSA320S before so I don't know if it will work. So be careful!by bodhi - Debian
Jörg, IIRC, your u-boot version set rootfstype to Ext2. Ext3 would work, but just to make it consistent you should use Ext2.by bodhi - uBoot
balbes150, Cool! can you post the output of dmesg? and boot log if you have serial console.by bodhi - Debian
Jörg, Everything looks good. You are running davygravy 2012 u-boot and the envs were flashed successfully. davygravy's Pogo E02 u-boot does not flash LED during booting. Look for the Pogo in your network (it's dynamic IP) router. Or if you have smartphone, use Fing to scan all the nodes in the network. Next step If you can't find it: Do you have a log of how you created tby bodhi - uBoot
Buttzy, Do you have serial console log for this? dmesg is not enough, rootfs mounting progress is shown only in serial console.by bodhi - Debian
Buttzy, So the problem is only after you've installed OMV? booting USB with the basic rootfs is OK?by bodhi - Debian
punker Wrote: ------------------------------------------------------- > Hi, > > is there a kernel for my iConnect with bluetooth > support? > > lg Yes. http://forum.doozan.com/read.php?2,12096by bodhi - Debian
OK, You can SSH in to the pogo again and do this: http://forum.doozan.com/read.php?3,18917,18935#msg-18935 Remember to keep the log of everything.by bodhi - uBoot
Jörg, Execute with full path: /usr/local/cloudengines/bin/blparam > /tmp/u-boot-envs.txtby bodhi - uBoot
Buttzy, It sounds as though there is no power to the USB port.by bodhi - Debian
Buttzy, Your dmesg looks OK: [ 1.838190] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.844847] ehci-pci: EHCI PCI platform driver [ 1.849391] ehci-orion: EHCI orion driver [ 1.853641] orion-ehci f1050000.ehci: EHCI Host Controller [ 1.859174] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1 [ 1.867110] orion-ehci f10by bodhi - Debian
cr2013, The envs look quite ugly :) I know people have set it up this way long time ago to get it working with stock u-boot. Now it is no longer necessary when you install new u-boot. Back to the problem. This is suspected: bootargs=console=ttyS0,115200 ramdisk=32768 mtdparts=orion_nand:0xc0000@0x0(uboot),0x20000@0xa0000(env),0x300000@0x100000(zImage),0x300000@0x540000(initrd),0x1f40000by bodhi - Debian
@duncan_h and others, I've updated the instruction regarding the uEnv.txt in the 1st post. I've modified it slightly to make it a little easier to remove the devices that are not availble (so you won't see the error messages about non-existing devices). D.1 Modify u-boot envsby bodhi - uBoot
Buttzy, Yes, with davygravy's u-boot (which does not have FDT support), the DTB must be appended to uImage. Everything looks great to me, espcially this about USB [ 2.243635] usb 1-1: new high-speed USB device number 2 using orion-ehci [ 2.405385] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608 [ 2.412145] usb 1-1: New USB device strings: Mfr=0, Product=1, Sby bodhi - Debian
Jörg, This install_uboot_mtd0.sh can not be run on the laptop. This u-boot installation script must be run on the pogoplug itself. My recommendation: 1. Make rootfs on another Linux box, use a single Ext3 partition (following instruction in the kernel thread I posted above). 2. SSH into the Pogo OS and run: cd /tmp wget http://jeff.doozan.com/debian/uboot/install_uboot_mtd0.shby bodhi - uBoot
> > Fdisk /dev/sdb, o, n, 1st partition using full > disk, w > mkfs.ext2 /dev/sdb1 (tried both ext2 and ext3 with > no change) > e2label /dev/sdb1 rootfs > mount /dev/sdb1 /meda/sdb1 > cd /media/sdb1 > tar -xjf > /home/user/Debian-3.17.0-kirkwood-tld-1-rootfs-bod > hi.tar.bz2 > > <insert whole FDT mkimage procedure here, placing > iconneby bodhi - Debian