First I will try ext4 as format for disk. Second thing is to use winscp to put something on this disk. If someting fail please provide "logread".by kofec - uBoot
Maybe it will be easier to check what is wrong with openwrt?by kofec - uBoot
I recommend to use uboot from openwrt. Environment variable will be set correctly. For sure you should have serial cable before you start your adventure.by kofec - uBoot
I sold mine with openwrt - There is nice www also polish version and many services can be easily installby kofec - uBoot
It is strange but still nothing: nsa325/kwboot-tool# ./kwboot -t -B 115200 /dev/ttyUSB0 -b ../uboot.2017.07-tld-1.nsa325.debug.mtd0.kwb -p Sending boot message. Please reboot the target...- Sending boot image... 0 % [......................................................................] 1 % [......................................................................] 2 % [............by kofec - uBoot
Thanks, I will try today when back homeby kofec - uBoot
Thanks a lot for you help. I also suspect RAM module but I was surprised that u-boot image loading was successful - As I understand it was loaded to RAM. If we tried all known simple methods to recover this device I going to sell it - I will describe all our findings. Maybe someone needs the case or have tools and knowledge to replace RAM module. So thanks again for you help.by kofec - uBoot
You are right. We I load your uboot the Power LED is not blinking after 30 seconds. Also fan is control (RPM is changing). On ethernet I don't see any packet (wireshark) but the physical link is up.by kofec - uBoot
> If you let it boot without kwboot and just run serial console, then what is the behavior? Nothing. Even single character > kwboot-2016.05.tar After unpack: ./kwboot bash: ./kwboot: cannot execute binary file: Exec format error I used both version of kwboot (from your website and provided with system) and the same result(first post). Current behavior is power led (blue) turby kofec - uBoot
Hi, There is no stock uboot or doesn't start. I don't know history of this hardware. Is it hardware issue or I can try something else: /kwboot-tool# kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p Sending boot message. Please reboot the target...\ Sending boot image... 0 % [......................................................................] 1by kofec - uBoot
As I understand there was not more information in "this" script ?by kofec - uBoot
Bodhi, Safarik, Yes, I understand/believe that these address are correct but I'm curious if someone who found it, can point us to any documentation/code to confirm it. And furthermore, maybe we will be able to find something more there.by kofec - uBoot
If we cannot control fan speed directly. Maybe we can control the MIN Temp and MAX Temp when the fan starts and achieve max speed. The same way we are able to control fan speed on NSA310. Which chip is using NSA325 ? Base on the documentation mention in topic: https://forum.doozan.com/read.php?2,91649,91694 Are we able to confirm that we read temp and RPM from correct address (below code) ?by kofec - uBoot
It was fine untill I want to upgrade to latest build: (Linux version 4.4.47 (buildbot@builds) (gcc version 5.4.0 (LEDE GCC 5.4.0 r3377-368cc8e) ) #0 Sun Feb 12 00:41:43 2017) Issue with upgrade: root@lede:/tmp# sysupgrade -d 5 lede-kirkwood-nsa310b-squashfs-sysupgrade.tar Image metadata not found Saving config files... Watchdog handover: fd=3 - watchdog - killall: telnetd: no processby kofec - Rescue System
bobafetthotmai, It is not working but it is not critical. With the original Zyxel firmware it works this way that I'm able to wake on lan via eth addr provided with device till there is no power outage. But when there is no power on NSA310 I have to use 00:00:00:00:00:30 also. Quotebobafetthotmai How is Wake on Lan working with this firmware after you set mac address? Does it still wby kofec - Rescue System
Thank you @bobafetthotmail and @bodhi Now almost everthing is fine. Two cosmetic issue: 1) root@lede:/tmp# sysupgrade -d 5 lede-kirkwood-nsa310b-squashfs-sysupgrade.tar Image metadata not found - shows something like this Saving config files... Connection to 192.168.1.162 closed by remote host. Connection to 192.168.1.162 closed. 2) it didn't read eth addr from uboot env but wby kofec - Rescue System
After these all experiminets I'm not able to start LEDE from my old USB and power buttom not working - start via wake on lan. So this is some hadware issue? Or some environment issue ? U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:59:20 -0700) ZyXEL NSA310 1-Bay Power Media Server SoC: Kirkwood 88F6281_A1 DRAM: 256 MiB WARNING: Caches not enabled NAND: 128 MiB In: serial Outby kofec - Rescue System
The diffrence is: when kernel load fine: ubi0: volume 2 ("rootfs_data") re-sized from 9 to 932 LEBs ubi0: attached mtd1 (name "mtd=3", size 123 MiB) ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512 ubi0: VID header offset: 512 (aligned 512), data offset: 2048 ubi0: good PEBs: 981, bad PEBs: 7by kofec - Rescue System
OK understand. What is your proposal. All I need is to have LEDE in nand and have sysupgrade working (not always connect via serial cable). After current sysupgrade I have below issue. NSA310> usb reset resetting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 3 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found NSA310> fatloadby kofec - Rescue System
With bobafetthotmail uboot still didn't work NSA310> NSA310> usb reset resetting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 3 USB Device(s) found NSA310> usb start NSA310> fatload usb 0:3 0x2000000 lede-kirkwood-nsa310b-squashfs-factory.bin ** Bad device usb 0 **by kofec - Rescue System
As it is writen : https://github.com/lede-project/source/pull/732 this commit allows to make both a standalone and a second-stage u-boot for nsa310b, but only first-stage u-boot is added in the makefile and available in the build system. The reason is that while both work fine if installed to flash or loaded with kwboot, I could not get stock u-boot nor bodhi's u-boot to chaiby kofec - Rescue System
When I want to start LEDE from USB using uImage (for bodhi uboot ) Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.4.42 (kofec@E5420Mint) (gcc version 5.4.0 (LEDE GCC 5.4.0 r3060+2-533f73e) ) #0 Mon Jan 23 12:12:08 2017 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f [ 0.000000] CPU: VIVT data cachby kofec - Rescue System
Bodhi, I start your uboot - using kwboot - the write to flash. Thanks a lot for help. Maybe you can also fix 2nd boot stage in your uboot. 97 % [......................................................................] 99 % [....................................] U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:59:20 -0700) ZyXEL NSA310 1-Bay Power Media Server SoC: Kirkwood 88F6281_Aby kofec - Rescue System
Ok last issue: U-Boot 2016.09.01 (Jan 24 2017 - 19:33:45 +0000) ZyXEL NSA310 1-Bay Power Media Server SoC: Kirkwood 88F6281_A1 DRAM: 256 MiB WARNING: Caches not enabled NAND: 128 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: egiga0 Error: egiga0 address not set. PHY reset timed out MV88E1318 PHY initialized onby kofec - Rescue System
It is fat but - it looks like I should use u-boot.kwb 95 % [......................................................................] 97 % [......................................................................] 99 % [....................................] U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:59:20 -0700) ZyXEL NSA310 1-Bay Power Media Server SoC: Kirkwood 88F6281_A1 Dby kofec - Rescue System
93 % [......................................................................] 94 % [......................................................................] 96 % [......................................................................] 98 % [......................................................................] 99 % [...] U-Boot 2016.09.01 (Jan 24 2017 - 19:33:45 +0000) ZyXEL NSby kofec - Rescue System
I will try with kwb fileby kofec - Rescue System
I follow your steps: 95 % [......................................................................] 97 % [......................................................................] 99 % [....................................] U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:59:20 -0700) ZyXEL NSA310 1-Bay Power Media Server SoC: Kirkwood 88F6281_A1 DRAM: 256 MiB WARNING: Caches notby kofec - Rescue System
Hi, I think I kill my uboot when I try test latest changes in LEDE: I follow the procedure: https://github.com/lede-project/source/pull/656#issuecomment-274945142 I compile the uboot: ~/openwrt/LEDEnsa310 $ ls -alh bin/targets/kirkwood/generic/u-boot-nsa310/ total 1,5M 508K Jan 25 21:28 u-boot.bin 508K Jan 25 21:28 u-boot.img 508K Jan 25 21:28 u-boot.kwb and take u-boot.bin theby kofec - Rescue System
I have question. Is it possibile to prepare this /boot/uEnv.txt to start original os from nand ?by kofec - uBoot