Hi everyone.
This is my first post and first time installing the doozan uBoot and a bootable Debian image on a Pogo V4. A few years ago I installed the Arch uBoot & bootable Arch image on some V4s, but now I'm trying to flash a newer uBoot to the remaining stock devices.
I followed many posts here on how to do this, and spent a couple of days trying to document it and do it right. At some point in the middle of it all the V4 rebooted, and now I don't know what the problem is and what to focus on to solve this.
Here's the posts I based my installation attempts on:
"2017.07 U-Boot Kirkwood" (primary) - forum.doozan.com/read.php?3,12381
"UART Booting HowTo" - forum.doozan.com/read.php?3,7852,7852
"U-Boot flashing" - forum.doozan.com/read.php?3,27280
"Linux Kernel 6.1.7 Kirkwood package and Debian rootfs" - forum.doozan.com/read.php?2,12096
I have a serial connection to the V4, hardwired to a RPi's serial port, so I can watch the boot sequence. UART booting using kwboot worked really well, and I used the uboot.2017.07-tld-1.pogo_v4.mtd0.kwb upload to step through the process.
If I could figure out where I really am in the steps I would gladly post any commands and results - but I have no clue what I've missed.
When I power the V4 up with the USB in place, it seems like U-Boot 2017.07-tld-1 must be installed, but then it doesn't boot off the drive. Here's what I see when it boots, and it lights up the front green & red LEDs then locks up:
Any help making sense out of this is greatly appreciated!
This is my first post and first time installing the doozan uBoot and a bootable Debian image on a Pogo V4. A few years ago I installed the Arch uBoot & bootable Arch image on some V4s, but now I'm trying to flash a newer uBoot to the remaining stock devices.
I followed many posts here on how to do this, and spent a couple of days trying to document it and do it right. At some point in the middle of it all the V4 rebooted, and now I don't know what the problem is and what to focus on to solve this.
Here's the posts I based my installation attempts on:
"2017.07 U-Boot Kirkwood" (primary) - forum.doozan.com/read.php?3,12381
"UART Booting HowTo" - forum.doozan.com/read.php?3,7852,7852
"U-Boot flashing" - forum.doozan.com/read.php?3,27280
"Linux Kernel 6.1.7 Kirkwood package and Debian rootfs" - forum.doozan.com/read.php?2,12096
I have a serial connection to the V4, hardwired to a RPi's serial port, so I can watch the boot sequence. UART booting using kwboot worked really well, and I used the uboot.2017.07-tld-1.pogo_v4.mtd0.kwb upload to step through the process.
If I could figure out where I really am in the steps I would gladly post any commands and results - but I have no clue what I've missed.
When I power the V4 up with the USB in place, it seems like U-Boot 2017.07-tld-1 must be installed, but then it doesn't boot off the drive. Here's what I see when it boots, and it lights up the front green & red LEDs then locks up:
U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700)
Pogoplug V4
SoC: Kirkwood 88F6192_A1
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 128 MiB
MMC: MVEBU_MMC: 0
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...
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found
Reset IDE: ide_preinit failed
Card did not respond to voltage select!
mmc_init: -95, time 14
Partition Map for USB device 0 -- Partition Type: DOS
Part Start Sector Num Sectors UUID Type
1 2048 120162304 00000000-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 **
no IDE devices available
Card did not respond to voltage select!
mmc_init: -95, time 14
running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 722 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
5435888 bytes read in 1013 ms (5.1 MiB/s)
loading uInitrd ...
9671091 bytes read in 966 ms (9.5 MiB/s)
loading DTB kirkwood-pogo_v4.dtb ...
** File not found kirkwood-pogo_v4.dtb **
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-5.13.6-kirkwood-tld-1
Created: 2021-09-24 0:22:58 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5435824 Bytes = 5.2 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-5.13.6-kirkwood-tld-1
Created: 2021-09-24 1:06:32 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 9671027 Bytes = 9.2 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
Loading Ramdisk to 071d0000, end 07b09173 ... OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Error: invalid dtb and unrecognized/unsupported machine ID
r1=0x00000f78, r2=0x00000100
r2[]=05 00 00 00 01 00 41 54 00 00 00 00 00 00 00 00
Available machine support:
ID (hex) NAME
ffffffff Generic DT based system
ffffffff Marvell Kirkwood (Flattened Device Tree)
Please check your kernel config and/or bootloader.
Any help making sense out of this is greatly appreciated!