How do I recover from a partial setup of a Pogo-e02 ?

I followed the instructions for how to replace the uboot, but never got the USB stick correctly created.
Now when the Pogo-e02 reboots I get a bunch of errors from the netconsole and I'm no longer able to ssh into the box.
With the empty USB inserted I get the following:
U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:13:18 -0700)
Pogo E02
gcc (Debian 6.3.0-18) 6.3.0 20170516
GNU ld (GNU Binutils for Debian) 2.28
Hit any key to stop autoboot: 0
starting 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
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'

Partition Map for USB device 0 -- Partition Type: DOS

Part Start Sector Num Sectors UUID Type
1 63 2008062 3c4431e5-01 83 Boot
2 2008125 514080 3c4431e5-02 82
3 2522205 27503280 3c4431e5-03 83

## 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 ...
** File not found /boot/uEnv.txt **
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'
running scan_disk ...
Scan device usb
device usb 0:1
** File not found /boot/uImage **
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 ...
** File not found /boot/uImage **
loading uInitrd ...
** File not found /boot/uInitrd **
loading DTB /boot/dts/kirkwood-pogo_e02.dtb ...
** File not found /boot/dts/kirkwood-pogo_e02.dtb **
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-2.6.22.18
Created: 2009-08-10 19:57:40 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1977716 Bytes = 1.9 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK


Starting kernel ...

At this point nothing further happens and i cannot connect via ssh.
I then removed the USB stick hoping that a 'default' kernel would load, but no such luck.
Now the netconsole show the follwing:
U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:13:18 -0700)
Pogo E02
gcc (Debian 6.3.0-18) 6.3.0 20170516
GNU ld (GNU Binutils for Debian) 2.28
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 **
loading uInitrd ...
** Bad device usb 0 **
loading DTB /boot/dts/kirkwood-pogo_e02.dtb ...
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
PogoE02> help
help
? - alias for 'help'
base - print or set address offset
bdinfo - print Board Info structure
boot - boot default, i.e., run 'bootcmd'
bootd - boot default, i.e., run 'bootcmd'
bootefi - Boots an EFI payload from memory
bootelf - Boot from an ELF image in memory
bootm - boot application image from memory
bootp - boot image via network using BOOTP/TFTP protocol
bootvx - Boot vxWorks from an ELF image
bootz - boot Linux zImage image from memory
chpart - change active partition
cmp - memory compare
coninfo - print console devices and information
cp - memory copy
crc32 - checksum calculation
date - get/set/reset date & time
dhcp - boot image via network using DHCP/TFTP protocol
dns - lookup the IP of a hostname
echo - echo args to console
editenv - edit environment variable
env - environment handling commands
exit - exit script
ext2load- load binary file from a Ext2 filesystem
ext2ls - list files in a directory (default /)
ext4load- load binary file from a Ext4 filesystem
ext4ls - list files in a directory (default /)
ext4size- determine a file's size
false - do nothing, unsuccessfully
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls - list files in a directory (default /)
fatsize - determine a file's size
fdt - flattened device tree utility commands
fsinfo - print information about jffs filesystems
fsload - load binary file from a jffs filesystem image
fsls - list jffs files in a directory (default /)
fstype - Look up a filesystem type
go - start application at address 'addr'
gpio - query and control gpio pins
gpt - GUID Partition Table
help - print command description/usage
iminfo - print header information for application image
imxtract- extract a part of a multi-image
itest - return true/false on integer compare
load - load binary file from a filesystem
loadb - load binary file over serial line (kermit mode)
loads - load S-Record file over serial line
loadx - load binary file over serial line (xmodem mode)
loady - load binary file over serial line (ymodem mode)
loop - infinite loop on address range
ls - list files in a directory (default /)
md - memory display
mii - MII utility commands
mm - memory modify (auto-incrementing address)
mtdparts- define flash/nand partitions
mw - memory write (fill)
nand - NAND sub-system
nboot - boot from NAND device
nfs - boot image via network using NFS protocol
nm - memory modify (constant address)
ping - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
reset - Perform RESET of the CPU
run - run commands in an environment variable
save - save file to a filesystem
saveenv - save environment variables to persistent storage
setenv - set environment variables
setexpr - set environment variable as the result of eval expression
showvar - print local hushshell variables
size - determine a file's size
sleep - delay execution for some time
sntp - synchronize RTC via network
source - run script from memory
test - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protocol
true - do nothing, successfully
ubi - ubi commands
ubifsload- load file from an UBIFS filesystem
ubifsls - list files in a directory
ubifsmount- mount UBIFS volume
ubifsumount- unmount UBIFS volume
usb - USB sub-system
usbboot - boot from USB device
version - print monitor, compiler and linker version
PogoE02>
I still cannot connect with ssh.
How do I recover and proceed ?
I there a way to create the USB stick on one of my Raspberry PIs ?

Thanks,
Henning

Raspbian / Raspberry Pi OS is Linux. Yes. You can create bootable USB for your pogo e02 on Raspberry Pi.

Just follow Bodhi's instructions carefully.

Use root. Not sudo.

Better use small (<64gb) USB 2.0 SanDisk drive.

Use mbr, not gpt, better successful possibilities.

You are in good shape, you have new u-boot installed, so no worries. It should be very easy.

daviddyer Wrote:
-------------------------------------------------------
> Raspbian / Raspberry Pi OS is Linux. Yes. You can
> create bootable USB for your pogo e02 on Raspberry
> Pi.
>
> Just follow Bodhi's instructions carefully.
>
> Use root. Not sudo.
>
> Better use small (<64gb) USB 2.0 SanDisk drive.
>
> Use mbr, not gpt, better successful possibilities.
>
>
> You are in good shape, you have new u-boot
> installed, so no worries. It should be very easy.

+1

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

Thanks for the quick response.
I'm still a little lost, and not sure which set of instructions/shell script to use for the install ?
Since I'm doing this on my Raspberry PI, I'm guessing I don't want to use any script that includes replacing the UBoot ?
If you can point me to the post with the instructions I need to follow, I would be grateful.

Thanks,
Henning

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


Note 1: You already have new u-boot.

Note 2: You need the whole root file system, kernel is included. You can upgrade to a new kernel later

Henning ,

daviddyer Wrote:
-------------------------------------------------------
> https://forum.doozan.com/read.php?2,12096
>
>
> Note 1: You already have new u-boot.
>
> Note 2: You need the whole root file system,
> kernel is included. You can upgrade to a new
> kernel later

"the whole root file system" as David said above is: create the rootfs on USB drive using this tarball following the instruction in the release thread

Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (01 Nov 2023)

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

Sorry to be such a pain, but I cannot find mkimage for the Raspberry PI ?
Any suggestions ?

Thanks,
Henning

Never mind about mkimage....

When running dpkg I get the following error:
root@raspberrypi5:/mnt/usb/boot# dpkg -i linux-image-6.6.3-kirkwood-tld-1_1_armel.deb
dpkg: error processing archive linux-image-6.6.3-kirkwood-tld-1_1_armel.deb (--install):
package architecture (armel) does not match system (arm64)
Errors were encountered while processing:
linux-image-6.6.3-kirkwood-tld-1_1_armel.deb
root@raspberrypi5:/mnt/usb/boot#

:(

Henning

Henning,

You are using the wrong instruction in the release thread. And so you tried to install the kernel on the rPi itsefl.

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

Quote

Latest released kernel: linux-6.6.3-kirkwood-tld-1-bodhi.tar.bz2 (01 Dec 2023)
Latest released rootfs: Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (01 Nov 2023)

Note: If this is your first time installation, then you only need rootfs Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (this has kernel linux-6.5.7-kirkwood-tld-1 already installed). Please scroll down to 01 Nov 2023 section for download link and installation instruction.

The tarball Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2 is all you need to create the rootfs. So scroll down to Section 01 Nov 2023.

Quote

Updated 01 Nov 2023:

Basic Debian bookworm Kirkwood rootfs for most Kirwood plugs:

- tarball size: 250MB
- install size: 714MB
- The init system used in this rootfs is sysvinit . To boot with systemd, see Notes below.
- Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, dialog, bzip2, nfs server/client, iperf, ethtool, sysvinit-core, sysvinit, sysvinit-utils, u-boot-tools, libubootenv-tool, mtd-utils, and orphan-sysvinit-scripts.
- see LED controls examples in /etc/rc.local, and /etc/init.d/halt
- see some useful aliases in /root/.profile
- root password: root

After creating the rootfs, bring it back to the Pogo E02 and cold start. It wil boot into the kernel linux-6.5.7-kirkwood-tld-1 on the rootfs.

And then later, while the box is running, install the latest kernel (linux-6.6.3-kirkwood-tld-1).

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



Edited 1 time(s). Last edit at 12/17/2023 05:04PM by bodhi.

Somewhat detailed commands.

Suppose you ssh into Raspberry pi as user pi
first run

sudo su -

to become root.

Then insert the flash drive to the Rpi's usb port--ALL the content of the usb flash drive will be erased! Make sure you use the correct drive!

run "dmesg" to get the info. Suppose the new usb drive is /dev/sda

run fdisk /dev/sda

delete all the partitions
create only one linux partition
wirte and exit

now make file system

mkfs.ext4 -L rootfs /dev/sda1

Now mount the usb drive

mount /dev/sda1 /mnt

cd /mnt

download the tar.bz2 file Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2

tar xvf Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2

then cd /mnt/boot

run the mkimage command

if system can not find mkimage, install this package in raspberry pi u-boot-tools
then run those mkimage commands

sync; sync; sync; cd /; umount /mnt

remove the usb flash drive from raspberry pi

insert the usb to pogo e02, power it on

Thanks for the detailed steps, the pogo e02 now boots the kernel on the USB stick.

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:13:18 -0700)
Pogo E02
gcc (Debian 6.3.0-18) 6.3.0 20170516
GNU ld (GNU Binutils for Debian) 2.28
Hit any key to stop autoboot: 0
starting 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
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'

Partition Map for USB device 0 -- Partition Type: DOS

Part Start Sector Num Sectors UUID Type
1 2048 30029202 3c4431e5-01 83

## 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 ...
** File not found /boot/uEnv.txt **
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'
running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 569 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
6348178 bytes read in 892 ms (6.8 MiB/s)
loading uInitrd ...
5791271 bytes read in 1017 ms (5.4 MiB/s)
loading DTB /boot/dts/kirkwood-pogo_e02.dtb ...
10322 bytes read in 1138 ms (8.8 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-6.5.7-kirkwood-tld-1
Created: 2023-12-21 13:50:55 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 6348114 Bytes = 6.1 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
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 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
Booting using the fdt blob at 0x1c00000


Starting kernel ...

But I still cannot ssh into the Pogo e02, any help would be appreciated.

Thanks,
Henning

Never mind, it was a 'pebcac'
It took a little while for it to show up, but now I'm able to logon.
Thanks for all you help, greatly appreciated.

Thanks,
Henning

Bodhi is the guy who makes everything easy for us.