iptester Wrote: ------------------------------------------------------- > Hi, > > ok, so I tried and tried more than 100 times and > no handshake occurs. > may be I could try with a different kwboot version > or a different pogo 4 u-boot ? Please post what you see when you attempt UART booting. Do you see any error message after you ctrl-C, up arrow, re-execute kwbooby bodhi - uBoot
Looks like the bootcmd is also bad, should reset it to: setenv bootcmd 'run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; reset' And then bootby bodhi - uBoot
@Christian, ALARM u-boot should have no problem with tftp (I have only run it once for experiment, though). Can you ping any computer from the serial prompt? or just the tftp server is out of reach? For sanity, you could use UART booting and boot my u-boot image (download both u-boot and kwboot using links from the 1st post): http://forum.doozan.com/read.php?3,12381 Further thought:by bodhi - Off-Topic
rustyspoons, > will the environments script in this > guide work? or will I brick the V4 > > http://vortexbox.org/forum/vortexbox/general/51318 > -install-vamp-0-6 You will brick it with that procedure! See this u-boot: http://forum.doozan.com/read.php?3,12381by bodhi - uBoot
What does your u-boot banner looks like, i.e version? I doubt that tftp does not work in Jeff or davygravy u-boot. It is a very fundamental command, and I remember using tftp from way back. Did you double check by pinging the server, make sure the tftp server is running, the file is at the tftp root folder, .… things like that?by bodhi - Off-Topic
Frederick Grayson, > I'm not running a netconsole listener (socat) when > I am looking at the serial console. It does not really matter whether the netconsole listener is running or not. If the serverip of the listener is the IP of a running box that responded to the 5 pings (might be the one running serial console), then you won't see the count down in serial console (becby bodhi - uBoot
devinger, When you see the u-boot banner, and the countdown: > U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:59:45) > Pogoplug V4 > > SoC: Kirkwood 88F6192_A1 > DRAM: 128 MiB > WARNING: Caches not enabled > NAND: 128 MiB > MMC: kwsdio: 0 > In: serial > Out: serial > Err: serial > Net: egiga0 > Warning: failed to set MAC addressby bodhi - uBoot
iptester, Quote> 3- I turn off my bricked pogo 4 This is wrong. Don't turn off the Pogo V4. Here is the sequence again: Run kwboot ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-1.pogo_v4.mtd0.kwb -p 2- turn on the bricked Pogo v4 and after 1-2 seconds (nothing will happen). 3. Then Ctrl+C. Use the up arrow to recall the kwboot command, hit enter. Keep doingby bodhi - uBoot
cmoewes, You need to define serverip and ipaddr before you can use tftp. Serverip is the IP of the tftproot machine, and ipaddr is the IP of this GFHome. Example: setenv serverip 192.168.0.100 setenv ipaddr 182.168.0.200by bodhi - Off-Topic
> > EDIT: problem solved by installing Bodhi headers. This. If you plan to compile any module, the 1st step is to install the kernel headers.by bodhi - Debian
Frederick Grayson Wrote: ------------------------------------------------------- > It really works, I rebooted half a dozen times and > got netconsole output on all of them on socat > running on Win 7. > > However, on the serial console of the E02, it > can't be interrupted to get to a Uboot prompt. > There is no countdown displayed. If your serial console anby bodhi - uBoot
sunfire Wrote: ------------------------------------------------------- > @bodhi > > Thanks for the new kernel, > > but the watchdog problem still exists :( Please remind me to try my 4TB if I forget.by bodhi - Debian
Stefnas, I'm still testing the kernel. It seems PowerOff is broken in 3.17, at least for me it is.by bodhi - Debian
Addy, Use rootfs label: http://forum.doozan.com/read.php?3,8044,8152#msg-8152by bodhi - Debian
Frederick Grayson, I gave it some thought. It's not elegant enough but should do the job. This should work on u-boot 2011.12. - start netconsole server on the other box - In Pogo E02 serial console: setenv preboot_nc 'setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netby bodhi - uBoot
Stefnas, Ah I see. However, I'm building kernel 3.17 FDT for NSA325 right now, and it has wakealarm root@Nsa325:~# ls /sys/class/rtc/rtc0/ . .. date dev device hctosys max_user_freq name power since_epoch subsystem time uevent wakealarm Update: It does work in my kernel 3.17 build.by bodhi - Debian
FWIW, I'm still not convinced that cryptodev on our plugs is stable yet. There have been reports of problems (memory corruption), some were fixed with certain patches or backports. But be careful to trust it with your important data, it should be considered experimental.by bodhi - Debian
Stefnas, NSA325 WOL and RTC have been working in the latest 2 kernel version (3.16.0-kirkwood-tld-2 and tld-3).by bodhi - Debian
There is hope! You can unbrick the Pogo V4 with UART booting: - Download the latest Pogo V4 u-boot and kwboot from this thread: http://forum.doozan.com/read.php?3,12381 - Start kwboot on a different Linux box ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07.tld-1.pogo_v4.mtd0.kwb -p - Power up the Pogo V4 - Within 1-2 seconds (but not too soon), Control-C to abort kwboot, and rby bodhi - uBoot
hachigo, > I thought it was necessary in case I break > something as per the instructions. > > I'm trying to learn as much Linux as I can with > this pogoplug and I'm more than likely going to > breaking somethings as I go. > Something got lost in the translation :)) By QuoteWhat do you use for netconsole server I meant what program do you run foby bodhi - uBoot
FYI, in case others coming across this while looking to solve serial connection problem. In my observation, the serial module type PL2303 pinout is a "true" pinout so so we always have to cross TXD and RXD lines when connecting to the plug. RXD-TXD, TXD-RXD. otoh, the serial module type CP2102 pinout is already crossed (i.e. the marker actually tell you what line on the plug to cby bodhi - uBoot
blackdevil, > I want to boot every time automatically the > "bootcmd". But i have to stop the autoboot and > start with the command "run bootcmd", otherwise > the System boots the original firmware from NAND, > and not the debian from disk. Any hints? You did not post the u-boot banner so I don't know which version. However, try this first:by bodhi - Debian
The Best Isaac, > I tried your linux-3.16.0-kirkwood-tld-3 kernel on > my NSA 310 but it doesn't boot; I get the > following error: "Error: unrecognized/unsupported > machine ID (r1 = 0x00000d0b)." arcNumber for the NSA310 in the mainline is 4022, which in hex is 0xFB6, so you should set both arcNumber and machid to correct values. WARNING: should only do tby bodhi - Debian
davidedg, > AFAIK, now there's a new repo which tracks more > recent kernels: > https://github.com/pkirchhofer/nsa325-linu > x-upstream Thanks. I'll take a look there. > > So this should not be needed anymore, but had not > a chance to test it (just too happy with your new > u-boot and your kernel patches ;P) > Bye! :) glad it works well. Iby bodhi - Debian
jst818, > But without usb attached i still get: > Quote > U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:29:52) > Pogo E02 > gcc (Debian 4.6.3-14) 4.6.3 > GNU ld (GNU Binutils for Debian) 2.22 > Hit any key to stop autoboot: 0 > (Re)start USB... > USB0: USB EHCI 1.00 > scanning bus 0 for devices... 2 USB Device(s) > found > scanning usb for storaby bodhi - uBoot
@davidedg, I have quite a few problems running this nsa325 DTS in kernel 3.17. May be it needs to be re-structured.by bodhi - Debian
addy75, QuoteSometimes it continuos and stopps while scanning the 4TB HDD. Whitout the 4TB it boots. Is this really the uboot? No, it is the watchdog, which resets the box when you take too long to boot with the 4TB. QuoteWill there be a new uboot soon? You can bug WarheadsSE :) Warhead will do a GitHub release after he's happy with what we have. And then I will release it heby bodhi - Debian
> Error: arch/arm/boot/dts/kirkwood.dtsi:2.1-9 > syntax error > FATAL ERROR: Unable to parse input tree Have figured out why this error occured. On to the next error!by bodhi - Debian
Yes, you can set the envs manually one by one using envs in that post, or use the attached script in this post to set the default set of envs: - Put this script on your rootfs USB /boot directory: /boot/uboot.2014.07-tld-1.environment.scr - Interrupt serial console - Execute command: > usb start > ext2load usb 0:1 0x800000 /boot/uboot.2014.07-tld-1.environment.scr > source 0by bodhi - uBoot
@davidedg, I'm testing kernel 3.17 FDT for all Kirkwood boxes. I am trying to compile the DTS file kirkwood-nsa325.dts, which I got from pkirchhofer Git (mentioned in your previous post, thanks!) And I got the syntax error: Error: arch/arm/boot/dts/kirkwood.dtsi:2.1-9 syntax error FATAL ERROR: Unable to parse input tree Have you seen this? all other DTS files compiled OK. Thanby bodhi - Debian