2012-05-29 18:39:15 +02:00
|
|
|
#!/bin/sh
|
|
|
|
|
#
|
2015-12-03 23:27:18 +01:00
|
|
|
# Copyright (C) 2012-2015 OpenWrt.org
|
2012-05-29 18:39:15 +02:00
|
|
|
#
|
|
|
|
|
|
2015-12-11 16:26:06 +01:00
|
|
|
. /lib/functions/uci-defaults.sh
|
2017-02-23 19:42:40 +01:00
|
|
|
. /lib/functions/system.sh
|
2014-06-24 20:18:53 +02:00
|
|
|
|
2015-12-03 23:27:18 +01:00
|
|
|
board_config_update
|
2012-05-29 18:39:15 +02:00
|
|
|
|
2017-05-12 22:36:07 +02:00
|
|
|
board=$(board_name)
|
2015-12-03 23:27:18 +01:00
|
|
|
|
2014-06-24 20:18:53 +02:00
|
|
|
case "$board" in
|
2017-12-28 10:18:48 +01:00
|
|
|
"seagate,dockstar"|\
|
|
|
|
|
"seagate,goflexhome"|\
|
|
|
|
|
"seagate,goflexnet"|\
|
|
|
|
|
"raidsonic,ib-nas62x0"|\
|
|
|
|
|
"iom,iconnect-1.1"|\
|
kirkwood: add pogoplug v4
also known as
POGO-V4-A3-02
or
POGO-V4-A3-01
SoC: Marvell 88F6192 800Mhz
SDRAM memory: 128MB
Gigabit ethernet: 1 Marvell 88E1310
Flash memory: 128MB
2 status LEDs (one green one red)
1 "Eject" button on the back (used as "Reset" button)
1 USB 2.0 port (on upper side)
1 sata slot (power + data) for 2.5'' drives (upper side)
2 USB 3.0 ports from a controller on PCIe x1 of the SoC
1 full-size SDcard slot (fits a whole SD card into it)
This device supports the (linux-only) kwboot tool to send
a new uboot over serial console, so it is easy to unbrick
in case the uboot is erased and the device won't boot.
-----
Install instructions:
-----
Since it's not possible to get ssh access to these
devices, the only way to take control is to
solder pins to get TTL serial access.
Case can be opened by removing screws beneath two rubber
feet at back of device, then lifting while prying the
sides of the upper part out to unhook a latch on each
side about 2/3rds of the way toward the front.
Serial connection pins are those labeled "J11", left
of SD as you face SD opening.
Pins are (from left to right, i.e. the first in the list
is the nearest to the SD slot) GND, Rx, Tx.
Do not connect +V pin if you use a USB (self-powered)
TTL-to-USB dongle. Any USB TTL-to-USB converter will work.
Baud rate is 115200, parity "none", databits "8",
flow control "none".
Stock uboot is unable to read ubi partitions (nor usb)
so we will replace it first with our uboot.
Start a TFTP server at IP address 169.254.254.254, and
place the uboot.kwb file in the folder of the server.
Start the serial session and then power up the device.
As soon as you see text on the serial start pressing random
letter keys to stop the boot process.
If you see something like the following line you can proceed:
CE>>
Otherwise if text is still scrolling by you missed the
opportunity, pull the plug and try again.
write
printenv ethaddr
The uboot will write something like this:
ethaddr=00:50:43:00:02:02
This is the device's MAC address, also present in the sticker
under the device.
Write this down as we will need to add it in the
new uboot configuration.
Use the following commands to load the new uboot:
tftp 0x20000 u-boot.kwb
If the uboot confirms that the transfer was successful,
then you can write it to flash with the following commands:
nand erase 0 0x200000
nand write 0x20000 0 0x1c0000
if after the last command the uboot wrote
"xxxx bytes written: OK"
then it was written correctly and we can proceed.
If it did not go well, try again or ask assistence in forums.
Shutting down or rebooting at this time will brick
the device, to unbrick it you will need to use the kwboot
tool from a Linux PC or Virtual Machine.
Now write:
reset
and press enter, the device will reboot and you should see
again text scrolling by.
Press a random key to stop it, and now you should see
pogoplugv4>
We now add the MAC address back, write:
setenv ethaddr '00:50:43:00:02:02'
Confirm that the uboot has understood by writing
printenv ethaddr
If all looks ok, save the setting with
saveenv
At this point the uboot is configured, and we only need to load
the firmware in the flash memory.
Follow the steps below in "Firmware recovery procedure".
----
Firmware recovery procedure
----
The new uboot allows easy recovery from a bad firmware upgrade
where you can't access the device anymore over ssh or luci.
Take a USB flash drive formatted as FAT32, and copy the
initramfs image file in it (it will have "initramfs" in the
file name), then rename it as "initramfs.bin".
Insert the USB drive in the USB 2.0 port of the pogoplug
(the port at the top).
Power up the device, and wait for it to finish booting.
The uboot should find and load the "initramfs.bin"
from usb and if you are connected with serial you should
see the linux kernel boot log (text scrolling by).
Once it is done, press Enter and you will be greeted by
the OpenWRT banner.
If you were not connected with serial just wait a bit and,
you will be able to access it with ssh or luci web interface
(once you find its IP).
The recovery "initramfs" images are run from RAM, so you will
have to do a normal sysupgrade (firmware upgrade) to write
a firmware image to flash memory.
Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
2018-01-02 16:07:19 +01:00
|
|
|
"cloudengines,pogoe02"|\
|
|
|
|
|
"cloudengines,pogoplugv4")
|
2015-12-03 23:27:18 +01:00
|
|
|
ucidef_set_interface_lan "eth0" "dhcp"
|
2013-10-31 13:04:04 +01:00
|
|
|
;;
|
2017-12-28 10:18:48 +01:00
|
|
|
"linksys,audi"|\
|
|
|
|
|
"linksys,viper")
|
2015-12-03 23:27:18 +01:00
|
|
|
ucidef_add_switch "switch0" \
|
|
|
|
|
"0:lan" "1:lan" "2:lan" "3:lan" "4:wan" "5@eth0" "6@eth1"
|
2014-05-28 23:43:39 +02:00
|
|
|
;;
|
2017-12-28 10:18:48 +01:00
|
|
|
"zyxel,nsa310b"|"zyxel,nsa325")
|
kirkwood: add ZyXEL NSA310b
The ZyXEL NSA310 device is a Kirkwood based NAS:
- SoC: Marvell 88F6702 1200Mhz
- SDRAM memory: 256MB DDR2 400Mhz
- Gigabit ethernet: Realtek (over pcie)
- Flash memory: 128MB
- 1 Power button
- 1 Power LED (blue)
- 5 Status LED (green/red)
- 1 Copy/Sync button
- 1 Reset button
- 2 SATA II port (1 internal and 1 external)
- 2 USB 2.0 ports (1 front and 1 back)
- Smart fan
The stock u-boot cannot read ubi so it should be replaced with the
LEDE/OpenWRT's u-boot or with a u-boot from here
https://github.com/mibodhi/u-boot-kirkwood
This device's boot ROM supports "kwboot" tool
(in mainline u-boot, built automatically if CONFIG_KIRKWOOD is declared)
that sends an uboot image to the board over serial connection, it is very easy to unbrick.
The stock bootloader can use usb and read from FAT filesystems,
so the installation process is simple, place the uboot file on a USB flashdrive
formatted as FAT (here it is "openwrt-kirkwood-nsa310.bin", then connect TTL
to the board and write the following commands in the bootloader console:
usb reset
fatload usb 0 0x1000000 openwrt-kirkwood-nsa310.bin
nand write 0x1000000 0x00000 0x100000
reset
Now you are rebooting in the new u-boot, write this in its console to install the firmware:
usb reset
fatload usb 0 0x2000000 lede-kirkwood-nsa310b-squashfs-factory.bin
nand erase.part ubi
nand write 0x2000000 ubi 0x600000
If your firmware file is bigger than 6 MiBs you should write its size in hex
instead of 0x600000 above, or remove that number entirely (it will take a while in this case).
If you are using another uboot that can read ubi, set mtdparts like this
mtdparts=mtdparts=orion_nand:0x00c0000(uboot),0x80000(uboot_env),0x7ec0000(ubi)
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 the device's mac address in the ethaddr u-boot env.
The MAC address is usually on a sticker under the device (one of the two codes is the serial),
it should begin with "107BEF" as it is assigned to ZyXEL.
write in the u-boot console (use your MAC address instead of the example)
setenv ethaddr 10:7B:EF:00:00:00
saveenv
to save the mac address in the u-boot.
Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
2017-01-23 20:34:29 +01:00
|
|
|
ucidef_set_interface_lan "eth0" "dhcp"
|
2017-02-06 10:20:47 +01:00
|
|
|
ucidef_set_interface_macaddr "lan" $( mtd_get_mac_ascii uboot_env ethaddr )
|
2014-12-19 12:05:13 +01:00
|
|
|
;;
|
2017-12-28 10:18:48 +01:00
|
|
|
"cisco,on100")
|
2017-05-24 17:37:24 +02:00
|
|
|
ucidef_set_interface_lan "eth0 eth1"
|
|
|
|
|
;;
|
2012-05-29 18:39:15 +02:00
|
|
|
*)
|
2016-09-10 09:46:14 +02:00
|
|
|
ucidef_set_interface_lan "eth0"
|
2012-05-29 18:39:15 +02:00
|
|
|
;;
|
|
|
|
|
esac
|
|
|
|
|
|
2015-12-04 00:13:04 +01:00
|
|
|
board_config_flush
|
2012-05-29 18:39:15 +02:00
|
|
|
|
|
|
|
|
exit 0
|