uBoot & Kernel upgrade problem on PogoPlug V4

Original posting here & here

Long story short. uboot was stuck at "Starting kernel ..." after I updated uBoot & Kernel (from 3.14.0 to 4.17.2) Tried to fall back by enter uBoot and load the backed up 3.14.0 uImage & uInitrd gives the same result.

MMC rescan: current device # 0 initialized OK
device mmc 0:1
1 bytes read in 13 ms (0 Bytes/s)
Found bootable drive on mmc 0
loading uImage ...
4125458 bytes read in 131 ms (30 MiB/s)
loading uInitrd ...
6284004 bytes read in 195 ms (30.7 MiB/s)
loading DTB /boot/dts/kirkwood-pogoplug_v4.dtb ...
9962 bytes read in 26 ms (374 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.17.2-kirkwood-tld-1
   Created:      2018-08-04   9:08:32 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4125394 Bytes = 3.9 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.17.2-kirkwood-tld-1
   Created:      2018-08-04   9:08:49 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6283940 Bytes = 6 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 ...

Further testing, from time to time the new uBoot gives "Verifying Checksum ... Bad Data CRC" when loading either uImage or uInitrd when boot. Tested SD card was good (and was the same one I have been using since day 1 in my PogoPlug V4) Is there some changes in uBoot to speed up SD card access?

Now it is getting weird....

Before all these, make a full image (3.14.0) backup using dd. And now I restored the image using dd, and did a cmp as well, make sure the image was good on SD card.

But still getting

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700)
Pogoplug V4
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... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: ide_preinit failed

MMC rescan: current device # 0 initialized OK
## 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 **

no IDE devices available

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

Part	Start Sector	Num Sectors	UUID		Type
  1	63        	16015297  	00000000-01	83
loading envs from mmc 0 ...
** File not found /boot/uEnv.txt **
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

Reset IDE: ide_preinit failed
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

MMC rescan: current device # 0 initialized OK
device mmc 0:1
Failed to iterate over directory boot
** File not found /boot/uImage **
device mmc 1:1
MMC Device 1 not found
MMC Device 1 not found
** Bad device mmc 1 **
device mmc 2:1
MMC Device 2 not found
MMC Device 2 not found
** Bad device mmc 2 **
device mmc 3:1
MMC Device 3 not found
MMC Device 3 not found
** Bad device mmc 3 **
loading uImage ...
ext4fs_devread read outside partition 134221976
loading uInitrd ...
 ** ext4fs_devread read error - block
** SI ext2fs read block (indir 1)failed. **
loading DTB /boot/dts/kirkwood-pogoplug_v4.dtb ...
** Can't read partition table on 0:0 **
** Invalid partition 1 **
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.14.0-kirkwood-tld-1
   Created:      2014-04-06  20:44:27 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2461352 Bytes = 2.3 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!
## Error: "bootcmd_pogo" not defined
resetting ...

Only different before (working for years) and after (stuck...) was uBoot and the envs... Any ideas?

And say if I wanted to try USB (to eliminate if it is new uBoot not working nicely with mmc on my PogoPlug V4), how do I "convert" my SD card image to USB?

Thanks.

ok, here is another attempt... I almost for sure something is not right in my uBoot...

I followed the simple instruction on "Updated 24 Jul 2017" here. Basically I formatted a 16GB USB in ext3fs and labelled it rootfs on my Ubuntu box. Then untar the Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 as instructed.

running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 691 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
3821592 bytes read in 987 ms (3.7 MiB/s)
loading uInitrd ...
7245696 bytes read in 1068 ms (6.5 MiB/s)
loading DTB /boot/dts/kirkwood-pogoplug_v4.dtb ...
10284 bytes read in 1769 ms (4.9 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.12.1-kirkwood-tld-1
   Created:      2017-07-20   8:11:24 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3821528 Bytes = 3.6 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.12.1-kirkwood-tld-1
   Created:      2017-07-24   0:18:23 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7245632 Bytes = 6.9 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 the result is the same. It stuck at "Starting kernel..." while LED turns from Solid Orange to Solid Green....

Derek,

There is nothing wrong here. The kernel most likely has booted

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700)
Pogoplug V4
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

unning scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 691 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
3821592 bytes read in 987 ms (3.7 MiB/s)
loading uInitrd ...
7245696 bytes read in 1068 ms (6.5 MiB/s)
loading DTB /boot/dts/kirkwood-pogoplug_v4.dtb ...
10284 bytes read in 1769 ms (4.9 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.12.1-kirkwood-tld-1
   Created:      2017-07-20   8:11:24 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3821528 Bytes = 3.6 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.12.1-kirkwood-tld-1
   Created:      2017-07-24   0:18:23 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7245632 Bytes = 6.9 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 ...

With netconsole, the only output you will see is until "Starting kernel ...". And the LED is solid green indicated the kernel has booted sucessfully.

Look for a new dynamic IP in your router, or try to ping its host name (wait for about 5 minutes after power up to make sure this hostname to be advertised inthe network):

ping debian.local

And btw, with the new u-boot envs, these additional envs are unecessary. The defaut envs already setup to boot with mmc automatically.

mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
mmc_init=mmc rescan
mmc_load_uimage=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1

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

Hi bodhi

Thanks! I have kind of figure out the problems along the way learning by trial and error... :) I have to admit I know nothing about uboot few days ago and now I think I get a hang of it. Yes, those mmc envs are unecessary, was copied from the (very) old instructions.

Again, long story short.. It booted (for now) the latest 4.17.2 on SD card.

But I still encounter some iffy issue that I believe it is uBoot related. Maybe I will end this thread and start a new one in uBoot forum. Thanks for the great work btw!