@Val532, Try this attached bin: tftp 0x80000 uboot.2014.07-tld-3.d2net_v2.bin go 0x80000 I'm not sure that it's going to work chainloading from a much older u-boot to this version. But it's worth a try :)by bodhi - uBoot
Val532 Wrote: ------------------------------------------------------- > Sorry but it's not the netspace_v2 but the D2 > network v2. > And in this web site i have not found > d2-network_v2_config or something else. So you do indeed have the D2 Net V2, not the Nespace V2. That's what I did built the image for previously. This D2Net_V2 variant has arcNumber 2203. OKby bodhi - uBoot
Val532 Wrote: ------------------------------------------------------- > @bodhi > > So i tried to load it by tftp methode by this way > : > > tftp 0x800000 uboot.kwb (i rename the file) > then > go 0x800200 > > and nothing happens. > > I found on the net a uboot ( version 2011.12 on > this web site > http://lacie-nas.org/doku.php?id=ubooby bodhi - uBoot
InfoScav, > 9. Erase 1 block starting 0x00100000 (See caveat > in step 2, do not do this step this if the kernel > is stock kernel, or not a FDT kernel) > > > /usr/sbin/flash_erase /dev/mtd0 0x00100000 1 > > Erasing 128 Kibyte @ 100000 -- 100 % complete > > > > 10. Flash uboot environment to 0x00100000 (See > caveat in step 2, do not flasby bodhi - Debian
LeggoMyEggo, > > If I can't do this from the OS level, is it > guaranteed to be changeable at the serial console? > I have to admit, I was kinda hoping that I would > have at least one PP that I didn't have to crack > open as that would indicate a little bit of > acquired skill and Linux mastery :) You can also change it in netconsole since you'reby bodhi - uBoot
You should be able to change it. If not, it's either mtd0 is not defined, or it is loaded as readonly by the kernel. Which u-boot and kernel? Btw, The default is set to a randomly generated local MAC address which is perfectly ok to use if it cannot be changed. But the problem should be fixed regardless.by bodhi - uBoot
Val532, > So the "uboot.2014.01-tld-1.d2net_v2.mtd0.kwb" > file does not work on my machine. In what way that it did not work? does UART booting work at all on this box? or did you try tftp or ext2load? > So for the moment I do not want a "flashable" file > but a bin file that I could load into launch via > TFTP. Not a problem rebuilding it, but Iby bodhi - uBoot
See if you can find the card: lspci -vvby bodhi - Debian
bodhi Wrote: ------------------------------------------------------- > Zyxel Nsa325 & 320 users, > > Here are the latest NSA325 and NSA320 > U-Boot-2014.07 for testing before release. These > u-boot images incorporated all of the latest > features as in other Kirkwood u-boots in the first > post. Anybody have run this on NSA320? I'd like to have feedbacksby bodhi - uBoot
InfoScav, > 1. prepare a rootfs with > Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2[ > on a linux-box > > 2. then install the new u-boot on pogo pro > > 3. plug in the new rootfs in pogo pro > Reboot at this point. > 4. install the latest kernel > linux-3.18.5-oxnas-tld-1-bodhi.tar.bz2 > (using the procedure outlined for plug with new >by bodhi - Debian
@InfoScav, See here for serial console parts: http://forum.doozan.com/read.php?8,13263 Yes, you can just SSH in and install it in Pogo OS. Serial console is just a precaution in case something goes wrong while flashing u-boot.by bodhi - Debian
@LeggoMyEggo, > if you could provide some pointers on how to load > mkenvimage on my linux box that would work too. I've realized I've missed this question! the reason you have problem loading this command because it is part of the u-boot build. It is not in Debian repository. So to run this and create a proper u-boot env image, you can use the attached binary in this postby bodhi - uBoot
nat, > - I tried to use the Jeff syntax for searching the > USB drives for the boot files with the 2014-07 > uboot, but it just wasn't working. It didn't like > the "usb=1 dev=sda1" syntax during the usb_scan > tests, and issues a series of "** Bad device ** > errors. So I dropped back to the Jeff uboot and > have it sorted out. Is the Jeffby bodhi - uBoot
Here is what the internal default envs look like. OX820> printenv autoload=no baudrate=115200 bootargs=console=ttyS0,115200n8 bootcmd=run bootcmd_uenv; run dt_bootcmd_usb; reset bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi bootdelay=10 console=console=ttyS0,115200n8 devices=usb ide dt_bootcmd_usb=usb start; run dt_usb_bootcmd; usb stop; resetby bodhi - uBoot
LeggoMyEggo Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > @ LeggoMyEggo, > > > > Please install and try this release version. > You > > only need to flash u-boot image (the SPL and > Pogo > > env are the same images). > > > > Droby bodhi - uBoot
LeggoMyEggo, > So this u-boot by default checks to see if there > is a uEnv.txt file in /boot before it > executes the bootenv's stored in nand? Is that > correct? Yes it does, but in reverse. u-boot envs are always checked before anything else. However, if the check failed because the NAND block is bad, then it will set the envs to the default values internally definby bodhi - uBoot
@ LeggoMyEggo, Please install and try this release version. You only need to flash u-boot image (the SPL and Pogo env are the same images). Dropbox: uboot.2013.10-tld-5.ox820.bodhi.tar md5: bf385f83b42cdeee1f2ecbf53f6cdec5by bodhi - uBoot
nat Wrote: ------------------------------------------------------- > Oops, sorry to have missed that. For whatever > reason, probably because of the long history of > posts in the forum or a lack of imagination in > search terms, I have a tough time locating the > exact post I am looking for. Thanks again for > your help. NP. It is indeed hard to search for this topiby bodhi - uBoot
kanote, The problem: [ 7.547057] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:00:00:00:00:00 Interrupt serial console and: setenv arcNumber 3960 setenv machid F78 setenv ethaddr 00:25:31:05:12:c6 saveenv bootby bodhi - uBoot
nat, > I see that Jeff's old uboot script sets up a scan > of all of the USB drives to locate the correct > device with the uImage on it and I could > incorporate this scan in my variables. Is this > the right way to fix this problem under newer > versions of uboot by Bodhi? Yes. I mentioned it in this thread (in my signature): u-boot & kernel booting procesby bodhi - uBoot
afuchs, Because of there are 2 partitions on the disks, it might have caused the problem with mounting rootfs. it is best to try these (in order): 1. Create a USB drive with only 1 partiiton that contains the rootfs extracted to it (remember to use the embedded uImage approach). Also, be sure to do this as root. And boot with it. 2. If that does not work, look at this partition labelby bodhi - Debian
LeggoMyEggo Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > In your case, you can't save the envs at all > > because the NAND block is bad, so you will have > to > > rely on the default envs internally defined by > > u-boot. The default bootcmd env mustby bodhi - uBoot
@LeggoMyEggo, > I am having trouble booting using uEnv.txt in > /boot while attempting unsupervised (i.e. no > serial console) from a cold start. Am I mistaken > in thinking the new u-boot automatically loads the > uEnv.txt file and does a "saveenv" before going > any further? Sorry LME, I've have misses a file version in the build :) that's wby bodhi - uBoot
Zyxel Nsa325 & 320 users, Here are the latest NSA325 and NSA320 U-Boot-2014.07 for testing before release. These u-boot images incorporated all of the latest features as in other Kirkwood u-boots in the first post. Successful UART booting with serial console is required as a recovery path, since you're going to need to flash these to NAND. So please try these only if you have bootby bodhi - uBoot
JanN, > I need 3.3V > from the serial for that, right? No. Do not connect power to the serial port!by bodhi - Debian
JanN, I'm going to release a new test version for NSA320 and NSA325 u-boot (2014.07) soon. WarheadsSE did mention some odd behaviour in that if you disconnect serial console, the NSA320 is not booting. But all that might be related to the stock u-boot quirk in USB power (I could be wrong). I can't give any advice on stock u-boot. IMO, we should just ignore its problem and flash tby bodhi - Debian
Hey Joey, Remember about how long did it take for you to be well verse in Windows (I mean the admin stuff)? It will take time to get use to embedded Linux. Even experienced desktop Linux users have to struggle a bit at the beginning (look at posts at various forums). If your goal is to install the system asap and then deal with applications only, then yes, choose a distro that enable you to doby bodhi - Off-Topic
LeggoMyEggo, > I loaded the latest u-boot and created uEnv.txt in > /boot and IT WORKED ! :) Cool :) > bootcmd=run dt_bootcmd_usb I don't think it is needed, or will take effect at all, since the uEnv.txt is loaded as part of the default bootcmd (but it does not hurt anything). To verify the sequence, boot with serial console, interrupt it, and then do printenvby bodhi - uBoot
Joey, Here is another option: the GoFlex Desk Base with USB 3.0. A lot of people bought the GF Desk to use the internal 3.5" HDD, and then sell the base on eBay. You might be able to get it cheaper than the adapter in your link. And the bonus is USB 3.0 i/f, just in case you ever get the Pogoplug V4, or connect it to a USB 3.0 port on PC/Mac. And no worry about the correct power source.by bodhi - Off-Topic
droidbox, Did you use the uEnv.txt to boot into Debian sucessfully?by bodhi - uBoot