@pengu, Please try this u-boot with two 3.5" HDDs installed. kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-4-test3.nsa310s.mtd0.kwb -pby bodhi - Debian
> /bin/echo 33 > /sys/class/gpio/export <- device or resource busy OK. Then we'll have to make it available. The more I think about it, the more it makes sense that the 12V voltage is the problem.by bodhi - Debian
@pengu, This might be the same problem we've seen in the NSA325. Where the HDD2 needs to be brought up separately during boot.IIRC, believe this was the issue with 12V vs 5V voltage, which makes sense if the 2.5" HDD works fine. There is such GPIO in the NSA320S DTS . And it's is a different GPIO from the NSA325's GPIO. Boot into Debian with both 3.5" HDD instalby bodhi - Debian
edinger Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > edinger, > > > > The NSA325 and NSA325-V2 are the same box > > (differences are only cosmetics). > > > > It is OK to update to new u-boot. But if > booting > > back to stock OS frby bodhi - Debian
edinger, The NSA325 and NSA325-V2 are the same box (differences are only cosmetics). It is OK to update to new u-boot. But if booting back to stock OS from the new U-Boot is important to you, then you should wait until I have some time to try that. I can't promise that it will work :)by bodhi - Debian
Here is the final pre-released version, ready to flash to NAND mtd0. This image can be flashed to mtd0 using the same instruction for the NSA325 u-boot in the U-Boot thread. Please test it using UART serial console first before flashing: kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-4.nsa310s.mtd0.kwb -p Download at Dropbox: uboot.2014.07-tld-4.nsa310s.bodhi.tar md5: 734d2baa84by bodhi - uBoot
ziggy, > > Writing data to block c0000 > > > This is not exactly the same as the output it > should give: > > Writing data to block 6 at offset 0xc0000 > This is fine. The output of different version of nandwrites are slightly different, but it is correct. The version you've downloaded from Jeff's site is older. After you've gone througby bodhi - uBoot
Anybody else seeing this 2nd port problem? If you have the NSA320S, please try with only one 3.5" HDD in the 2nd port.by bodhi - Debian
@FileDescriptor, Thanks! it looks good. And yes about NAND error. I guess your u-boot envs have some old settings that causes mtd1 to be accessed somehow. But you're actually not using NAND at all, booting from external HDD.by bodhi - Debian
Ziggy, I don't see anything wrong with the ouput above.by bodhi - uBoot
Looks like I've missed the Ethernet PHY fix in the previous test version (uboot.2014.07-tld-4.nsa310s.uart.kwb). Update: Attached is another test version that bring up the link properly.by bodhi - uBoot
pengu, Regarding testing the new u-boot: http://forum.doozan.com/read.php?3,23039,23334#msg-23334 Did you try the working 3.5" HDD on the 2nd slot?by bodhi - Debian
This is the wrong thread :) but thanks for testing!by bodhi - uBoot
Please see this post for new u-boot: http://forum.doozan.com/read.php?3,12381,23331,page=27#msg-23331by bodhi - Debian
Please see this post for new u-boot: http://forum.doozan.com/read.php?3,12381,23331,page=27#msg-23331by bodhi - Debian
I've successful built and tested a working U-Boot version for Zyxel NSA310S/320S. Please try and report! It should be loaded with UART in serial console: kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-4.nsa310s.uart.kwb Warning: this image is not for flashing to NAND. UPDATE: The final NAND version was uploaded here: http://forum.doozan.com/read.php?3,23331,23348#msgby bodhi - uBoot
Hi restamp, Looks like it has got to jessie. Update: perhaps I've misread the version number. If you install and it ask you for confirmation then I think that was it. I said no to this option, but I believe seeing it as default.by bodhi - Debian
Hi ziggy, Your system info looks OK. You can proceed with the installation, however, I did not like the look of the output you've shown in step 6. So proceed but starting from step 6. And the expected output shoutd be like shown in the instruction: 6. Erase mtd0 ./flash_erase /dev/mtd0 0 4 Expected output: Erase Total 4 Units Performing Flash Erase of length 131072 at oby bodhi - uBoot
pengu, I will upload the new testing U-boot for nsa3x0s. You can try that.by bodhi - Debian
Good news! ./kwboot-tool/kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-4.nsa310s.uart.kwb Sending boot message. Please reboot the target...| Sending boot image... 0 % [......................................................................] 2 % [......................................................................] 4 % [...................................................by bodhi - Debian
edinger, First, the approach to boot between to_linux and to_stock is a non-optimal technique. You should avoid it when possible. It is best to set it up so that you can boot to stock by removing the stick. That way it can serve as a rescue system. > 1. Boot into stock os without usb stick after > booting into debian does not work with your > command. I needed to_stock commands -by bodhi - Debian
FYI, Beware that apt-get dist-upgrade on your rootfs could lock you out from root login through SSH (if you don't have a normal user account to log in through SSH, or if you don't have a serial connection). QuotePotentially-incompatible Changes -------------------------------- * Support for the legacy SSH version 1 protocol is disabled by default at compile time. * Suby bodhi - Debian
@FileDescriptor, > Akos, many thanks, I just booted my Medion STS212 > system with your installer into Debian with kernel > 4.1. > > FileDescriptor Cool! if you have serial console, please post the entire boot log. If, you don't, please post the output of dmesg.by bodhi - Debian
Kristof, Quotesh flash_erase This command is a wrong way to execute it. When you download a binary and want to execute it, cd to the directory where the binary is and: ./flash_erase /dev/mtd0 0 4 Quoteflash_eraseall /dev/mtd0 0 4 You should never execute a flash_eraseall like above. Use flash_erase only to avoid mistake. And flash_eraseall has been deprecated, too. With all that saby bodhi - uBoot
Joey, > 15-day return-exchange policy at Best Buy, so I > might add $10 and get a Seagate backup plus or > something like that. Still, strangers will have > 750 GB of my stuff :-( Sorry to hear, that's the death click! it could not hurt if you find a strong magnet and stick it to the disk for a while to mess up the data inside before returning it.by bodhi - Off-Topic
pengu, > the other port .. is different .. > a 2,5'' HDD is coming up fine ... > all 3.5 '' HDDs doesn't spin up .. sometimes > nothing is logged, sometimes it's detected shortly > but after a > "EH complete" nothing more It sounds like the 2nd port does not supply enough power for the 3.5" HDD. Have you tried to boot wiby bodhi - Debian
pengu, If the above did not work, regenerate uImage using the kirkwood-nsa310s.dtb, boot, and repeat the same GPIO commands.by bodhi - Debian
Do this for the 1st case with the missing 2nd HDD: After booted into Debian: /bin/echo 47 > /sys/class/gpio/export /bin/echo "out" > /sys/class/gpio/gpio47/direction /bin/echo 49 > /sys/class/gpio/export /bin/echo "out" > /sys/class/gpio/gpio49/direction /bin/echo 1 > /sys/class/gpio/gpio49/value /bin/echo 1 > /sys/class/gpio/gpio47/value /biby bodhi - Debian
pengu, Were both of the boot logs above from a power down status? i.e. removed power cord.by bodhi - Debian
@edinger, In serial console, setenv bootcmd 'setenv mainlineLinux yes; run bootcmd_linux; setenv mainlineLinux no; run bootcmd_stock' boot See if this works. And post the serial boot log when you boot without the USB.by bodhi - Debian