Welcome! Log In Create A New Profile

Advanced

U-Boot VAMP 0.6 Pogoplug V4

Posted by rustyspoons 
U-Boot VAMP 0.6 Pogoplug V4
October 21, 2014 07:37AM
I have a collection of Pogoplugs thank's to the great U-Boot on here, brilliant little devices.

I also have serial access on them all.

On one of them I run VAMP 0.6 as a music player, I have tried a squeezelite install on ARCH/Debian but it does not seem to work as well as the Fedora based VAMP image that they have created on Vortexbox.

As the E02 is getting harder to find, I have ordered a V4 device, I would like to stick this in the AV rack and use it as just a music player.

The VAMP install is based on a Doozan U-Boot with modified environments, I would love to get VAMP running on a V4 but I believe the U-Boot is different, will the environments script in this guide work? or will I brick the V4

http://vortexbox.org/forum/vortexbox/general/51318-install-vamp-0-6

/usr/sbin/fw_setenv usb_scan 'usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done'
/usr/sbin/fw_setenv usb_boot 'mw 0x800000 0 1; ext2load usb $usb_device 0x800000 uImage; if ext2load usb $usb_device 0x1100000 uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi'
/usr/sbin/fw_setenv usb_scan_1 "usb=0:1 dev=sda3"
/usr/sbin/fw_setenv usb_scan_2 "usb=1:1 dev=sdb3"
/usr/sbin/fw_setenv usb_scan_3 "usb=2:1 dev=sdc3"
/usr/sbin/fw_setenv usb_scan_4 "usb=3:1 dev=sdd3"
/usr/sbin/fw_setenv usb_rootfstype ext4


If it's a no go, what's required to get this image running on a V4, it looks a perfect device to run as a Squeezebox player, I am not bothered whether it will SD or USB boot, SD would be nice though.

Any help would be gratefully appreciated, keep up the good work :)
Re: U-Boot VAMP 0.6 Pogoplug V4
October 21, 2014 11:42AM
rustyspoons,

> will the environments script in this
> guide work? or will I brick the V4
>
> http://vortexbox.org/forum/vortexbox/general/51318
> -install-vamp-0-6

You will brick it with that procedure! See this u-boot:
http://forum.doozan.com/read.php?3,12381

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: U-Boot VAMP 0.6 Pogoplug V4
October 21, 2014 12:03PM
bodhi Wrote:
-------------------------------------------------------
> rustyspoons,
>
> > will the environments script in this
> > guide work? or will I brick the V4
> >
> >
> http://vortexbox.org/forum/vortexbox/general/51318
>
> > -install-vamp-0-6
>
> You will brick it with that procedure! See this
> u-boot:
> http://forum.doozan.com/read.php?3,12381


Hi Bodhi,

Thanks for your reply, I wasn't going to use the U-Boot from the VAMP link, but the one on here, will the environment script in that link with the U-Boot you listed?

Cheers



Edited 1 time(s). Last edit at 10/21/2014 01:13PM by rustyspoons.
Re: U-Boot VAMP 0.6 Pogoplug V4
October 22, 2014 12:32AM
rustyspoons,

Please read the 1st post of that thread. If you are unsure about any part, post your questions here.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: U-Boot VAMP 0.6 Pogoplug V4
October 22, 2014 02:07AM
Sorry just realised there was a word missing in my reply and didn't make sense.

In my original post I put environment commands in a code box, which is what's needed to boot the image.

I wanted to know if that environment is compatible with the U-Boot for the V4, I know those strings work with the U-Boot for the E02 with the U-Boot from here.

However the VAMP image will not boot on an E02 unless you specify those environmental strings.

Will they work with the V4 U-Boot or are there some changes I need to make or are there alternative commands.

I'm not sure exactly which string is the one that gets VAMP to boot.

Thanks,
Dale
Re: U-Boot VAMP 0.6 Pogoplug V4
October 22, 2014 02:41AM
@Dale,

With the new u-boot you can set whatever envs you need. If it's a Fedora image, then it should boot without problem. However, as always, it is prudent to try it out without flashing to NAND if you can. The Pogo V4 has UART booting, so you should try that since you have serial console. As instructed in the 1st post of my u-boot thread:

Quote

Important Note: If possible, try to test this boot image with UART booting before flashing to NAND. See davygravy's UART booting using kwboot instruction: here in this thread.

So download the u-boot image for Pogo V4, and kwboot. Try UART booting, and interrupt serial console, enter those envs that you know needed for booting the VAMP image. And boot it. If you booted into VAMP, then in VAMP, you should be able to flash this u-boot for real. The important part is UART booting, once you know you can do that, flashing u-boot manually is safe to do.

Also see here for how to boot UART with the Pogo V4 (a little bit trickier than other boxes):
http://forum.doozan.com/read.php?3,18153,18200#msg-18200

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



Edited 1 time(s). Last edit at 10/22/2014 02:43AM by bodhi.
Re: U-Boot VAMP 0.6 Pogoplug V4
October 22, 2014 03:30AM
bodhi Wrote:
-------------------------------------------------------
> @Dale,
>
> With the new u-boot you can set whatever envs you
> need. If it's a Fedora image, then it should boot
> without problem. However, as always, it is prudent
> to try it out without flashing to NAND if you can.
> The Pogo V4 has UART booting, so you should try
> that since you have serial console. As instructed
> in the 1st post of my u-boot thread:
>
>
Quote

Important Note: If possible, try to test
> this boot image with UART booting before flashing
> to NAND. See davygravy's UART booting using kwboot
> instruction: here in this thread.
>
> So download the u-boot image for Pogo V4, and
> kwboot. Try UART booting, and interrupt serial
> console, enter those envs that you know needed for
> booting the VAMP image. And boot it. If you booted
> into VAMP, then in VAMP, you should be able to
> flash this u-boot for real. The important part is
> UART booting, once you know you can do that,
> flashing u-boot manually is safe to do.
>
> Also see here for how to boot UART with the Pogo
> V4 (a little bit trickier than other boxes):
> http://forum.doozan.com/read.php?3,18153,18200#msg
> -18200

Thanks Bodhi,

Very informative information,

Will report back when I get this working, should make a lot of VAMP users happy if this will work on a V4 :D
Re: U-Boot VAMP 0.6 Pogoplug V4
October 22, 2014 03:42AM
> Will report back when I get this working, should
> make a lot of VAMP users happy if this will work
> on a V4 :D

That would be cool :) I'll give you a hand whenever you need an answer in setting up u-boot for that.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: U-Boot VAMP 0.6 Pogoplug V4
October 22, 2014 06:42AM
Bodhi,

I have your UBOOT installed and also have a working copy of Debian on a flash stick, device is working fine, can boot to Debian perfectly, got root access and SSH.

It will not boot from VAMP image as I expected, the green light flashes then flashes red and re-boots, I just need to figure out what the environment differences are to boot the VAMP image.

Thanks,
Dale
Re: U-Boot VAMP 0.6 Pogoplug V4
October 22, 2014 08:34AM
This is what I get if I manually insert the environemnts listed in Post 1 and try and boot the VAMP image.

Pogov4> boot
 b o o t 
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
** Bad device usb 0x800000 **
** Bad device usb 0x1100000 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
** Bad device mmc 0 **
** Bad device mmc 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!

Reset IDE: ide_preinit failed
** Bad device size - ide 0 **
** Bad device size - ide 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
resetting ...


Current Printenv:

Pogov4> printenv
 p r i n t e n v 
arcNumber=3960
baudrate=115200
bootcmd=run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; reset
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot;
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
device=0:1
ethact=egiga0
ethaddr=00:25:31:05:2a:77
if_netconsole=ping $serverip
ipaddr=192.168.1.10
led_error=orange blinking
led_exit=green off
led_init=green blinking
machid=F78
mainlineLinux=yes
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
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
ncip=192.168.1.100
partition=nand0,2
preboot=run if_netconsole start_netconsole
preboot_nc=run if_netconsole start_netconsole
rootdelay=10
rootfstype=ext3
sata_boot=mw 0x800000 0 1; run sata_load_uimage; if run sata_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_init=ide reset
sata_load_uimage=ext2load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext2load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
serverip=192.168.1.100
set_bootargs_mmc=setenv bootargs console=$console root=$mmc_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_sata=setenv bootargs console=$console root=$sata_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 uImage; if ext2load usb $usb_device 0x1100000 uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_init=usb start
usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd
usb_root=/dev/sda1
usb_rootfstype=ext4
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_1=usb=0:1 dev=sda3
usb_scan_2=usb=1:1 dev=sdb3
usb_scan_3=usb=2:1 dev=sdc3
usb_scan_4=usb=3:1 dev=sdd3

Environment size: 2743/131068 bytes



Edited 1 time(s). Last edit at 10/22/2014 09:31AM by rustyspoons.
Re: U-Boot VAMP 0.6 Pogoplug V4
October 22, 2014 12:14PM
These needs to be adjusted:

usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd

to
usb_load_uimage=ext2load usb $device 0x800000 /uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /uInitrd

because as you said, VAMP likes this better:
/usr/sbin/fw_setenv usb_boot 'mw 0x800000 0 1; ext2load usb $usb_device 0x800000 uImage; if ext2load usb $usb_device 0x1100000 uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi'

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: U-Boot VAMP 0.6 Pogoplug V4
October 22, 2014 12:55PM
del



Edited 5 time(s). Last edit at 10/23/2014 05:45PM by rustyspoons.
Re: U-Boot VAMP 0.6 Pogoplug V4
October 22, 2014 01:45PM
UPDATE,

Re-installed your uboot.2014.07-tld-1.environment.img, now entering the 2 commands at Uboot console gets it booting off VAMP kernel...

Progress is happening!!
Re: U-Boot VAMP 0.6 Pogoplug V4
October 22, 2014 01:49PM
rustyspoons Wrote:
-------------------------------------------------------
> UPDATE,
>
> Re-installed your
> uboot.2014.07-tld-1.environment.img, now entering
> the 2 commands at Uboot console gets it booting
> off VAMP kernel...
>
> Progress is happening!!

U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:59:45)
Pogoplug V4
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Hit any key to stop autoboot:  9 
 0 
Pogov4> setenv usb_load_uimage ext2load usb $device 0x800000 /uImage
 s e t e n v   u s b _ l o a d _ u i m a g e   e x t 2 l o a d   u s b   $ d e v i c e   0 x 8 0 0 0 0 0   / u I m a g e 
Pogov4> setenv usb_load_uinitrd ext2load usb $device 0x1100000 /uInitrd 
 s e t e n v   u s b _ l o a d _ u i n i t r d   e x t 2 l o a d   u s b   $ d e v i c e   0 x 1 1 0 0 0 0 0   / u I n i t r d   
Pogov4> boot
 b o o t 
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
3604400 bytes read in 380 ms (9 MiB/s)
15522922 bytes read in 1452 ms (10.2 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   3.9.4-200.fc18.armv5tel.kirkwood
   Created:      2013-06-04  19:13:51 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3604336 Bytes = 3.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs
   Created:      2013-06-04  19:13:52 UTC
   Image Type:   ARM Linux RAMDisk Image (uncompressed)
   Data Size:    15522858 Bytes = 14.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK


Starting kernel ...

Got a Green/Red LED on together and it's hung at starting Kernel.
Re: U-Boot VAMP 0.6 Pogoplug V4
October 22, 2014 02:18PM
Starting kernel ...

Is that netconsole output or serial console output?
Re: U-Boot VAMP 0.6 Pogoplug V4
October 22, 2014 02:20PM
Netconsole, Will get serial up soon, lost my CP2012, hunting around for it :)
Re: U-Boot VAMP 0.6 Pogoplug V4
October 22, 2014 02:31PM
On netconsole, Starting kernel ... is all you will see, it isn't necessarily hung.

Serial console will show you more, a lot more. If the boot is normal, it will show you a login prompt.
Re: U-Boot VAMP 0.6 Pogoplug V4
October 22, 2014 02:38PM
U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:59:45)
Pogoplug V4

SoC:   Kirkwood 88F6192_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  128 MiB
MMC:   kwsdio: 0
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
No link on egiga0
ping failed; host 192.168.1.100 is not alive
Hit any key to stop autoboot:  0
Pogov4> setenv usb_load_uimage ext2load usb $device 0x800000 /uImage
Pogov4> setenv usb_load_uinitrd ext2load usb $device 0x1100000 /uInitrd
Pogov4> boot
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
3604400 bytes read in 417 ms (8.2 MiB/s)
15522922 bytes read in 1610 ms (9.2 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   3.9.4-200.fc18.armv5tel.kirkwood
   Created:      2013-06-04  19:13:51 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3604336 Bytes = 3.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs
   Created:      2013-06-04  19:13:52 UTC
   Image Type:   ARM Linux RAMDisk Image (uncompressed)
   Data Size:    15522858 Bytes = 14.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
Using machid 0xf78 from environment

Starting kernel ...

Uncompressing Linux... done, booting the kernel.


Serial console, and hung :(
Re: U-Boot VAMP 0.6 Pogoplug V4
October 22, 2014 02:54PM
Current NAND env (without me overiding) Of My V4
Pogov4> printenv
arcNumber=3960
baudrate=115200
bootargs=console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext3 mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
bootcmd=run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; reset
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot;
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
device=0:1
ethact=egiga0
ethaddr=00:25:31:05:2a:77
if_netconsole=ping $serverip
ipaddr=192.168.1.10
led_error=orange blinking
led_exit=green off
led_init=green blinking
machid=F78
mainlineLinux=yes
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
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
partition=nand0,2
preboot=run if_netconsole start_netconsole
preboot_nc=run if_netconsole start_netconsole
rootdelay=10
rootfstype=ext3
sata_boot=mw 0x800000 0 1; run sata_load_uimage; if run sata_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_init=ide reset
sata_load_uimage=ext2load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext2load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
serverip=192.168.1.100
set_bootargs_mmc=setenv bootargs console=$console root=$mmc_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_sata=setenv bootargs console=$console root=$sata_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
usb_boot=mw 0x800000 0 1; run usb_load_uimage; if run usb_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_init=usb start
usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd
usb_root=/dev/sda1
usb_rootfstype=ext3

Re: U-Boot VAMP 0.6 Pogoplug V4
October 22, 2014 03:06PM
Booting....

setenv machid
setenv archnumber

Now get as far as....

[   20.602809] scsi 0:0:0:0: Direct-Access     Lexar    USB Flash Drive  8.07 PQ: 0 ANSI: 4
[   20.616490] sd 0:0:0:0: [sda] 15659008 512-byte logical blocks: (8.01 GB/7.46 GiB)
[   20.626105] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   20.637734] sd 0:0:0:0: [sda] Write Protect is off
[   20.649733] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[   20.670941]  sda: sda1 sda2 sda3
[   20.684355] sd 0:0:0:0: [sda] Attached SCSI removable disk
[   21.189022] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem
[   21.203459] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)
dracut-initqueue[133]: Warning: e2fsck returned with 1
[   24.479397] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem
[   25.032156] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)
dracut-initqueue[133]: Warning: /sysroot has no proper rootfs layout, ignoring and removing offending mount hook
dracut-initqueue[133]: Warning: Can't mount root filesystem
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Reached target Basic System.
dracut-initqueue[133]: Warning: e2fsck returned with 1
dracut-initqueue[133]: Warning: /sysroot has no proper rootfs layout, ignoring and removing offending mount hook
dracut-initqueue[133]: Warning: Can't mount root filesystem


Entering emergency mode. Exit the shell to continue.
Type "journalctl" to view system logs.

dracut:/#

Re: U-Boot VAMP 0.6 Pogoplug V4
October 22, 2014 04:44PM
Make sure your u-boot env rootfstype matches what fs you have on the USB drive (ext2,3,4).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: U-Boot VAMP 0.6 Pogoplug V4
October 22, 2014 04:47PM
bodhi Wrote:
-------------------------------------------------------
> Make sure your u-boot env rootfstype matches what
> fs you have on the USB drive (ext2,3,4).

I've tried ext4 but still the same.
Re: U-Boot VAMP 0.6 Pogoplug V4
October 22, 2014 08:40PM
rustyspoons Wrote:
-------------------------------------------------------
> bodhi Wrote:
> --------------------------------------------------
> -----
> > Make sure your u-boot env rootfstype matches
> what
> > fs you have on the USB drive (ext2,3,4).
>
> I've tried ext4 but still the same.

Your dmesg showed that the kernel thinks the VAMP rootfs is Ext2.

- Does the rootfs labeled "rootfs"?
- what is the content of fstab?
- what are the ouput of:
ls -l /
ls -l /boot

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: U-Boot VAMP 0.6 Pogoplug V4
October 23, 2014 07:52AM
bodhi Wrote:
-------------------------------------------------------
> rustyspoons Wrote:
> --------------------------------------------------
> -----
> > bodhi Wrote:
> >
> --------------------------------------------------
>
> > -----
> > > Make sure your u-boot env rootfstype matches
> > what
> > > fs you have on the USB drive (ext2,3,4).
> >
> > I've tried ext4 but still the same.
>
> Your dmesg showed that the kernel thinks the VAMP
> rootfs is Ext2.
>
> - Does the rootfs labeled "rootfs"? - Yes
> - what is the content of fstab?
> - what are the ouput of:
> ls -l /
> ls -l /boot

I see dmesg mention that, but in the original VAMP script to set the envs it states rootfs as ext4?,

I will fire this image up on a serial attached E02 and check some things, I think there is a slight difference somewhere with your UBoot env's and Jeff's UBoot envs?


Yes it's labled "rootfs"

rootfs

dale@HP7800:/media/dale/rootfs$ ls -l
total 76
lrwxrwxrwx.  1 root root     7 Feb  2  2013 bin -> usr/bin
drwxr-xr-x.  2 root root  4096 Feb  2  2013 boot
drwxr-xr-x.  2 root root  4096 Feb  2  2013 dev
drwxr-xr-x. 91 root root  4096 Oct 22 20:55 etc
drwxr-xr-x.  2 root root  4096 Jul 23  2012 home
lrwxrwxrwx.  1 root root     7 Feb  2  2013 lib -> usr/lib
drwx------.  2 root root 16384 Feb  2  2013 lost+found
drwxr-xr-x.  2 root root  4096 Jul 23  2012 media
drwxr-xr-x.  2 root root  4096 Jul 23  2012 mnt
drwxr-xr-x.  3 root root  4096 May 21  2013 opt
drwxr-xr-x   2 root root  4096 Feb  2  2013 proc
dr-xr-x---.  3 root root  4096 Apr 24  2013 root
drwxr-xr-x. 14 root root  4096 Feb  2  2013 run
lrwxrwxrwx.  1 root root     8 Feb  2  2013 sbin -> usr/sbin
drwxr-xr-x.  2 root root  4096 Jul 23  2012 srv
drwxr-xr-x.  2 root root  4096 Feb  2  2013 sys
drwxrwxrwt.  2 root root  4096 Feb  2  2013 tmp
drwxr-xr-x. 12 root root  4096 Feb  2  2013 usr
drwxr-xr-x. 19 root root  4096 Apr 24  2013 var

boot

dale@HP7800:/media/dale/borootfsot$ ls -l
total 58265
-rw-r--r--  1 root root      195 Feb  2  2013 boot.cmd.mmc
-rw-r--r--  1 root root      195 Feb  2  2013 boot.cmd.usb
-rw-r--r--  1 root root      267 Feb  2  2013 boot.scr
-rw-r--r--  1 root root      267 Feb  2  2013 boot.scr.mmc
-rw-r--r--  1 root root      267 Feb  2  2013 boot.scr.usb
-rw-r--r--  1 root root   120709 May 26  2013 config-3.9.4-200.fc18.armv5tel.kirkwood
drwxr-xr-x  2 root root     1024 Jun  4  2013 dtb-3.9.4-200.fc18.armv5tel.kirkwood
drwxr-xr-x  3 root root     1024 Feb  2  2013 grub2
-rw-------  1 root root 15522858 Jun  4  2013 initramfs-3.9.4-200.fc18.armv5tel.kirkwood.img
-rw-r--r--  1 root root   242272 Feb  2  2013 initrd-plymouth.img
-rw-------  1 root root       33 Jun  4  2013 klist.txt
drwx------. 2 root root    12288 Feb  2  2013 lost+found
-rw-------  1 root root  1649327 May 26  2013 System.map-3.9.4-200.fc18.armv5tel.kirkwood
-rw-r--r--  1 root root  3604400 Jun  4  2013 uImage
-rw-r--r--  1 root root  3604400 Jun  4  2013 uImage-3.9.4-200.fc18.armv5tel.kirkwood
-rw-r--r--  1 root root 15522922 Jun  4  2013 uInitrd
-rw-r--r--  1 root root 15522922 Jun  4  2013 uInitrd-3.9.4-200.fc18.armv5tel.kirkwood
-rwxr-xr-x  1 root root  3604336 May 26  2013 vmlinuz-3.9.4-200.fc18.armv5tel.kirkwood

/etc/fstab

#
# /etc/fstab
# Created by anaconda on Fri Feb  1 23:08:47 2013
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=997e9b52-62a6-4273-9427-ffe2c16ac534 /                       ext4    defaults        1 1
UUID=c5755968-e771-4898-a876-3af2fc0cdfc3 /boot                   ext2    defaults        1 2
UUID=798c08db-e355-4bad-b721-59f0c7656465 swap                    swap    defaults        0 0

Thanks Bodhi,
Dale
Re: U-Boot VAMP 0.6 Pogoplug V4
October 23, 2014 01:41PM
Thought this might help

Pogoplug E02 with VAMP, Working uBOOT Env

U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02

SoC:   Kirkwood 88F6281_A0
DRAM:  256 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found


u-boot>> printenv
arcNumber=2097
baudrate=115200
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
bootdelay=3
console=ttyS0,115200
ethact=egiga0
ethaddr=00:25:31:00:51:EE
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
stderr=serial
stdin=serial
stdout=serial
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 uImage; if ext2load usb $usb_device 0x1100000 uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_device=0:1
usb_init=run usb_scan
usb_root=/dev/sda1
usb_rootdelay=10
usb_rootfstype=ext4
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_1=usb=0:1 dev=sda3
usb_scan_2=usb=1:1 dev=sdb3
usb_scan_3=usb=2:1 dev=sdc3
usb_scan_4=usb=3:1 dev=sdd3
usb_scan_list=1 2 3 4
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params



Edited 2 time(s). Last edit at 10/23/2014 01:46PM by rustyspoons.
Re: U-Boot VAMP 0.6 Pogoplug V4
October 23, 2014 04:10PM
@Dale,

The new u-boot is a drop-in replacement for davygravy's u-boot, which is what you have installed on Pogo E02. All envs are reusable as they are. Of course, each machine needs a different u-boot binary, but the code is common. As for kernel, I suspect there might be a different issue lurking, but you have not got to that point yet! Currently you are still at the rootfs mounting stage.

If this rootfs partition is labeled "rootfs" (not the /boot partition)
UUID=997e9b52-62a6-4273-9427-ffe2c16ac534 /                       ext4    defaults        1 1

Then use the rootfs partition label approach. Base on your current env for the Pogo V4 above, you can do this:

In serial console:
setenv usb_root 'LABEL=rootfs'
And then go ahead, boot. If you can't boot, then please repost the envs. If you boot into VAMP or got stuck somewhere, then post the entire serial console log.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: U-Boot VAMP 0.6 Pogoplug V4
October 23, 2014 05:40PM
Bodhi,

It's working :D

Few little tweaks and I'll make a script to install the env's, amazing, boots quicker than E02 and playing music right now :D :D, thanks for your assistance :D


Fedora release 18 (Spherical Cow)
Kernel 3.9.4-200.fc18.armv5tel.kirkwood on an armv5tel (ttyS0)

localhost login: root
Password:
[root@localhost ~]# [  174.858681] usb 2-1: new full-speed USB device number 2 using xhci_hcd
[  174.880098] usb 2-1: New USB device found, idVendor=08bb, idProduct=2704
[  174.886784] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  174.893933] usb 2-1: Product: USB Audio DAC
[  174.898359] usb 2-1: Manufacturer: Burr-Brown from TI
[  174.905311] usb 2-1: ep 0x85 - rounding interval to 64 microframes, ep desc says 80 microframes

Re: U-Boot VAMP 0.6 Pogoplug V4
October 23, 2014 06:35PM
Awesome :)

Yes, please post your script, or instruction here so others looking for installing VAMP or just Fedora can find it.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: U-Boot VAMP 0.6 Pogoplug V4
October 24, 2014 04:21AM
Bodhi,

Fedora doesn't boot with a machid and has no control over the LED, so both green and red light up, is there anything in uBOOT I can change just so I get green LED?
Re: U-Boot VAMP 0.6 Pogoplug V4
October 24, 2014 05:11AM
Dale,

Please post these:

dmesg
cat /proc/cpuinfo
ls /sys/class/leds/ -l

I want to see if the kernel identifies the box as Pogo V4. If not then the LEDs can not be controlled correctly. However, there might be a work around if we can take a look at (where is the Git) the source tree used to build the Fedora kernel.

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



Edited 1 time(s). Last edit at 10/24/2014 05:13AM by bodhi.
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: