bodhi Wrote: ------------------------------------------------------- > bandicoot, > > > I got it to run again by doing a fsck (appeared > to > > be nothing wrong?!) and copying uImage and > uIntrd > > from your rootfs to /boot on my disk, thanks. > > Cool! so now you can reinstall the kernel with > linux-image-5.2.9-kirkwood-tld-1 using dpkg -i.by bandicoot - uBoot
Bodhi, I got it to run again by doing a fsck (appeared to be nothing wrong?!) and copying uImage and uIntrd from your rootfs to /boot on my disk, thanks. I just ran: root@NSA320:/boot# update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.19.2-kirkwood-tld-1 I: The initramfs will attempt to resume from /dev/sdb1 I: (UUID=e410ee0f-8aa3-4af5-af2e-0cbab3fc195e) I: Set theby bandicoot - uBoot
Hi Bodhi, Thanks a lot for the quick response. Sorry, this is the full log from the reboot after the Bullseye udate: U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:46:11 -0700) ZyXEL NSA320 2-Bay Power Media Server SoC: Kirkwood 88F6281_A1 DRAM: 512 MiB WARNING: Caches not enabled NAND: 128 MiB In: serial Out: serial Err: serial Net: egiga0 MV88E1318 PHY initialized onby bandicoot - uBoot
Hi Bodhi, I first ugraded my kernel to the latest available and rebooted, that worked fine. I was able to succesfully upgrade my NSA320 from Buster to Bullseye. But after the reboot it is not coming up. I have a serial-console and this is what is happening now: NSA320> boot Initializing devices... Reset IDE: Bus 0: OK Bus 1: OK Device 0: Model: ST2000DL003-9VT166 Firm: CC45 Seby bandicoot - uBoot
bodhi, I am continuing here, because this thread is about setting gpio's, only my case is not in serial. I am able to run on my NSA320: i2cset -y 0x0 0x50 0x06 0x01 b But the ones for NSA326 I can't use, write error's: According to https://forum.doozan.com/read.php?2,27108,106644#msg-106644 If you want WOL + auto turn on after power loss: /usr/sbin/i2cset -y 0x0by bandicoot - uBoot
bodhi, I think none of the zyxel's is capable of fan speed, only on or off as far as I could find on the internet. This should be the case for NSA320, NSA325 and NSA326, and maybe also for the NSAXXXs versions. I have an NSA320 and the fan is not turned on, so I am wondering if I can turn it on myself, I do see the temperature. Cheersby bandicoot - Debian
bodhi, Thanks so much! I do have a working NSA320 with the new uboot now. I did put the mtdparts definition into /boot/uEnv.txt and that is working fine. My /boot/uEnv.txt nowlooks like this: mtdparts=orion_nand:0x100000(uboot),0x80000(stock_uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) devices=usbby bandicoot - uBoot
Koen Wrote: ------------------------------------------------------- > When I run i2cdetect it gives the following > output: > > > root@debian:~# i2cdetect -y 0x0 > 0 1 2 3 4 5 6 7 8 9 a b c d e . . . . > > root@debian:~# i2cdump -y 0x0 0x50 > No size specified (using byte-data access) > 0 1 2 3 4 5 6 7 8 9 a bby bandicoot - Debian
bodhi, Thanks for your quick reply. I do have the mtdparts from stock uboot printenv in the following line, will these do then?: bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/nfs rw init=/init then probably only this bby bandicoot - uBoot
bodhi, I did the copying in /boot end continued with the steps: 1. # cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xc0000 0x20000 0x20000 # cat /proc/mtd dev: size erasesize name mtd0: 00100000 00020000 "uboot" mtd1: 00080000 00020000 "uboot_env" mtd2: 00080000 0002000by bandicoot - uBoot
I am getting confused in what the output of fw_printenv should be, it is a huge difference with the printenv from stock uboot. I know the ethaddr should be set in the env, but I do not inderstand in which env, in the stock uboot or in where fw_printenv gets its settings from. Also fw_printenv warns continuously the following: "Warning: Bad CRC, using default environment" Is thby bandicoot - uBoot
The kwboot worked, I tried a boot as well, but that did not work because I had two rootfs's, one on ide and one on usb, it did find the usb-stick though ;), I only had to add -b to kwboot, because I used 64 version within fedora: # ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa320.mtd0.kwb -p Sending boot message. Please reboot the target...\ Sending boot image... 0 %by bandicoot - uBoot
Would I install the latest then?: 2017.07 U-Boot Kirkwood - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug, NSA325, NSA320, NSA310S, NSA320S, NSA310, HP T5325, Dreamplug ==> https://forum.doozan.com/read.php?3,12381by bandicoot - uBoot
I am getting this: root@NSA320:~# /bin/echo 21 > /sys/class/gpio/export /bin/echo: write error: Device or resource busy If I read the link you gave well then it looks like gpio21 is not defined in the dts file, i am not able to write to this file. Do I have to create a .dts file somehow? I have looked for a .dts file that looks relevant for the NSA320, but I could not find one.by bandicoot - uBoot
I have done this: Hit any key to stop autoboot: 0 NSA320>> md.l 0xF1010100 1 f1010100: 10029000 .... NSA320>> mw.l 0xF1010100 10229000 NSA320>> usb start (Re)start USB... USB: scanning bus for devices... 2 USB Device(s) found scanning bus for storage devices... 0 Storage Device(s) found NSA320>> md.l 0xF1010100 1 f1010100: 10229000 NSA320>>by bandicoot - uBoot
bodhi Wrote: ------------------------------------------------------- > Here is an example for the Armada boxes. > > https://forum.doozan.com/read.php?2,76314,112684#msg-112684 > > For Kirkwood boxes like this NSA320 the GPIO > addresses are different. And the USB power GPIO > must be used. So I'll write a new set of > commands. > > ============ &by bandicoot - Debian
bodhi Wrote: ------------------------------------------------------- > bandicoot, > > > Thanks so much, i did not have to set up udev > or > > automount. I did not see sdc/sdc1 appear. > Reading > > up in the links you gave brought me to running > > > > usbreset vendor:product > > > > That did the trick, it looks like the usbresetby bandicoot - Debian
Hi LillianCastrinio, What did you do to update the driver? Did you update one of the mtdblock's to do that? Cheersby bandicoot - Debian
Hi bodhi, Thanks so much, i did not have to set up udev or automount. I did not see sdc/sdc1 appear. Reading up in the links you gave brought me to running usbreset vendor:product That did the trick, it looks like the usbreset in debian does power up the USB, and I found the message in /var/log/messages that sdc was found and I could mount it myself. At this moment i do not care much aboutby bandicoot - Debian
Hi, I have the same problem with USB not working. In my case I think something happened to probably my env beause one day I had to reboot my NSA320 and it would not start. Installing debian on a USB-stick did not work, it would not boot from that with the right USB boot settings, so i had to install it on a disk. Also after booting debian from disk I still did not have access to USB again.by bandicoot - Debian
Hi Bodhi, I already managed to get it going on a hd replacing usb by ide in the boot sequence: setenv ide_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial' setenv load_uimage 'ext2load ide 0:1 0x800000 /boot/uImage' setenv load_uinitrd 'ext2load ide 0:1 0x2100000 /boot/uInitrd' setenv ide_boot 'mw 0x80by bandicoot - Debian
Hi Bodhi, The powersupply of my fedora desktop is dead, so I ended up creating a fedora usb stick to boot my laptop. I did everything you instructed and also ran in to long lines in stock uboot and had to use the second set you gave to Paul in the link you gave me for the booting instructions. But now I ran into another issue on my NSA320. It appears the USB system is dead. It can not findby bandicoot - Debian
Hi Bodhi, Thanks so much for your help! I will give the instructions a go tomorrow. I have a fedora desktop machine, would for example the mkimage work correctly in fedora to create a kernelimage for the NSA320, or do I really need a Debian system for that as well? Cheersby bandicoot - Debian
Hi there, I am new on this forum, so if I should not post my issue here, could you tell me where I should post it? I also would like to upgrade to Debian on my NSA320. But unfortunately I have sort of bricked my NAS in testing all sorts of commands which I thought were only reading, but I must have done something that makes the boot fail. I had fonz fun plug and entware installed, and I dby bandicoot - Debian