How to install LEDE/openwrt on a Pogo E02:
You can do this similar with all the kirkwoodplugs using the matching files...

Note: If you dont have serial console (USB/serial adapter), NC (NetCat) should be configured properly!

1. Upgrade the Uboot + uboot-envs to most recent bodhi version
(atm = uboot.2017.07-tld-1.pogo_e02.bodhi + uboot.2016.05-tld-1.environment)

download, (rename) and place the lede-kirkwood-pogo_e02-initramfs-uImage on the root of a USB flash drive
formatted with FAT32 and insert it in the device

https://downloads.lede-project.org/releases/17.01.4/targets/kirkwood/generic/lede-17.01.4-kirkwood-pogo_e02-initramfs-uImage

That file is a LEDE system image that runs from RAM, and you will only use that
to do a sysupgrade as normal with lede-kirkwood-pogo_e02-squashfs-sysupgrade.tar.
It will reformat flash if needed, deal with any bad blocks and so on.
Put this stick into Pogo
then from uboot write set the new parameters

2. Set additional parameters for dualboot LEDE/nand and debian/stick (based on bodhis uboot.2016.05-tld-1 envs)
with this envs extensions you can upgrade nand only with WIF, but soft reboot works (didnt work with old one)
and you have to change the envs only once with the following:

# bootenvs for Pogo E02 based on uboot.2016.05-tld-1.environment:

setenv mtdparts 'mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)' 
setenv partition 'nand0,0' 
setenv set_bootargs_lede 'setenv bootargs console=ttyS0,115200 $mtdparts'
setenv bootcmd_lede 'run set_bootargs_lede; ubi part ubi; ubi read 0x800000 kernel; bootm 0x800000'
setenv bootcmd 'run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_lede'
setenv bootcmd_exec 'if run load_uimage; then; 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; fi'
saveenv
nand erase.part ubi

# when you change/add a new partition layout you always need to erase the ubi nand first before new install:
nand erase.part ubi

3. Run the following code for starting the process:

# @bootloader run LEDE from usb pendrive
usb reset; fatload usb 0 0x800000 lede-kirkwood-pogo_e02-initramfs-uImage; bootm 0x800000

Here you have the choice how to upgrade: 4a CLI or 4b over LEDE/openwrt-WIF - use this!!

4a. CLI upgrade: (wont work anymore, you will run out of space with newer Lede or openwrt - use 4b)

opkg update
opkg install libustream-openssl ubi-utils
cd /tmp
wget https://downloads.lede-project.org/releases/17.01.4/targets/kirkwood/generic/lede-17.01.4-kirkwood-pogo_e02-squashfs-sysupgrade.tar
sysupgrade lede*kirkwood-pogo_e02-squashfs-sysupgrade.tar

or:

4b. LEDE/openwrt-WIF upgrade:

log in a Webbrowser session @pogos ipadress
download the upgrade-File on your PC.
Link:
lede-17.01.04-kirkwood-pogo_e02-squashfs-sysupgrade.tar

in the LEDE menue search for Upgrade device/router and select your downloaded file
press upgrade and wait

Pogo will reboot and start from nand with LEDE/openwrt

5. change/create the /etc/fw_env.config in LEDE/openwrt to:

/dev/mtd0 0xc0000 0x20000 0x20000

Than you can install all the pakets you need... :)

opkg update
opkg install ca-bundle ca-certificates libustream-openssl ubi-utils nano bzip2 openssh-sftp-server    # for example

enjoy joerg_999

========

bodhi: promoted this as a sticky thread and change topic title to OpenWrt/Lede



Edited 42 time(s). Last edit at 01/16/2024 09:58AM by bodhi.

Nice :) Added to Wiki thread.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 11/17/2017 03:40AM by bodhi.

I checked LEDE kirkwood list od supported devices and sadly HP t5325 isn't listed.
Any ideas if it can be installed on t5325?

Hi,

I've tried this method and I'm able to run lede from memory. However when I run sysupgrade something goes wrong and lede does not get installed to nand. The reboot after sysupgrade results in the uboot prompt. Maybe this was due to the fat32 usb stick still being plugged in so I repeated the steps but removed the usb stick before the sysupgrade command. Unfortunately the result is the same uboot prompt and lede has not been installed to nand. When I plug in the debian usb stick and restart the device it starts debian without problems. Could someone more knowledgeable have a look at my config and see if they can spot what causes the problem?

Thanks

root@debian:~# cat /proc/mtd 
dev:    size   erasesize  name
mtd0: 00100000 00020000 "u-boot"
mtd1: 07f00000 00020000 "ubi"

root@debian:~# fw_printenv 
arcNumber=2097
bootargs_lede= 
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_lede
bootcmd_exec=if run load_uimage; then; 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; 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
bootdelay=10
bootdev=usb
device=0:1
devices=usb ide mmc
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-pogo_e02.dtb
ethact=egiga0
ethaddr=52:3b:20:9c:11:51
if_netconsole=ping $serverip
ipaddr=192.168.0.231
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=0x1c00000
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:0x100000@0x0(u-boot),-@0x100000(ubi)
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
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.0.220
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=serial
stdin=serial
stdout=serial
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

----
Mod: use code tags



Edited 1 time(s). Last edit at 03/03/2018 05:50PM by bodhi.

konus,

Looks like your envs were messed up.

Update: never mind. The envs look OK as I can tell. You will need to post a log of the reboot so we can see it better.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 2 time(s). Last edit at 03/03/2018 05:58PM by bodhi.

It's good to hear the envs look OK. I've started again from the beginning (but skipping the initial envs setup) and put the output of the steps below.

output from serial / picocom:

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:13:18 -0700)
Pogo E02

SoC:   Kirkwood 88F6281_A0
DRAM:  256 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Hit any key to stop autoboot:  0 
PogoE02>

PogoE02> nand erase.part ubi

NAND erase.part: invalid partition number 2 for device nand0 (orion_nand)
no such partition
device 0 offset 0x100000, size 0x7f00000
Skipping bad block at  0x056e0000                                          
Skipping bad block at  0x05700000                                          
Erasing at 0x7fe0000 -- 100% complete.
OK

PogoE02> nand erase.part ubi

NAND erase.part: device 0 offset 0x100000, size 0x7f00000
Skipping bad block at  0x056e0000                                          
Skipping bad block at  0x05700000                                          
Erasing at 0x7fe0000 -- 100% complete.
OK

PogoE02> usb reset; fatload usb 0 0x800000 lede-kirkwood-pogo_e02-initramfs-uImage; bootm 0x800000
resetting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found
reading lede-kirkwood-pogo_e02-initramfs-uImage
3219150 bytes read in 217 ms (14.1 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   ARM LEDE Linux-4.4.92
   Created:      2017-10-17  17:46:20 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3219086 Bytes = 3.1 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
Using machid 0x831 from environment

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.4.92 (buildbot@builds-02.infra.lede-project.org) (gcc version 5.4.0 (LEDE GCC 5.4.0 r3103-1b51a49) ) #0 Tue Oct 17 17:46:20 2017
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine model: Cloud Engines Pogoplug E02
[    0.000000] Memory policy: Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
[    0.000000] Kernel command line: console=ttyS0,115200n8
[    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Memory: 249548K/262144K available (4082K kernel code, 142K rwdata, 652K rodata, 5128K init, 201K bss, 12596K reserved, 0K cma-reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xd0800000 - 0xff800000   ( 752 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc04a7db4   (4736 kB)
[    0.000000]       .init : 0xc04a8000 - 0xc09aa000   (5128 kB)
[    0.000000]       .data : 0xc09aa000 - 0xc09cdbc8   ( 143 kB)
[    0.000000]        .bss : 0xc09cdbc8 - 0xc0a0027c   ( 202 kB)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[    0.000009] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[    0.000085] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
[    0.090088] pid_max: default: 32768 minimum: 301
[    0.090205] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090224] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090791] CPU: Testing write buffer coherency: ok
[    0.091144] Setting up static identity map for 0x81e0 - 0x821c
[    0.091390] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x2
[    0.095956] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.095983] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.096070] pinctrl core: initialized pinctrl subsystem
[    0.097146] NET: Registered protocol family 16
[    0.097502] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.098219] cpuidle: using governor ladder
[    0.098532] Feroceon L2: Enabling L2
[    0.098577] Feroceon L2: Cache support initialised.
[    0.098851] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[    0.116381] SCSI subsystem initialized
[    0.117102] usbcore: registered new interface driver usbfs
[    0.117179] usbcore: registered new interface driver hub
[    0.117246] usbcore: registered new device driver usb
[    0.118040] clocksource: Switched to clocksource orion_clocksource
[    0.118926] NET: Registered protocol family 2
[    0.119528] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[    0.119564] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[    0.119594] TCP: Hash tables configured (established 2048 bind 2048)
[    0.119651] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.119673] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.119819] NET: Registered protocol family 1
[    0.206051] Crashlog allocated RAM at address 0x3f00000
[    0.218614] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.218628] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.221302] io scheduler noop registered
[    0.221315] io scheduler deadline registered (default)
[    0.222516] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[    0.223081] irq: Cannot allocate irq_descs @ IRQ32, assuming pre-allocated
[    0.223433] irq: Cannot allocate irq_descs @ IRQ64, assuming pre-allocated
[    0.254807] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.257781] console [ttyS0] disabled
[    0.257853] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 25, base_baud = 12500000) is a 16550A
[    0.701586] console [ttyS0] enabled
[    0.706466] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[    0.712881] nand: Hynix NAND 128MiB 3,3V 8-bit
[    0.717342] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    0.724967] Scanning device for bad blocks
[    0.802599] Bad eraseblock 695 at 0x0000056e0000
[    0.807286] Bad eraseblock 696 at 0x000005700000
[    0.846522] 4 ofpart partitions found on MTD device orion_nand
[    0.852392] Creating 4 MTD partitions on "orion_nand":
[    0.857553] 0x000000000000-0x000000100000 : "u-boot"
[    0.864264] 0x000000100000-0x000000500000 : "uImage"
[    0.870386] 0x000000500000-0x000002500000 : "pogoplug"
[    0.876668] 0x000002500000-0x000008000000 : "root"
[    0.883281] libphy: orion_mdio_bus: probed
[    0.888229] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    0.896347] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 52:3b:20:9c:11:51
[    0.905167] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    0.911742] ehci-pci: EHCI PCI platform driver
[    0.916271] ehci-platform: EHCI generic platform driver
[    0.921666] ehci-orion: EHCI orion driver
[    0.925847] orion-ehci f1050000.ehci: EHCI Host Controller
[    0.931404] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[    0.939234] orion-ehci f1050000.ehci: irq 29, io mem 0xf1050000
[    0.958059] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[    0.964808] hub 1-0:1.0: USB hub found
[    0.968789] hub 1-0:1.0: 1 port detected
[    0.973179] usbcore: registered new interface driver usb-storage
[    1.288053] usb 1-1: new high-speed USB device number 2 using orion-ehci
[    1.440280] hub 1-1:1.0: USB hub found
[    1.444374] hub 1-1:1.0: 4 ports detected
[    1.728051] usb 1-1.1: new high-speed USB device number 3 using orion-ehci
[    1.839587] usb-storage 1-1.1:1.0: USB Mass Storage device detected
[    1.846276] scsi host0: usb-storage 1-1.1:1.0
[    1.988051] rtc-mv f1010300.rtc: internal RTC not ticking
[    1.993577] i2c /dev entries driver
[    1.997809] orion_wdt: Initial timeout 21 sec
[    2.005550] marvell-cesa f1030000.crypto: CESA device successfully registered
[    2.013722] NET: Registered protocol family 10
[    2.019735] NET: Registered protocol family 17
[    2.024240] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[    2.036935] 8021q: 802.1Q VLAN Support v1.8
[    2.043349] hctosys: unable to open rtc device (rtc0)
[    2.064294] Freeing unused kernel memory: 5128K
[    2.101348] init: Console is alive
[    2.104908] init: - watchdog -
[    2.114402] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    2.121618] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[    2.131548] init: - preinit -
[    2.206026] random: jshn: uninitialized urandom read (4 bytes read, 4 bits of entropy available)
[    2.239608] random: jshn: uninitialized urandom read (4 bytes read, 4 bits of entropy available)
[    2.271346] random: jshn: uninitialized urandom read (4 bytes read, 5 bits of entropy available)
[    2.303648] random: jshn: uninitialized urandom read (4 bytes read, 5 bits of entropy available)
[    2.333320] random: jshn: uninitialized urandom read (4 bytes read, 5 bits of entropy available)
[    2.362609] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[    2.372541] mv643xx_eth_port mv643xx_eth_port.0 eth0: link down
[    2.379664] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    2.400668] random: procd: uninitialized urandom read (4 bytes read, 5 bits of entropy available)
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
[    2.848960] scsi 0:0:0:0: Direct-Access     SanDisk  Cruzer           1.26 PQ: 0 ANSI: 5
[    2.858926] sd 0:0:0:0: [sda] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
[    2.868400] sd 0:0:0:0: [sda] Write Protect is off
[    2.873894] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    2.888813]  sda: sda1
[    2.894146] sd 0:0:0:0: [sda] Attached SCSI removable disk
[    4.496065] procd: - early -
[    4.499471] procd: - watchdog -
[    5.322209] procd: - watchdog -
[    5.325563] procd: - ubus -
[    5.332798] random: ubusd: uninitialized urandom read (4 bytes read, 20 bits of entropy available)
[    5.378765] random: ubusd: uninitialized urandom read (4 bytes read, 20 bits of entropy available)
[    5.388078] random: ubusd: uninitialized urandom read (4 bytes read, 20 bits of entropy available)
[    5.397116] random: ubusd: uninitialized urandom read (4 bytes read, 20 bits of entropy available)
[    5.407097] procd: - init -
Please press Enter to activate this console.
[    5.501480] kmodloader: loading kernel modules from /etc/modules.d/*
[    5.510062] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    5.521669] ip_tables: (C) 2000-2006 Netfilter Core Team
[    5.531116] nf_conntrack version 0.5.0 (3979 buckets, 15916 max)
[    5.554827] xt_time: kernel timezone is -0000
[    5.565648] PPP generic driver version 2.4.2
[    5.571509] NET: Registered protocol family 24
[    5.578874] kmodloader: done loading kernel modules from /etc/modules.d/*
[    8.759197] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[    8.818103] device eth0 entered promiscuous mode
[    8.854412] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[    9.738700] br-lan: port 1(eth0) entered forwarding state
[    9.744165] br-lan: port 1(eth0) entered forwarding state
[    9.787066] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[   11.738051] br-lan: port 1(eth0) entered forwarding state
[   64.158948] random: nonblocking pool is initialized



BusyBox v1.25.1 () built-in shell (ash)

     _________
    /        /\      _    ___ ___  ___
   /  LE    /  \    | |  | __|   \| __|
  /    DE  /    \   | |__| _|| |) | _|
 /________/  LE  \  |____|___|___/|___|                      lede-project.org
 \        \   DE /
  \    LE  \    /  -----------------------------------------------------------
   \  DE    \  /    Reboot (17.01.4, r3560-79f57e422d)
    \________\/    -----------------------------------------------------------

=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
root@LEDE:/#

root@LEDE:/# opkg update
Downloading http://downloads.lede-project.org/releases/17.01.4/targets/kirkwood/generic/packages/Packages.gz
Updated list of available packages in /var/opkg-lists/reboot_core
Downloading http://downloads.lede-project.org/releases/17.01.4/targets/kirkwood/generic/packages/Packages.sig
Signature check passed.
Downloading http://downloads.lede-project.org/releases/17.01.4/packages/arm_xscale/base/Packages.gz
Updated list of available packages in /var/opkg-lists/reboot_base
Downloading http://downloads.lede-project.org/releases/17.01.4/packages/arm_xscale/base/Packages.sig
Signature check passed.
Downloading http://downloads.lede-project.org/releases/17.01.4/packages/arm_xscale/luci/Packages.gz
Updated list of available packages in /var/opkg-lists/reboot_luci
Downloading http://downloads.lede-project.org/releases/17.01.4/packages/arm_xscale/luci/Packages.sig
Signature check passed.
Downloading http://downloads.lede-project.org/releases/17.01.4/packages/arm_xscale/packages/Packages.gz
Updated list of available packages in /var/opkg-lists/reboot_packages
Downloading http://downloads.lede-project.org/releases/17.01.4/packages/arm_xscale/packages/Packages.sig
Signature check passed.
Downloading http://downloads.lede-project.org/releases/17.01.4/packages/arm_xscale/routing/Packages.gz
Updated list of available packages in /var/opkg-lists/reboot_routing
Downloading http://downloads.lede-project.org/releases/17.01.4/packages/arm_xscale/routing/Packages.sig
Signature check passed.
Downloading http://downloads.lede-project.org/releases/17.01.4/packages/arm_xscale/telephony/Packages.gz
Updated list of available packages in /var/opkg-lists/reboot_telephony
Downloading http://downloads.lede-project.org/releases/17.01.4/packages/arm_xscale/telephony/Packages.sig
Signature check passed.
root@LEDE:/#

root@LEDE:/# opkg install ca-bundle ca-certificates libustream-openssl ubi-utils
 kmod-mtd-rw
Installing ca-bundle (20170717) to root...
Downloading http://downloads.lede-project.org/releases/17.01.4/packages/arm_xscale/base/ca-bundle_20170717_all.ipk
Installing ca-certificates (20170717) to root...
Downloading http://downloads.lede-project.org/releases/17.01.4/packages/arm_xscale/base/ca-certificates_20170717_all.ipk
Installing libustream-openssl (2016-07-02-ec80adaa-2) to root...
Downloading http://downloads.lede-project.org/releases/17.01.4/packages/arm_xscale/base/libustream-openssl_2016-07-02-ec80adaa-2_arm_xscale.ipk
Installing zlib (1.2.11-1) to root...
Downloading http://downloads.lede-project.org/releases/17.01.4/packages/arm_xscale/base/zlib_1.2.11-1_arm_xscale.ipk
Installing libopenssl (1.0.2n-1) to root...
Downloading http://downloads.lede-project.org/releases/17.01.4/packages/arm_xscale/base/libopenssl_1.0.2n-1_arm_xscale.ipk
Package ubi-utils (1.5.2-1) installed in root is up to date.
Installing kmod-mtd-rw (4.4.92+git-20160214-1) to root...
Downloading http://downloads.lede-project.org/releases/17.01.4/targets/kirkwood/generic/packages/kmod-mtd-rw_4.4.92+git-20160214-1_arm_xscale.ipk
Configuring zlib.
Configuring libopenssl.
Configuring libustream-openssl.
Configuring kmod-mtd-rw.
Configuring ca-certificates.
Configuring ca-bundle.
root@LEDE:/#

Everything seems OK so far. Opened another teminal and ssh-ed in.

ssh root@192.168.1.117
The authenticity of host '192.168.1.117 (192.168.1.117)' can't be established.
RSA key fingerprint is SHA256:M8BVFmiao5i8TWZ7IZiLeemQpi5sE/TBJ3sH1T3NhHA.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.1.117' (RSA) to the list of known hosts.


BusyBox v1.25.1 () built-in shell (ash)

     _________
    /        /\      _    ___ ___  ___
   /  LE    /  \    | |  | __|   \| __|
  /    DE  /    \   | |__| _|| |) | _|
 /________/  LE  \  |____|___|___/|___|                      lede-project.org
 \        \   DE /
  \    LE  \    /  -----------------------------------------------------------
   \  DE    \  /    Reboot (17.01.4, r3560-79f57e422d)
    \________\/    -----------------------------------------------------------

=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
root@LEDE:~#

root@LEDE:~# cd /tmp
root@LEDE:/tmp# wget https://downloads.lede-project.org/releases/17.01.4/targets/kirkwood/generic/lede-17.01.4-kirkwood-pogo_e02-squas
hfs-sysupgrade.tar
Downloading 'https://downloads.lede-project.org/releases/17.01.4/targets/kirkwood/generic/lede-17.01.4-kirkwood-pogo_e02-squashfs-sysupgrade.tar';
Connecting to 148.251.78.235:443
Writing to 'lede-17.01.4-kirkwood-pogo_e02-squashfs-sysupgrade.tar'
lede-17.01.4-kirkwoo 100% |*******************************|  3310k  0:00:00 ETA
Download completed (3389440 bytes)
root@LEDE:/tmp# 
root@LEDE:/tmp# ls
TZ                                                      log
board.json                                              opkg-lists
dhcp.leases                                             resolv.conf
dnsmasq.d                                               resolv.conf.auto
dropbear                                                run
etc                                                     shm
hosts                                                   state
lede-17.01.4-kirkwood-pogo_e02-squashfs-sysupgrade.tar  sysinfo
lib                                                     tmp
lock                                                    usr
root@LEDE:/tmp#

Quick check of the checksum to make sure the file is correct

root@LEDE:/tmp# sha256sum lede-17.01.4-kirkwood-pogo_e02-squashfs-sysupgrade.tar 
dc8dfe6faf705b6b1498303efe00b810b628a4c163cb3410291060091b836d98  lede-17.01.4-kirkwood-pogo_e02-squashfs-sysupgrade.tar
root@LEDE:/tmp#

remove the fat32 usb stick results in the following message over serial:

root@LEDE:/# [ 1180.339880] usb 1-1.1: USB disconnect, device number 3

The sysupgrade output will be put in a new message to make things easier to read.

So I think everything looks OK until now. Below is the rest of the output from the sysupgrade process.

from ssh session run sysupgrade using the -v option to try to get more verbose output:

root@LEDE:/tmp# sysupgrade -v lede*kirkwood-pogo_e02-squashfs-sysupgrade.tar
Image metadata not found
Cannot save config while running from ramdisk.
Connection to 192.168.1.117 closed by remote host.
Connection to 192.168.1.117 closed.

output of the serial connection / picocom during the sysupgrade process:

root@LEDE:/# Watchdog handover: fd=3
- watchdog -
killall: telnetd: no process killed
Sending TERM to remaining processes ... ubusd logd rpcd netifd odhcpd uhttpd ntpd dnsmasq 
Sending KILL to remaining processes ... 
cannot find ubi mtd partition rootfs
libubi: error!: "/dev/" is not a character device
ubiupdatevol: error!: error while probing "/dev/"
              error 22 (Invalid argument)
tar: write error: Broken pipe
libubi: error!: "/dev/" is not a character device
ubiupdatevol: error!: error while probing "/dev/"
              error 22 (Invalid argument)
tar: write error: Broken pipe
sysupgrade successful
umount: c[ 1511.201136] reboot: Restarting system


U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:13:18 -0700)
Pogo E02

SoC:   Kirkwood 88F6281_A0
DRAM:  256 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Hit any key to stop autoboot:  0 
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'
## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
** Bad device usb 0 **
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'
running scan_disk ...
Scan device usb
device usb 0:1
** Bad device usb 0 **
device usb 1:1
** Bad device usb 1 **
device usb 2:1
** Bad device usb 2 **
device usb 3:1
** Bad device usb 3 **
Scan device ide
Unknown command 'ide' - try 'help'
device ide 0:1
** Bad device ide 0 **
device ide 1:1
** Bad device ide 1 **
device ide 2:1
** Bad device ide 2 **
device ide 3:1
** Bad device ide 3 **
Scan device mmc
Unknown command 'mmc' - try 'help'
device mmc 0:1
** Bad device mmc 0 **
device mmc 1:1
** Bad device mmc 1 **
device mmc 2:1
** Bad device mmc 2 **
device mmc 3:1
** Bad device mmc 3 **
loading uImage ...
** Bad device usb 0 **
invalid partition number 2 for device nand0 (orion_nand)
no such partition
ubi0: attaching mtd1
ubi0: scanning is finished
ubi0: empty MTD device detected
ubi0: attached mtd1 (name "mtd=1", size 127 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi0: VID header offset: 512 (aligned 512), data offset: 2048
ubi0: good PEBs: 1014, bad PEBs: 2, corrupted PEBs: 0
ubi0: user volume: 0, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 0
ubi0: available PEBs: 992, total reserved PEBs: 22, PEBs reserved for bad PEB handling: 18
Read 0 bytes from volume kernel to 800000
Volume kernel not found!
Wrong Image Format for bootm command
ERROR: can't get kernel image!
PogoE02>

So there clearly are some errors during the sysupgrade process but it finishes with the message 'sysupgrade successful' so maybe it is OK? The uboot message shows an empty mtd device so I guess the write to nand has failed or uboot can't find the partition.

output from mtdparts:

PogoE02> mtdparts 

device nand0 <orion_nand>, # parts = 2
 #: name                size            offset          mask_flags
 0: u-boot              0x00100000      0x00000000      0
 1: ubi                 0x07f00000      0x00100000      0

active partition: nand0,0 - (u-boot) 0x00100000 @ 0x00000000

defaults:
mtdids  : none
mtdparts: none
PogoE02>

below the output of printenv:

PogoE02> printenv 
arcNumber=2097
bootargs=console=ttyS0,115200 mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)
bootargs_lede= 
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_lede
bootcmd_exec=if run load_uimage; then; 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; 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
bootdelay=10
bootdev=usb
device=0:1
devices=usb ide mmc
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-pogo_e02.dtb
ethact=egiga0
ethaddr=52:3b:20:9c:11:51
if_netconsole=ping $serverip
init_ide=ide reset
init_mmc=mmc rescan
init_usb=usb start
ipaddr=192.168.0.231
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=0x1c00000
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
mtddevname=u-boot
mtddevnum=0
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)
partition=nand0,0
preboot_nc=run if_netconsole start_netconsole
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
scan_ide=ide reset
scan_mmc=mmc rescan
scan_usb=usb start
serverip=192.168.0.220
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=serial
stdin=serial
stdout=serial
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_loaded=0
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

Environment size: 3331/131068 bytes
PogoE02>

konus,

Everything looks OK. Try to find the box IP and log in with SSH.


If it did not start and you cannot find the IP. Try installation again, and use -n option when running sysupgrade:

sysupgrade -n lede*kirkwood-pogo_e02-squashfs-sysupgrade.tar

The output should looks like

Image metadata not found
Connection to 192.168.1.117 closed by remote host.
Connection to 192.168.1.117 closed.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi Bodhi,

thanks for your time. I've tried all sysupgrade -n, -i, and -p options but none seem to make it work. One thing I noticed is that my printenv shows

arcNumber=2097

while joerg_999's printenv from another thread shows

arcNumber=3542

Could that be the issue?

OK that seems to have done the trick

setenv arcNumber 3542
saveenv
reset

Then follow all the steps in joerg_999's original description at the top of the page.

This results in a lede install in nand. It still boots debian when I reboot while the correct usb stick is plugged in.

Thanks a lot for your time. These little boxes are great low power backup machines for different family members. I install the sshelper app on android and then use a cron rsync script to backup phones and tablets to an usb drive without the need to use any of the big cloud providers. They also run openvpn providing a safe connection when using public wifi.

That's odd.

The Pogo E02 arcNumber is 3542. But it should work with arcNumber 2097 which is the Reference Board which work with Sheevaplug, Dockstar, Pogoplug E02, GFHome/Net. Something is not right about this LELDE configuration.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Something even stranger here! This is a FDT kernel, which should not care about arcNumber.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

konus Wrote:
-------------------------------------------------------
> OK that seems to have done the trick
>
> setenv arcNumber 3542
> saveenv
> reset
>
> Then follow all the steps in joerg_999's original
> description at the top of the page.
>
> This results in a lede install in nand. It still
> boots debian when I reboot while the correct usb
> stick is plugged in.
>
> Thanks a lot for your time. These little boxes are
> great low power backup machines for different
> family members. I install the sshelper app on
> android and then use a cron rsync script to backup
> phones and tablets to an usb drive without the
> need to use any of the big cloud providers. They
> also run openvpn providing a safe connection when
> using public wifi.

I will do a complement for safety in the first post but like bodhi said,
on the one hand 3542 ist the correct arcNumber for the Pogo E02 and
on the other hand this is a FDT kernel, which should not care about arcNumber.

-- joerg_999

joerg,

Try remove arcNumber temorarily in serial console

setenv arcNumber

And boot

boot

See it will boot into LEDE.

By the way, this is not needed to do.

setenv bootargs_lede ' '

And these 2 should not be done, because you want to keep these envs for booting with Debian on USB. In booting LEDE, the env set_bootargs_lede is enough.

setenv bootargs
setenv console

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

hallo bodhi,
i´ve tried your suggestion and it
worked also without any arcNumber....
LEDE and debian

-- joerg_999

joerg_999 Wrote:
-------------------------------------------------------
> hallo bodhi,
> i´ve tried your suggestion and it
> worked also without any arcNumber....
> LEDE and debian
>
> -- joerg_999

Cool!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Does this instrstruction work with Pogo V3 Classic/Pro?

pogoplug-v3-squashfs-sysupgrade.tar
pogoplug-v3-squashfs-ubinized.bin
pogoplug-v3-u-boot-initramfs.bin
pogoplug-v3-uImage
pogoplug-v3-ubifs-sysupgrade.tar
pogoplug-v3-ubifs-ubinized.bin

Use the pogoplug-v3-u-boot-initramfs.bin to replace lede-kirkwood-pogo_e02-initramfs-uImage?

rynax Wrote:
-------------------------------------------------------
> Does this instrstruction work with Pogo V3
> Classic/Pro?
>

> pogoplug-v3-squashfs-sysupgrade.tar
> pogoplug-v3-squashfs-ubinized.bin
> pogoplug-v3-u-boot-initramfs.bin
> pogoplug-v3-uImage
> pogoplug-v3-ubifs-sysupgrade.tar
> pogoplug-v3-ubifs-ubinized.bin
>

>
> Use the pogoplug-v3-u-boot-initramfs.bin to
> replace lede-kirkwood-pogo_e02-initramfs-uImage?

Yes. That's the general idea.

But the instruction in the 1st page is is not applicable to the Pogo V3 plug. You need new instruction.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

rynax,

https://forum.doozan.com/read.php?4,54044,57009#msg-57009

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I'm trying to follow instructions here for installing OpenWrt (LEDE) and adapt them to a GoFlex Home unit. I believe the first step is to use kwboot with uboot.2017.07-tld-1.goflexhome.bodhi.tar to boot the unit

ie:

kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.goflexhome.mtd0.kwb -p

Not sure what to do next...

Has anyone attempted to install 18.06.2?

My aim is to create a simple guide for installing OpenWrt on a GoFlex Home unit.

If I kwboot from uboot.2017.07-tld-1 and use the envs from uboot.2016.05-tld-1.environment amended for GoFlex Home,

ie.

setenv mtdparts 'mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)'.
setenv partition 'nand0,0'.
setenv set_bootargs_openwrt 'setenv bootargs console=ttyS0,115200 $mtdparts'
setenv bootcmd_openwrt 'run set_bootargs_openwrt; ubi part ubi; ubi read 0x800000 kernel; bootm 0x800000'
setenv bootcmd 'run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_openwrt'
setenv bootcmd_exec 'if run load_uimage; then; 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; fi'

I guess that should be OK... One of those lines is particularly long, so may well have a typo...

In principle the installation should consist of:-

kwbooting
amending the environment
booting initramfs from an attached USB stick
running sysupgrade

Does that sound right?

Hi guys,

the following might help others, so I thought I'd share. Here is my report:

---

So I tried this with my Dockstar, but managed to semi-brick it ...

Status is that I can still connect via netconsole and I can boot the LEDE image (also the newer 18.2 image), but the sysupgrade seems to have messed things up (obviously, I did replace the 'pogo_e02' part with 'dockstar' in the files to be downloaded). The box neither boots from NAND nor from the Debian stick.

The latter is a small wonder, since the uBoot environment variables do not correspond to bodhi's anymore. Also, I get:

cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "u-boot"
mtd1: 0ff00000 00020000 "ubi"

So the NAND layout is not as required in the uBoot thread.

Here is the good news: Nonetheless, I can get that environment back, since I did save my environment variables to a text file. Using a small python script, namely

path = "/home/chessplayer/HTPC/Dockstar/uBoot/"
fobj_in = open(path+"new_envs_dockstar.txt")
fobj_out = open(path+"new_envs_dockstar_set.txt","w")
for line in fobj_in:
    line = line.rstrip()
    splitat = line.find('=')
    envvar = line[:splitat]
    envval = line[splitat+1:]
    fobj_out.write("fw_setenv "+envvar+" '"+envval+"'\n")
fobj_in.close()
fobj_out.close()

I converted that to a file which sets those variables one by one.

Before I was able to make use of that, I had to do one more thing, namely edit /etc/fw_env.config, because:

fw_printenv
Warning: Bad CRC, using default environment
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=5
baudrate=115200

The reason is that according to /etc/fw_env.config of the LEDE system, it looks for the environment variables elsewhere:

 # MTD device name	Device offset	Env. size	Flash sector size	Number of sectors 
/dev/mtd1 0x0 0x20000 0x20000

while it should be

 # MTD device name	Device offset	Env. size	Flash sector size	Number of sectors 
/dev/mtd0 0xc0000 0x20000 0x20000

Again, unfortunately, LEDE does not come equipped with nano and opkg does not let me install it, so I must use vim to edit the file (not hard,
but a web search is needed in order to come to terms with vim ...). With that done, I can check that fw_printenv now displays the actual uBoot environment variables and subsequently, I can overwrite those by copying the data from the file new_envs_dockstar_set.txt into the ssh concole to LEDE.

Afterwards, at least the Debian stick boots again. The only issue remaining now is that the NAND layout is still not as it should be:

cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00400000 00020000 "uImage"
mtd2: 0fb00000 00020000 "data"

i.e., the rootfs-partition is missing.

Anyway, I can now try the procedure once more, hoping I do not screw it up again and being confident that if I do, I can still get the box working again, just no rescue system to speak of ...

Cheers,

chessplayer

---
Standart ist der Standardfehler



Edited 1 time(s). Last edit at 06/06/2019 12:40PM by chessplayer.

So, I got everything working and since I believe that the process can be improved and generalized, I opened a new thread for Kirkwood boxes in general. The procedure described therein was tested on Dockstar, GoFlex Net and PogoE02 with OpenWrt 18.06.2 (and LEDE 17.01.6) and worked well in all cases, even with older uBoots and kernel+rootfs.

Cheers,

chessplayer

---
Standart ist der Standardfehler

chessplayer,

> The latter is a small wonder, since the uBoot
> environment variables do not correspond to bodhi's
> anymore. Also, I get:
>

> cat /proc/mtd
> dev:    size   erasesize  name
> mtd0: 00100000 00020000 "u-boot"
> mtd1: 0ff00000 00020000 "ubi"
>

>
> So the NAND layout is not as required in the
> uBoot
> thread.

That's is not quite accurate! remember we only care about mtd0 while installing new u-boot.

Quote
https://forum.doozan.com/read.php?3,12381
Note: for boxes such as Pogo V4 and Zyxel NSA3xx, the mtd partition definition are kept the same as stock definition, therefore is different from the one above.

If you don't have /etc/fw_env.config file in your system then go ahead and create this file with the above content. MTD parts are not important for booting and it can be adjusted later. For users who like to keep the stock mtd definition, there is no need to adjust it to the above definition. As long as mtd0 is defined as 1MB (0x00100000) or greater then it will be OK:

mtd0: 00100000 00020000 "u-boot"

> Here is the good news: Nonetheless, I can get that
> environment back, since I did save my environment
> variables to a text file. Using a small python
> script, namely
>

> path = "/home/chessplayer/HTPC/Dockstar/uBoot/"
> fobj_in = open(path+"new_envs_dockstar.txt")
> fobj_out =
> open(path+"new_envs_dockstar_set.txt","w")
> for line in fobj_in:
>     line = line.rstrip()
>     splitat = line.find('=')
>     envvar = line[:splitat]
>     envval = line[splitat+1:]
>     fobj_out.write("fw_setenv "+envvar+"
> '"+envval+"'\n")
> fobj_in.close()
> fobj_out.close()
>

>
> I converted that to a file which sets those
> variables one by one.
>
> Before I was able to make use of that, I had to do
> one more thing, namely edit /etc/fw_env.config,
> because:
>

> fw_printenv
> Warning: Bad CRC, using default environment
> bootcmd=bootp; setenv bootargs root=/dev/nfs
> nfsroot=${serverip}:${rootpath}
> ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off;
> bootm
> bootdelay=5
> baudrate=115200
>

>
> The reason is that according to /etc/fw_env.config
> of the LEDE system, it looks for the environment
> variables elsewhere:
>

>  # MTD device name	Device offset	Env. size	Flash
> sector size	Number of sectors 
> /dev/mtd1 0x0 0x20000 0x20000
>

>
> while it should be
>

>  # MTD device name	Device offset	Env. size	Flash
> sector size	Number of sectors 
> /dev/mtd0 0xc0000 0x20000 0x20000
>

That is a requirement when you install Kirwood u-boot.

1. uBoot envs config should be defined as followed in your /etc/fw_env.config

Quote
https://forum.doozan.com/read.php?3,12381
cat /etc/fw_env.config
# MTD device name Device offset Env. size Flash sector size Number of sectors
/dev/mtd0 0xc0000 0x20000 0x20000

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> chessplayer,
>
> > The latter is a small wonder, since the uBoot environment variables do not correspond to bodhi's anymore. Also, I get:
> >

> > cat /proc/mtd
> > dev:    size   erasesize  name
> > mtd0: 00100000 00020000 "u-boot"
> > mtd1: 0ff00000 00020000 "ubi"
> >

> >
> > So the NAND layout is not as required in the uBoot thread.
>
> That's is not quite accurate! remember we only
> care about mtd0 while installing new u-boot.
>
... [snip] ...
> >
> > Before I was able to make use of that, I had to do one more thing, namely edit /etc/fw_env.config, because:
> >

> > fw_printenv
> > Warning: Bad CRC, using default environment
> > bootcmd=bootp; setenv bootargs root=/dev/nfs
> > nfsroot=${serverip}:${rootpath} 
> > ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off;
> > bootm
> > bootdelay=5
> > baudrate=115200
> >

> >
> > The reason is that according to /etc/fw_env.config of the LEDE system, it looks for the environment variables elsewhere:
> >

> >  # MTD device name	Device offset	Env. size	Flash sector size	Number of sectors 
> > /dev/mtd1 0x0 0x20000 0x20000
> >

> >
> > while it should be
> >

> >  # MTD device name	Device offset	Env. size	Flash sector size	Number of sectors 
> > /dev/mtd0 0xc0000 0x20000 0x20000
> >

>
> That is a requirement when you install Kirwood u-boot.


Yes, writing up the new instructions for installing OpenWrt, I came to terms with these issues. I did not quite understand the implications of the remark

Quote
bodhi
Note: for boxes such as Pogo V4 and Zyxel NSA3xx, the mtd partition definition are kept the same as stock definition, therefore is different from the one above.

from your uBoot instructions. It might make more sense there to say explicitly, that it is the mtd0 part which is a must and the rest depends on whatever is in NAND (e.g. OpenWrt, where the layout is as shown above).

Furthermore, I find it interesting that, depending on which box you want to install on, the fw_envs.config is either wrong (see above for Dockstar, also for Pogo E02) or not present at all (GoFlex Net) in the uImage provided by OpenWrt/LEDE. So, to me, this seems to be the crucial step in order to get OpenWrt to NAND and at the same time be able to still boot whatever system is on a USB drive, at least in connection with your environment, bodhi. I will make that clear in my new writeup.

---
Standart ist der Standardfehler