@drdevil: I could send you a working 3.18.2 Kernel with arch-patches. But it would be better if you use bodhi's u-boot for nsa325, too. I am using a micro usb-stick for wheezy.by balou1974 - uBoot
I looked in stock-kernel code (3.18.2) there is DTB-support for ix2_200 but no mach support. There are a few new kernel-options to trade with old u-boot and DTB-files (try make ARCH=arm menuconfig , there you will see options for building zImage with appended DTB: -there is an option to check the appended dtb -there are options to include kernel-command line in the kernel and a few othersby balou1974 - uBoot
wasn't it a problem with rtc and hpet? Don't know for sure but I have not run into problems for now ;) hopefully they fixed it finally ...by balou1974 - uBoot
If there is no dtb file, do you use a mach-kernel? U-boot 1.1.4 does not support dtb files, only mach-kernel(special kernel patched for your device to support it). A not patched kernel will not work. You can download kernel-source from kernel.org, most patches for kirkwood you might find at archlinuxarm or maybe debian (if not included in kernel). You will need a toolchain for arm little endian (by balou1974 - uBoot
please check your kernel-parameters in u-boot there should be a line console=ttyS0,115200 you wont get output if there is no default for that. Might be some wrong addresses or crashed kernel, tooby balou1974 - uBoot
Problems are magically gone! I am running 4 kirkwood devices using linux kernel 3.18.2 now but only Dns320 with dt-blob and kernel. The rest is still with mach-kernel Ts-219, 2x Nsa325 all with Patches from archlinuxarm. Thanks a lot! Regards balouby balou1974 - uBoot
Thanks again! You are right! I simply cloned everything (u-boot, u-boot-env, and the debian system and simply changed ethaddr) ... Is there a easy way to clean that up (marking new bad blocks for the new device)? By-the-way, kernel 3.18.2 was released yesterday - many things have been fixed as it looks like the big lockup, tooby balou1974 - uBoot
Found out another thing: !!! NEVER FORGET TO SET THE HARDWARE-CLOCK :) !!! you will run into problems for sure :)by balou1974 - uBoot
Today, I tried a second unit (new one). Everything seems fine except this: [ 20.982092] end_request: I/O error, dev mtdblock5, sector 0 [ 20.987690] Buffer I/O error on device mtdblock5, logical block 0 [ 20.993992] __nand_correct_data: uncorrectable ECC error [ 20.999334] __nand_correct_data: uncorrectable ECC error [ 21.004848] __nand_correct_data: uncorrectable ECC error [by balou1974 - uBoot
The good thing is they found a bunch of other heavy bugs while investigating that bug ;)by balou1974 - uBoot
I am running a patched 3.16.1 (NSA325v2) mainline Kernel (archlinuxarm patches) and debian wheezy from an usb-stick with the new u-boot. It took a while but it is working fine now. If you have question just ask. regards balouby balou1974 - uBoot
I think you mean the lockup problems starting with 3.17.x and not solved since today (3.18.x). Well 3.16.1 is quite okay for a while ;)by balou1974 - uBoot
I tried 3.18.1 for TS-219 already but it did not boot. Combined TS-219 zImage with dtb as the mach-support in 3.18.1 is very limited and tried that with a very old u-boot (2009 1.1.4). Maybe I had to include a kernel command line or something else was wrong ... Which important bug do you mean? I may wait, too, if it is to dangerous ....by balou1974 - uBoot
Up and running !!! There are still a few in the OLD (1.1.4 Marvell) u-boot I do not understand: to_stock=setenv mainlineLinux no; setenv bootcmd \'run bootcmd_stock\'; saveenv; reset to_linux=setenv mainlineLinux yes; setenv bootcmd \'run bootcmd_linux\'; saveenv; reset I do not know how to rewrite this for the new u-boot but at the moment my machine booted up with lessby balou1974 - uBoot
Can it be that the brackets are changed from () to {} ??? Checked the wiki at denx and they use "{}"-brackets for scripting? Edit: Testet u-boot with "{}"-brackets and it seems like that was my mistake ;)by balou1974 - uBoot
Uuuh, found out that the brackets like "ext2load usb 0:1 $(loadaddr) /boot/uImage" will result in a Kernel that reside on address 0x0000000 but it should be 0x800000 or old way 0x02000000. If I say "ext2load usb 0:1 $loadaddr /boot/uImage" I will get an error saying " ** File not found 0x0800000 ** " . So the meaning of the brackets is obsolet?! Something changed ..by balou1974 - uBoot
Still a few problems, I tried to setup u-boot enviroment like before but I found out a few commands changed (bootm). I got uImage and uintrd loaded but when I start the kernel with 'bootm start $(loadaddr) 0x1100000' 'bootm go' it will show 'Starting kernel ...' and thats it ...by balou1974 - uBoot
Flashing u-boot worked like a charm!!! Thanks again! Changed a line in the file ./arch/arm/mach-kirkwood/nsa325-setup.c as you said: static struct mtd_partition nsa325_nand_parts[] = { { .name = "uboot", .offset = 0, .size = SZ_1M, /* .mask_flags = MTD_WRITEABLE */ }, { I compiled a new zImage, adby balou1974 - uBoot
Thanks again! I will compile the kernel with changed options should be no problem. But how about flashing with uart u-boot? is this possible? Off-topic: You can look all QNAP - Sources (including U-Boot + Kernel + Applications) here if it helps you porting newer u-boot to that device: http://sourceforge.net/projects/qosgpl/by balou1974 - uBoot
Easy to say :) self compiled 3.16.1 with patch from archlinuxarm to support sata leds. If it is protected than there must be an option to change, maybe for compiling? I can post my config if would help?! By the way, is there any u-boot for Qnap TS-219 P ? Thanks a lot for your great work!by balou1974 - uBoot
Well I tried it. Does not let me write ... root@debian:~/u-boot-utils# ./flash_erase /dev/mtd0 0 4 File open errorby balou1974 - uBoot
Hello :) I am trying to flash a NSA325v2 with testing u-boot uboot.2013.10-tld-1.nsa325.mtd0.kwb, the uart-version is working fine. I am using debian wheezy on a pluged usb-stick. Problem is that I want to use the new device tree features and original u-boot (1.1.4) does not include support for DT. Actually I can not flash because I have bad blocks. What can I do? regards Here are someby balou1974 - uBoot