LeggoMyEggo Wrote: ------------------------------------------------------- > For experimentation with what I suggested, you > could use SillyPutty or Playdoh - maybe put some > non-marring masking tape down first so you don't > have to worry about oil staining. Thanks! Interesting: putty & playdoh :) about the Dynamat, certainly inexpensive if I can find a small sizeby bodhi - Off-Topic
Val532, I've just noticed that you did not use the option -p in your kwboot. It should be used because it is a NAND version. Sorry, I should have mentioned that. root@debian:/media/usb# ./kwboot -t -B 115200 /dev/ttyACM0 -b uboot.2014.07-tld-3.d2net_v2.kwb -pby bodhi - uBoot
@Rainer, Gravelrash is right on the money about your third option. QuoteThey are all good options. One thing to note is that the http://www.amazon.fr/niceeshop-PL2303HX-RS232-Module-Convertisseur/dp/B00F167PWE/ref=sr_1_6?ie=UTF8&qid=1426935789&sr=8-6&keywords=PL-2303HX will be difficult to fit to the headers, without some form of modification, either to the pogoppluby bodhi - Debian
TEN, That was a job very well done! If you'd like, please post your procedure here in the U-Boot section when you're done with the details. I think it is great to have a manual procedure like that for others who need to do the same thing.by bodhi - uBoot
All, I've been running NSA325v2 only on demand with WOL, because I can't stand the noise. From what I've read (I don't have the V1) it is a great improvement over the V1. However, still it's just a little bit too much during the night, I can hear it from a different room (cursed with good hearing :). On a whim, I took the front panel door off, and now I can barely hearby bodhi - Off-Topic
TEN, Are there any other questions unanswered?by bodhi - uBoot
QuoteOn your uBoot's netconsole, entering things such as nand0,1 setenv mtdparts ... setenv devices ... will be passed on to the system booted from there but NOT persist through a reboot in the environment unless I do an explicit saveenv (i.e. Debian, Arch or Stock won't invoke that on their own at shutdown?) - so can be tried without a risk of bricking (as nothing gets written toby bodhi - uBoot
@grayman4hire, > Their uBoot is for ALARM and it works fine for > that. Yes, I agree, it should support Debian by > default, but maybe they want people using ALARM > and not Debian :) Right :)) But you can modify their u-boot envs to boot Debian, too. It was just not set up that way afer installation. > Regarding how the archlinuxarm uboot handles the > NAND partitby bodhi - uBoot
@Tomas, I'd suggest it's time to move this MD-related booting problem to a new thread! you can repost or point to the starting point of try to bring up run MD.by bodhi - Debian
@Rainer, As stated by others above, serial console is indispensible while modding. If you cannot get a serial console soon enough for whatever reason. Right now, you should: - Make sure that the kernel file uImage have the DTB embedded inside (retracing your step when you create the rootfs using the instruction in the kernel/rootfs thread) - Boot, interrupt netconsole, and get a listby bodhi - Debian
safarik Wrote: ------------------------------------------------------- > @bodhi DTB has the time when I compiled the > kernel. If I understand it correctly DTB is > included in the uImage. > > > safarik@ts-n:~/00zyxel/vanilla/linux-3.18.5/arch/a > rm/boot/dts$ ls -la kirkwood-nsa325* > -rw-r--r-- 1 root root 14262 bře 19 14:37 > kirkwood-nsa325.dtb > -rby bodhi - Debian
safarik, Something about your earlyprintk that does not seems to work. I would expect to see more in serial console (I could have remembered incorrectly, though). > When I search on internet about simillar problem. > People often solve it by "recompiling device tree" > -> > http://forums.xilinx.com/t5/Embedded-Linux/Got-stu > ck-on-Calibrating-delay-loop/td-pby bodhi - Debian
TEN, > As I could not find any recovery images for E02 > mtds1-3 or the entire NAND, I wonder if all but > mtd0 are identical bit for bit across V2s, since I > happen to have access to more of these black "pink > Pogos" in other places. Yes. They are identical. > with your uBoot (that would also let me set Arch's > partitioning). mtd0 is probablyby bodhi - uBoot
grayman4hire, > Agreed. Or moonman's arch version. Yes. I like what moonman did very much. Having latest kernel for a rescue system? fantastic!!!. I would go for that just in case I need to use it. But TEN needs to go back to 2 MTD partitions for that. Which is not a bad thing any mean, as I said I would do it for my personal boxes.by bodhi - uBoot
FelipeC Wrote: ------------------------------------------------------- > Hi Again Bodhi, im really sorry for the previous > post, i tried to erase it but i couldn't. > > I did the whole flash again and i manage to get > to the terminal console. However every time i > reboot the device, it doesn't start anymore, so i > have to re flash it and get to the terby bodhi - uBoot
Gravelrash Wrote: ------------------------------------------------------- > thanks for the benchmarks. gives me something to > compare mine against..... > doesnt surprise me tho, when its a single core > arm5te versus an armv6 dual core with faster > memory. Yes, dual-core the reason.by bodhi - Off-Topic
TEN Wrote: ------------------------------------------------------- > QuotebodhiOn Ubuntu you might need netcat > traditional. And: > nc -lup 6666 <pogoipaddr> > 6666 > Had been using that, though without the -l as its > manpage says that must not be alongside -p. > > Hammering Enter a few times during the countdown > did the trick, while socat would ofteby bodhi - uBoot
QuoteStill wondering what the 2 eraseblocks before and 1 after 0xc0000 are (reserved) for: If both U-Boot and fw_envs need to be replaced, would there be anything wrong with flash_erase /dev/mtd0 0 8 ? Must only erase first 4 blocks to install u-boot. The stock envs and the new envs are in the second 4 blocks in mtd0. They don't occupy the entire area, but the free blocks in between shouby bodhi - uBoot
@TEN, Here is my recommendation: you should install Jeff/davygravy rescue system if you don't care for Pogoplug service. These systems are much more robust with newer kernel and installed utilities.by bodhi - uBoot
Val532, Try the same method that we use for Pogo V4: When you see that "xmodem Protocol error", up arrow to recall the kwboot command and execute it again. Repeat this as many times as you can until the handshake is completed successfully.by bodhi - uBoot
tufkal, When you recompile using a different platform, different code generated (different library), so it might mask the bug on that platform.by bodhi - Debian
safarik, Try NSA325> setenv bootargs 'console=ttyS0,115200 earlyprintk=serial root=/dev/md0 rw rootwait loglevel=8 print_fatal_signals=1 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2)'by bodhi - Debian
@Rainer, You don't have to have everything in fstab. Just rootfs. The external HDD is not going to by checked for error if it's not in fstab. Add a mount statement in /etc/rc.local to mount it. That way you can delay mounting it the way you intended. For your purpose, it's best to use Ext3 for everything so that the system will survive any dirty shutdown (since you expectby bodhi - Debian
javatmn Wrote: ------------------------------------------------------- > That is a bogus number, i can not relate that with > any network params. Sounds like a coding error :) 3456 must be some default value somewhere. On your armhf system, which gcc version is used for compiling?by bodhi - Debian
@Yong, > Frankly speaking I do not think it is related with > kernel oddity. It is more likely an application > bug. Agree. Still good to see the config differrence because it might give some hints! Especially when you guys said that armhf 32-bit systems work fine. > It seems that the source ip is not extracted > corrected and cause the packet to be dropped. In > myby bodhi - Debian
Cool! On Ubuntu you might need netcat traditional. And: nc -lup 6666 <pogoipaddr> 6666by bodhi - uBoot
@Yong, Kudos! @tufkal, Please post the kernel config for this (after installing on the working box).by bodhi - Debian
TEN, > I.e. I could now reboot into that without further > changes (as would be required for FDT) ? > # ls -l /proc/device-tree/ > ls: cannot access /proc/device-tree/: No such file > or directory OK. So it is non-FDT. You can reboot. But before doing that, I would confirm the connection by doing a few pings - On the Pogo, ping the netconsole server 192.168.2.101 -by bodhi - uBoot
TEN, The lack of DTB file kirkwood-pogo_e02.dtb and cpuinfo do seem to indicate your rootfs is non-FDT: # cat /proc/cpuinfo processor : 0 model name : Feroceon 88FR131 rev 1 (v5l) BogoMIPS : 1191.11 Features : swp half thumb fastmult edsp CPU implementer : 0x56 CPU architecture: 5TE CPU variant : 0x2 CPU part : 0x131 CPU revision : 1 Hardware : Pogoplug E02 Revision : 0000by bodhi - uBoot