Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
kirkwood: add ZyXEL NSA310b #656
kirkwood: add ZyXEL NSA310b
The ZyXEL NSA310 device is a Kirkwood based NAS:
The stock u-boot cannot read ubi so it should be replaced with the
This device's boot ROM supports "kwboot" tool
The stock bootloader can use usb and read from FAT filesystems,
Now you are rebooting in the new u-boot, write this in its console to install the firmware:
If your firmware file is bigger than 6 MiBs you should write its size in hex
If you are using another uboot that can read ubi, set mtdparts like this
And set your bootcmd to be like this
bootcmd=run setenv bootargs; ubi part ubi; ubi read 0x800000 kernel; bootm 0x800000
Then you can install the firmware as described above.
After you installed (or configured) the u-boot for booting the firmware,
write in the u-boot console (use your MAC address instead of the example)
setenv ethaddr 10:7B:EF:00:00:00
to save the mac address in the u-boot.
Signed-off-by: Alberto Bursi firstname.lastname@example.org
That change was actually done by nbd168 , all kirkwood devices have kernel (uimage) inside the ubi image now, so there is no separate uimage.
This PR for nsa310 generates an uimage (the kernel) and a ubi with rootfs+rootfs_data that works the same as older way, as when I tried to make it with kernel in ubi like for other kirkwoods, the kernel fails to mount the ubi partition even if uboot can mount it and read it fine.
to boot it with bodhi's uboot (and also with stock uboot with minor adjustments) you must set these envs
then append "; run bootcmd_lede" to the list in your bootcmd, mine is
referenced this pull request
Jan 1, 2017
I flashed from bootloader with (there is a partition named "ubi" in the mtdparts):
I used same commands (different partitions) to flash the kernel and the lede-kirkwood-nsa310b-squashfs-factory.bin that has only rootfs+rootfs_data and that boots fine.
No. I tried now and yes it works fine if I install it like that. Thanks.
Will update the PR later as I also need to make a second-stage bootloader now.
So I do it manually and received:
but the devices didn't boot up - I don't have time to connect via serial.
OK When I find I while I will start wiki for this device. Like for other already exist:
Updated, now also power button and smart fan work correctly.
EDIT: hmmm, while it works, mac address is set as 00:00:00:00:00:30, which is not the right one. Here stock uboot can't set mac addresses as it does not initialize the eth, but it does have a variable with a mac. I guess I'll have to set uboot-envtools too and read from old envs to get the right mac.
ok, updated. Now it loads the mac address from u-boot's variable "ethaddr".
Since stock firmware is using a random mac and there is no mac stored anywhere (the mac in stock uboot is bogus, it's the same for all nsa310 devices, I looked at hexdumps of all stock partitions, no mac address anywhere), the user has to read the mac from the sticker under the NAS and set himself the ethaddr variable to uboot after installation.
I opened yet another PR here #731 to add support for this device to uboot-envtools, that PR is obviously a prerequisite for this PR.
It depends from how your custom LEDE is set up.
Imho it would be better if you use LEDE forum for most questions about that. I'm "bobafetthotmail" also in the forum.
I have started wiki - it is late - tomorrow I will add more info https://wiki.openwrt.org/toh/hwdata/zyxel/zyxel_nsa310_1b 2017-01-24 22:31 GMT+01:00 Alberto Bursi <email@example.com>:…
It depends from how your custom LEDE is set up. If you use the serial cable is better, also in case of mistakes it's easier to recover. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#656 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ARv6dfQ_7iB4YZbshQ4R5sQ7NAjQ1ppAks5rVm2mgaJpZM4LYmDn> .