[solved] Install problem on Zyxel NSA 310

[moonman]

I can't tell you why this is happening. The kernel should support this device, but I've got none to test. It did in the past so I don't see why suddenly the support would be broken now and other devices are fine.

Try new U-Boot version, maybe you will have more luck with that
http://mirror.archlinuxarm.org/arm/alar ... pkg.tar.xz
Use kwboot to send uboot image to the device and see if it boots (without actually flashing the uboot).

There is a caveat with this uboot: there is no MAC address assigned to the NIC, so you won't be able to bring it up until you assign it manually: viewtopic.php?f=53&t=8857&start=40#p48186

[WarheadsSE]

Sounds like a problem between your bootloader and the kernel, not our kernel.

[dietgert]

Yes, you`re right.
Moonman gave me the decisive clue this with his link already.
My uboot loader seems to be pretty outdated:
U-Boot 1.1.4.
I have to find now a useful way to upgrade the U-Boot-loader..

Best regards,
didi

[dietgert]

Ok, i'm through now, device seems to be bricked now (1 blue and 5 red leds together ).
Moonman, thanks for your support anyway.

BR
didi

[moonman]

You can't really brick it. You can always send uboot image over serial, boot up and flash the device again.
You need kwboot on the system you are running on.
Use this (as an example)
$this->bbcode_second_pass_code('', 'kwboot -t -B 115200 /dev/ttyUSB0 -b /path/to/uboot-nsa310.kwb -p')
where
ttyUSB0 is your serial interface to the device
uboot-nsa310.kwb is uboot image
now power on your device.

[dietgert]

Thank You moonman,

this worked surprisingly well , indeed.
But now i dont know what to do next.
I think i must now do the following steps:

flash_erase /dev/mtd0 0 4
flash_erase /dev/mtd0 0xc0000 1
nandwrite /dev/mtd0 /path/to//uboot-nsa325.kwb
nandwrite -s 0xc0000 /dev/mtd0 /path/to/uboot-nsa325.env

But in the u-boot file , there is no such flash_erase command .
there is a nand erase.part as part of the nand command instead.
the other subcommand then could be nand write .
Is it possible from here to link to a file on an usb stick directly?

edit:
I tried another method:

placed the µImage from the latest Kirkwood installer in a "boot" folder on a fat-formatted usb stick.
It was booted via the kwbooted uboot.

...many bad eraseblocks...
then init problem.

edit 2: booted now to login after changing the file system to ext2 .
so the uboot update should be possible via arc-linux-script now.


Best Regards,
didi

[moonman]

Get the networking going and install uboot-nsa310 with pacman. It will pull necessary dependencies and flash uboot. I would recommend using ext4 for the filesyatem. You will have lots of problems with ext2 if you keep it.

[dietgert]

Did that.

[root@alarm dist]# pacman -U uboot-nsa310-2015.07-3-arm.pkg.tar.xz
loading packages...
warning: uboot-nsa310-2015.07-3 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) uboot-nsa310-2015.07-3

Total Installed Size: 0.63 MiB
Net Upgrade Size: 0.00 MiB

:: Proceed with installation? [Y/n] Y
(1/1) checking keys in keyring [######################] 100%
(1/1) checking package integrity [######################] 100%
(1/1) loading package files [######################] 100%
(1/1) checking for file conflicts [######################] 100%
(1/1) checking available disk space [######################] 100%
(1/1) reinstalling uboot-nsa310 [######################] 100%
A new U-Boot version needs to be flashed to NAND.
Do you want to do this now? [y|N]
y
Too few good blocks within range
>> Error: Could not find MAC address from current U-Boot.


[root@alarm dist]# ifconfig
enp0s1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.13 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 2a02:8070:f187:5d00:b4d0:5eff:fexx:xxxx prefixlen 64 scopeid 0x0<global>
inet6 fe80::b4d0:5eff:fexx:xxxx prefixlen 64 scopeid 0x20<link>
ether b6:d0:5e:xx:xx:xx txqueuelen 1000 (Ethernet)
RX packets 209 bytes 38704 (37.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 49 bytes 4654 (4.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 166 bytes 13138 (12.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 166 bytes 13138 (12.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

[root@alarm dist]#


So my questions are now: Where is this scrict looking for the mac-address ?
Can I ignore the too few good blocks message ?

BR
didi

[moonman]

You will have to flash it manually. As described for nsa 325, except of course change the name of uboot image.

After you flashed it, set the ethaddr manually as well using fw_setenv.

[dietgert]

This fails with the first step already:

[root@alarm ~]# flash_erase /dev/mtd0 0 4
flash_erase: Skipping bad block at 00000000
flash_erase: Skipping bad block at 00020000
flash_erase: Skipping bad block at 00040000
flash_erase: Skipping bad block at 00060000
Erasing 128 Kibyte @ 60000 -- 100 % complete


[root@alarm ~]# flash_erase -uN /dev/mtd0 0 4
Erasing 128 Kibyte @ 0 -- 0 % complete libmtd: error!: MEMUNLOCK ioctl failed for eraseblock 0 (mtd0)
error 95 (Operation not supported)
flash_erase: error!: /dev/mtd0: MTD unlock failure
error 95 (Operation not supported)
Erasing 128 Kibyte @ 20000 -- 25 % complete libmtd: error!: MEMUNLOCK ioctl failed for eraseblock 1 (mtd0)
error 95 (Operation not supported)
flash_erase: error!: /dev/mtd0: MTD unlock failure
error 95 (Operation not supported)
Erasing 128 Kibyte @ 40000 -- 50 % complete libmtd: error!: MEMUNLOCK ioctl failed for eraseblock 2 (mtd0)
error 95 (Operation not supported)
flash_erase: error!: /dev/mtd0: MTD unlock failure
error 95 (Operation not supported)
Erasing 128 Kibyte @ 60000 -- 75 % complete libmtd: error!: MEMUNLOCK ioctl failed for eraseblock 3 (mtd0)
error 95 (Operation not supported)
flash_erase: error!: /dev/mtd0: MTD unlock failure
error 95 (Operation not supported)
Erasing 128 Kibyte @ 60000 -- 100 % complete
[root@alarm ~]#

I think i must now clean the /dev/mtd0 in uboot itself, but have absolutely no clue with which command.

BR
didi