Welcome! Log In Create A New Profile

Advanced

Pogoplug Pogo-E02 can't flash Uboot

Posted by kiro 
kiro
Pogoplug Pogo-E02 can't flash Uboot
June 06, 2024 02:22AM
Hello,

I have an old Pogoplug Pogo-E02, which so far I am using only for making my external HDDs/USB Flash drives available through the local network. I discovered that this box can run different OS - Debian or OpenWRT and so can be used not only for network storage sharing but also for a DLNA server and a torrent downloader. I have read some threads, bough UBS to serial adapter and tried to flash the device's Uboot using this commands:
cd /tmp
wget http://jeff.doozan.com/debian/uboot/install_uboot_mtd0.sh
chmod +x install_uboot_mtd0.sh
./install_uboot_mtd0.sh

So far so good, but then I am getting an error message, that wget can't handle https so it cannot download .md5 and exit the installation. Then I tried with kwboot using:

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

When hit enter, the it ask me to restart/power on the device, but when I do so - nothing happens?!
If not using kwboot, I am able to see all the booting process from the UART console, I can interrupt the booting process and use some commands, but that's it.

I've search thru that forum, as there are many threats about Podo E02, but I'm totally confused, as almost all of the threads points to some previous threat and I actually can't find a step-by-step tutorial how to flash uboot, and Debian/OpenWRT afterwards from the stock FW.
Please help!
Re: Pogoplug Pogo-E02 can't flash Uboot
June 06, 2024 12:59PM
Kiro,

That script by Jeff is quite old. Here is how we install Debian and new u-boot (optional).

Wiki thread
https://forum.doozan.com/read.php?2,23630

Quote

Kirkwood plugs

Basic steps to install Debian and new u-boot on Kirkwood boxes
Boot Kirkwood rootfs with stock u-boot

Latest Linux Kirkwood kernel and rootfs
Latest Kirkwood u-boots

The Pogo E02 does not support UART booting, so kwboot will not work. For this reason, when and if you install new u-boot you must be careful. The recovery path from a bad flash is to connect JTAG (big hassle, need soldering a header to the board).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Kiro
Re: Pogoplug Pogo-E02 can't flash Uboot
June 07, 2024 02:35AM
bodhi,

Are those the steps I should take:

1. I should plug an empty 8+ GB USB flash drive into a Linux PC, and run:
fdisk /dev/sdb
mke2fs -j /dev/sdb1

2. Mount the new partition, copy to and extract Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2 file to the root of the new partition:
cd /media/sdb1 
tar xjf Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2

3. Create specific rootfs for the Pogo-E02:
cd /media/sdb1/boot
cp -a zImage-6.5.7-kirkwood-tld-1  zImage.fdt
cat dts/kirkwood-pogo_e02.dtb  >> zImage.fdt
mv uImage uImage.orig
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-6.5.7-kirkwood-tld-1 -d zImage.fdt  uImage
sync

4. Unplug the USB drive from the Linux PC, plug it into POGO-E02, power-on the device, interrupt u-boot and:
setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial'
setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage'
setenv load_uinitrd 'ext2load usb 0:1 0x2100000 /boot/uInitrd'
setenv usb_boot 'mw 0x800000 0 1; run load_uimage; run load_uinitrd; bootm 0x800000 0x2100000'
setenv usb_bootcmd 'run usb_set_bootargs; run usb_boot'
setenv bootcmd 'usb reset; run usb_bootcmd; usb stop; reset'

5. Restart the POGO-E02, and it will boot into Debian installer. Is that right?
Re: Pogoplug Pogo-E02 can't flash Uboot
June 07, 2024 02:02PM
Kiro,

> 1. I should plug an empty 8+ GB USB flash drive
> into a Linux PC, and run:

First, become root at this point:
su -

>
> fdisk /dev/sdb
> mke2fs -j /dev/sdb1
>
>
> 2. Mount the new partition, copy to and extract
> Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2
> file to the root of the new partition:
>
> cd /media/sdb1 
> tar xjf
> Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2
>
>
> 3. Create specific rootfs for the Pogo-E02:
>
> cd /media/sdb1/boot
> cp -a zImage-6.5.7-kirkwood-tld-1  zImage.fdt
> cat dts/kirkwood-pogo_e02.dtb  >> zImage.fdt
> mv uImage uImage.orig
> mkimage -A arm -O linux -T kernel -C none -a
> 0x00008000 -e 0x00008000 -n
> Linux-6.5.7-kirkwood-tld-1 -d zImage.fdt  uImage
> sync
>
>
> 4. Unplug the USB drive from the Linux PC, plug it
> into POGO-E02, power-on the device, interrupt
> u-boot and:
>
> setenv usb_set_bootargs 'setenv bootargs
> console=ttyS0,115200 root=LABEL=rootfs
> rootdelay=10 earlyprintk=serial'
> setenv load_uimage 'ext2load usb 0:1 0x800000
> /boot/uImage'
> setenv load_uinitrd 'ext2load usb 0:1 0x2100000
> /boot/uInitrd'
> setenv usb_boot 'mw 0x800000 0 1; run load_uimage;
> run load_uinitrd; bootm 0x800000 0x2100000'
> setenv usb_bootcmd 'run usb_set_bootargs; run
> usb_boot'
> setenv bootcmd 'usb reset; run usb_bootcmd; usb
> stop; reset'
>
>

All look good until this point.

> 5. Restart the POGO-E02, and it will boot into
> Debian installer. Is that right?

Don't restart. The setenvs above are transient. At this point
boot

And it will boot into the Debian rootfs. This rootfs is already a full basic system running kernel 6.5.7-kirkwood-tld-1 (it is not a Debian installer).

And you should repeat the boot procedure above a couple times to see everything is OK. And then boot again, repeat the setenvs, but before boot do a saveenv:

setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial'
setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage'
setenv load_uinitrd 'ext2load usb 0:1 0x2100000 /boot/uInitrd'
setenv usb_boot 'mw 0x800000 0 1; run load_uimage; run load_uinitrd; bootm 0x800000 0x2100000'
setenv usb_bootcmd 'run usb_set_bootargs; run usb_boot'
setenv bootcmd 'usb reset; run usb_bootcmd; usb stop; reset'
saveenv

and then boot
boot

Now it will boot automatically to the USB roofs when you power up or reboot.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Kiro
Re: Pogoplug Pogo-E02 can't flash Uboot
June 07, 2024 02:54PM
bodhi,

At step 4 I had to do:

setenv eth1addr 00:00:00:00:00
setenv ipaddr 192.168.1.33
setenv serverip 192.168.1.20
setenv bootargs 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial'
mw 0x800000 0 1
tftpboot 0x800000 uImage
tftpboot 0x2100000 uInitrd
printenv
bootm 0x800000 0x2100000

The box starts booting, but I get an error message - something like "LABEL=rootfs not found". When I rebooted the box load the stock FW. Now I am about to do all the steps again, but if i have no success this time, I will pest here the full log, so it will be easier for anybody to help.
Kiro
Re: Pogoplug Pogo-E02 can't flash Uboot
June 07, 2024 03:08PM
Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz 

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB 
DRAM Total size 256MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:128 MB

CPU : Marvell Feroceon (Rev 1)
CLOUD ENGINES BOARD: PPV2

Streaming disabled 
Write allocate disabled


USB 0: host mode

PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0 
CE>> 

CE>> setenv eth1addr 00:25:31:00:59:30setenv eth1addr 00:25:31:00:59:30

CE>> saveenvsaveenv

Saving Environment to NAND...
Erasing Nand...Writing to Nand... done
CE>> setenv ipaddr 192.168.1.55setenv ipaddr 192.168.1.55

CE>> setenv serverip 192.168.1.13setenv serverip 192.168.1.13

CE>> setenv bootargs 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial'setenv bootargs 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial'

CE>> mw 0x800000 0 1mw 0x800000 0 1

CE>> tftpboot 0x800000 uImagetftpboot 0x800000 uImage

Using egiga0 device
TFTP from server 192.168.1.13; our IP address is 192.168.1.55
Filename 'uImage'.
Load address: 0x800000
Loading: ##T ###############################################################
	 ################T ##################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #####################################T ############################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 ##############################################################T ####
	 #################################################################
	 #################################################################
	 #################################################################
	 ################################################
done
Bytes transferred = 6235609 (5f25d9 hex)
CE>> tftpboot 0x2100000 uInitrdtftpboot 0x2100000 uInitrd

Using egiga0 device
TFTP from server 192.168.1.13; our IP address is 192.168.1.55
Filename 'uInitrd'.
Load address: 0x2100000
Loading: #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 ######################T ###########################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 ###########################
done
Bytes transferred = 5791271 (585e27 hex)
CE>> printenvprintenv

baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
run_diag=yes
console=console=ttyS0,115200
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/mtdblock2 ro
ethmtu=1500
usb0Mode=host
nandEcc=1bit
ethact=egiga0
ethaddr=00:25:31:00:59:30
cesvcid=3NCGF8MP4JY32XUS36N742CHBN
ceboardver=PPV2
bootcmd=nand read.e 0x800000 0x100000 0x200000; setenv bootargs $(console) $(bootargs_root);bootm 0x800000
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
eth1addr=00:25:31:00:59:30
bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial
filesize=585e27
fileaddr=2100000
netmask=255.255.0.0
ipaddr=192.168.1.55
serverip=192.168.1.13

Environment size: 867/131068 bytes
CE>> bootm 0x800000 0x2100000bootm 0x800000 0x2100000

## Booting image at 00800000 ...
   Image Name:   Linux-6.5.7-kirkwood-tld-1
   Created:      2024-06-07  17:28:43 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    6235545 Bytes =  5.9 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 02100000 ...
   Image Name:   initramfs-6.5.7-kirkwood-tld-1
   Created:      2023-10-31  22:53:55 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    5791207 Bytes =  5.5 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

[    0.000000][    T0] Booting Linux on physical CPU 0x0
[    0.000000][    T0] Linux version 6.5.7-kirkwood-tld-1 (root@tldDebian) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #2 PREEMPT Wed Oct 18 21:14:11 PDT 2023
[    0.000000][    T0] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005317f
[    0.000000][    T0] CPU: VIVT data cache, VIVT instruction cache
[    0.000000][    T0] OF: fdt: Machine model: Seagate GoFlex Net
[    0.000000][    T0] printk: bootconsole [earlycon0] enabled
[    0.000000][    T0] Memory policy: Data cache writeback
[    0.000000][    T0] Zone ranges:
[    0.000000][    T0]   Normal   [mem 0x0000000000000000-0x000000000fffffff]
[    0.000000][    T0] Movable zone start for each node
[    0.000000][    T0] Early memory node ranges
[    0.000000][    T0]   node   0: [mem 0x0000000000000000-0x000000000fffffff]
[    0.000000][    T0] Initmem setup node 0 [mem 0x0000000000000000-0x000000000fffffff]
[    0.000000][    T0] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial
[    0.000000][    T0] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
[    0.000000][    T0] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes, linear)
[    0.000000][    T0] Built 1 zonelists, mobility grouping on.  Total pages: 64960
[    0.000000][    T0] mem auto-init: stack:off, heap alloc:on, heap free:off
[    0.000000][    T0] Memory: 232348K/262144K available (12288K kernel code, 1755K rwdata, 5416K rodata, 1024K init, 301K bss, 29796K reserved, 0K cma-reserved)
[    0.000000][    T0] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000][    T0] trace event string verifier disabled
[    0.000000][    T0] rcu: Preemptible hierarchical RCU implementation.
[    0.000000][    T0] 	Trampoline variant of Tasks RCU enabled.
[    0.000000][    T0] 	Tracing variant of Tasks RCU enabled.
[    0.000000][    T0] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.000000][    T0] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000][    T0] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[    0.000000][    T0] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[    0.000001][    T0] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[    0.008531][    T0] Switching to timer-based delay loop, resolution 5ns
[    0.015698][    T0] Console: colour dummy device 80x30
[    0.020932][    T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000)
[    0.032174][    T0] CPU: Testing write buffer coherency: ok
[    0.037862][    T0] pid_max: default: 32768 minimum: 301
[    0.052046][    T0] LSM: initializing lsm=capability,integrity
[    0.060311][    T0] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.068319][    T0] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.089104][    T1] RCU Tasks: Setting shift to 0 and lim to 1 rcu_task_cb_adjust=1.
[    0.097173][    T1] RCU Tasks Trace: Setting shift to 0 and lim to 1 rcu_task_cb_adjust=1.
[    0.105900][    T1] Setting up static identity map for 0x100000 - 0x100058
[    0.113154][    T1] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x2
[    0.119405][    T1] rcu: Hierarchical SRCU implementation.
[    0.124893][    T1] rcu: 	Max phase no-delay instances is 1000.
[    0.133768][    T1] devtmpfs: initialized
[    0.147891][    T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.158600][    T1] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
[    0.168964][    T1] prandom: seed boundary self test passed
[    0.179076][    T1] prandom: 100 self tests passed
[    0.183864][    T1] pinctrl core: initialized pinctrl subsystem
[    0.193535][    T1] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    0.201729][    T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.214700][    T1] audit: initializing netlink subsys (disabled)
[    0.222800][    T1] thermal_sys: Registered thermal governor 'step_wise'
[    0.223007][    T1] cpuidle: using governor ladder
[    0.234545][   T19] audit: type=2000 audit(0.210:1): state=initialized audit_enabled=0 res=1
[    0.243101][    T1] cpuidle: using governor menu
[    0.248339][    T1] Feroceon L2: Enabling L2
[    0.252673][    T1] Feroceon L2: Cache support initialised.
[    0.268677][    T1] No ATAGs?
[    0.638548][    T1] raid6: int32x8  gen()   108 MB/s
[    0.978548][    T1] raid6: int32x4  gen()   104 MB/s
[    1.318574][    T1] raid6: int32x2  gen()   132 MB/s
[    1.658548][    T1] raid6: int32x1  gen()    98 MB/s
[    1.663502][    T1] raid6: using algorithm int32x2 gen() 132 MB/s
[    2.018548][    T1] raid6: .... xor() 83 MB/s, rmw enabled
[    2.024024][    T1] raid6: using intx1 recovery algorithm
[    2.040265][    T1] SCSI subsystem initialized
[    2.049112][    T1] usbcore: registered new interface driver usbfs
[    2.055382][    T1] usbcore: registered new interface driver hub
[    2.078619][    T1] usbcore: registered new device driver usb
[    2.084748][    T1] pps_core: LinuxPPS API ver. 1 registered
[    2.098613][    T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    2.108448][    T1] PTP clock support registered
[    2.140987][    T1] vgaarb: loaded
[    2.145236][    T1] clocksource: Switched to clocksource orion_clocksource
[    2.164618][    T1] VFS: Disk quotas dquot_6.6.0
[    2.185692][    T1] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    2.233384][    T1] NET: Registered PF_INET protocol family
[    2.245607][    T1] IP idents hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    2.266472][    T1] tcp_listen_portaddr_hash hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    2.285490][    T1] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    2.293927][    T1] TCP established hash table entries: 2048 (order: 1, 8192 bytes, linear)
[    2.315295][    T1] TCP bind hash table entries: 2048 (order: 2, 16384 bytes, linear)
[    2.323149][    T1] TCP: Hash tables configured (established 2048 bind 2048)
[    2.345974][    T1] MPTCP token hash table entries: 512 (order: 0, 6144 bytes, linear)
[    2.354106][    T1] UDP hash table entries: 256 (order: 0, 4096 bytes, linear)
[    2.385283][    T1] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes, linear)
[    2.393813][    T1] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    2.416334][    T1] RPC: Registered named UNIX socket transport module.
[    2.422932][    T1] RPC: Registered udp transport module.
[    2.435263][    T1] RPC: Registered tcp transport module.
[    2.440644][    T1] RPC: Registered tcp-with-tls transport module.
[    2.455257][    T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    2.462380][    T1] PCI: CLS 0 bytes, default 32
[    2.488301][   T10] Trying to unpack rootfs image as initramfs...
[    3.489084][   T10] Freeing initrd memory: 5656K
[    4.369456][    T1] Initialise system trusted keyrings
[    4.374695][    T1] Key type blacklist registered
[    4.380997][    T1] workingset: timestamp_bits=14 max_order=16 bucket_order=2
[    4.388390][    T1] zbud: loaded
[    4.411017][    T1] NFS: Registering the id_resolver key type
[    4.416877][    T1] Key type id_resolver registered
[    4.421745][    T1] Key type id_legacy registered
[    4.426648][    T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    4.434034][    T1] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[    4.443756][    T1] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    4.452406][    T1] fuse: init (API version 7.38)
[    4.458619][    T1] orangefs_debugfs_init: called with debug mask: :none: :0:
[    4.466156][    T1] orangefs_init: module version upstream loaded
[    4.472638][    T1] SGI XFS with ACLs, security attributes, realtime, scrub, quota, no debug enabled
[    4.694512][    T1] xor: measuring software checksum speed
[    4.708893][    T1]    arm4regs        :  1112 MB/sec
[    4.728698][    T1]    8regs           :   667 MB/sec
[    4.744137][    T1]    32regs          :   947 MB/sec
[    4.749193][    T1] xor: using function: arm4regs (1112 MB/sec)
[    4.755100][    T1] async_tx: api initialized (async)
[    4.760161][    T1] Key type asymmetric registered
[    4.764935][    T1] Asymmetric key parser 'x509' registered
[    4.823074][    T1] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[    4.831848][    T1] io scheduler bfq registered
[    5.026720][    T1] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[    5.036507][    T1] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation.
[    5.047516][    T1] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation.
[    5.058754][    T1] mv_xor f1060800.xor: Marvell shared XOR driver
[    5.127960][    T1] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    5.140926][    T1] mv_xor f1060900.xor: Marvell shared XOR driver
[    5.207960][    T1] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    5.221359][    T1] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    5.231235][    T1] printk: console [ttyS0] disabled
[    5.236981][    T1] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 27, base_baud = 12500000) is a 16550A
[    5.246729][    T1] printk: console [ttyS0] enabled
[    5.246729][    T1] printk: console [ttyS0] enabled
[    5.256575][    T1] printk: bootconsole [earlycon0] disabled
[    5.256575][    T1] printk: bootconsole [earlycon0] disabled
[    5.299585][    T1] loop: module loaded
[    5.304588][    T1] sata_mv f1080000.sata: slots 32 ports 2
[    5.315439][    T1] scsi host0: sata_mv
[    5.320963][    T1] scsi host1: sata_mv
[    5.325354][    T1] ata1: SATA max UDMA/133 irq 28
[    5.330180][    T1] ata2: SATA max UDMA/133 irq 28
[    5.336418][    T1] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[    5.343520][    T1] nand: Hynix NAND 128MiB 3,3V 8-bit
[    5.348730][    T1] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    5.357098][    T1] Scanning device for bad blocks
[    5.471354][    T1] 4 fixed-partitions partitions found on MTD device orion_nand
[    5.478824][    T1] Creating 4 MTD partitions on "orion_nand":
[    5.484701][    T1] 0x000000000000-0x000000100000 : "u-boot"
[    5.491257][    T1] 0x000000100000-0x000000500000 : "uImage"
[    5.497818][    T1] 0x000000500000-0x000002500000 : "pogoplug"
[    5.504718][    T1] 0x000002500000-0x00000fd00000 : "root"
[    5.510279][    T1] mtd: partition "root" extends beyond the end of device "orion_nand" -- size truncated to 0x5b00000
[    5.523040][    T1] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[    5.531657][    T1] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
[    5.569781][    T1] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    5.668749][   T52] ata1: SATA link down (SStatus 0 SControl F300)
[    6.016893][   T54] ata2: SATA link down (SStatus 0 SControl F300)
[    6.316725][    T1] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:25:31:00:59:30
[    6.326951][    T1] orion-ehci f1050000.ehci: EHCI Host Controller
[    6.333212][    T1] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[    6.341908][    T1] orion-ehci f1050000.ehci: irq 31, io mem 0xf1050000
[    6.375271][    T1] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[    6.382365][    T1] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.05
[    6.391415][    T1] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    6.399404][    T1] usb usb1: Product: EHCI Host Controller
[    6.405015][    T1] usb usb1: Manufacturer: Linux 6.5.7-kirkwood-tld-1 ehci_hcd
[    6.412388][    T1] usb usb1: SerialNumber: f1050000.ehci
[    6.418978][    T1] hub 1-0:1.0: USB hub found
[    6.423504][    T1] hub 1-0:1.0: 1 port detected
[    6.429299][    T1] usbcore: registered new interface driver usb-storage
[    6.436792][    T1] mousedev: PS/2 mouse device common for all mice
[    6.715279][   T49] usb 1-1: new high-speed USB device number 2 using orion-ehci
[    6.917041][   T49] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice= 9.01
[    6.926015][   T49] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    6.933920][   T49] usb 1-1: Product: USB2.0 Hub
[    6.939749][   T49] hub 1-1:1.0: USB hub found
[    6.944542][   T49] hub 1-1:1.0: 4 ports detected
[    7.265269][   T49] usb 1-1.1: new high-speed USB device number 3 using orion-ehci
[    7.416418][   T49] usb 1-1.1: New USB device found, idVendor=0781, idProduct=5567, bcdDevice= 2.01
[    7.425566][   T49] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    7.433644][   T49] usb 1-1.1: Product: Cruzer Blade
[    7.438663][   T49] usb 1-1.1: Manufacturer: SanDisk
[    7.443663][   T49] usb 1-1.1: SerialNumber: 4C532000030511105363
[    7.450910][   T49] usb-storage 1-1.1:1.0: USB Mass Storage device detected
[    7.457993][    T1] rtc-mv f1010300.rtc: internal RTC not ticking
[    7.464408][    T1] i2c_dev: i2c /dev entries driver
[    7.470334][   T49] scsi host2: usb-storage 1-1.1:1.0
[    7.477730][    T1] device-mapper: uevent: version 1.0.3
[    7.483768][    T1] device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: dm-devel@redhat.com
[    7.493645][    T1] device-mapper: multipath round-robin: version 1.2.0 loaded
[    7.500998][    T1] device-mapper: multipath queue-length: version 0.2.0 loaded
[    7.508386][    T1] device-mapper: multipath service-time: version 0.3.0 loaded
[    7.515833][    T1] device-mapper: dm-log-userspace: version 1.3.0 loaded
[    7.526521][    T1] ledtrig-cpu: registered to indicate activity on CPUs
[    7.533438][    T1] hid: raw HID events driver (C) Jiri Kosina
[    7.539873][    T1] drop_monitor: Initializing network drop monitor service
[    7.548500][    T1] NET: Registered PF_INET6 protocol family
[    7.556399][    T1] Segment Routing with IPv6
[    7.560789][    T1] RPL Segment Routing with IPv6
[    7.565694][    T1] In-situ OAM (IOAM) with IPv6
[    7.570468][    T1] NET: Registered PF_PACKET protocol family
[    7.576710][    T1] Key type dns_resolver registered
[    7.602267][    T1] registered taskstats version 1
[    7.607510][    T1] Loading compiled-in X.509 certificates
[    7.636611][    T1] Key type .fscrypt registered
[    7.641278][    T1] Key type fscrypt-provisioning registered
[    7.653923][    T1] Key type big_key registered
[    7.705155][    T1] Key type encrypted registered
[    7.820372][  T106] "cryptomgr_test" (106) uses obsolete ecb(arc4) skcipher
[    8.499875][   T18] scsi 2:0:0:0: Direct-Access     SanDisk  Cruzer Blade     2.01 PQ: 0 ANSI: 6
[    8.526331][   T29] sd 2:0:0:0: [sda] 62530624 512-byte logical blocks: (32.0 GB/29.8 GiB)
[    8.545314][   T29] sd 2:0:0:0: [sda] Write Protect is off
[    8.555292][   T29] sd 2:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    8.603950][   T29]  sda: sda1
[    8.615826][   T29] sd 2:0:0:0: [sda] Attached SCSI disk
[   10.219386][    T1] clk: Disabling unused clocks
[   10.227495][    T1] Freeing unused kernel image (initmem) memory: 1024K
[   10.246104][    T1] Checked W+X mappings: passed, no W+X pages found
[   10.252519][    T1] Run /init as init process
Loading, please wait...
Starting systemd-udevd version 252.17-1~deb12u1
[   11.730790][  T150] usbcore: registered new interface driver uas
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for root file system device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  LABEL=rootfs does not exist.  Dropping to a shell!


BusyBox v1.35.0 (Debian 1:1.35.0-4+b3) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) 
kiro
Re: Pogoplug Pogo-E02 can't flash Uboot
June 07, 2024 05:09PM
success!

I managed to boot into Debian. Thanks a lot, bodhi!
So fat I have not restarted the box, but I am assuming this will result in boot the stock OS.
So probably now I should flash newer uboot to the device? Can I do that from Debian itself, or I should do it thru the serial console?

I get this, and I am not sure if I should continue:

root@debian:/tmp# /usr/sbin/nandwrite -s 786432 /dev/mtd0 uboot.2016.05-tld-1.environment.img
Writing data to block 6 at offset 0xc0000
Written 62 blocks containing only 0xff bytes
Those block may be incorrectly treated as empty!
Re: Pogoplug Pogo-E02 can't flash Uboot
June 07, 2024 07:16PM
Kiro,

Here is what I wrote but forgot to hit the "post message" button :)

There are 2 problems.

1. I missed your first problem in your post above.

Quote

1. I should plug an empty 8+ GB USB flash drive into a Linux PC, and run:
fdisk /dev/sdb
mke2fs -j /dev/sdb1

You also need to label the partition rootfs as said in the instruction

Quote

1. Format a new USB drive with a single Ext3 partition, and label it rootfs. This step should be done at Linux command line using fdisk, mkfs.ext3 (don't use GUI or gparted). Once you have booted the box, then you could try GPT partition and/or Ext4.

e2label /dev/sdb1 rootfs

2. The 2nd problem is with the DTB. As said in the instruction, you need to replace kirkwood-goflexnet.dtb with the DTB for this Pogo E02 box.

Quote

4. (Stock u-boot only) Create uImage with embedded DTB for booting with older u-boots (2012 or earlier). Skip this step if you have installed the latest U-Boot for Kirkwood (or are installing this u-boot at the same time, or running kwboot with latest u-boot image).

Please replace kirkwood-goflexnet.dtb below with the correct DTB name for your box (see the folder /media/sdb1/boot/dts for the exact spelling of your Kirkwood box name).

Generate the uImage with DTB embedded inside:
cd /media/sdb1/boot
cp -a zImage-6.5.7-kirkwood-tld-1 zImage.fdt
cat dts/kirkwood-goflexnet.dtb >> zImage.fdt
mv uImage uImage.orig
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-6.5.7-kirkwood-tld-1 -d zImage.fdt uImage
sync

So repeat Step 4 above with the Pogo E02 DTB

cat dts/kirkwood-pogo_e02.dtb >> zImage.fdt

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Pogoplug Pogo-E02 can't flash Uboot
June 07, 2024 07:21PM
kiro,

> success!
>
> I managed to boot into Debian. Thanks a lot,
> bodhi!

Congrats!

> So fat I have not restarted the box, but I am
> assuming this will result in boot the stock OS.
> So probably now I should flash newer uboot to the
> device? Can I do that from Debian itself, or I
> should do it thru the serial console?
>
> I get this, and I am not sure if I should
> continue:
>

>
> root@debian:/tmp# /usr/sbin/nandwrite -s 786432
> /dev/mtd0 uboot.2016.05-tld-1.environment.img
> Writing data to block 6 at offset 0xc0000
> Written 62 blocks containing only 0xff bytes
> Those block may be incorrectly treated as empty!
>

You should flash u-boot and the default envs image in Debian. The instruction was written for flashing in Linux. Remember to check for bad blocks. If you see anything not expected, don't reboot, and post the question here with the log of what you did.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
kiro
Re: Pogoplug Pogo-E02 can't flash Uboot
June 08, 2024 12:52AM
bodhi,

Actually I was made a typo - rooFTs. When corrected, everything came into place. Thanks!
Also I decided to proceed flashing uboot, and (somehow) manage to do it. I am not quite sure it is 100% correct, but it works. So thank you a lot.

The stock OS was automatically mounting USB drives and makes them accessible thru the network. Now I need to find a way to repeat that, or to install some webUI for easily managing storage...
Re: Pogoplug Pogo-E02 can't flash Uboot
June 08, 2024 02:19PM
kiro,

We have a Wiki thread here:

https://forum.doozan.com/read.php?2,23630

Quote

udev

Automount USB drives with udev rules using disk label

Quote

Samba

Samba smb.conf for a simple set up
HowTo setup Samba/CIFS shares
Samba server project on POGO-V4

Quote

NFS

NFS - HowTo set up NFS shares (and boot NFS rootfs), see also Debian 12 (bookworm) settings
Boot your Dockstar (and other plugs) using NFS rootfs, see also Debian 12 (bookworm) settings
Increase NFSD max_block_size
Reduce NFS threads

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
kiro
Re: Pogoplug Pogo-E02 can't flash Uboot
June 09, 2024 12:50AM
bodhi Wrote:
-------------------------------------------------------
> kiro,
>
> We have a Wiki thread here:
>
> https://forum.doozan.com/read.php?2,23630
>
>
Quote

udev

WOW, thanks a lot! You are great guys!

I spot that transmission's behavior is kind of strange. I have set a 2048 KB/s limit, and when I add new job it starts to download at approximately that speed 1.7-1.8 MB/s. But it regularly drops to 0 KB/s. So far I was unable to understood the pattern. What I'm observing is that it downloads with about 2 MB/s for a minute or so, after that it drops to 0 MB/s for about the twice that time, then again speeds up to 2 MB/s and so on. A 600 MB file is transferring about 30-40 minutes, when it suppose to take something like 5-6 min. So far I have never use the box for other than sharing storage, so I am not aware if that is due to a hardware limitations, or misconfiguration on my side?
Re: Pogoplug Pogo-E02 can't flash Uboot
June 09, 2024 02:15PM
kiro,

> I spot that transmission's behavior is kind of
> strange. I have set a 2048 KB/s limit, and when I
> add new job it starts to download at approximately
> that speed 1.7-1.8 MB/s. But it regularly drops to
> 0 KB/s. So far I was unable to understood the
> pattern. What I'm observing is that it downloads
> with about 2 MB/s for a minute or so, after that
> it drops to 0 MB/s for about the twice that time,
> then again speeds up to 2 MB/s and so on.

There is not enough info to say why it has this behaviour. The pure network performance for this box is very good (800Mbs-900Mbs). But it has a lot of other limitation: The biggest limitation is it has only USB ports, and 256MB RAM. The drop-off in speed might also be CPU maxing out. Or swapping to USB disk occurs.

Look in the Wiki thread for some hints in tuning

Quote

Perfornance Tuning & Benchmarks

Pogo ProV3 vs Pogo E02
Another Pogo Pro V3 benchmarks
Network performance - SAMBA - NFS (various protocols)
Pogo Pro V3 Network NFS benchmarks
Kirkwood vs OXNAS network performance (with flow control)
Kirkwood vs OXNAS network performance (flow control turned off )
OXNAS vs OXNAS network performance (flow control turned off)
Network Benchmarks for Thecus N2350 (Armada 385) and Zyxel NSA325 (Kirkwood 6820)
Network Benchmarks for Zyxel NSA310S (Kirkwood 6281) and GTI Mirabox (Armada 370)
Samba Tuning
Mount NTFS with big_writes
Increase NFSD max_block_size
Reduce NFSD threads

Quote

Memory & Swap Settings

Tuning for low RAM boxes.Also read several posts after for setups for logging to RAM.
logrotate examples
How to create and use a Swap file

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
kiro
Re: Pogoplug Pogo-E02 can't flash Uboot
June 16, 2024 07:55AM
bodhi,

I'm getting this message:
Jun 16 05:41:41 pogo-e02 transmission-daemon[3001]: [2024-06-16 05:41:41.238] UDP Failed to set receive buffer: requested 4194304, got 360448 (tr-udp.c:97)
Jun 16 05:41:41 pogo-e02 transmission-daemon[3001]: [2024-06-16 05:41:41.238] UDP Failed to set send buffer: requested 1048576, got 360448 (tr-udp.c:105)

So, correct me if I'm wrong, but this means the system cannot set the "correct" send/receive buffers, can it? I'm assuming these numbers are in bytes, so we are talking about requesting 4 MB receive and 1 MB send buffer, and gets only about 300 KB each? So can I set these buffers manually and will this resolve my issue?
I don't think 5 MB of RAM reserved for Transmission will anyhow slows the system down?
Re: Pogoplug Pogo-E02 can't flash Uboot
June 16, 2024 02:34PM
kiro,

> I don't think 5 MB of RAM reserved for
> Transmission will anyhow slows the system down?

Right! I don't think Transmision has any problem running in this box. I ran it on the GoFlex Net for a few years, and that Kirkwood box has only 128MB RAM and same CPU as this Pogo E02.

I have not run Transmission in the last few years so I don't know if there is new bug, but I've never see these error "UDP Failed to set receive buffer: requested..." before.

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

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: