Welcome! Log In Create A New Profile

Advanced

Debian on CISCO ON100-K9

Posted by rayknight 
Re: Debian on CISCO ON100-K9
August 13, 2016 06:59PM
My box is no good :) I think it must have been DOA when I got it. Time to RTFM to see if it can be reset.

There is a RESET button.

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



Edited 1 time(s). Last edit at 08/13/2016 07:02PM by bodhi.
Re: Debian on CISCO ON100-K9
August 13, 2016 07:13PM
They say 10 seconds.. good luck :-)
-update- oh oh :-(

=========
-= Cloud 9 =-



Edited 1 time(s). Last edit at 08/13/2016 08:45PM by JoeyPogoPlugE02.
Re: Debian on CISCO ON100-K9
August 14, 2016 03:49AM
JoeyPogoPlugE02 Wrote:
-------------------------------------------------------
> They say 10 seconds.. good luck :-)
> -update- oh oh :-(

Yup. All LEDs blinking, can't kwboot it. Piece of crap :))

But I will build new u-boot for you guys.

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



Edited 1 time(s). Last edit at 08/14/2016 03:51AM by bodhi.
Re: Debian on CISCO ON100-K9
August 14, 2016 12:43PM
Bodhi/Gravelrash will the sellers exchange for another unit? If not, Ray's link still has them shipped for $11US

As another afterthought, I know all the lights are on when the TTY is hooked-up, but the order of that first didn't work for me.

=========
-= Cloud 9 =-



Edited 1 time(s). Last edit at 08/14/2016 02:27PM by JoeyPogoPlugE02.
Re: Debian on CISCO ON100-K9
August 14, 2016 03:40PM
I'm looking to get another one.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Debian on CISCO ON100-K9
August 14, 2016 05:52PM
Wasn't it Dean Martin who crooned you're no Bodhi 'till some Bodhi loves you.

=========
-= Cloud 9 =-
Re: Debian on CISCO ON100-K9
August 14, 2016 06:09PM
The thing that really annoyed me is the unit is sealed in box. Perhaps it was re-shrinkwrapped? I did not pay attention.

I opened the case and turned it on withoutplugging the ethernet cable and all LEDS are flashing. That's it.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Debian on CISCO ON100-K9
August 15, 2016 12:29AM
Mine was so clean I don't think it was repackaged, but I can only guess maybe the RTC battery ran out in storage.

If there's a day this is bootable/Debian I'll definitely take a risk and try to get an order for at least one more. It's these nerdy headless units that I'd most benefit long-term because if I make a home "server" and it's got direct video out, I'll never get serving.
So my strategy is get the infrastructure working and then goof off.

=========
-= Cloud 9 =-
Re: Debian on CISCO ON100-K9
August 18, 2016 03:12AM
While I'm waiting for my box, please try this build with kwboot.

kwboot  -t -B 115200 /dev/ttyUSB0 -b uboot.2016.05-tld-2.1.on100_k9.mtd0.kwb  -p


Interrupt serial console if you can load it with kwboot, and ping your router to see if you can get network connection. I still need to add GPIOs so disk drive might not work. Thanks Ray for the GPL, found the GPIOs in there.

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



Edited 2 time(s). Last edit at 08/18/2016 03:57AM by bodhi.
Attachments:
open | download - uboot.2016.05-tld-2.1.on100_k9.mtd0.kwb (512 KB)
Re: Debian on CISCO ON100-K9
August 18, 2016 02:32PM
I don't understand, is kwboot built into Cisco's firmware so once we interrupt boot it might do commands?
And where do I put that file then? On a FAT32 USB stick plugged in to the ON100? In the folder puTTY resides?

I tried doing research on kwboot and unfortunately got to a semi-hazardous website with aggressive popup virus warnings.

=========
-= Cloud 9 =-
Re: Debian on CISCO ON100-K9
August 18, 2016 03:09PM
Joey,

No need to search, it's mentioned in the main u-boot thread:
http://forum.doozan.com/read.php?3,12381

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. The latest u-boot image released here should be used for UART booting, if your box is the type that supports it (these do not: Dockstar, Pogo E02, iConnect).

To connect serial console with tty you run putty on Windows, or picocom on a Linux box. That's what you've been doing.

To boot with UART, you would run kwboot on the Linux box that has the serial module converter (in lieu of picocom). kwboot connects to the plug and sends a new version of u-boot, that you specified. Afetr the plug bootROM has received the completed image, it will load it to RAM and execute it. This is how we usually test a new version of u-boot without flashing to NAND.

ATM, you can only run kwboot on a Linux ARM box, not Windows. For example, using the T5325 as the serial module converter host, and the ON100 as the target plug.

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



Edited 1 time(s). Last edit at 08/18/2016 03:12PM by bodhi.
Re: Debian on CISCO ON100-K9
August 18, 2016 03:11PM
JoeyPogoPlugE02 Wrote:
-------------------------------------------------------
> I don't understand, is kwboot built into Cisco's
> firmware

It is a hardware feature baked in the chip's internal initialization firmware that allows you to send it a new uboot over serial connection.

>And where do I put that file then?
read this thread.
http://forum.doozan.com/read.php?3,7852,7852

You must likely use the -p flag (the second command).

EDIT: ninja'd by bodhi. :)



Edited 1 time(s). Last edit at 08/18/2016 06:07PM by bobafetthotmail.
Re: Debian on CISCO ON100-K9
August 18, 2016 07:58PM
Well thanks a lot gents - is the E02 Debi-arm? But for now I'm satisfied it's worth dedicating a Debian ARM or Ubuntu ARM for future projects. The Cisco box seems good for it but a little catch-22 right now lol

=========
-= Cloud 9 =-
Re: Debian on CISCO ON100-K9
August 19, 2016 12:36AM
bodhi Wrote:
-------------------------------------------------------
> While I'm waiting for my box, please try this
> build with kwboot.
>
>
> kwboot  -t -B 115200 /dev/ttyUSB0 -b
> uboot.2016.05-tld-2.1.on100_k9.mtd0.kwb  -p
>
>
>
> Interrupt serial console if you can load it with
> kwboot, and ping your router to see if you can get
> network connection. I still need to add GPIOs so
> disk drive might not work. Thanks Ray for the GPL,
> found the GPIOs in there.

Here are the results:

 99 % [....................................]
[Type Ctrl-\ + c to quit]


U-Boot 2016.05-tld-2.1 (Aug 18 2016 - 01:44:47 -0700)
Cisco ON100_K9

SoC:   Kirkwood 88F6282_A1
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  512 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   egiga0, egiga1
Error: egiga1 address not set.

MV88E1310 PHY initialized on egiga0
Hit any key to stop autoboot:  0 
ON100_K9> ping 192.168.11.1
*** ERROR: `ipaddr' not set
ping failed; host 192.168.11.1 is not alive
ON100_K9> setenv ipaddr 192.168.11.100
ON100_K9> ping 192.168.11.1           
Using egiga0 device

ARP Retry count exceeded; starting again
ping failed; host 192.168.11.1 is not alive
ON100_K9>

I did notice that this has egiga0 and egaga1 switched from what stock U-Boot identifies. Your U-Boot identifies the MON port as egiga0 device while stock identifies the LAN port as egiga0. Good news is that there are no issues with kwbooting.

Ray
Re: Debian on CISCO ON100-K9
August 19, 2016 01:38AM
rayknight,

> U-Boot 2016.05-tld-2.1 (Aug 18 2016 - 01:44:47
> -0700)
> Cisco ON100_K9
>
> SoC: Kirkwood 88F6282_A1
> DRAM: 512 MiB
> WARNING: Caches not enabled
> NAND: 512 MiB
> *** Warning - bad CRC, using default environment
>
> In: serial
> Out: serial
> Err: serial
> Net: egiga0, egiga1
> Error: egiga1 address not set.
>
> MV88E1310 PHY initialized on egiga0
> Hit any key to stop autoboot: 0

> Good news is that there are no issues with
> kwbooting.

Cool! thanks Ray. That means the board file is working.

And that switched egiga0/1 sounds interesting, how did you determine this?:

Quote

> I did notice that this has egiga0 and egaga1
> switched from what stock U-Boot identifies. Your
> U-Boot identifies the MON port as egiga0 device
> while stock identifies the LAN port as egiga0.

Looks like I did not complete the ethernet activation for both ports. So a new version is coming!

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



Edited 1 time(s). Last edit at 08/19/2016 01:39AM by bodhi.
Re: Debian on CISCO ON100-K9
August 19, 2016 10:10PM
And how did you determine this? LEDs?

>
>
Quote

> I did notice that this has egiga0 and
> egaga1
> > switched from what stock U-Boot identifies.
> Your
> > U-Boot identifies the MON port as egiga0 device
> > while stock identifies the LAN port as
> egiga0.

Remmember I dont have the box, you need to describe what you saw as much as you can. Ie, did the MON Ethernet LED blink?

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



Edited 1 time(s). Last edit at 08/20/2016 02:13AM by bodhi.
Re: Debian on CISCO ON100-K9
August 20, 2016 02:55AM
This version has 2 new things added:

1. Activate egiga0 and egiga1
2. Turn on GPIOs (I am not really sure which one is which yet). Stock u-boot is a real pain to read :)

Please try kwboot like before. This time try both egiga 0 and 1, and then do some USB or SD initialization

ping <router ip>
usb start
mmc rescan

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Attachments:
open | download - uboot.2016.05-tld-2.2.on100_k9.mtd0.kwb (512 KB)
Re: Debian on CISCO ON100-K9
August 20, 2016 05:30PM
bodhi Wrote:
-------------------------------------------------------
> This version has 2 new things added:
>
> 1. Activate egiga0 and egiga1
> 2. Turn on GPIOs (I am not really sure which one
> is which yet). Stock u-boot is a real pain to read
> :)
>
> Please try kwboot like before. This time try both
> egiga 0 and 1, and then do some USB or SD
> initialization
>
>
> ping <router ip>
> usb start
> mmc rescan
>

First below is stock U-Boot with Ethernet attached only to LAN port an 8GB USB stick and a 4GB SD card. Link lite for LAN port is green as well as Power lite. Status lites 1 and 2 are orange. All other lites are off.

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_ 
| | | |___|  _ \ / _ \ / _ \| __| 
| |_| |___| |_) | (_) | (_) | |_ 
 \___/    |____/ \___/ \___/ \__| 
 ** MARVELL BOARD: DB-88F6282A-BP LE 

U-Boot 1.1.4 (Feb 22 2011 - 14:06:09) Marvell version: 3.5.9 - Cisco Plasma

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006D2340

Soc: 88F6282 A1CPU running @ 1600Mhz L2 running @ 533Mhz
SysClock = 400Mhz , TClock = 200Mhz 

DRAM (DDR3) CAS Latency = 6 tRP = 6 tRAS = 15 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB 
DRAM CS[1] base 0x10000000   size 256MB 
DRAM Total size 512MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled 
Write allocate disabled

Module 0 is RGMII

USB 0: host mode
PEX 0: interface detected no Link.
PEX 1: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0 
Plasma>> ping 192.168.11.1
Using egiga0 device
host 192.168.11.1 is alive
Plasma>> usb start 
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
1 Storage Device(s) found
Plasma>> mmc rescan
Usage:
mmcinit - init mmc card

Plasma>> mmcinit
SDHC found. Card desciption is:
Manufacturer:       0x27, OEM "PH"
Product name:       "SD04G", revision 2.0
Serial number:      2084250414
Manufacturing date: 10/2010
Capacity :          3796 MB
Total blocks:       7774208 ( 512 bytes per block)
CRC:                0x00, b0 = 0
Plasma>>

Now same setup but using kwboot with your latest uboot file. This time Link and Act lites are on for the MON port and Act is on for the LAN port. Other lites are the same as with stock U-Boot.

[Type Ctrl-\ + c to quit]


U-Boot 2016.05-tld-2.2 (Aug 20 2016 - 00:24:37 -0700)
Cisco ON100_K9

SoC:   Kirkwood 88F6282_A1
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  512 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   egiga0, egiga1
Error: egiga1 address not set.

MV88E1310 PHY initialized on egiga0
PHY reset timed out
MV88E1310 PHY initialized on egiga1
Hit any key to stop autoboot:  0 
ON100_K9> ping 192.168.11.1
No link on egiga0
*** ERROR: `ipaddr' not set
ping failed; host 192.168.11.1 is not alive
ON100_K9> usb start
starting 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
ON100_K9> mmc rescan
Unknown command 'mmc' - try 'help'
ON100_K9> help mmc
Unknown command 'mmc' - try 'help' without arguments for list of all known commands
ON100_K9> setenv ipaddr 192.168.11.100
ON100_K9> ping 192.168.11.1
*** ERROR: `eth1addr' not set
ping failed; host 192.168.11.1 is not alive
ON100_K9> setenv eth1addr 64:00:F1:20:DF:66
ON100_K9> ping 192.168.11.1
Using egiga1 device

ARP Retry count exceeded; starting again
ping failed; host 192.168.11.1 is not alive
ON100_K9>

You can see that after i set ipaddr and eth1addr it uses egiga1 device for ping. For first ping it responded:
No link on egiga0
But after setting eth1addr it responds with:
Using egiga1 device
This leads me to suspect it detects the link on LAN as the egiga1 device instead of egiga0 on stock U-Boot.

Also it appears the mmc command is not enabled in this U-Boot.

Ray
Re: Debian on CISCO ON100-K9
August 20, 2016 06:09PM
Thanks Ray!

1. USB works. Cool.

2. MMC is missing. This is true. I forgot to port this code.

3. Ethernet

Now same setup but using kwboot with your latest uboot file. This time Link and Act lites are on for the MON port and Act is on for the LAN port. Other lites are the same as with stock U-Boot.

After this

ON100_K9> setenv eth1addr 64:00:F1:20:DF:66
ON100_K9> ping 192.168.11.1
Using egiga1 device

Link and Act LEDs are on for both ports?

I'm doing the basic to start Ethernet, but it might be the case that we need more seeing this:
PHY reset timed out

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



Edited 1 time(s). Last edit at 08/20/2016 06:37PM by bodhi.
Re: Debian on CISCO ON100-K9
August 20, 2016 06:37PM
bodhi Wrote:
-------------------------------------------------------
> Thanks Ray!
>
> 1. USB works. Cool.
>
> 2. MMC is missing. This is true. I forgot to port
> this code.
>
> 3. Ethernet
>
>
> Now same setup but using kwboot with your latest
> uboot file. This time Link and Act lites are on
> for the MON port and Act is on for the LAN port.
> Other lites are the same as with stock U-Boot.
>
>
> After this
>
>
> ON100_K9> setenv eth1addr 64:00:F1:20:DF:66
> ON100_K9> ping 192.168.11.1
> Using egiga1 device
>
>
> Link and Act LEDs are on for both ports?
>
> I'm doing the basic to start Ethernet, but it
> might be the case that we need more.

No the Link lite is off for the LAN ports and other lites are on even though there is no Ethernet in the MON port. I believe the lites are opposite of what they should be with your U-Boot. I have Ethernet plugged into LAN port, but Link lite is off with your U-Boot. Link lite is on with stock U-Boot.

Ray
Re: Debian on CISCO ON100-K9
August 20, 2016 10:51PM
Playing around with this again trying to boot a Linux kernel with a hacked dtb file appended. Get the following output:

Uncompressing Linux... done, booting the kernel.

Error: unrecognized/unsupported machine ID (r1 = 0x0000020f).

Available machine support:

ID (hex) NAME
ffffffff Generic DT based system
ffffffff Marvell Kirkwood (Flattened Device Tree)

Can someone clue me in to what role the machine ID plays when attempting to boot with an appended Flattened Device Tree? Do I need to set some environment variable before attempting to boot?

Ray
Re: Debian on CISCO ON100-K9
August 21, 2016 02:13AM
rayknight Wrote:
-------------------------------------------------------
> Playing around with this again trying to boot a
> Linux kernel with a hacked dtb file appended.
> Get the following output:
>
> Uncompressing Linux... done, booting the kernel.
>
> Error: unrecognized/unsupported machine ID (r1 =
> 0x0000020f).
>
> Available machine support:
>
> ID (hex) NAME
> ffffffff Generic DT based system
> ffffffff Marvell Kirkwood (Flattened Device Tree)
>
> Can someone clue me in to what role the machine ID
> plays when attempting to boot with an appended
> Flattened Device Tree? Do I need to set some
> environment variable before attempting to boot?
>
> Ray

Ray,

This error happens when you forgot to append the DTB to the uImage when booting, and the kernel expects to find it but could not.

But error like this is best to see with the full serial boot log. It's depending on what you did before booting the kernel, regarding envs settings + bootargs + u-boot version + kernel version.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Debian on CISCO ON100-K9
August 23, 2016 11:53PM
I have no idea if it worked. I got into Debian Pogoplug both with SSH and RDP. Plugged in the TTY thing (which leads to the ON100 pins) and while terminal command didn't work so well, I right-clicked on the folder containing kwboot and uboot.2016.05-tld-2.2.on100_k9.mtd0.kwb. Something about terminal and I entered:

root@debian:/usr/local/bin# ./kwboot  -t -B 115200 /dev/ttyUSB0 -b uboot.2016.05-tld-2.2.on100_k9.mtd0.kwb  -p

It said something like "trying to send boot stuff, reboot target" so I turned ON100 off and on and watched the lights sequence. Now after a while it's far left green steady. two reds blink together and the greens over to the right" left green steady and right green blinking.

Now sure about pinging, but from Win7 I pinged the on100's IP and got
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

>ping 192.168.178.110

Pinging 192.168.178.110 with 32 bytes of data:
Reply from 192.168.178.110: bytes=32 time<1ms TTL=64
Reply from 192.168.178.110: bytes=32 time<1ms TTL=64
Reply from 192.168.178.110: bytes=32 time<1ms TTL=64
Reply from 192.168.178.110: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.178.110:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

7x64>

So I don't know if that's useful to anyone, but seems the the pings wouldn't reply before this.
Off to bed and a big day tomorrow, but I'll stop by later on if you have any ideas or whatever.

* Pretty sure I can't serial into ON100 from Windows anymore.

** I've learned a valuable lesson, that it's a lot better to use an ARM_Linux box with built in video instead of this chain of Windows >SSH/RDP> PogoplugDebian > USB-TTY thing > pins on ON100. Gets confusing real easy.

*** Hey was I supposed to have a USB stick plugged in or something? I dunno.

=========
-= Cloud 9 =-



Edited 3 time(s). Last edit at 08/24/2016 01:17AM by JoeyPogoPlugE02.
Re: Debian on CISCO ON100-K9
August 25, 2016 02:41AM
Please try this new version.

- mmc should work.
- LEDs light should looks OK.
- Ethernet should have both ports. I've not looked into this further other than making sure both are initialized with a sane default ether addr.

Let me know what happened when you ping the router using each ethaddr.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Attachments:
open | download - uboot.2016.05-tld-2.3.on100_k9.mtd0.kwb (512 KB)
Re: Debian on CISCO ON100-K9
August 25, 2016 09:53AM
...grumble...grumble.... i wanna play... cant find a cheap one this side of the pond.......grumble...grumble....
Re: Debian on CISCO ON100-K9
August 25, 2016 11:22AM
This looks pretty cool. Faster than E02 and twice the RAM! But there doesn't seem to be any available at the moment for less than $25 shipped.
Re: Debian on CISCO ON100-K9
August 25, 2016 03:09PM
nwestfal Wrote:
-------------------------------------------------------
> This looks pretty cool. Faster than E02 and twice
> the RAM! But there doesn't seem to be any
> available at the moment for less than $25 shipped.

You might try messaging the seller that they are unlikely to sell something no longer supported by the vendor that needs to download software from a vendor site that no longer exists. The units being sold are just poor doorstops unless we can get Debian running on them.

Ray
Re: Debian on CISCO ON100-K9
August 25, 2016 03:33PM
> The units
> being sold are just poor doorstops unless we can
> get Debian running on them.

We should be able to. With this stock u-boot source, it is a slow process, but it is all we got to start from.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Debian on CISCO ON100-K9
August 25, 2016 04:05PM
rayknight Wrote:
-------------------------------------------------------
> nwestfal Wrote:
> --------------------------------------------------
> -----
> > This looks pretty cool. Faster than E02 and
> twice
> > the RAM! But there doesn't seem to be any
> > available at the moment for less than $25
> shipped.
>
> You might try messaging the seller that they are
> unlikely to sell something no longer supported by
> the vendor that needs to download software from a
> vendor site that no longer exists. The units
> being sold are just poor doorstops unless we can
> get Debian running on them.
>
> Ray


Most sellers have no idea of what they are selling. There is a %&$$%£ from Austria that has these boxes on ebay for like 90 euros. Contacted the seller linking also Cisco's EOL site, got generic dumb answer from a random secretary that they are already discounting the item (by like 5%).

I'm not happy, same side of the pond of Gravelrash.
Re: Debian on CISCO ON100-K9
August 25, 2016 04:30PM
root@debian:/usr/local/bin# ./kwboot  -t -B 115200 /dev/ttyUSB0 -b uboot.2016.05-tld-2.3.on100_k9.mtd0.kwb  -p
Sending boot message. Please reboot the target...|

Lucky to get that far! Then after nothing did anything I unplugged the ON100 and didn't notice any real sequence. The lights, all steady on are the far left green, twin greens midway and far right green. Anything I should try from here?

2nd try, I turned the switch to ON100 of and on, and it looks like a "normal" boot sequence, settling on left green on, both reds blinking and the middle greens: left on - right alternating. Far right green off.

My gut tells me it took, but what now then?

3rd try: I plugged in the Debian E02 backup stick, and made ON100 boot. For a while it looked like they were talking something meaningful.
I know it's a totally not smart but i don't know what to try otherwise.

4th try: I might have a loose pin @#^!!! So here's there serial how it boots now, from where Serial (this time puTTY from Win7) captured it:


### JFFS2 loading 'boot.img' to 0x400000
Scanning JFFS2 FS: . done.
### JFFS2 load complete: 382 bytes loaded to 0x400000
## Executing script at 00400000
"PLASMA Booting FIRST partition @ 0x400000"

NAND read: device 0 offset 0x400000, size 0x600000

Reading data from 0x9ff800 -- 100% complete.
 6291456 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.31.8PATCH-29
   Created:      2011-06-01  21:56:16 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2323016 Bytes =  2.2 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux..................................................................................................................................................... done, booting the kernel.
Linux version 2.6.31.8PATCH-29 (jamwyatt@aesop) (gcc version 4.3.2 (sdk3.2rc1-ct-ng-1.4.1) ) #1 Wed Jun 1 16:56:06 CDT 2011
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Feroceon-KW
Using UBoot passing parameters structure
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 130048
Kernel command line: console=ttyS0,115200 max_loop=64 mtdparts=nand_mtd:2m(uBoot)ro,2m(dualboot),6m(kernel1),8m(rootfs1),6m(kernel2),8m(rootfs2),470m(datafs),-(misc) root=/dev/mtdblock3 ro serialNo=DNI15440BHM hwVer=ON100-K9_V01 ip=::::DB88FXX81:eth0:none rootfstype=jffs2
PID hash table entries: 2048 (order: 11, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 256MB 256MB = 512MB total
Memory: 510592KB available (4348K code, 315K data, 124K init, 0K highmem)
Hierarchical RCU implementation.
NR_IRQS:128
Console: colour dummy device 80x30
Calibrating delay loop... 1599.07 BogoMIPS (lpj=7995392)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Feroceon L2: Enabling L2
Feroceon L2: Cache support initialised.

CPU Interface
-------------
SDRAM_CS0 ....base 00000000, size 256MB
SDRAM_CS1 ....base 10000000, size 256MB
SDRAM_CS2 ....disable
SDRAM_CS3 ....disable
PEX0_MEM ....base e0000000, size 128MB
PEX0_IO ....base f2000000, size   1MB
PEX1_MEM ....base e8000000, size 128MB
PEX1_IO ....base f2100000, size   1MB
INTER_REGS ....base f1000000, size   1MB
NFLASH_CS ....base fa000000, size   2MB
SPI_CS ....base f4000000, size  16MB
BOOT_ROM_CS ....no such
DEV_BOOTCS ....no such
CRYPT_ENG ....base f0000000, size   2MB

  Marvell Development Board (LSP Version KW_LSP_5.1.3_patch29)-- DB-88F6282A-BP  Soc: 88F6282 A1 LE

 Detected Tclk 200000000 and SysClk 400000000
MV Buttons Device Load
btns_init_data - plasma
btns_init_data - Number of configured buttons: 1
Marvell USB EHCI Host controller #0: d0054740
PEX0 interface detected no Link.
PEX1 interface detected no Link.
PCI: bus0: Fast back to back transfers enabled
PCI: bus1: Fast back to back transfers enabled
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
TCP established hash table entries: 65536 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 65536 bind 65536)
TCP reno registered
NET: Registered protocol family 1
rtc mv_rtc: rtc core: registered kw-rtc as rtc0
RTC registered
cpufreq: Init kirkwood cpufreq driver
Kirkwood hwmon thermal sensor initialized.
XOR registered 4 channels
XOR 2nd invalidate WA enabled
cesadev_init(c000c990)
mvCesaInit: sessions=640, queue=64, pSram=f0000000
Warning: TS unit is powered off.
MV Buttons Driver Load
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
msgmni has been set to 997
alg: No test for cipher_null (cipher_null-generic)
alg: No test for ecb(cipher_null) (ecb-cipher_null)
alg: No test for digest_null (digest_null-generic)
alg: No test for compress_null (compress_null-generic)
alg: No test for stdrng (krng)
alg: No test for hmac(digest_null) (hmac(digest_null-generic))
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler anticipatory registered (default)
Initializing ths8200_init
Initializing dove_adi9889_init
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
loop: module loaded
Integrated Sata device found
IRQ 21/mvSata: IRQF_DISABLED is not guaranteed on shared IRQs
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
Loading Marvell Ethernet Driver:
  o Cached descriptors in DRAM
  o DRAM SW cache-coherency
  o 2 Giga ports supported
  o Single RX Queue support - ETH_DEF_RXQ=0
  o Single TX Queue support - ETH_DEF_TXQ=0
  o TCP segmentation offload (TSO) supported
  o Large Receive offload (LRO) supported
  o Receive checksum offload supported
  o Transmit checksum offload supported
  o Network Fast Processing (Routing) supported - (Disabled)
  o Driver ERROR statistics enabled
  o Proc tool API enabled
  o SKB Reuse supported - (Disabled)
  o SKB Recycle supported - (Disabled)
  o Rx descripors: q0=128
  o Tx descripors: q0=532
  o Loading network interface(s):
     o register under mv88fx_eth platform
     o eth0, ifindex = 2, GbE port = 0
     o eth1, ifindex = 3, GbE port = 1

mvFpRuleDb (d07f0000): 16384 entries, 65536 bytes
Counter=0, opIdx=6, overhead=16
Counter=1, opIdx=2, overhead=0
Counter=2, opIdx=1, overhead=18
Counter=3, opIdx=2, overhead=0
Intel(R) PRO/1000 Network Driver - version 7.3.21-k3-NAPI
Copyright (c) 1999-2006 Intel Corporation.
e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
e1000e: Copyright (c) 1999-2008 Intel Corporation.
e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver net1080
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver zaurus
NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 1471 at 0x00000b7e0000
Bad eraseblock 1911 at 0x00000eee0000
Bad eraseblock 2539 at 0x000013d60000
Bad eraseblock 2854 at 0x0000164c0000
Bad eraseblock 3405 at 0x00001a9a0000
8 cmdlinepart partitions found on MTD device nand_mtd
Using command line partition definition
Creating 8 MTD partitions on "nand_mtd":
0x000000000000-0x000000200000 : "uBoot"
0x000000200000-0x000000400000 : "dualboot"
0x000000400000-0x000000a00000 : "kernel1"
0x000000a00000-0x000001200000 : "rootfs1"
0x000001200000-0x000001800000 : "kernel2"
0x000001800000-0x000002000000 : "rootfs2"
0x000002000000-0x00001f600000 : "datafs"
0x00001f600000-0x000020000000 : "misc"
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
uhci_hcd: USB Universal Host Controller Interface driver
usbcore: registered new interface driver usblp
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
usbcore: registered new interface driver ums-usbat
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
Orion Watchdog Timer: Initial timeout 21 sec
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
Registered led device: plasma:green:s1
Registered led device: plasma:red:s1
Registered led device: plasma:green:s2
Registered led device: plasma:red:s2
GRE over IPv4 tunneling driver
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
rtc mv_rtc: setting system clock to 2016-08-26 06:16:39 UTC (1472192199)
CLEANMARKER node found at 0x00000000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x00020000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x00040000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x00060000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x00080000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x000a0000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x000c0000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x000e0000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x00100000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x00120000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x00140000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x00160000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x00180000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x001a0000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x001c0000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x001e0000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x00200000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x00220000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x00240000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x00260000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x00280000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x002a0000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x002c0000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x002e0000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x00300000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x00320000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x00340000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x00360000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x00380000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x003a0000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x003c0000 has totlen 0xc != normal 0x0
CLEANMARKER node found at 0x003e0000 has totlen 0xc != normal 0x0
VFS: Mounted root (jffs2 filesystem) readonly on device 31:3.
Freeing init memory: 124K
Creating R/W root
Start up on R/W root
Root Filesystem Version: 18.45

        Set LED STATE to: init_state


Linux ON100_6400F120FFB6 2.6.31.8PATCH-29 #1 Wed Jun 1 16:56:06 CDT 2011
eth0: link down
eth0: started
eth0: link up, full duplex, speed 1 Gbps
eth1: started
initFinish.sh: Starting HTTPD - Status info now available
UBI: attaching mtd6 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd6 to ubi0
UBI: MTD device name:            "datafs"
UBI: MTD device size:            470 MiB
UBI: number of good PEBs:        3755
UBI: number of bad PEBs:         5
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 3755
UBI: number of PEBs reserved for bad PEB handling: 37
UBI: max/mean erase counter: 37/35
UBI: image sequence number: 2124868612
UBI: background thread "ubi_bgt0d" started, PID 749
UBI device number 0, total 3755 LEBs (484485120 bytes, 462.0 MiB), available 0 LEBs (0 bytes), LEB size 129024 bytes (126.0 KiB)
initFinish.sh: ubiattach was successful to ubi0
initFinish.sh: mknod was successful for /dev/ubi0
initFinish.sh: Starting mount of internal flash .... ubi0 onto /mnt/INTFLASH
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "datafs"
UBIFS: file system size:   477388800 bytes (466200 KiB, 455 MiB, 3700 LEBs)
UBIFS: journal size:       23869440 bytes (23310 KiB, 22 MiB, 185 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  4952683 bytes (4836 KiB)
initFinish.sh: .... successfully completed mount

        Set LED STATE to: netconf_active


killall: udhcpc: no process killed
info, udhcpc (v0.9.9-pre) started
debug, Sending discover...
debug, Sending select for 192.168.178.110...
info, Lease of 192.168.178.110 obtained, lease time 86400
udhcpc.sh: update default gw
udhcpc.sh: deleting routes
udhcpc.sh: Router is 192.168.178.1 eth0
udhcpc.sh: skip update dns

        Set LED STATE to: net_complete


initFinish.sh: Attempting to mount /dev/sda1 flash device
mount: Mounting /dev/sda1 on /mnt/EXTFLASH failed: No such device or address
mount: Mounting /dev/sda1 on /mnt/EXTFLASH failed: No such device or address
net.ipv4.neigh.eth0.gc_stale_time = 360
net.ipv4.neigh.default.gc_stale_time = 360
net.ipv4.conf.all.arp_filter = 1
vm.swappiness = 0
initFinish.sh: No CRAMFS file, we have run out of options .... failsafe time

        Set LED STATE to: netconf_active


info, udhcpc (v0.9.9-pre) started
debug, Sending discover...
debug, Sending select for 192.168.178.110...
info, Lease of 192.168.178.110 obtained, lease time 86400
udhcpc.sh: update default gw
udhcpc.sh: deleting routes
udhcpc.sh: Router is 192.168.178.1 eth0
udhcpc.sh: skip update dns

        Set LED STATE to: net_complete



        Set LED STATE to: failsafe


ap_failSafeUpdate: Beginning fail safe recovery
ap_failSafeUpdate: Cleaning up left-over rogue processes ... should already have stopped
UBIFS: un-mount UBI device 0, volume 0
ap_failSafeUpdate: Beginning reformat of internal flash ....
ubi0
Volumes count:                           1
Logical eraseblockUBI: mtd6 is detached from ubi0
 size:                 129024 bytes, 126.0 KiB
Total amount of logical eraseblocks:     3755 (484485120 bytes, 462.0 MiB)
Amount of available logical eraseblocks: 0 (0 bytes)
Maximum count of volumes                 128
Count of bad physical eraseblocks:       5
Count of reserved physical eraseblocks:  37
Current maximum erase counter value:     37
Minimum input/output unit size:          2048 bytes
Character device major/minor:            252:0
Present volumes:                         0
ap_formatInternalFlash-ON100: Detached the UBI volume from mtd6
ubiformat: mtd6 (nand), size 492830720 bytes (470.0 MiB), 3760 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 3759 -- 100 % complete
ubiformat: 3755 eraseblocks have valid erase counter, mean value is 35
ubiformat: 5 bad eraseblocks found, numbers: 1215, 1655, 2283, 2598, 3149
ubiformat: formatting eraseblock 3748 UBI: attaching mtd6 to ubi0
-- 99 % completeUBI: physical eraseblock size:   131072 bytes (128 KiB)
ubiformat: foUBI: logical eraseblock size:    129024 bytes
rmatting eraseblUBI: smallest flash I/O unit:    2048
ock 3749 -- 99 %UBI: sub-page size:              512
ubifUBI: VID header offset:          512 (aligned 512)
ormat: formattinUBI: data offset:                2048
ubiformat: formatting eraseblock 3759 -- 100 % complete
ap_formatInternalFlash-ON100: UBI Format completed
UBI: attached mtd6 to ubi0
UBI: MTD device name:            "datafs"
UBI: MTD device size:            470 MiB
UBI: number of good PEBs:        3755
UBI: number of bad PEBs:         5
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     0
UBI: available PEBs:             3714
UBI: total number of reserved PEBs: 41
UBI: number of PEBs reserved for bad PEB handling: 37
UBI: max/mean erase counter: 38/36
UBI: image sequence number: 1208912032
UBI: background thread "ubi_bgt0d" started, PID 1271
UBI device number 0, total 3755 LEBs (484485120 bytes, 462.0 MiB), available 3714 LEBs (479195136 bytes, 457.0 MiB), LEB size 129024 bytes (126.0 KiB)
ap_formatInternalFlash-ON100: ubiattach was successful to ubi0
ap_formatInternalFlash-ON100: mknod was successful for /dev/ubi0
Set volume size to 479195136
Volume ID 0, size 3714 LEBs (479195136 bytes, 457.0 MiB), LEB size 129024 bytes (126.0 KiB), dynamic, name "datafs", alignment 1
ap_formatInternalFlash-ON100: ubimkvol was successful for /dev/ubi0
UBIFS: default file-system created
UBIFS: mounted UBI device 0, volume 0, name "datafs"
UBIFS: file system size:   477388800 bytes (466200 KiB, 455 MiB, 3700 LEBs)
UBIFS: journal size:       23869440 bytes (23310 KiB, 22 MiB, 185 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  4952683 bytes (4836 KiB)
ap_failSafeUpdate: .... Format Completed
ap_failSafeUpdate: Attempt #1 to retrieve http://failsafe.imageboot.com/failsafe/failsafe.html?model=ON100&mac=64:00:F1:20:FF:B6&serial=DNI15440BHM&pid=ON100-K9&vid=01
ap_failSafeUpdate: Bundle download was successful - in terms of a successful transfer ...
ap_failSafeUpdate: Downloaded the bundle fine, but the tar file is corrupt
ap_failSafeUpdate: Failed attempt 1 to download the recovery file!

That's what I got!

No there's more: I got one more Serial boot, maybe this will help someone:


         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: DB-88F6282A-BP LE

U-Boot 1.1.4 (Feb 22 2011 - 14:06:09) Marvell version: 3.5.9 - Cisco Plasma

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006D2340

Soc: 88F6282 A1CPU running @ 1600Mhz L2 running @ 533Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM (DDR3) CAS Latency = 6 tRP = 6 tRAS = 15 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled

Module 0 is RGMII

USB 0: host mode
PEX 0: interface detected no Link.
PEX 1: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0

Right now it's where I've stopped autoboot, so let me know if I should enter stuff in there. This from Win7/Putty

=========
-= Cloud 9 =-



Edited 5 time(s). Last edit at 08/25/2016 05:01PM by JoeyPogoPlugE02.
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: