HowTo: OpenWrt on Kirkwood boxes [color=#0608a0]chessplayer's edit (Aug 14th, 2022): Since there is obviously renewed interest in the subject starting, apparently, in June this year and there is now also a [url=https://forum.doozan.com/read.php?4,132635]sibling thread for the OXNAS[/url] machines, some new insights have been gained (or resurfaced), which is why I am making some corrections and/or additions. Thanks go to many people for this, first and foremost, obviously, to [url=https://forum.doozan.com/profile.php?2,297]bodhi[/url], but also to [url=https://forum.doozan.com/read.php?4,86219,86419#msg-86419]daviddyer for his post from three years ago[/url]. This goes along with an apology for my dismissing his part A at the time, which now turns out to be essential, [url=https://forum.doozan.com/read.php?4,132635,132759#msg-132759]especially for the OXNAS[/url], but apparently also for some of the Kirkwood boxes. Another point is that I am removing all references to LEDE (which was the project's name [url=https://openwrt.org/about]for a brief period only[/url], but it was during this period that the [url=https://forum.doozan.com/read.php?4,42279,86214#msg-86214]thread this tutorial is based on[/url] was written - this is how it crept in), since it does not have a place here anymore now (and should not have had when this HowTo was originally written). [/color] My major changes will be reflected [color=#0608a0]in dark blue[/color]. ======== [b][u]How to install OpenWrt on Kirkwood boxes[/u][/b] This thread is a new version of one started by [url=https://forum.doozan.com/read.php?4,42279,86214#msg-86214]joerg_999[/url] since I did run into a few problems with that one and I wanted to suggest a way which seems slightly easier to me and is also more general, since it is not restricted to Pogo E02. Also, I believe Jörg's post is missing a crucial step in connection with bodhi's [url=https://forum.doozan.com/read.php?3,12381]uBoot[/url]. But, a big "Thank you!" goes to Jörg for his original post. The procedure described in this thread is confirmed to work for Dockstar, GoFlexNet, [color=#0608a0]GoFlexHome, Zyxel NSA325, ZyxelNSA320 (see the hints in steps 1. and 2. for these), Pogo v4 (see the link in bodhi's edit above as well as the hint in steps 1 and 5 for this box)[/color], and Pogo E02, so I am confident it will also work for the other Kirkwood boxes OpenWrt provides images for ;-) [b][u]Assumptions[/u][/b] I assume that the box in question has the latest uBoot and is able to boot a USB device with the latest kernel and rootfs according to the first two links in section [b]Kirkwood plugs[/b] of the [url=https://forum.doozan.com/read.php?2,23630]wiki[/url]. [b]Remark:[/b] The procedure described below also seems to work with older uBoots in connection with older kernels and rootfs, which I tested with a GoFlexNet. However, it will be [i][u]absolutely necessary[/u][/i] to be able to reach the box via netconsole or serial console. [b][u]The plan[/u][/b] We now want to install OpenWrt on our box. The steps we will need to take are [list=1] [*] Boot into debian, [color=#0608a0]do some checks on[/color] and make some modifications to the uBoot environment variables [*] Download, rename and copy an OpenWrt Image to a FAT32 USB drive [*] Reboot the box without a USB device but with netconsole to interact with it and [color=#0608a0][b]erase NAND[/b][/color] cat /proc/mtd dev: size erasesize name mtd0: 00200000 00020000 "u-boot" mtd1: 07f00000 00020000 "ubi" [/code] [/color] [i][u]Temporarily generate or modify /etc/fw_env.config[/u][/i] Check whether the file /etc/fw_env.config has the following contents: [code] # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xc0000 0x20000 0x20000 [/code] If not, or the file does not exist at all, the easiest way to generate/overwrite it is [code] echo '/dev/mtd0 0xc0000 0x20000 0x20000' > /etc/fw_env.config [/code] Afterwards, check that the uBoot environment is found by printing the variables to screen using [code] fw_printenv [/code] [i][u]Remark:[/u][/i] Since OpenWrt only runs in RAM at the moment, this is a temporary change. If you want to be able to access the uBoot environment from the OpenWrt rescue system later on, this step will most likely have to be repeated (see step 7 below). [b][u]6. Install to NAND[/u][/b] Finally, we can perform a sysupgrade of OpenWrt either using the LUCI WIF (Web Interface) or the command line. Since we are already logged in via ssh, I only describe the latter option, while the former may be found, e.g., in step 4.b of [url=https://forum.doozan.com/read.php?4,42279]Jörg's original post[/url]. We must do: [code] opkg update opkg install ca-certificates cd /tmp wget sysupgrade [/code] The desired upgrade file may be found the same way as we found the image in step 2 above starting from the [url=https://downloads.openwrt.org/releases/]release page[/url] (but, ideally, you kept the browser tab open in step 2). There you can just copy the link address to the sysupgrade file (tar or bin depending on the release) and paste it into the ssh window. [color=#0608a0] Remark: For older releases of OpenWrt, there might be more you have to install. E.g., for 18.06.2, ca-bundle, libustream-openssl, and ubi-utils were needed as well.[/color] The upgrade process will result in an automatic reboot (during which I removed the USB stick, but that may not be necessary). [b][u]7. Boot from NAND and log in to OpenWrt[/u][/b] It is, unfortunately, quite certain that OpenWrt in NAND also cannot find the uBoot environment (as before in the case of the image loaded into RAM). Therefore, you have to [i][u]repeat step 5. above[/u][/i] in order to be able to modify the uBoot environment. This time, it will be a permanent modification of /etc/fw_env.config allowing you to make changes to the uBoot environment using your new rescue system. [color=#0608a0] [b]Remark:[/b] If ever you decide to do a sysupgrade later on, be it via LUCI WIF or ssh, be aware that you will most probably have to repeat this after the sysupgrade, since only the files in /etc/config seem to be saved and restored during the process! [b][u]8. Optional Modifications[/u][/b] Seeing that OpenWrt will most probably only serve as a last resort on these boxes, these modifications are entirely optional, of course. Nonetheless, some people may find them useful, so I thought I would include them in the updated post. All of these modifications can be done via the LUCI WIF and that is what I will describe here. Alternatively, it may be done directly by modifying the relevant files or using opkg via ssh, but whoever wants to do that may figure out themselves how to. The LUCI WIF is reached via [code] https:// [/code] [list=1] [*][i][u]Install additional packages[/u][/i] First, you should [i]update the package lists[/i] in [i]System - Software[/i] by klicking on the button [i]Update lists ...[/i]. Afterwards, you can use the [i]Filter[/i]-box to find the packages you are looking for. One of those should be ca-certificates. Also, personally, I do not use vim and prefer nano, which I therefore installed. [*][i][u]Set MAC-Address[/u][/i] Should you experience the problem that OpenWrt does not respect the MAC address provided via uBoot or if you want to test something which requires a different MAC-address, you can achieve this by going to [i]Network - Interfaces[/i] and navigating to the [i]Devices[/i] tab, where you should set the MAC-address for both br-lan as well as eth0 to the desired value via the [i]Configure ...[/i] button. [b]Remark:[/b] These changes will result in a different IP address to be assigned if you use DHCP, so when the confirmation pop-up appears, you will have to find out the new IP address [b]in time[/b] and point your browser to that one for the changes to take effect! Otherwise, they will be rolled back! [*][i][u]Change hostname and Timezone[/u][/i] This can be done via [i]System - System[/i] and making the appropriate modifications in the corresponding fields of the [i]General Settings[/i] tab. [*][i][u]Dark Design[/u][/i] Also in [i]System - System[/i], you can navigate to the [i]Language and Style[/i] tab and choose your design. [b]Remark:[/b] If you also want to be able to choose a different language, you first have to install the relevant language pack. [/list] [/color] [b][u]9. Enjoy[/u][/b] ======== bodhi's edit: removed my notice about Pogoplug V4. https://forum.doozan.com/read.php?4,86219,86219#msg-86219 Wed, 11 Mar 2026 07:58:42 -0500 Phorum 5.2.23 https://forum.doozan.com/read.php?4,86219,140595#msg-140595 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,140595#msg-140595

OpenWRT 24.10.04

installs and runs flawlessly. but imho use brodhis lastest uboot (for nsa325 its 2025.10 version with a lot of fixes eg usb enhancements over the "old" (2020) openwrt released uboots). but always kwboot new uboots for testing. sometimes they are broken.]]> Sash Rescue System Wed, 03 Dec 2025 07:02:41 -0600 https://forum.doozan.com/read.php?4,86219,139990#msg-139990 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,139990#msg-139990
* boot into debian usb
* 
apt install dropbear-bin
cd /etc/ssh
dropbearconvert openssh dropbear ssh_host_ed25519_key dropbear_ed25519_host_key
dropbearconvert openssh dropbear ssh_host_rsa_key dropbear_rsa_host_key
shutdown -h now
* remove debian usb
* boot into openwrt
* insert debian usb
* 
opkg update; opkg install block-mount kmod-usb-storage usbutils libblkid gdisk kmod-fs-cifs kmod-fs-exfat kmod-fs-ext4 e2fsprogs
mkdir -p /mnt/sda1
mount /dev/sda1 /mnt/sda1
cd /etc/dropbear
cp -p /mnt/sda1/etc/ssh/dropbear* .
service dropbear restart

Now ssh host keys would be the same.]]> eno789 Rescue System Fri, 04 Jul 2025 17:39:43 -0500 https://forum.doozan.com/read.php?4,86219,139301#msg-139301 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,139301#msg-139301 In case I mess network settings.]]> Tbd6 Rescue System Sat, 08 Mar 2025 15:43:05 -0600 https://forum.doozan.com/read.php?4,86219,136575#msg-136575 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,136575#msg-136575 Before continuing into the technical (of how to do this) I'd like to verify what I am trying to accomplish regarding a rescue system.
I'll start a new topic Under "Rescue System".
Sorry for the confusion.]]> bowent@encorecsl.com Rescue System Tue, 16 Jan 2024 01:59:00 -0600 https://forum.doozan.com/read.php?4,86219,136552#msg-136552 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,136552#msg-136552 > output of the fw_printenv command.

+1

And @bowent, when asking question please show context like this

Quote

1. Modify uBoot variables

First, we need to boot the box to debian and log in. Then, we perform some checks and add to the environment.

1.a Check mtdparts definition

fw_printenv mtdparts
]]> bodhi Rescue System Fri, 05 Jan 2024 21:31:57 -0600 https://forum.doozan.com/read.php?4,86219,136551#msg-136551 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,136551#msg-136551 -------------------------------------------------------
> Greetings, installing rescue system on Pink
> Pogoplug E02 and am getting errors right out of
> the gate.
> Ran command: 
> fw_printenv mtdparts
>
>
> Got this error: 
> ## Error: "mtdparts" not defined
>
> Any help appreciated.

mtdparts is defined in U-Boot, so that indicates it has not been set. Please provide the entire output of the fw_printenv command.]]> rayknight Rescue System Fri, 05 Jan 2024 18:45:53 -0600 https://forum.doozan.com/read.php?4,86219,136550#msg-136550 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,136550#msg-136550 Ran command: 
fw_printenv mtdparts

Got this error: 
## Error: "mtdparts" not defined
Any help appreciated.]]> bowent@encorecsl.com Rescue System Fri, 05 Jan 2024 18:35:29 -0600 https://forum.doozan.com/read.php?4,86219,132976#msg-132976 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,132976#msg-132976 -------------------------------------------------------
> pm4888 Wrote:
> -------------------------------------------------------
> > Just want to add that OpenWrt 21.02 works on
> E02
> > just follow the top post.
> >
> > Thanks a lot.
>
> Do you mean the first post from chessplayer / How
> to install OpenWrt on Kirkwood boxes & just use
> the image from latest 21.02.3 or do you upgrade
> from openwrt version 19 or 18?

No it was not upgrade from 18/19 to 21. It was archlinux to openwrt in NAND. USB HDD is debian.]]> pm4888 Rescue System Sat, 10 Sep 2022 08:39:19 -0500 https://forum.doozan.com/read.php?4,86219,132883#msg-132883 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,132883#msg-132883
Please post the log of how you install, and also the serial boot log. I might be able to see some step missing.]]> bodhi Rescue System Sat, 27 Aug 2022 18:43:26 -0500 https://forum.doozan.com/read.php?4,86219,132882#msg-132882 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,132882#msg-132882 What is the correct u-boot variable mtdparts?

I have use the tutorial on this site to create a ubi image file.]]> andy_help Rescue System Sat, 27 Aug 2022 04:30:52 -0500 https://forum.doozan.com/read.php?4,86219,132726#msg-132726 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,132726#msg-132726
I've tried reinstalling OpenWrt today on my NSA310S and having quite a bit of problem. Perhaps something has changed in sysupgrade process.

Update:

This image works 

https://downloads.openwrt.org/releases/22.03.0-rc6/targets/kirkwood/generic/openwrt-22.03.0-rc6-kirkwood-zyxel_nsa310s-squashfs-sysupgrade.bin
]]> bodhi Rescue System Wed, 10 Aug 2022 18:33:45 -0500 https://forum.doozan.com/read.php?4,86219,132634#msg-132634 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,132634#msg-132634 bodhi Rescue System Fri, 29 Jul 2022 22:46:45 -0500 https://forum.doozan.com/read.php?4,86219,132320#msg-132320 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,132320#msg-132320 bodhi Rescue System Sun, 12 Jun 2022 18:05:19 -0500 https://forum.doozan.com/read.php?4,86219,132319#msg-132319 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,132319#msg-132319 -------------------------------------------------------
> This is also suspected. Will get to that if the
> setenv's did not work.
>
> 
> Sun Jun 12 17:49:29 UTC 2022 upgrade: Device
> cloudengines,pogoe02 not supported by this image
>

Sorry, false alert!
I made a mistake, lol, after I installed Openwrt on Pogoplug E02, I continued to install Openwrt on Pogoploug V4, but I re-used the same uImage from E02!

After I realized and used correct V4 uImage, everything goes well according your instruction for V4
fw_setenv mtdparts 'mtdparts=orion_nand:0x200000@0x0(u-boot),-@0x100000(ubi)'

Thanks Bodhi!]]> happydiy Rescue System Sun, 12 Jun 2022 16:50:25 -0500 https://forum.doozan.com/read.php?4,86219,132318#msg-132318 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,132318#msg-132318 
Sun Jun 12 17:49:29 UTC 2022 upgrade: Device cloudengines,pogoe02 not supported by this image
]]> bodhi Rescue System Sun, 12 Jun 2022 16:14:15 -0500 https://forum.doozan.com/read.php?4,86219,132317#msg-132317 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,132317#msg-132317
Interupt serial/net console at count down, and 

setenv arcNumber 3960
setenv machid f78

And continue installation. If it works, I'll need to revise the u-boot installation instruction to remind users of this.]]> bodhi Rescue System Sun, 12 Jun 2022 16:07:42 -0500 https://forum.doozan.com/read.php?4,86219,132316#msg-132316 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,132316#msg-132316 -------------------------------------------------------
> happydiy,
>
>
> > Got the following error, somehow, messed up
> with
> > Pogoplug E02 env setup
> >
> > Sun Jun 12 17:49:29 UTC 2022 upgrade: Device
> > cloudengines,pogoe02 not supported by this
> image
> > Sun Jun 12 17:49:29 UTC 2022 upgrade: Supported
> > devices: cloudengines,pogoplugv4
> > Image check failed.
> >
>
> Power up, interrupt serial console and
>
> 
> ver
> printenv
>
>
> And post the entire serial console log here. 

ver

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700)
Pogoplug V4
gcc (Debian 6.3.0-18) 6.3.0 20170516
GNU ld (GNU Binutils for Debian) 2.28

printenv

arcNumber=2097
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_lede
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd_lede=run set_bootargs_lede; ubi part ubi; ubi read 0x800000 kernel; bootm 0x800000
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi; sleep 10
bootdelay=10
bootdev=usb
device=0:1
devices=usb ide mmc
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-pogoplug_v4.dtb
ethact=egiga0
ethaddr=00:25:31:05:24:99
if_netconsole=ping $serverip
ipaddr=192.168.1.11
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x2c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
machid=0x831
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:0x200000@0x0(u-boot),-@0x100000(ubi)
ncip=192.168.1.177
partition=nand0,0
preboot=run if_netconsole start_netconsole
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
serverip=192.168.1.177
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
set_bootargs_lede=setenv bootargs console=ttyS0,115200 $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_ready_retry=15

======
moderator edit: please use code tags (Formated code button) to post log.]]> happydiy Rescue System Sun, 12 Jun 2022 15:56:34 -0500 https://forum.doozan.com/read.php?4,86219,132314#msg-132314 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,132314#msg-132314

> Got the following error, somehow, messed up with
> Pogoplug E02 env setup
>
> Sun Jun 12 17:49:29 UTC 2022 upgrade: Device
> cloudengines,pogoe02 not supported by this image
> Sun Jun 12 17:49:29 UTC 2022 upgrade: Supported
> devices: cloudengines,pogoplugv4
> Image check failed.
>

Power up, interrupt serial console and 

ver
printenv

And post the entire serial console log here.]]> bodhi Rescue System Sun, 12 Jun 2022 15:15:45 -0500 https://forum.doozan.com/read.php?4,86219,132313#msg-132313 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,132313#msg-132313 -------------------------------------------------------
> For Pogo V4 the following
> change should be done for the instruction
> in the 1st post.
>
>
>
Quote

1. Modify uBoot variables
>
> First, we need to boot the box to debian, log in
> and then do the following:
>
> fw_setenv mtdparts
> 'mtdparts=orion_nand:0x200000@0x0(u-boot),-@0x100000(ubi)'
>
> This is needed for furture upgrade of u-boot.
> Since release my u-boot defines the mtd0 as 2MB
> (same as stock u-boot).


At step
sysupgrade openwrt-21.02.3-kirkwood-cloudengines_pogoplugv4-squashfs-sysupgrade.bin

Got the following error, somehow, messed up with Pogoplug E02 env setup

Sun Jun 12 17:49:29 UTC 2022 upgrade: Device cloudengines,pogoe02 not supported by this image
Sun Jun 12 17:49:29 UTC 2022 upgrade: Supported devices: cloudengines,pogoplugv4
Image check failed.

Would you please help to resolve this issue?

Thanks]]> happydiy Rescue System Sun, 12 Jun 2022 13:06:01 -0500 https://forum.doozan.com/read.php?4,86219,132312#msg-132312 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,132312#msg-132312 -------------------------------------------------------
> happydiy,
>
> > To confirm, for E02, the following has to be
> the
> > exact same
> >
> > fw_setenv mtdparts
> >
> 'mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)'
> > fw_setenv partition 'nand0,0'
> > fw_setenv set_bootargs_lede 'setenv bootargs
> > console=ttyS0,115200 $mtdparts'
> > fw_setenv bootcmd_lede 'run set_bootargs_lede;
> ubi
> > part ubi; ubi read 0x800000 kernel; bootm
> > 0x800000'
>
> Correct.
>
> And you'll need OpenWrt image for the Pogo E02. As
> mentioned in step2.
>
>
Quote

2. Download an OpenWrt/LEDE image
>
> Next, we need the appropriate image. Start on the
> release page of OpenWrt and choose the one you
> like best and then navigate to
> targets/kirkwood/generic
> Then, download the uImage appropriate for your
> box. Rename it to uImage and place it in the
> root of a FAT32 formatted USD device.

Work perfect for Pogoplug E02 and Openwrt 21.02.3

Thanks Bodhi]]> happydiy Rescue System Sun, 12 Jun 2022 13:03:25 -0500 https://forum.doozan.com/read.php?4,86219,132308#msg-132308 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,132308#msg-132308 following change should be done for the instruction in the 1st post.


Quote

1. Modify uBoot variables

First, we need to boot the box to debian, log in and then do the following:

fw_setenv mtdparts 'mtdparts=orion_nand:0x200000@0x0(u-boot),-@0x100000(ubi)'

This is needed for future u-boot upgrade. Since my released u-boot defines the mtd0 as 2MB (same as stock u-boot), best to use the same definition.]]> bodhi Rescue System Sat, 11 Jun 2022 22:26:57 -0500 https://forum.doozan.com/read.php?4,86219,132306#msg-132306 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,132306#msg-132306
> To confirm, for E02, the following has to be the
> exact same
>
> fw_setenv mtdparts
> 'mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)'
> fw_setenv partition 'nand0,0'
> fw_setenv set_bootargs_lede 'setenv bootargs
> console=ttyS0,115200 $mtdparts'
> fw_setenv bootcmd_lede 'run set_bootargs_lede; ubi
> part ubi; ubi read 0x800000 kernel; bootm
> 0x800000'

Correct.

And you'll need OpenWrt image for the Pogo E02. As mentioned in step2.

Quote

2. Download an OpenWrt/LEDE image

Next, we need the appropriate image. Start on the release page of OpenWrt and choose the one you like best and then navigate to
targets/kirkwood/generic
Then, download the uImage appropriate for your box. Rename it to uImage and place it in the root of a FAT32 formatted USD device.
]]> bodhi Rescue System Sat, 11 Jun 2022 22:11:07 -0500 https://forum.doozan.com/read.php?4,86219,132305#msg-132305 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,132305#msg-132305 -------------------------------------------------------
> happydiy,
>
> > Comparing the new envs
> > fw_setenv mtdparts
> >
> 'mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)'
> > fw_setenv partition 'nand0,0'
> > fw_setenv set_bootargs_lede 'setenv bootargs
> > console=ttyS0,115200 $mtdparts'
> > fw_setenv bootcmd_lede 'run set_bootargs_lede;
> ubi
> > part ubi; ubi read 0x800000 kernel; bootm
> > 0x800000'
> >
> > Do I have to change the two mtdparts &
> partition?
>
> Yes, it is required to reformat the mtd1. For Pogo
> E02 it is the same mtd0 definition (1MB ) so it is
> OK. Use the exisiting Pogo E02 u-boot that you
> have.
>
> > Has anyone tried Pogoplug V4?
> > If yes, are they the same steps?
>
> However, for the Pogo V4, mtd0 is 2MB so
> I need to check chessplayer's
> instruction to see if it is consistent.
> Don't try it yet.

Hi Bodhi,

To confirm, for E02, the following has to be the exact same

fw_setenv mtdparts 'mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)'
fw_setenv partition 'nand0,0'
fw_setenv set_bootargs_lede 'setenv bootargs console=ttyS0,115200 $mtdparts'
fw_setenv bootcmd_lede 'run set_bootargs_lede; ubi part ubi; ubi read 0x800000 kernel; bootm 0x800000']]> happydiy Rescue System Sat, 11 Jun 2022 20:58:04 -0500 https://forum.doozan.com/read.php?4,86219,132303#msg-132303 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,132303#msg-132303
> Comparing the new envs
> fw_setenv mtdparts
> 'mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)'
> fw_setenv partition 'nand0,0'
> fw_setenv set_bootargs_lede 'setenv bootargs
> console=ttyS0,115200 $mtdparts'
> fw_setenv bootcmd_lede 'run set_bootargs_lede; ubi
> part ubi; ubi read 0x800000 kernel; bootm
> 0x800000'
>
> Do I have to change the two mtdparts & partition?

Yes, it is required to reformat the mtd1. For Pogo E02 it is the same mtd0 definition (1MB ) so it is OK. Use the exisiting Pogo E02 u-boot that you have.

> Has anyone tried Pogoplug V4?
> If yes, are they the same steps?

However, for the Pogo V4, mtd0 is 2MB so I need to check chessplayer's instruction to see if it is consistent. Don't try it yet.]]> bodhi Rescue System Sat, 11 Jun 2022 20:11:33 -0500 https://forum.doozan.com/read.php?4,86219,132301#msg-132301 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,132301#msg-132301 mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
set_bootargs_lede=
bootcmd_lede=

Comparing the new envs
fw_setenv mtdparts 'mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)'
fw_setenv partition 'nand0,0'
fw_setenv set_bootargs_lede 'setenv bootargs console=ttyS0,115200 $mtdparts'
fw_setenv bootcmd_lede 'run set_bootargs_lede; ubi part ubi; ubi read 0x800000 kernel; bootm 0x800000'

Do I have to change the two mtdparts & partition?

Has anyone tried Pogoplug V4?
If yes, are they the same steps?

Thanks]]> happydiy Rescue System Sat, 11 Jun 2022 19:20:36 -0500 https://forum.doozan.com/read.php?4,86219,132237#msg-132237 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,132237#msg-132237 -------------------------------------------------------
> pm4888 Wrote:
> -------------------------------------------------------
> > Just want to add that OpenWrt 21.02 works on
> E02
> > just follow the top post.
> >
> > Thanks a lot.
>
> Do you mean the first post from chessplayer / How
> to install OpenWrt on Kirkwood boxes & just use
> the image from latest 21.02.3 or do you upgrade
> from openwrt version 19 or 18?

I meant the first post. The essence is to boot with initramfs-uImage, modify fw_env.config and finally sysupgrade with squashfs-sysupgrade image.]]> pm4888 Rescue System Sat, 28 May 2022 13:55:18 -0500 https://forum.doozan.com/read.php?4,86219,132236#msg-132236 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,132236#msg-132236 -------------------------------------------------------
> Just want to add that OpenWrt 21.02 works on E02
> just follow the top post.
>
> Thanks a lot.

Do you mean the first post from chessplayer / How to install OpenWrt on Kirkwood boxes & just use the image from latest 21.02.3 or do you upgrade from openwrt version 19 or 18?]]> happydiy Rescue System Sat, 28 May 2022 12:51:20 -0500 https://forum.doozan.com/read.php?4,86219,132164#msg-132164 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,132164#msg-132164
fw_printenv(difference between default debian uboot and mine): 
mtdparts=mtdparts=orion_nand:1M(uboot),-(ubi)
bootubi=echo Trying to boot from NAND ...; ubi part ubi; ubi read 0x800000 kernel; setenv bootargs console=ttyS0,115200 ${mtdparts}; bootm 0x800000
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootubi


dmesg
[    0.608281] Creating 2 MTD partitions on "orion_nand":
[    0.613444] 0x000000000000-0x000000100000 : "uboot"
[    0.618988] 0x000000100000-0x000008000000 : "ubi"

root@OpenWrt:/tmp# ubinfo -a
UBI version:                    1
Count of UBI devices:           1
UBI control device major/minor: 10:62
Present UBI devices:            ubi0

ubi0
Volumes count:                           3
Logical eraseblock size:                 129024 bytes, 126.0 KiB
Total amount of logical eraseblocks:     1016 (131088384 bytes, 125.0 MiB)
Amount of available logical eraseblocks: 0 (0 bytes)
Maximum count of volumes                 128
Count of bad physical eraseblocks:       0
Count of reserved physical eraseblocks:  20
Current maximum erase counter value:     4
Minimum input/output unit size:          2048 bytes
Character device major/minor:            250:0
Present volumes:                         0, 1, 2

Volume ID:   0 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        19 LEBs (2451456 bytes, 2.3 MiB)
State:       OK
Name:        kernel
Character device major/minor: 250:1
-----------------------------------
Volume ID:   1 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        18 LEBs (2322432 bytes, 2.2 MiB)
State:       OK
Name:        rootfs
Character device major/minor: 250:2
-----------------------------------
Volume ID:   2 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        955 LEBs (123217920 bytes, 117.5 MiB)
State:       OK
Name:        rootfs_data
Character device major/minor: 250:3
]]> pm4888 Rescue System Mon, 02 May 2022 16:00:42 -0500 https://forum.doozan.com/read.php?4,86219,132163#msg-132163 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,132163#msg-132163
Thanks a lot.]]> pm4888 Rescue System Mon, 02 May 2022 15:22:48 -0500 https://forum.doozan.com/read.php?4,86219,109989#msg-109989 Re: HowTo: OpenWrt on Kirkwood boxes https://forum.doozan.com/read.php?4,86219,109989#msg-109989 https://forum.doozan.com/read.php?4,109979,109984#msg-109984]]> echowarrior108 Rescue System Sun, 25 Oct 2020 11:34:11 -0500