Hello, in the process of tinkering with the environment of me NSA 320, i did a stupid thing: i had a good serial connection to the box, and copied the output of "env print" to a textfile(2018-01-18_env_save.txt) on the NSA320. This was meant to have a backup, in case i mess things up. But when i did sudo fw_setenv --script 2018-01-18_env_save.txt it wrote all env lines in the wrby shivahoj - Debian
You could do this just as well with a TFTP-boot, but i like to depend as little as possible on other machines or hard-to-debug protocols...by shivahoj - uBoot
Hello, i understand that most Key=Value pairs in the environment are either u-boot commands, that are passed directly to uboot, or script commands, that populate env variables, run other commands etc. I found a list of uboot commands here, and an explanation on u-boot here. This got me deep into understanding the boot process. But there are also other things like the LED section: ledby shivahoj - uBoot
Hello, I am learning to use ansible, to automatize linux installation of server farms for my job, and i need A LOT of fresh untampered debian installs to play with. I have come to use one of my NSA320 to boot form different partitions(on same or different hard disks), depending on environment settings. Thus i can just mount and erase a broken installation of a debian server, say on /dev/sdbby shivahoj - uBoot
Hello, now it worked, and i can use fw_setenv. My mtdparts line is a bit different, since i am on a NSA320(Linux version 4.12.1-kirkwood-tld-1, U-Boot 2016.05-tld-1) Just as a reminder for the others out there, here is my command lines(excerpt from my history): cat /proc/cmdline cd /boot touch uEnv.txt echo "mtdparts=mtdparts=orion_nand:1M(u-boot),512K(uboot_env),512K(key_store)by shivahoj - Debian
Hello, just to clarify: i have a mac with a coolterm (serial terminal program) and an USB serial port hooked to the NSA320, and also a "regular" terminal window open, with an netcat that listens on UDP port 6666. Of course the mac IP matches the netcat destination IP. i set this up before powering up the NSA320. Both program's windows are side by side, and i see messages appeariby shivahoj - uBoot
Hello DonCharisma, did You have any success sending the u-boot messages to both NC and serial? After Power-on the first lines appear on my serial, then text goes to nc, then back to serial. Pretty annoying! This is the first serial console text: U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:52:06 -0700) ZyXEL NSA320 2-Bay Power Media Server SoC: Kirkwood 88F6281_A1 DRAM: 512 MiB WARNING:by shivahoj - uBoot
this is my most recent dmesg output, there is no hwmon-related error AFAIK. Could the "local-mac-address is not set" thing in the beginning be related to my netcat not running? root@publik:~# dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.8.3-kirkwood-tld-1 (root@tldDebian) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 PREEMPT Thu Oct 20 23:33:18by shivahoj - Debian
Hello, i think i fried the out port of the UART. This must have happened while i was double checking, and crossing the Serial lines. I checked the PCB, and the serial out line runs right into the Kirkwood SoC chip, no other semiconductors involved, as far as i can see. The voltage on the Serial out is about +3 Volts (in silence) and the data transmissions drop it to about +2.6V instead of 0V whby shivahoj - Debian
root@publik:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xc0000 0x20000 0x20000 root@publik:~# ls -l /dev/mtd* crw------- 1 root root 90, 0 Dec 1 21:36 /dev/mtd0 crw------- 1 root root 90, 1 Dec 1 21:36 /dev/mtd0ro crw------- 1 root root 90, 2 Dec 1 21:36 /dev/mtd1 crw------- 1 root root 90, 3 Dec 1 21:36 /dev/by shivahoj - Debian
root@publik:~# uname -a Linux publik 4.8.3-kirkwood-tld-1 #1 PREEMPT Thu Oct 20 23:33:18 PDT 2016 armv5tel GNU/Linux root@publik:~# cat /proc/cmdline console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=mtdparts=orion_nand:1M(u-boot),512K(uboot_env),512K(key_store),512K(info),10M(etc),10M(kernel_1),48896K(rootfs1),10M(kernel_2),-(rootfs2) root@publik:~# cat /proc/mtd dev: sizeby shivahoj - Debian
I just came across this: root@publik:~# fw_setenv ipaddr 10.9.1.208 Can't open /dev/mtd0: Permission denied Error: can't write fw_env to flash root@publik:~# How do i fix this?by shivahoj - Debian
Hello, here is the info you requested: root@publik:~# uname -a Linux publik 4.8.3-kirkwood-tld-1 #1 PREEMPT Thu Oct 20 23:33:18 PDT 2016 armv5tel GNU/Linux root@publik:~# ls -lart /boot total 76184 -rw-r--r-- 1 root root 140949 Jan 26 2016 config-4.4.0-kirkwood-tld-1 -rwxr-xr-x 1 root root 3154832 Jan 26 2016 zImage-4.4.0-kirkwood-tld-1 -rw------- 1 root root 3154832 Jan 26 201by shivahoj - Debian
This did not work unfortunately: root@publik:~# modprobe nsa320-hwmon modprobe: ERROR: ../libkmod/libkmod.c:557 kmod_search_moddep() could not open moddep file '/lib/modules/4.8.3-kirkwood-tld-1/modules.dep.bin' root@publik:~# depmod depmod: ERROR: could not open directory /lib/modules/4.8.3-kirkwood-tld-1: No such file or directory depmod: FATAL: could not search modules: No suchby shivahoj - Debian
Hello, i managed to update both of my NSA-320 to the latest U-Boot(2016.05) and kernel(4.8.3) For the half bricked one, i succeeded in kwbooting and then installing u-Boot. The other one i updated by the regular method ( boot a 4.2.x kernel from SATA hdd , and then following the appropriate steps for flashing nand / creating the files in /boot. But now, as all is up and running, upon installby shivahoj - Debian
Sorry, this should have gone to the uboot category...by shivahoj - uBoot
Hello, i have two nsa320's, that i both want to update to latest u-Boot. The process went fine on one NSA, but on the other one i have some issues: Right now there are no harddrives installed, but i could take the HD containing the rootfs from the other working NSA. Unfortunately, all stdin, stout, stderr are set to nc,(which works fine). But i need to have it set to serial to be able toby shivahoj - uBoot
Yep it is there: root@public:/home/dirk# strings /lib/modules/4.2.0-kirkwood-tld-1/kernel/drivers/hwmon/nsa3xx-hwmon.ko |grep of_get_named_gpio_flags of_get_named_gpio_flags of_get_named_gpio_flags root@public:/home/dirk# i wonder why it doesnt perform at all...by shivahoj - Debian
Hello pbg4, i have just re-installed bodhi's 4.2.0 kernel after the 4b method(4a didnt work for me, maybe i made some typos, but i won't dig into that now). This is a minor issue, and if its much work , i'll just leave it as is now. Could You please describe how You persuaded the kernel to create the directory and its contents in sys/class/platform/hwmon ? i have succesfullyby shivahoj - Debian
Yes, at least the thing isnt totally mute and deaf anymore... for clarfication of the above: 10.9.1.209 is the adress of the nas, as it is laid out on the dhcp servers /etc/dhcp3/dhcpd.conf. 10.9.1.200 is the adress of my mac, that is waiting with an open netconsole. 10.9.1.1 is the dhcp server (another linux box in our net). Its /var/log/messages shows the successful dhcp handshake with theby shivahoj - Debian
Hello, i have two NSA-320's, one is perfectly working(with latest u-boot and debian), the other one gives me headaches. It is the one i wrote about in this thread:http://forum.doozan.com/read.php?2,24478,24478#msg-24478. Now I managed to get serial access, but the thing stays dead otherwise. I cannot ping the devices' IP, and it does no dhcp requeston itself. But when i issue &qby shivahoj - Debian
OK, thanks alot to both of You. I (sort of) puzzled this out by myself, but this gives a lot clearer picture.by shivahoj - Debian
Sorry, this was intended NOT to go in the u-boot forum, but into the Debian section.by shivahoj - Debian
Hello all, maybe i am the only one with this fundamental lack of understanding, in which case i am sorry for wasting Your time: I always read about FDT and non-FDT, and i understand that this Flattened-device-tree is just a file(or data structure) describing a particular hardware, where are the adresses of the several devices on the internal bus(ses), amongst other things. But can i just choby shivahoj - Debian
Hello, i just updated to the latest u-boot and kernel 4.2 (by Your method 4b), which worked fine. From the information You provided about the recent kernels i thought the hwmon issue was somehow solved. But unfortunately the sys/class/hwmon/directory ist still empty, before and after insmod nsa3xx_hwmon. Also sensors-detect doesnt find anything. Is this maybe a FDT vs. non-FDT thing? (I stillby shivahoj - Debian
Hello, i just updated to a new kernel, 4.2. In the last few months, i tried and tested a lot of software, like mediatomb, cups, munin, nagios, netboot, dhcp-probe etc. Now in the path of this upgrade, i of course made a backup of the whole filesystem, and was hoping to have a "fresh" installation, where i could install the things i want to keep. A bit naive, i know.... Now everywby shivahoj - Off-Topic
Hello, after quite some time i finally got to test the UART-Booting. Sadly, the NSA320 doesnt respond at all to the uboot offered via serial. This is what i see: root@ubuntu:/home/dirk/Downloads# ./kwboot -t -B 115200 /dev/ttyUSB1 -b uboot.2015.10-tld-1.nsa320.mtd0.kwb -p Sending boot message. Please reboot the target.../ Sending boot image... 0 % [+xmodem: Protocol error The sign aftby shivahoj - Debian
Hello, as i already thought, battery removal didnt help. Type type on both systems is a plain 320, no S, following a sticker at the back. with the LEDs i mean the 5 in a row, backlighting the front panel symbols. of course the top blue one is also lit... after power-on ALL multicolored LEDS on the front panel come on for 2 secs, then the green stay lit. the fan spins up a few rpms(from zerby shivahoj - Debian
Hello, i have 2 Zyxel NSA320s, one with factory firmware(dont know which version), thats been lying in my shelf for a year now, and one with a recent(-ish) debian on it. The latter one works perfect, and thus I now wanted to also flash the stock firmware to the newest available debian, so that i could have a backup system. I remember the stock firmware system worked well, when i put the thing aby shivahoj - Debian
Sorry, i saw right after posting, that i posted in the wrong category. I found options to edit my post, but not to delete it completely. My NSA320 uses a network chip right next to the magnetics: (Marvel Logo) 88E1318-NNB2 P4H7680.14 1118 A0P TWby shivahoj - Debian