@WarheadsSE, So right you are! Upon reboot, I did get to completion with your new U-Boot and it froze when it started. Cold boot never got to 99%. Perhaps we need to whack the watchdog immediately in main.c? I also extracted stock U-Boot from mtd0 and UART it succesfully (so it seems to run smoothly). But it works only when we reboot, not cold boot. However, I can't verify that extby bodhi - Debian
I've checked. ALARM is just a little bit under 4M currently. There must have been something in 3.15.x kernel and my Debian config that has made the size increase by that much. But it's been running OK for all other Kirkwood boxes.by bodhi - Debian
@fsm, At the moment, you will need to run UART booting to boot up the Pogo Mobile. There is really no work around (yet) that allows you to permanently fix it. The location of the bad block (0xc0000) unfortunately is right at the envs NAND location. And this can't be changed to another location because this is the common location for all Kirkwood boxes, so I can't do that. So go keby bodhi - uBoot
grayman4hire, SSH into Pogo OS, try running lspci or ifconfig (the PCI is populated with wifi card in the Pro).by bodhi - Debian
@fsm, > I'm NOT going to power this sucker down until I > hear back from you! :D :D Pls get output of dmesg and post here!by bodhi - uBoot
rickgtx, Go ahead and flash (you will see one block is skipped). Please post output here! nandwrite /dev/mtd0 uboot.2014.07-tld-1.pogo_v4.mtd0.kwb BTW, there is a syntax error: setenv mmc_set_bootargs 'setenv bootargs $bootargs_console root=/dev/mmcblk0p1 rootdelay=10 $mtdparts'by bodhi - uBoot
Regarding the freezing problem with kernel 3.15.3 for NSA325. Prelimilary finding: there seems to be a limitation of 4M memory for uImage with stock U-Boot. Stock U-Boot code is difficult to read, so this needs to be confirmed later. I'm wondering, anybody booting Arch with > 4M uImage? please post (I have not downloaded Arch rootfs to check).by bodhi - Debian
rickgtx, On this bad-block Pogo Mobile, boot uboot.2014.07-tld-1 with UART, and change bootargs to include MTDparts: Pogov4> mmc_set_bootargs 'setenv bootargs console=$bootargs_console root=/dev/mmcblk0p1 rootdelay=10 $mtdparts' Pogov4> setenv bootcmd 'run mmc_set_bootargs; run bootcmd_mmc; bootm 0x00800000 0x01100000' Then boot into Debian. Check: cat /proc/by bodhi - uBoot
@dfarning, Use Ext3 and it should work (Ext4 not supported).by bodhi - Debian
WarheadsSE, > I just wish I had a way to perma-disable that > watchdog clock... Would be so nice to be able to > have time kwboot the 325 Yeah, I got UART to load to 99% and it craps out. I've dowloaded the stock U-Boot source and looking at it to see if they have a way. I can't compile it yet (trying to change the make file to compile natively and it would not work, thby bodhi - Debian
grayman4hire, You're right! I meant to consolidate the variable names, but forgot the instruction for the rootfs still use usb_ prefix. I think I will go back to spell out each type of rootfs to make things simpler.by bodhi - uBoot
CasperJim, > Oh yes, I reverted the filesystem to ext2, and > changed "rootfstype" to ext2. It worked. So I > assume to permanently set it, I use this command? > # fw_setenv rootfstype ext2 Yes. Either set it to ext2, or not set it at all (the kernel will figure it out if you dont set it).by bodhi - uBoot
rickgtx, This is the warning I have in the instruction, you did not check your NAND! Your bad block is right in the midle of 1M (block 3 is at 384K). Quote4. Be sure there is no bad block in the first 1M of your NAND (check dmesg). This is very important, if there is bad block in the first 1M, don't flash u-boot, because you will almost certainly brick your box. Please post your questiby bodhi - uBoot
CasperJim, rootfstype should be ext2! Not usb_rootfstype. Sorry I wrote from memory :) it's the common name in all 3 bootargs. So rootfstype should be either Ext2 or not set.by bodhi - uBoot
CasperJim, Quote> Starting kernel … Netconsole does not output more than this. To see more info you must have serial console. But this is pretty far you got! a few things to check and try in this order: Double check ( (baby steps but easy to forget so double check them): - Make sure you have extracted the rootfs to your USB as root user. And sync before umount. - If bootargs roby bodhi - uBoot
dfarning Wrote: ------------------------------------------------------- > I think that there needs to be an entry in > /etc/fstab to point from the boot partition to the > /boot/ directory in the rootfs partition. > > This will enable apt-get to find and modify the > kernel from which the system boots. Good point! The typical installation is just a single partition bby bodhi - Debian
Tripleflix, Follow the instruction on creating rootfs: QuoteUpdated 15 April 2014: Rootfs Debian-3.14.0-kirkwood-tld-1 was uploaded. Please read each thread's 1st post completely before attempting the installation.by bodhi - Debian
Tripleflix, Quotedo i first install the uboot files or do i have to prepare a usb/sdcard with debian first,, i tried to use jeffs script for this but it seems to be broken. i am still on a stock atm. Jeff's script does not have support for the Pogo V4/Mobile. I meant to modify it to do installation, but it is a time consuming task (changing script is easy, but a lots of testing needby bodhi - Debian
fsm, No need for JTAG for the Pogo Mobile, you already have serial! unless the serial port is fried, you can always recover with UART.by bodhi - uBoot
@fkyle, You don't need to compile for the Classic. Compile for the Pro and when you use the Classic DTB to boot it will be OK. Re the error in booting, please post your output of printenv in serial console. I think what igmar said was most likely the case, missing dtb in bootm command?by bodhi - Debian
fsm, Thanks! I saw that but was not sure if it is the last one davygravy has. I'm trying to boot the NSA325 with UART, so far unsuccesffuly, so just trying get as many different U-Boot versions as I can get my hands on.by bodhi - uBoot
Regarding RTC on NSA325: > I've found that the NSA325 RTC driver was loaded > as module. This was too late in the boot process. > Will see if I can get it working and include it in > either in kernel 3.15.3 or a special version of > 3.14.0. This was the reason. Once the driver module for NSA325 was compiled in, it works. Apparently, the rtc-mv still is going to spit oby bodhi - Debian
saudagar, Quote> I followed below steps to install debian on my > pogo V4-A1. > http://blog.qnology.com/2014/07/hacking-pogoplug-v > 4-series-4-and-mobile.html > Blogger claims that instock > firmware is present in NAND but needs change in > uBoot to access it. It further suggests that i can > reboot the pogo with 'revert' as a empty folder in > aby bodhi - Debian
Tripleflix, The answer to all your questions is yes. You only needs to follow 2 posts to install U-Boot and Rootfs: http://forum.doozan.com/read.php?3,12381 http://forum.doozan.com/read.php?2,12096by bodhi - Debian
Fsm, Don't bother trying different card! It's the root device as parameter to the kernel that you can't set.by bodhi - uBoot
ptosch, > mw.l f1010100 0020c000; ide reset; ext2load ide > 0:1 0x800000 /uImage; ext2load ide 0:1 0x01100000 > /uInitrd ; bootm 0x800000 0x1100000; > > mw.l f1010100 0020c000; ide reset; ext2load ide > 0:1 0x800000 /uImage; ext2load ide 0:1 0x01100000 > /uInitrd ; bootm 0x800000 0x2000000; > > Both command lines lead to the described effect of > freeziby bodhi - Debian
All, I'm looking for download the link to davygravy's NSA320 u-boot image. Please post if you have that download link. Thanks!by bodhi - uBoot
fsm, > mmc1 is available > Loading file "/uImage" from mmc device 0:1 (xxa1) > ** File not found /uImage > 't get kernel image! The above is why you could not boot. The default envs are being used, and it tells u-boot to find the boot files at / directory, not at the usual location in the rootfs. So you can either symlink the files or copy them (assuming /mediby bodhi - uBoot
Tinkerer, Cool! you can plug in your Arch rootfs and continue booting at serial console: GoFlexHome > boot If you see error during booting, capture the entire log and post it here.by bodhi - uBoot
fsm, Get the latest rootfs, and extract it to an SD card or USB thumb formatted as Ext3. If you don't have another Linux box then use a Linux Live CD on Mac/Windows PC (if you have a Mac, you might be able to run fdisk and mke2fs at command line). 1. What error did you see when you setenv? this usually occurs when you run a different U-Boot image (e.g. uboot.2014.07-tld-1.pogo_v4.mtdby bodhi - uBoot