Pogoplug E02 information sought ...

I'm in need of some data : I need a few snippets of the boot log from your Pogoplug E02... and basic info.

1. output of :

dmesg | egrep '(Machine:)|( NAND )|(Memory)|(Feroceon L2:)|( Linux version )'

2. output of :

fw_printenv arcNumber

3. which u-boot you have installed : (specify which option fits for your Pogoplug E02)
A Jeff's
B another u-boot : version


4. your LED behavior : : (specify which option fits for your Pogoplug E02)
C front LED is always OFF, green
D front LED is always ON/SOLID, green
E front LED is always ON/SOLID, orange
F other - specify please

- thanks, davy
(I'm trying to get the behavior of a u-boot upgrade just right. Knowing correct and incorrect behaviors will help.)

=====================================================

• davy's Github Repo's rescue-dg

Edited 3 time(s). Last edit at 02/20/2012 05:36PM by davygravy.

I'm not sure I have what you're looking for (my Pogoplug Pink E02 is still a basic plug, using older kernel). But in case it's helpful, here is the info:

1)
root@PogoPink1:~# dmesg | egrep '(Machine:)|( NAND )|(Memory)|(Feroceon L2:)|( Linux version )'
[ 0.000000] Linux version 2.6.32-5-kirkwood (Debian 2.6.32-30) (ben@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Wed Jan 12 15:27:07 UTC 2011
[ 0.000000] Machine: Marvell SheevaPlug Reference Board
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] Memory: 256MB = 256MB total
[ 0.000000] Memory: 250496KB available (3512K code, 583K data, 124K init, 0K highmem)
[ 21.717830] Feroceon L2: Cache support initialised.
[ 22.402300] NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)

2)
root@PogoPink1:~# fw_printenv arcNumber
arcNumber=2097

3)
A - Jeff's UBoot

4)
- LED: F other

Use "echo default-on > /sys/class/leds/plug:green:health" to turn on.
Use "echo none > /sys/class/leds/plug:green:health" to turn off.

root@PogoPink1:~# ls -R /sys/class/leds
/sys/class/leds:
. .. plug:green:health

My Pogo is labeled (on the box) as a P21 but the label on the bottom of the Pogo says E02

rich@Pogo-alarm ~]$ dmesg | egrep '(Machine:)|( NAND )|(Memory)|(Feroceon L2:)|( Linux version )'
[ 0.000000] Linux version 3.1.10-2-ARCH (root@platinum) (gcc version 4.6.2 20111223 (prerelease) (GCC) ) #1 PREEMPT Fri Feb 3 01:54:23 UTC 2012
[ 0.000000] Machine: Marvell SheevaPlug Reference Board
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] Memory: 256MB = 256MB total
[ 0.000000] Memory: 253308k/253308k available, 8836k reserved, 0K highmem
[ 4.317336] Feroceon L2: Cache support initialised.
[ 4.630496] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)

[root@Pogo-alarm rich]# fw_printenv arcNumber
arcNumber=2097


3. which u-boot you have installed : (specify which option fits for your Pogoplug E02)
A Jeff's

4. your LED behavior : : (specify which option fits for your Pogoplug E02)

E front LED is always ON/SOLID, orange



Edited 1 time(s). Last edit at 02/20/2012 07:30PM by laprjns.

1

[    0.000000] Linux version 2.6.32-5-kirkwood (Debian 2.6.32-45) (dannf@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Sun May 6 16:57:51 UTC 2012
[    0.000000] Machine: Marvell SheevaPlug Reference Board
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] Memory: 256MB = 256MB total
[    0.000000] Memory: 250880KB available (3516K code, 583K data, 124K init, 0K highmem)
[   21.718756] Feroceon L2: Enabling L2
[   21.718790] Feroceon L2: Cache support initialised.
[   22.385551] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)

2
arcNumber=2097
should the arc number be 3542?
http://www.arm.linux.org.uk/developer/machines/

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

4
E front LED is always ON/SOLID, orange



Edited 1 time(s). Last edit at 06/24/2012 07:09AM by rynax.

[ 0.000000] Linux version 2.6.32-5-kirkwood (Debian 2.6.32-48) (ben@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Sat Feb 16 04:43:37 UTC 2013
[ 0.000000] Machine: Marvell SheevaPlug Reference Board
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] Memory: 256MB = 256MB total
[ 0.000000] Memory: 250752KB available (3520K code, 583K data, 124K init, 0K highmem)
[ 0.243890] Feroceon L2: Enabling L2
[ 0.243925] Feroceon L2: Cache support initialised.
[ 0.913799] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)

arcNumber: 2097

Jeff's u-Boot

E front LED is always ON/SOLID, orange

bodhi,

I tried

"echo default-on > /sys/class/leds/plug:green:health/trigger"
(I added the trigger part)

to turn on the green LED and nothing happens on mine. Can you point me to where to download your kernel?
Thanks

lincomatic Wrote:
-------------------------------------------------------
> bodhi,
>
> I tried
>
> "echo default-on >
> /sys/class/leds/plug:green:health/trigger"
> (I added the trigger part)
>
> to turn on the green LED and nothing happens on
> mine. Can you point me to where to download your
> kernel?
> Thanks

I've uploaded my 3.2.28 kernel in this post.

To use the Pogo E02 as a basic reference board 2097, you only needs mainline 2.6.x kernel. With mainline 3.2.x kernel, you'll have more supports, but no Pogo E02. The kernel I built is the mainline 3.2.28+ patches for various Kirwood plugs, including E02. So the /sys/class/leds/... directory will have the correct trigger files for Pogo E02.

bodhi Wrote:

> I've uploaded my 3.2.28 kernel in
> this
> post.
>
> To use the Pogo E02 as a basic reference board
> 2097, you only needs mainline 2.6.x kernel. With
> mainline 3.2.x kernel, you'll have more supports,
> but no Pogo E02. The kernel I built is the
> mainline 3.2.28+ patches for various Kirwood
> plugs, including E02. So the /sys/class/leds/...
> directory will have the correct trigger files for
> Pogo E02.

Thanks, but the download link is blocked by mediafire now.
Could you post it elsewhere? Or, I can host the file on my pogoplug for everyone to download if you like :)

@lincomatic,

I will reupload it to Dropbox instead. But it will take awhile, I have a very slow uplink :)

I've reuploaded it to Dropbox.

And here are my 2 cents worth:

1:
[ 0.000000] Linux version 3.3.2-kirkwood-dg (davygravy@bitbaker64) (gcc version 4.6.1 (Sourcery CodeBench Lite 2011.09-70) ) #1 Mon Apr 23 17:09:27 CDT 2012
[ 0.000000] Machine: Marvell SheevaPlug Reference Board
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] Memory: 256MB = 256MB total
[ 0.000000] Memory: 247748k/247748k available, 14396k reserved, 0K highmem
[ 14.737809] Feroceon L2: Enabling L2
[ 14.737845] Feroceon L2: Cache support initialised.
[ 15.976320] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)

2: 3542

3: A

4: E

Really exited about you trying to build what sounds like a "universal uboot" for the Marvells!!! However, if you were to crack the OXNAS, you would be a real hero ... ;-)

---
Standart ist der Standardfehler

chessplayer, you're not really running Pogo E02! it is running as a 2097 reference board.

[ 0.000000] Machine: Marvell SheevaPlug Reference Board

This is probably because of the machid env was not set to dd6.

bodhi Wrote:
-------------------------------------------------------
> chessplayer, you're not really running Pogo E02!
> it is running as a 2097 reference board.
>
>

> [ 0.000000] Machine: Marvell SheevaPlug Reference
> Board
>

>
> This is probably because of the machid env was not
> set to dd6.

Hi bodhi,

I'm sorry, but you lost me here. What is the significance of this? I understand that dd6(HEX) = 3542 (DEC), which is the arcNumber I provided, but what do I need the machid for and especially, where do I set it? More to the point: why should I do that when apparently the machine works just fine (apart from the LED)?

I guess, all this also has to do with your efforts in putting together a, let me call it, universal kernel?

Maybe some day I will really understand and not just use this stuff ...

---
Standart ist der Standardfehler

Hi chessplayer,

The reason is the current uBoot has a glitch that it will ignore arcNumber 3542, and not passing it to the kernel. So we need to also set machid to dd6 using "fw_setenv machid dd6". I've posted it here: http://forum.doozan.com/read.php?2,11601,11637#msg-11637.

And I really defer to davygravy for the effort to have a "universal kernel" :) I only want to contribute my built kernel for people to use, if for whatever reason, a different kernel did not work. As a matter of fact, the go-to rootfs should be Davy's NSA320 rootfs, with which you can boot just about any Kirkwood plug.

With reference board env 2097 setting, all Kirkwood plugs should work just fine. The things you would gain is to be able to "see" other special devices like LEDs, SATA, PCIe better with appropriate arcNumber (therefore patched code needed).

- bodhi

Ok, so I took bodhi's advice and set the machid using the rescue system. With rescue, the answers to the questions are now as follows:

1:

e02-rescue:~# dmesg | egrep '(Machine:)|( NAND )|(Memory)|(Feroceon L2:)|( Linux version )'
[    0.000000] Linux version 3.3.2-kirkwide (davygravy@bitbaker64) (gcc version 4.3.5 (Buildroot 2010.08) ) #1 Mon Oct 29 17:52:07 CDT 2012
[    0.000000] Machine: Pogoplug E02
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] Memory: 256MB = 256MB total
[    0.000000] Memory: 252028k/252028k available, 10116k reserved, 0K highmem
[    5.955352] Feroceon L2: Enabling L2
[    5.955388] Feroceon L2: Cache support initialised.
[    6.683198] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)

2 and 3 are obviously as before: 3542 and A

4: D (--> brilliant!!)

However, when I try to boot with the stick that worked before (see my post above), the situation is quite different. I do see it booting via netconsole, but I can't ssh to the machine anymore; looks like it does not get an IP (hope nobody read the nonsense I wrote here before the edit ...)

Also, the LED goes to state C (always off; green somewhere inside if you look closely).

Hope this helps somehow. But for me the question is: what now?

I would also like to point out shv's post which describes more or less the same situation.

Addendum March 5, 2013
----------------------------------

As of today, I have a second POGO E02 (pink this time) where the phenomena are exacly the same. There is just one difference, namely the NAND seems to be a Samsung instead of a Hynix.

---
Standart ist der Standardfehler



Edited 2 time(s). Last edit at 03/05/2013 08:40AM by chessplayer.

@chessplayer,

I've suspected that davy's rootfs (Linux version 3.3.2-kirkwide ) does not have E02 support. When I looked at that rootfs config file I did not see Pogoplug E02 or V4. But it was on the Dropbox so I can't be sure.

So I guess you can do these:

1. Use netconsole to remove machid (use command setenv machid) so that you're back to old settings.

2. After you're back to old booting system, you can install my built kernel
http://forum.doozan.com/read.php?2,11601
and then set machid again.

bodhi Wrote:
-------------------------------------------------------
> @chessplayer,
>
> I've suspected that davy's rootfs (Linux version
> 3.3.2-kirkwide ) does not have E02 support. When I
> looked at that rootfs config file I did not see
> Pogoplug E02 or V4. But it was on the Dropbox so I
> can't be sure.
>

Thanks, bodhi, I will consider that. However, in the above there is a mistake: the 3.3.2-kirkwide is the Linux version of the rescue system, which works for the POGO. However, as pointed out by shv, the kernel 3.3.2-kirkwood-dg used in davy's rootfs does not seem to have support for POGO-E02. Strange ...

And another thing: there is no need for netconsole to revert the machid, since rescue works just fine, so I can just ssh to the machine with rescue booted.

But anyway, thanks for the help!

---
Standart ist der Standardfehler



Edited 1 time(s). Last edit at 03/05/2013 08:43AM by chessplayer.

Both 3.3.2 kernel configuration files are available from davy's post. You can find a link to the kirkwood-dg config file in the message (config-3.3.2-kirkwood-dg-wide) and the kirkwide config file (linux-3.3.2-wider-config-Buildroot-module-set) in the link to davygravys dropbox (Kirkwood Downloads). The patch file is also available in the dropbox (linux-3.3.2-wider-patch). If I compare both config files the support for both Pogoplug devices is missing in the kirkwood-dg configuration:

CONFIG_MACH_POGOPLUGV4=y
CONFIG_MACH_POGO_E02=y

The NSA320 which I already tested doesn't contain support for the Pogoplug arcNumbers and machids. You can find a list of supported arcNumbers/machids in the following message: my post.



Edited 4 time(s). Last edit at 03/05/2013 08:56AM by shv.

[    0.000000] Linux version 2.6.32-5-kirkwood (Debian 2.6.32-46) (dannf@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Sun Sep 23 22:53:30 UTC 2012
[    0.000000] Machine: Marvell SheevaPlug Reference Board
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] Memory: 256MB = 256MB total
[    0.000000] Memory: 250880KB available (3516K code, 583K data, 124K init, 0K highmem)
[   21.718774] Feroceon L2: Enabling L2
[   21.718809] Feroceon L2: Cache support initialised.
[   22.386609] NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)

# fw_printenv arcNumber
arcNumber=2097

Jeff's uBoot
Solid Orange

With Jeff's script, davygravy's u-boot, and bodhi's kernel, here is what I got:

1. Seems black comes with Hynix NAND while pink has Samsung.

(%3)(10:05)(punk)~> dmesg | egrep '(Machine:)|( NAND )|(Memory)|(Feroceon L2:)|( Linux version )'
[    0.000000] Linux version 3.2.28-kirkwood-tld (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 PREEMPT Sun Feb 24 05:23:49 PST 2013
[    0.000000] Machine: Pogoplug E02
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] Memory: 256MB = 256MB total
[    0.000000] Memory: 247612k/247612k available, 14532k reserved, 0K highmem
[   17.174773] Feroceon L2: Enabling L2
[   17.174811] Feroceon L2: Cache support initialised.
[   18.350642] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)

2. No need for machid(see 3 for why).

(%3)(10:06)(punk)~> sudo fw_printenv arcNumber
arcNumber=3542
(%3)(10:06)(punk)~> sudo fw_printenv machid
## Error: "machid" not defined

3. From netconsole with C-j.

U-Boot 2011.12 (Jun 08 2012 - 11:41:39)
Pogoplug E02
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot:  7 
 0 
pogoE02>

4. LED all works.

(%3)(10:10)(punk)~> ll /sys/class/leds
total 0
lrwxrwxrwx 1 root root 0 Mar 15 01:26 status:green:health -> ../../devices/platform/leds-gpio/leds/status:green:health/
lrwxrwxrwx 1 root root 0 Mar 15 01:27 status:orange:fault -> ../../devices/platform/leds-gpio/leds/status:orange:fault/

5. One more.

(%3)(10:26)(punk)~> cpu
Processor       : Feroceon 88FR131 rev 1 (v5l)
BogoMIPS        : 1191.11
Features        : swp half thumb fastmult edsp 
CPU implementer : 0x56
CPU architecture: 5TE
CPU variant     : 0x2
CPU part        : 0x131
CPU revision    : 1

Hardware        : Pogoplug E02
Revision        : 0000
Serial          : 0000000000000000

Thanks Jeff, davygravy and bodhi.



Edited 1 time(s). Last edit at 03/16/2013 10:51AM by syong.