bobafetthotmail, What you described is a big part of u-boot :) i.e. some function is not possible implement without bringing in a large part of u-boot. QuoteAlso, if someone writes the uboot applications in some unused part of the NAND or places them in a ext2 or fat partition, could this help add functionality to a crappy stock Uboot, like ext4load or f2fsload or true netconsole or the thiby bodhi - uBoot
> ok, what about the Uboot Standalone Application or > Program? > http://www.denx.de/wiki/U-Bootdoc/StandaloneProgra > ms > > I have the "go" command in stock Uboot (to run > such applications). Yes, it would work. > > I only need something to have the stock uboot > write things to GPIO so it can disable the > watchdog. So if I underby bodhi - uBoot
pengu, > perhaps they think its the > same like NSA320 Yes, I think you're right. It seems so. I think we're ready to add it to the support list in kernel 4.1 (released in a day or two).by bodhi - Debian
Johnny, It's not in the archive. When you install kernel 4.0 with dpkg -i linux-image-4.0.0-kirkwood-tld-1_1_armel.deb it will be generated automatically along with other kernel files.by bodhi - Debian
@pengu, The NSA320S has only 256MB and also 1.0 GHz. That's why you can run your NSA310S correctly. Otherwise you would have seen 512MB RAM. See: ftp://ftp2.zyxel.com/NSA320S/datasheet/NSA320S_2.pdfby bodhi - Debian
JohnnyUSA Wrote: ------------------------------------------------------- > Here is the full bootlog: > http://pastebin.com/pAyj62Eb Johnny, You should regenerate the uInitrd. You are running with older version of the initramfs. Your kernel is 4.0 ## Booting image at 00800000 ... Image Name: Linux-4.0.0-kirkwood-tld-2 Created: 2015-06-26 8:47:53 UTC Image Typeby bodhi - Debian
@pengu, Thanks! I see. Same SoC and everything. I think that cover all bases, except 2 items: - memory: the NSA320S has 256MB RAM, I thought the NSA310S also has 256MB? - The number of SATA ports needs to be defined as 1 port for NSA310S. This is not that important, but should be corrected nevertheless.by bodhi - Debian
bobafetthotmail, No, it is not possible to chainload new u-boot from stock u-boot. This is due to the structural differences between the old and new u-boot code. Note that it is possible to chainload some stock u-boot from the new u-boot. This is due to the way older u-boot versions were coded.by bodhi - uBoot
@pengu, I would like to announce in the kernel thread that the NSA310S has been tested and supported. Can you verify (at least on paper) that the specs of NSA310S versus NSA320S are more or less the same regarding the kernel DTS? I know you and Johnny have been running it fine as NSA320S. However, there must be something different between the 2 boxes, and I just want to make sure that the dby bodhi - Debian
schnee, Quote> After running apt-get install --reinstall > binutils now i have > libopcodes-2.22-system.so installed on the system > and was able to install pycups. Thanks, I'll make sure to check this for future basic rootfs releases.by bodhi - Debian
Johnny, Cool! so it was just the USB stick problem, like we suspected. For power button, I like davidedg's use of esekeyd daemon. See instruction here.by bodhi - Debian
@Hiro.AK47, > Be careful, following comment in this patch is > probably mistake (at least, source code isn't > so): > > "184:+ MPP37_GPIO, /* reset button input */" Got it. That comment was indeed a mistake! Thanks! I'm recompiling the DTB and done.by bodhi - Debian
@Hiro.AK47, > I revised DTS file. > It works fine on my Stora. I've reviewed your version of the DTS. Everything looks good to me, including the trigger name changes (I think the trigger names are now consistent with the other Kirkwood trigger naming convention). One thing that stands out and needs to be confirmed. The reset button was 37 in the orginal non-FDT setup code (keby bodhi - Debian
Dirk, > One strange thing: i tried your "4b" solution on > the USB flash stick first, but it couldnt find the > root filesystem(as i think of it now, not THAT > strange). T hen i copied the entire /boot folder > to the harddisk, and there it worked. Because the instruction was written for installing kernel on a live system. If you mount the USB on a different maby bodhi - uBoot
Dirk, You're running u-boot 2011.12 which does not support FDT kernel booting the normal way. So to run kernel or rootfs 3.17.0-kirkwood-tld-1, you need to append the NSA320 DTB file to the uImage. In the instruction for kernel 3.17, this step stated: Quote4b. Boot with DTB file embedded in the kernel image (no U-Boot envs change needed) Generate the uImage and uInitrd: cd /bby bodhi - uBoot
@Johnny, That Cruzer Fit will do the job just fine! I use this for all my plugs that boot with USB. Heads up: If the cold boot problem is still there even with Sandisk drive, you'll need serial console to troubleshoot this. Too bad we don't have newer u-boot for NSA310 yet. So serial console is a sure way to troubleshoot. But before getting serial console, please post back forby bodhi - Debian
schnee, You should have libopcodes-2.25-system.so in your system. You can make a symlink for libopcodes.so to point to that: cd /usr/lib ln -s libopcodes-2.25-system.so libopcodes.soby bodhi - Debian
pbg4, Got it. > it would also be a good idea to put the newest > frontend firmware for m88ds3103 into your next > rootfs, > in /lib/firmware, it is also attached in the pm, > md5sum should be b31080dd205ce1659ed7aedf2b153e03 > for > the firmware dvb-demod-m88ds3103.fw, Good idea! this also reminded me that I should add the Iogear BT 4.0 firmware to the rootfs,by bodhi - Debian
pengu, > The only things I have changed in the uEnv.txt is > the network part for netconsole. Netconsole is not scriptable in uEnv.txt, atm. I plan to revise the default envs so that it can be. > This is also shown by the LED: > After plugging it starts to blink for 33 seconds, > then it turns red. This indicated that the kernel files have not been loaded successfuby bodhi - uBoot
ubermacin Wrote: ------------------------------------------------------- > Okay, I think I got it all running now. Just took > a while, thanks again Bohdi! Cool! And thanks for the feedback about the instruction. I'll see if I can improve the part about Arch u-boot migration.by bodhi - uBoot
@Johnny, Some USB sticks have problem with coldboot (some also have problem with warmboot, but not coldboot). If you can, get a Sandisk stick (any model) and try that. nc problem: this is expected with stock u-boots in general. So don't waste time trying. Usually we need custom u-boot to support netconsole. @pengu, No, I think the watchdog problem is diffferent. Eventhough it seeby bodhi - Debian
ubermacin Wrote: ------------------------------------------------------- > Also strange, when I try to boot into arch I see > in the net console: Unknown command 'setexpr' - > try 'help' > > I see that in the bootcmd, and now I can't boot > into arch now: > > [ 12.439090] scsi 0:0:0:0: Direct-Access > SanDisk Cruzer Glideby bodhi - uBoot
Johnny, I'd strongly recommend using a SINGLE partition of type Ext3. Extract the rootfs to it. Dont worry about swap until you can boot consistently.by bodhi - Debian
Sure, but you will run into problem later! See "u-boot and kernel booting process" in my signature for explanation.by bodhi - Debian
What pengu said were all true, but one item: the u-boot envs are not set up properly for 2 partition rootfs, yet. So Johnny should use only one Ext3 partition, to ensure successful booting.by bodhi - Debian
Johnny, Your u-boot envs look sane. So it's not that. Since you did this on a Ubuntu VM, retrace your steps to make sure: - When you copied rootfs, you were the root user? - The USB has only one partition and it must be Ext3 - The partition label must be rootfs When preparing the rootfs (either new or update), you must be the root user. If you still can't boot afer verifby bodhi - Debian
@maihoamv, I did not see any familiar config listed (I have not looked closely). However, in general, it's needed to be little endian and arch needed to be ARM.by bodhi - Off-Topic
Johnny, cd to the USB boot directory (assuming the USB is mounted as sdb1), and then cd /media/sdb1/boot cp -a zImage-3.18.5-kirkwood-tld-1 zImage.fdt cat dts/kirkwood-nsa320s.dtb >> zImage.fdt mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.18.5-kirkwood-tld-1 -d zImage.fdt uImage mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -eby bodhi - Debian
maihoaomv Wrote: ------------------------------------------------------- > I was able to compile rtl8812au on my GoFlexHome. > I changed Makefile PLATFORM like this i386=n and > ARM_Rpi=y as mentioned back on page 1 of the post. > I was able to build it with a bunch of warnings > but no errors. it worked when i did insmod > 8812au.ko and it seems so far to be working finby bodhi - Off-Topic
@pengu, Since you are using the NSA320S DTS, have you verified that the all specs is the same? Ie. find the differences between NSA310S and NSA320S and make sure they are taken cared of.by bodhi - Debian