Pogoplug E02, default SSH PWD unknown

Hi,

I've been looking at a lot of threads in an attempt to get Linux working on my now redundant Pogoplug E02.

My ultimate aim was to get own cloud running to share photos and avoid Google photos for all my scanned 'analog' photos. I read a lot and it looked achievable!

I tried to get an SSH connection from my Ubuntu box. The connection was refused. Of course I tried using sudo SSH...

I tried the curl method to see if I can get an SSH connection. I did, but the password was rejected.

So, I wonder is there a way to reset the SSH password. I have followed another sites guidance to reset to factory default, but this was generic and I have little confidence that it worked.

I've also tried connecting my CP2102 evb to the serial console on the E02. Some success. I get a console output and after boot there is no console prompt! I think (99%) that the serial connection is working since I can interrupt the boot process at "press any key"... When I type on cutecom it tells me commands like ls are not loaded. The only doubt I have is that since I'm using individual 0.1" pitch wires I can't fit the Find wire in that connector. There is a VERY small impedance between the desired Gnd pin and the pin 1 of the connector to the left of the serial connector. This assumes you are viewing the PCB with the serial connector at the top of the board. Like I say I'm pretty confident that it works. I just don't want to waste anyone's time.

Because this seeming last resort didn't work I try following instructions to create an Ubuntu boot USB stick. I followed the instructions to the letter.
I put the stick into the E02 and held my breath. It booted up the regular firmware. I sighed, a long sigh! I imagine there is more of that ahead.

I'd appreciate any help to get me to a console prompt over the serial connection or any other route towards my end goal...

Familiar with Linux and a veteran Raspi owner. There are a few here. A complete novice with getting anything desirable to happen on my E02!

Wireless_fae,

> I tried to get an SSH connection from my Ubuntu
> box. The connection was refused. Of course I tried
> using sudo SSH...
>
> I tried the curl method to see if I can get an SSH
> connection. I did, but the password was rejected.

Was the password ceadmin? or stxadmin?

> serial console on the E02. Some success. I get a
> console output and after boot there is no console
> prompt! I think (99%) that the serial connection
> is working since I can interrupt the boot process
> at "press any key"...

Even without the prompt, can you run

ver
printenv
boot

and see any output and the stock FW booting?

Please post the entire serial console log here.

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

Hi bohdi,

thanks for your response.

I did stop the boot & can run ver, printenv & boot. but not after a full boot... like the boot sequence below.

First things first. here is the full serial console log. there are no USB sticks plugged in.

BTW - I said in my inital post that I had made an Ubuntu boot disk. It was actually Debian 5.2.9.

U-Boot 1.1.4 (Sep 28 2009 - 11:55:23) Cloud Engines v2.0 (3.4.16)

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 00690D60

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:  3  2  1  0 

NAND read: device 0 offset 0x100000, size 0x200000


Reading data from 0x100000 --   0% complete.
Reading data from 0x105000 --   1% complete.
Reading data from 0x10a000 --   2% complete.
Reading data from 0x10f000 --   3% complete.
Reading data from 0x114000 --   4% complete.
Reading data from 0x119800 --   5% complete.
Reading data from 0x11e800 --   6% complete.
Reading data from 0x123800 --   7% complete.
Reading data from 0x128800 --   8% complete.
Reading data from 0x12e000 --   9% complete.
Reading data from 0x133000 --  10% complete.
Reading data from 0x138000 --  11% complete.
Reading data from 0x13d000 --  12% complete.
Reading data from 0x142800 --  13% complete.
Reading data from 0x147800 --  14% complete.
Reading data from 0x14c800 --  15% complete.
Reading data from 0x151800 --  16% complete.
Reading data from 0x157000 --  17% complete.
Reading data from 0x15c000 --  18% complete.
Reading data from 0x161000 --  19% complete.
Reading data from 0x166000 --  20% complete.
Reading data from 0x16b800 --  21% complete.
Reading data from 0x170800 --  22% complete.
Reading data from 0x175800 --  23% complete.
Reading data from 0x17a800 --  24% complete.
Reading data from 0x17f800 --  25% complete.
Reading data from 0x185000 --  26% complete.
Reading data from 0x18a000 --  27% complete.
Reading data from 0x18f000 --  28% complete.
Reading data from 0x194000 --  29% complete.
Reading data from 0x199800 --  30% complete.
Reading data from 0x19e800 --  31% complete.
Reading data from 0x1a3800 --  32% complete.
Reading data from 0x1a8800 --  33% complete.
Reading data from 0x1ae000 --  34% complete.
Reading data from 0x1b3000 --  35% complete.
Reading data from 0x1b8000 --  36% complete.
Reading data from 0x1bd000 --  37% complete.
Reading data from 0x1c2800 --  38% complete.
Reading data from 0x1c7800 --  39% complete.
Reading data from 0x1cc800 --  40% complete.
Reading data from 0x1d1800 --  41% complete.
Reading data from 0x1d7000 --  42% complete.
Reading data from 0x1dc000 --  43% complete.
Reading data from 0x1e1000 --  44% complete.
Reading data from 0x1e6000 --  45% complete.
Reading data from 0x1eb800 --  46% complete.
Reading data from 0x1f0800 --  47% complete.
Reading data from 0x1f5800 --  48% complete.
Reading data from 0x1fa800 --  49% complete.
Reading data from 0x1ff800 --  50% complete.
Reading data from 0x205000 --  51% complete.
Reading data from 0x20a000 --  52% complete.
Reading data from 0x20f000 --  53% complete.
Reading data from 0x214000 --  54% complete.
Reading data from 0x219800 --  55% complete.
Reading data from 0x21e800 --  56% complete.
Reading data from 0x223800 --  57% complete.
Reading data from 0x228800 --  58% complete.
Reading data from 0x22e000 --  59% complete.
Reading data from 0x233000 --  60% complete.
Reading data from 0x238000 --  61% complete.
Reading data from 0x23d000 --  62% complete.
Reading data from 0x242800 --  63% complete.
Reading data from 0x247800 --  64% complete.
Reading data from 0x24c800 --  65% complete.
Reading data from 0x251800 --  66% complete.
Reading data from 0x257000 --  67% complete.
Reading data from 0x25c000 --  68% complete.
Reading data from 0x261000 --  69% complete.
Reading data from 0x266000 --  70% complete.
Reading data from 0x26b800 --  71% complete.
Reading data from 0x270800 --  72% complete.
Reading data from 0x275800 --  73% complete.
Reading data from 0x27a800 --  74% complete.
Reading data from 0x27f800 --  75% complete.
Reading data from 0x285000 --  76% complete.
Reading data from 0x28a000 --  77% complete.
Reading data from 0x28f000 --  78% complete.
Reading data from 0x294000 --  79% complete.
Reading data from 0x299800 --  80% complete.
Reading data from 0x29e800 --  81% complete.
Reading data from 0x2a3800 --  82% complete.
Reading data from 0x2a8800 --  83% complete.
Reading data from 0x2ae000 --  84% complete.
Reading data from 0x2b3000 --  85% complete.
Reading data from 0x2b8000 --  86% complete.
Reading data from 0x2bd000 --  87% complete.
Reading data from 0x2c2800 --  88% complete.
Reading data from 0x2c7800 --  89% complete.
Reading data from 0x2cc800 --  90% complete.
Reading data from 0x2d1800 --  91% complete.
Reading data from 0x2d7000 --  92% complete.
Reading data from 0x2dc000 --  93% complete.
Reading data from 0x2e1000 --  94% complete.
Reading data from 0x2e6000 --  95% complete.
Reading data from 0x2eb800 --  96% complete.
Reading data from 0x2f0800 --  97% complete.
Reading data from 0x2f5800 --  98% complete.
Reading data from 0x2fa800 --  99% complete.
Reading data from 0x2ff800 -- 100% complete.
 2097152 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2010-10-19  23:05:02 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1979140 Bytes =  1.9 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux............................................................................................................................ done, booting the kernel.

[    0.000000] Linux version 2.6.22.18 (bdietrich@buildman) (gcc version 4.2.1) #81 Tue Oct 19 16:05:00 PDT 2010
[    0.000000] CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053177
[    0.000000] Machine: Feroceon-KW
[    0.000000] Using UBoot passing parameters structure
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] CPU0: D VIVT write-back cache
[    0.000000] CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
[    0.000000] CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
[    0.000000] Built 1 zonelists.  Total pages: 65024
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/mtdblock2 ro
[    0.000000] PID hash table entries: 1024 (order: 10, 4096 bytes)
[    0.000000] Console: colour dummy device 80x30
[    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.010000] Memory: 256MB 0MB 0MB 0MB = 256MB total
[    0.010000] Memory: 255872KB available (3592K code, 253K data, 124K init)
[    0.250000] Mount-cache hash table entries: 512
[    0.250000] CPU: Testing write buffer coherency: ok
[    0.250000] NET: Registered protocol family 16
[    0.250000] 
[    0.250000] CPU Interface
[    0.250000] -------------
[    0.250000] SDRAM_CS0 ....base 00000000, size 256MB 
[    0.250000] SDRAM_CS1 ....disable
[    0.250000] SDRAM_CS2 ....disable
[    0.250000] SDRAM_CS3 ....disable
[    0.250000] PEX0_MEM ....base e8000000, size 128MB 
[    0.250000] PEX0_IO ....base f2000000, size   1MB 
[    0.250000] INTER_REGS ....base f1000000, size   1MB 
[    0.250000] NFLASH_CS ....base fa000000, size   2MB 
[    0.250000] SPI_CS ....base f4000000, size  16MB 
[    0.250000] BOOT_ROM_CS ....no such
[    0.250000] DEV_BOOTCS ....no such
[    0.250000] CRYPT_ENG ....base f0000000, size   2MB 
[    0.250000] 
[    0.250000]   Marvell Development Board (LSP Version KW_LSP_4.2.7_patch21_with_rx_desc_tuned)-- SHEEVA PLUG  Soc: 88F6281 A0 LE
[    0.250000] 
[    0.250000]  Detected Tclk 200000000 and SysClk 400000000 
[    0.250000] MV Buttons Device Load
[    0.250000] Marvell USB EHCI Host controller #0: c0652600
[    0.750000] PEX0 interface detected no Link.
[    0.750000] PCI: bus0: Fast back to back transfers enabled
[    0.750000] SCSI subsystem initialized
[    0.750000] usbcore: registered new interface driver usbfs
[    0.750000] usbcore: registered new interface driver hub
[    0.750000] usbcore: registered new device driver usb
[    0.750000] NET: Registered protocol family 2
[    0.760000] Time: kw_clocksource clocksource has been installed.
[    0.850000] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.850000] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[    0.850000] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[    0.850000] TCP: Hash tables configured (established 8192 bind 8192)
[    0.850000] TCP reno registered
[    0.880000] RTC has been updated!!!
[    0.880000] RTC registered
[    0.880000] Use the XOR engines (acceleration) for enhancing the following functions:
[    0.880000]   o RAID 5 Xor calculation
[    0.880000]   o kernel memcpy
[    0.880000]   o kenrel memzero
[    0.880000] Number of XOR engines to use: 4
[    0.880000] cesadev_init(c00117b0)
[    0.880000] mvCesaInit: sessions=640, queue=64, pSram=f0000000
[    0.880000] MV Buttons Driver Load
[    0.880000] squashfs: version 3.3 (2007/10/31) Phillip Lougher
[    0.880000] squashfs: LZMA suppport for slax.org by jro
[    0.880000] JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.880000] io scheduler noop registered
[    0.880000] io scheduler anticipatory registered (default)
[    0.900000] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
[    0.900000] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[    0.910000] RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
[    0.920000] Loading Marvell Ethernet Driver:
[    0.920000]   o Cached descriptors in DRAM
[    0.920000]   o DRAM SW cache-coherency
[    0.930000]   o Single RX Queue support - ETH_DEF_RXQ=0
[    0.930000]   o Single TX Queue support - ETH_DEF_TXQ=0
[    0.940000]   o TCP segmentation offload enabled
[    0.940000]   o Receive checksum offload enabled
[    0.950000]   o Transmit checksum offload enabled
[    0.950000]   o Network Fast Processing (Routing) supported
[    0.960000]   o Driver ERROR statistics enabled
[    0.960000]   o Driver INFO statistics enabled
[    0.970000]   o Proc tool API enabled
[    0.970000]   o Rx descripors: q0=128
[    0.970000]   o Tx descripors: q0=532
[    0.980000]   o Loading network interface(s):
[    0.990000]     o eth0, ifindex = 1, GbE port = 0
[    0.990000]     o eth1, ifindex = 2, GbE port = 1
[    1.000000] 
[    1.000000] mvFpRuleDb (cfdf6000): 2048 entries, 8192 bytes
[    1.000000] Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
[    1.010000] Copyright (c) 1999-2006 Intel Corporation.
[    1.020000] e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
[    1.020000] e100: Copyright(c) 1999-2006 Intel Corporation
[    1.030000] 
[    1.030000] Warning Sata is Powered Off
[    1.030000] NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
[    1.040000] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)
[    1.050000] Scanning device for bad blocks
[    1.100000] Using static partition definition
[    1.110000] Creating 4 MTD partitions on "nand_mtd":
[    1.110000] 0x00000000-0x00100000 : "u-boot"
[    1.120000] 0x00100000-0x00500000 : "uImage"
[    1.120000] 0x00500000-0x02500000 : "root"
[    1.130000] 0x02500000-0x08000000 : "data"
[    1.130000] ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
[    1.140000] ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
[    1.180000] ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
[    1.200000] ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[    1.200000] usb usb1: configuration #1 chosen from 1 choice
[    1.210000] hub 1-0:1.0: USB hub found
[    1.210000] hub 1-0:1.0: 1 port detected
[    1.330000] USB Universal Host Controller Interface driver v3.0
[    1.610000] usb 1-1: new high speed USB device using ehci_marvell and address 2
[    1.760000] usb 1-1: configuration #1 chosen from 1 choice
[    1.760000] hub 1-1:1.0: USB hub found
[    1.770000] hub 1-1:1.0: 4 ports detected
[    1.880000] usbcore: registered new interface driver usblp
[    1.880000] drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
[    1.890000] Initializing USB Mass Storage driver...
[    1.890000] usbcore: registered new interface driver usb-storage
[    1.900000] USB Mass Storage support registered.
[    1.910000] mice: PS/2 mouse device common for all mice
[    1.910000] i2c /dev entries driver
[    1.910000] Linux telephony interface: v1.00
[    1.920000] md: linear personality registered for level -1
[    1.920000] md: raid0 personality registered for level 0
[    1.930000] md: raid1 personality registered for level 1
[    2.100000] raid6: int32x1     97 MB/s
[    2.270000] raid6: int32x2    114 MB/s
[    2.440000] raid6: int32x4    122 MB/s
[    2.610000] raid6: int32x8    110 MB/s
[    2.610000] raid6: using algorithm int32x4 (122 MB/s)
[    2.610000] md: raid6 personality registered for level 6
[    2.620000] md: raid5 personality registered for level 5
[    2.620000] md: raid4 personality registered for level 4
[    2.630000] raid5: measuring checksumming speed
[    2.680000]    arm4regs  :  1084.000 MB/sec
[    2.730000]    8regs     :   754.800 MB/sec
[    2.780000]    32regs    :   899.600 MB/sec
[    2.780000] raid5: using function: arm4regs (1084.000 MB/sec)
[    2.790000] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
[    2.790000] dm_crypt using the OCF package.
[    2.800000] sdhci: Secure Digital Host Controller Interface driver
[    2.800000] sdhci: Copyright(c) Pierre Ossman
[    2.810000] usbcore: registered new interface driver usbhid
[    2.810000] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
[    2.820000] TCP cubic registered
[    2.820000] NET: Registered protocol family 1
[    2.830000] NET: Registered protocol family 17
[    2.830000] md: Autodetecting RAID arrays.
[    2.840000] md: autorun ...
[    2.840000] md: ... autorun DONE.
[    3.180000] mtd->read(0x1f6ec bytes from 0x120914) returned ECC error
[    5.260000] Empty flash at 0x009ac208 ends at 0x009ac800
[   10.010000] VFS: Mounted root (jffs2 filesystem) readonly.
[   10.020000] Freeing init memory: 124K
[   10.950000] mtd->read(0x74 bytes from 0x13bf8c) returned ECC error
[   10.960000] mtd->read(0x4cc bytes from 0x138334) returned ECC error
[   11.180000] mtd->read(0x869 bytes from 0x13e000) returned ECC error
[   11.180000] JFFS2 notice: (1) check_node_data: wrong data CRC in data node at 0x0013e000: read 0x44f122a7, calculated 0x3525916.
[   11.200000] mtd->read(0x789 bytes from 0x13b800) returned ECC error
[   11.200000] JFFS2 notice: (1) check_node_data: wrong data CRC in data node at 0x0013b800: read 0x3c613c58, calculated 0x94b098de.
[   11.610000] mtd->read(0x656 bytes from 0x137cdc) returned ECC error
[   11.620000] Data CRC e06af965 != calculated CRC 7d441ec2 for node at 00137c98
[   11.630000] mtd->read(0x44 bytes from 0x13bf8c) returned ECC error

init started: BusyBox v1.7.0 (2[   11.640000] mtd->read(0x656 bytes from 0x137cdc) returned ECC error
008-02-26 19:25:[   11.650000] Data CRC e06af965 != calculated CRC 1bec6c04 for node at 00137c98
17 IST)

======
moderator edit: please use code tags posting logs.



Edited 1 time(s). Last edit at 08/31/2019 04:06PM by bodhi.

Hi bohdi

Answering your other question.

When using curl I used ceadmin and the default pwd. That came back satisfactorily.

Weird that using the same login and password that SSH failed.

Hi bohdi,

so you don't have to ask for it, here is the output from ver & printenv.
you'll have seen from the boot log that there is no ethernet cable currently attached.

CE>> ver

U-Boot 1.1.4 (Sep 28 2009 - 11:55:23) Cloud Engines v2.0 (3.4.16)
CE>> printenv

baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.0.0
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
bootargs=console=ttyS0,115200 root=/dev/mtdblock2 ro
serverip=169.254.254.252
ipaddr=169.254.254.253
ethaddr=00:25:31:00:57:B3
cesvcid=ZLSQQ2SFHVUKCHMRGVBA4LA2D2
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

Environment size: 786/131068 bytes
CE>>

Edited 1 time(s). Last edit at 08/31/2019 04:07PM by bodhi.

Wireless_fae,

> When using curl I used ceadmin and the default
> pwd. That came back satisfactorily.
>

Nice.

> Weird that using the same login and password that
> SSH failed.

That was expected. This box has web interface where you enable SSH. But since Cloud Engine abandoned Pogo this cloud service, that is no longer possible.

OK so you got to the point that you can log in stock OS. And your log with envs showed eveyhting is normal as stock FW is concerned.

What you can do to boot Debian is doing both installation at the same time while inside stock OS.

1. Create the rootfs Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 on USB.
https://forum.doozan.com/read.php?2,12096

2. Install new u-boot using uboot.2017.07-tld-1.pogo_e02.bodhi.tar
https://forum.doozan.com/read.php?3,12381

Read the first post of these 2 threads to see if you want to do this.

Note that the Pogo E02 does not have an easy recovery mechanism using UART booting (through serial console) like other Kirkwood boxes. So you need to be extra careful with installation.

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

Hi bohdi,

Thanks for your guidance.

2 questions...

1) I'd already created the debian 5.2.9 USB exactly per these instructions & it didn't boot. I just plugged it in & hit the reset button. Did I miss something? If not, then I guess I made some error & need to do it again.
### I think I answered my own question. This time, as I'm going to do the Debian-5.2.9 installation & upgrade uboot at the same time I need to skip step 4 in the Debian image creation. ###
2) are you not worried by the mtd->read ECC errors on my boot log?

Thanks - wireless_fae



Edited 1 time(s). Last edit at 09/01/2019 02:50AM by Wireless_fae.

Wireless_fae,

> 2) are you not worried by the mtd->read ECC errors
> on my boot log?
>

No worries. That CRC error is not relevant to u-boot installation. This is more important:

[    1.030000] NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
[    1.040000] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)
[    1.050000] Scanning device for bad blocks
[    1.100000] Using static partition definition
[    1.110000] Creating 4 MTD partitions on "nand_mtd":
[    1.110000] 0x00000000-0x00100000 : "u-boot"
[    1.120000] 0x00100000-0x00500000 : "uImage"
[    1.120000] 0x00500000-0x02500000 : "root"
[    1.130000] 0x02500000-0x08000000 : "data"

You have no bad blocks in NAND.

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

bohdi,

it doesn't say so, but I assume that the boot flag must be set on the USB drive on which the image is placed. Correct?

-wireless_fae

Wireless_fae Wrote:
-------------------------------------------------------
> bohdi,
>
> it doesn't say so, but I assume that the boot flag
> must be set on the USB drive on which the image is
> placed. Correct?
>
> -wireless_fae

It used to be necessary long time ago. But it is not relevant anymore.

However, it's a good practice to set the active boot flag for the rootfs partition on USB drive.

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

hi bohdi,

thanks for the latest responses. very reassuring. As everyone seems to do with your help, I'm learning too.

given that I've already tried to boot Debian-5.2.9 & it didn't boot, should I not try again & get that working, since the uboot upgrade is risky? Is there anything to suggest that a correctly prepared Debian USB drive would not boot?

-wireless_fae

hi bohdi -

can I download the uboot image & put it into the /boot folder with the Debian-5.2.9 & *will it boot* ?

THEN as a separately install the uboot image (2017.07-kirkwood-tld-1) into NAND?

if so that feels less risky.
-wireless_fae

bohdi -

Again I might have answered my own question... if I go for option C in the 'installation' of the uboot. Looks like I can do a boot without flashing the NAND. Correct?

BTW - with option A, the instructions (nanddump, fw_printenv & dmesg) to install uboot.2017.07-tld-1 these are executed on the pogo plug, after interrupting the stock boot? The stuff before (editing & checking files) is done on a linux box. Correct?

I think my biggest barrier is comprehending which environment that the commands are relevant to. That & not understanding enough about these embedded linux devices!

-Wireless_fae



Edited 1 time(s). Last edit at 09/01/2019 08:05AM by Wireless_fae.

Wireless_fae,

Quote

given that I've already tried to boot Debian-5.2.9 & it didn't boot, should I not try again & get that working, since the uboot upgrade is risky? Is there anything to suggest that a correctly prepared Debian USB drive would not boot?

The reason the new rootfs did not boot, because stock u-boot is not set up to boot with USB rootfs.

Quote

can I download the uboot image & put it into the /boot folder with the Debian-5.2.9 & *will it boot* ?

Unlike the rPi which has a different SoC and can load u-boot from a storage drive. The Pogo, like other Kirkwood boxes, must have u-boot image stored in flash (NAND or SPI).

Quote

BTW - with option A, the instructions (nanddump, fw_printenv & dmesg) to install uboot.2017.07-tld-1 these are executed on the pogo plug, after interrupting the stock boot? The stuff before (editing & checking files) is done on a linux box. Correct?

To install new u-boot, It is required to follow all the steps in Section A. Section C is optional, meaning it is something you could do, but not neccessary.

====

Going back to my post above.

For a box that has stock FW, like yours, both Debian rootfs and new u-boot must be installed at the same time. The USB rootfs can be prepared outsite the box using a different Linux box (e.g. rPi). The new u-boot must be installed from inside stock OS. And then you plug in the newly created Debian USB rootfs. And reboot.

You are right in being cautious. If something abnormal happens such as power outage, or you have a typo in the installation commands, the box will be bricked. UART booting (loading u-boot through serial console) is not possible for this box. So in that case the only way to unbrick is using JTAG (it is possible but too much works).

There is a way to boot the new rootfs using stock 2009 u-boot. That's how we booted Debian on this Pogo E02 up until 2011-2012. I might have saved the instruction somewhere, but not sure.

But I don't suggest people using stock u-boot because it is too limited. And I would not want to spend time reinventing the wheel if I have to write instruction for stock u-boot :)

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