Debian on CISCO ON100-K9
Posted by rayknight
|
Re: Debian on CISCO ON100-K9 August 02, 2016 02:46PM |
Admin Registered: 13 years ago Posts: 18,580 |
> I wonder if that will only work temporarily as it
> should be using your own authentication for that
> link.
I think boba is right, I got 403 error trying today.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> should be using your own authentication for that
> link.
I think boba is right, I got 403 error trying today.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on CISCO ON100-K9 August 02, 2016 10:49PM |
Admin Registered: 13 years ago Posts: 18,580 |
rayknight Wrote:
-------------------------------------------------------
> bodhi Wrote:
> --------------------------------------------------
> -----
> > Anybody who has connected serial console,
> please
> > post pintouts.
>
>
> On 1 of my units the Serial Port closest to the
> board edge with Ground on the left has a 4 pin
> connector soldered (but I suspect a bad solder
> joint) as it shows garbage characters when
> booting. The 4 pins on the other side work fine.
> On the second unit it doesn't seem to matter
> which port I use as both work equally well.
>
>
> Ray
Hi Ray,
Could you double check the pins? I did not have any luck using either JP1 port, outside or inside.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> bodhi Wrote:
> --------------------------------------------------
> -----
> > Anybody who has connected serial console,
> please
> > post pintouts.
>
> J4 J6 3.3V | RXD | TXD | > GND > JTAG X|X|X|X|X|X|X|X|X|X| JP1 > X|X|X|X|X|X|X|X|X|X| GND | TXD | RXD | > 3.3V > ______________________________________________ > Front Edge Of Cisco ON100-K9 Board > >>
>
> On 1 of my units the Serial Port closest to the
> board edge with Ground on the left has a 4 pin
> connector soldered (but I suspect a bad solder
> joint) as it shows garbage characters when
> booting. The 4 pins on the other side work fine.
> On the second unit it doesn't seem to matter
> which port I use as both work equally well.
>
>
> Ray
Hi Ray,
Could you double check the pins? I did not have any luck using either JP1 port, outside or inside.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on CISCO ON100-K9 August 03, 2016 05:22AM |
Registered: 9 years ago Posts: 1,037 |
@bodhi - you are experiencing the same issues that i had. only thing i didnt try was connecting the device to a network.
From reading the thread again, it seems that the device "wants" to be connect to a network before it will boot.
i imagine that looping a cable between the ethernet ports could be sufficient to accomplish this.
From reading the thread again, it seems that the device "wants" to be connect to a network before it will boot.
i imagine that looping a cable between the ethernet ports could be sufficient to accomplish this.
|
Re: Debian on CISCO ON100-K9 August 03, 2016 12:52PM |
Admin Registered: 13 years ago Posts: 18,580 |
Gravelrash Wrote:
-------------------------------------------------------
> @bodhi - you are experiencing the same issues that
> i had. only thing i didnt try was connecting the
> device to a network.
>
> From reading the thread again, it seems that the
> device "wants" to be connect to a network before
> it will boot.
>
> i imagine that looping a cable between the
> ethernet ports could be sufficient to accomplish
> this.
Thanks Gravelrash! it might be the cause. Although, I can't believe (as in shaking head) Cisco would mod u-boot to do this right of the starting point :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> @bodhi - you are experiencing the same issues that
> i had. only thing i didnt try was connecting the
> device to a network.
>
> From reading the thread again, it seems that the
> device "wants" to be connect to a network before
> it will boot.
>
> i imagine that looping a cable between the
> ethernet ports could be sufficient to accomplish
> this.
Thanks Gravelrash! it might be the cause. Although, I can't believe (as in shaking head) Cisco would mod u-boot to do this right of the starting point :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on CISCO ON100-K9 August 10, 2016 03:47AM |
Admin Registered: 13 years ago Posts: 18,580 |
All,
What is the behavior of the LEDs when you turn on the box? mine (the whole row) flashing. And I got no output from either serial header.
I'm using 3 jumper wires and plugging the male ends into the holes (there is no solder button, just header holes on the board). I'm looping the ethernet cable from one port to the other as Gravelrash suggested.
And I could not see whether the inside of these holes are conducting. Should I whip out my magnifier (mad scientist)? or if you know for a fact that they are conducting?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 08/10/2016 03:49AM by bodhi.
What is the behavior of the LEDs when you turn on the box? mine (the whole row) flashing. And I got no output from either serial header.
I'm using 3 jumper wires and plugging the male ends into the holes (there is no solder button, just header holes on the board). I'm looping the ethernet cable from one port to the other as Gravelrash suggested.
And I could not see whether the inside of these holes are conducting. Should I whip out my magnifier (mad scientist)? or if you know for a fact that they are conducting?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 08/10/2016 03:49AM by bodhi.
|
Re: Debian on CISCO ON100-K9 August 10, 2016 05:31AM |
Registered: 9 years ago Posts: 1,037 |
|
Re: Debian on CISCO ON100-K9 August 10, 2016 05:52AM |
Registered: 9 years ago Posts: 1,037 |
@bodhi - it looks like uboot has silent output..!.!.!
taken from the manual
DHCP (required for initial startup only).
At initial startup, the OnPlus Network Agent must obtain a LAN IP address using DHCP.
Once you are connected to the OnPlus Network Agent and have started the activation process, you can assign a static LAN IP address to the device if needed
http://www.cisco.com/c/dam/en/us/td/docs/net_mgmt/other_net_mgmt/onplus/network_agent/quick_start/onplus_on100_network_agent_qsg_7819952_03.pdf
LIGHT SEQUENCES ARE ON PAGE 8
Edited 1 time(s). Last edit at 08/10/2016 05:55AM by Gravelrash.
taken from the manual
DHCP (required for initial startup only).
At initial startup, the OnPlus Network Agent must obtain a LAN IP address using DHCP.
Once you are connected to the OnPlus Network Agent and have started the activation process, you can assign a static LAN IP address to the device if needed
http://www.cisco.com/c/dam/en/us/td/docs/net_mgmt/other_net_mgmt/onplus/network_agent/quick_start/onplus_on100_network_agent_qsg_7819952_03.pdf
LIGHT SEQUENCES ARE ON PAGE 8
Edited 1 time(s). Last edit at 08/10/2016 05:55AM by Gravelrash.
|
Re: Debian on CISCO ON100-K9 August 10, 2016 12:46PM |
Registered: 9 years ago Posts: 1,516 |
-4th edit-
I connected it to router with Internet unplugged, got address reservation with router's DHCP. I couldn't quite get MON to show itself but I almost swear I saw it in DHCP list and I couldn't reserve it in time. I don't know about Bonjour but neither Win7 nor OSX snow Leopard can see it on the network, so far.
The lights look healthy, they sequence through stages and ends-up left amber solid and right amber blinking. But I lack a stable way to hold the pins in place, and get pins then, and for sure know what holes, and orientation. Hindsight is 2nd nature but this ain't hindsight.
=========
-= Cloud 9 =-
Edited 4 time(s). Last edit at 08/10/2016 06:16PM by JoeyPogoPlugE02.
I connected it to router with Internet unplugged, got address reservation with router's DHCP. I couldn't quite get MON to show itself but I almost swear I saw it in DHCP list and I couldn't reserve it in time. I don't know about Bonjour but neither Win7 nor OSX snow Leopard can see it on the network, so far.
The lights look healthy, they sequence through stages and ends-up left amber solid and right amber blinking. But I lack a stable way to hold the pins in place, and get pins then, and for sure know what holes, and orientation. Hindsight is 2nd nature but this ain't hindsight.
=========
-= Cloud 9 =-
Edited 4 time(s). Last edit at 08/10/2016 06:16PM by JoeyPogoPlugE02.
|
Re: Debian on CISCO ON100-K9 August 10, 2016 06:06PM |
Registered: 9 years ago Posts: 442 |
I had both of my ON100-K9's attached via Ethernet to my router so they were picking up a DHCP address. I didn't have any problems getting output from either header, on one box the output from the header nearest the board edge was corrupt, I believe from a bad solder joint on the header pins. Have you checked to ensure you don't have RX and TX reversed?
I was also able to UART boot both boxes using kwboot.
Ray
I was also able to UART boot both boxes using kwboot.
Ray
|
Re: Debian on CISCO ON100-K9 August 10, 2016 06:58PM |
Registered: 9 years ago Posts: 1,037 |
JoeyPogoPlugE02 Wrote:
-------------------------------------------------------
> The lights look healthy, they sequence through
> stages and ends-up left amber solid and right
> amber blinking.
Swap the cables/ports around. Your pattern means : Acquiring an IP address.
If this pattern displays for more than two minutes, it indicates that the OnPlus
Network Agent has failed to obtain an IP address.
If a static IP is configured, this pattern is never displayed for more than 10 seconds.
-------------------------------------------------------
> The lights look healthy, they sequence through
> stages and ends-up left amber solid and right
> amber blinking.
Swap the cables/ports around. Your pattern means : Acquiring an IP address.
If this pattern displays for more than two minutes, it indicates that the OnPlus
Network Agent has failed to obtain an IP address.
If a static IP is configured, this pattern is never displayed for more than 10 seconds.
|
Re: Debian on CISCO ON100-K9 August 10, 2016 08:12PM |
Registered: 9 years ago Posts: 1,516 |
Thanks to Gravelrash I might have come up with a way to do the pins. Take a shirt pin, and cut it so it's about 1/4" or longer, insert into hole and use the TTY pin holding grabber on the bottom side. Gravity should pull the connection together. I beg someone though, edit that picture of the holes and make three arrows, it'd make all the difference for me. that XX-textual chart can be interpreted too many ways. Or a picture of what you've got proper. I can figure that out and try to run this now.
-update- I might "get" the pinouts after re-reading this thread. So it's probably just a matter of working proper physical pins.
Well my unit is open for the long haul and I'll be dreaming of pins and TTY apps; will proceed forward as luck will have it.
* about the lights, remember this was always connected to a DHCP-enabled router which was disconnected from Internet.
=========
-= Cloud 9 =-
Edited 2 time(s). Last edit at 08/11/2016 10:45AM by JoeyPogoPlugE02.
-update- I might "get" the pinouts after re-reading this thread. So it's probably just a matter of working proper physical pins.
Well my unit is open for the long haul and I'll be dreaming of pins and TTY apps; will proceed forward as luck will have it.
* about the lights, remember this was always connected to a DHCP-enabled router which was disconnected from Internet.
=========
-= Cloud 9 =-
Edited 2 time(s). Last edit at 08/11/2016 10:45AM by JoeyPogoPlugE02.
|
Re: Debian on CISCO ON100-K9 August 11, 2016 12:58AM |
Admin Registered: 13 years ago Posts: 18,580 |
> Have you checked to ensure you don't
> have RX and TX reversed?
:)) Funny, I've just advised other forum member about TX-RX crossing.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> have RX and TX reversed?
:)) Funny, I've just advised other forum member about TX-RX crossing.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on CISCO ON100-K9 August 11, 2016 01:01AM |
Admin Registered: 13 years ago Posts: 18,580 |
Joey,
> The lights look healthy, they sequence through
> stages and ends-up left amber solid and right
> amber blinking.
Thanks, that's what I wanted to know. Seems Gravelrash and I got bad luck.
I'll take a look again during the weekend.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> The lights look healthy, they sequence through
> stages and ends-up left amber solid and right
> amber blinking.
Thanks, that's what I wanted to know. Seems Gravelrash and I got bad luck.
I'll take a look again during the weekend.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on CISCO ON100-K9 August 11, 2016 03:58PM |
Admin Registered: 13 years ago Posts: 18,580 |
Gravelrash Wrote:
-------------------------------------------------------
> @bodhi - it looks like uboot has silent
> output..!.!.!
>
> taken from the manual
> DHCP (required for initial startup only).
> At initial startup, the OnPlus Network Agent must
> obtain a LAN IP address using DHCP.
> Once you are connected to the OnPlus Network Agent
> and have started the activation process, you can
> assign a static LAN IP address to the device if
> needed
>
> http://www.cisco.com/c/dam/en/us/td/docs/net_mgmt/
> other_net_mgmt/onplus/network_agent/quick_start/on
> plus_on100_network_agent_qsg_7819952_03.pdf
>
> LIGHT SEQUENCES ARE ON PAGE 8
Thanks Gravelrash.
I'm still not convinced. I think usually those description above is when the stock OS is running, not when u-boot started.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> @bodhi - it looks like uboot has silent
> output..!.!.!
>
> taken from the manual
> DHCP (required for initial startup only).
> At initial startup, the OnPlus Network Agent must
> obtain a LAN IP address using DHCP.
> Once you are connected to the OnPlus Network Agent
> and have started the activation process, you can
> assign a static LAN IP address to the device if
> needed
>
> http://www.cisco.com/c/dam/en/us/td/docs/net_mgmt/
> other_net_mgmt/onplus/network_agent/quick_start/on
> plus_on100_network_agent_qsg_7819952_03.pdf
>
> LIGHT SEQUENCES ARE ON PAGE 8
Thanks Gravelrash.
I'm still not convinced. I think usually those description above is when the stock OS is running, not when u-boot started.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on CISCO ON100-K9 August 11, 2016 04:14PM |
Registered: 9 years ago Posts: 442 |
You can't run the stock OS unless you pick up a used unit that was previously deployed. A new unit will attempt to download and install the stock firmware. This will fail as the URL used is no longer valid and re-directs to what most AV software thinks is a known malware distribution site. I won't have time to work on this again until the weekend, but I have been able to boot Debian. I just need to figure out a valid DTB file that will enable Ethernet.
Ray
Ray
|
Re: Debian on CISCO ON100-K9 August 11, 2016 08:35PM |
Registered: 9 years ago Posts: 1,516 |
Have you checked with Cisco to see if the download site is actually valid? I ask for two reasons.
One, Symantec is frequently criticized for false positives..
Two, it's hard to imagine Cisco not using a domain and IP that'll weather changes, particularly if it's hard coded like that.
Unimaginable if they let that slip because Cisco switches pretty much run the Internet don't they? It's been a while.
I'll get out of your hair, let you think....
=========
-= Cloud 9 =-
Edited 1 time(s). Last edit at 08/11/2016 08:57PM by JoeyPogoPlugE02.
One, Symantec is frequently criticized for false positives..
Two, it's hard to imagine Cisco not using a domain and IP that'll weather changes, particularly if it's hard coded like that.
Unimaginable if they let that slip because Cisco switches pretty much run the Internet don't they? It's been a while.
I'll get out of your hair, let you think....
=========
-= Cloud 9 =-
Edited 1 time(s). Last edit at 08/11/2016 08:57PM by JoeyPogoPlugE02.
|
Re: Debian on CISCO ON100-K9 August 11, 2016 09:06PM |
Admin Registered: 13 years ago Posts: 18,580 |
rayknight Wrote:
-------------------------------------------------------
> You can't run the stock OS unless you pick up a
> used unit that was previously deployed. A new
> unit will attempt to download and install the
> stock firmware.
I am not really interested in stock OS. U-boot only. If you know what that means?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> You can't run the stock OS unless you pick up a
> used unit that was previously deployed. A new
> unit will attempt to download and install the
> stock firmware.
I am not really interested in stock OS. U-boot only. If you know what that means?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on CISCO ON100-K9 August 12, 2016 01:43AM |
Admin Registered: 13 years ago Posts: 18,580 |
FYI, my kwboot does not even start handshaking. So I think it is a faulty serial connection in some way.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on CISCO ON100-K9 August 12, 2016 06:11AM |
Registered: 8 years ago Posts: 298 |
JoeyPogoPlugE02 Wrote:
-------------------------------------------------------
> Have you checked with Cisco to see if the download
> site is actually valid? I ask for two reasons.
> One, Symantec is frequently criticized for false
> positives..
The download site is redirected to a site that shows as malware also on Firefox and Chrome, and to redirect there someone has bought the domain to plant a redirect.
> Two, it's hard to imagine Cisco not using a domain
> and IP that'll weather changes, particularly if
> it's hard coded like that.
This device was supposed to provide a network-based service (remote management of Cisco stuff done by them directly) that ceased in 2013 I think, all infrastructure connected to that has been long since repurposed, and all devices still on sale are dead weight even if they had an OS already installed.
So yeah, it makes sense to just drop any domain connected to this device.
-------------------------------------------------------
> Have you checked with Cisco to see if the download
> site is actually valid? I ask for two reasons.
> One, Symantec is frequently criticized for false
> positives..
The download site is redirected to a site that shows as malware also on Firefox and Chrome, and to redirect there someone has bought the domain to plant a redirect.
> Two, it's hard to imagine Cisco not using a domain
> and IP that'll weather changes, particularly if
> it's hard coded like that.
This device was supposed to provide a network-based service (remote management of Cisco stuff done by them directly) that ceased in 2013 I think, all infrastructure connected to that has been long since repurposed, and all devices still on sale are dead weight even if they had an OS already installed.
So yeah, it makes sense to just drop any domain connected to this device.
|
Re: Debian on CISCO ON100-K9 August 12, 2016 11:01AM |
Registered: 9 years ago Posts: 1,516 |
-edit previous supposings-
Using solder I tacked four shirt pins in the front row and got it hooked to the TTY USB thing. I'm not able to get anything using COM1 Serial @ 9600. However it doesn't time out either. So puTTY opens with it like you're waiting for Name entry and it just sits there. This is with Ethernet plugged in but only leading to router and not Internet. I could loop it like Gravelrash said, let me know.
There's reasons to think I did a good job, including, if I unplug the USB-TTY there's a puTTY error and the lights seem healthy. Green lights to the far right flash quickly and there's the one amber on and other amber blinking, and occasionally turning red and then many moments of right amber flashing. So let me know, but I fear moving this around will break the pin tacks.
=========
-= Cloud 9 =-
Edited 2 time(s). Last edit at 08/12/2016 08:08PM by JoeyPogoPlugE02.
Using solder I tacked four shirt pins in the front row and got it hooked to the TTY USB thing. I'm not able to get anything using COM1 Serial @ 9600. However it doesn't time out either. So puTTY opens with it like you're waiting for Name entry and it just sits there. This is with Ethernet plugged in but only leading to router and not Internet. I could loop it like Gravelrash said, let me know.
There's reasons to think I did a good job, including, if I unplug the USB-TTY there's a puTTY error and the lights seem healthy. Green lights to the far right flash quickly and there's the one amber on and other amber blinking, and occasionally turning red and then many moments of right amber flashing. So let me know, but I fear moving this around will break the pin tacks.
=========
-= Cloud 9 =-
Edited 2 time(s). Last edit at 08/12/2016 08:08PM by JoeyPogoPlugE02.
|
Re: Debian on CISCO ON100-K9 August 12, 2016 10:25PM |
Registered: 9 years ago Posts: 1,516 |
Gents, I might have something with PuTTY and maybe not, check attached image. This is with connection to Internet and probably downloading malware.So I have a long page of these kind of machine ramblings right now... any ideas...
-update- cool, something....
RESET! I hit reset for over 10 seconds and got this right around that time:
Wow at least it outputted something, that's a relief. Hey I don't know the ways of this, but like the first poster, I set both my Device Manager device AND puTTY to 115200 and it seemed it got through then. Food for thought.
=========
-= Cloud 9 =-
Edited 2 time(s). Last edit at 08/12/2016 10:33PM by JoeyPogoPlugE02.
-update- cool, something....
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 39 to download the recovery file! ap_failSafeUpdate: Attempt #40 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 40 to download the recovery file! ap_failSafeUpdate: Attempt #41 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 41 to download the recovery file!
RESET! I hit reset for over 10 seconds and got this right around that time:
Button pressed : 16010 ms.####### # ### # ##### # ####### #######
# # # # # # # # # # #
# # # # # # # # # #
##### # # # # ##### # # ##### #####
# ####### # # # ####### # #
# # # # # # # # # # #
# # # ### ####### ##### # # # #######
Set LED STATE to: failsafe
Set LED STATE to: failsafe
ap_failSafeUpdate: Beginning fail safe recovery
ap_failSafeUpdate: Cleaning up left-over rogue processes ... should already have stopped
Wow at least it outputted something, that's a relief. Hey I don't know the ways of this, but like the first poster, I set both my Device Manager device AND puTTY to 115200 and it seemed it got through then. Food for thought.
=========
-= Cloud 9 =-
Edited 2 time(s). Last edit at 08/12/2016 10:33PM by JoeyPogoPlugE02.
|
Re: Debian on CISCO ON100-K9 August 12, 2016 11:03PM |
Admin Registered: 13 years ago Posts: 18,580 |
JoeyPogoPlugE02 Wrote:
-------------------------------------------------------
>
> RESET! I hit reset for over 10 seconds and got
> this right around that time:
> Wow at least it outputted something, that's a
> relief. Hey I don't know the ways of this, but
> like the first poster, I set both my Device
> Manager device AND puTTY to 115200 and it seemed
> it got through then. Food for thought.
OK so your serial console is working! cool.
Please post:
- Serial console settings (I can't tell from your post if 11520 or 9600 works).
- Serial pins out (is it same as Ray's post?). Which header, outside or inside?
- Is the ethernet cable connected? is the router connected to internet?
- Unplug the internet cable from your router, and then power up. Is serial console still working?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
>
> RESET! I hit reset for over 10 seconds and got
> this right around that time:
> Wow at least it outputted something, that's a
> relief. Hey I don't know the ways of this, but
> like the first poster, I set both my Device
> Manager device AND puTTY to 115200 and it seemed
> it got through then. Food for thought.
OK so your serial console is working! cool.
Please post:
- Serial console settings (I can't tell from your post if 11520 or 9600 works).
- Serial pins out (is it same as Ray's post?). Which header, outside or inside?
- Is the ethernet cable connected? is the router connected to internet?
- Unplug the internet cable from your router, and then power up. Is serial console still working?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on CISCO ON100-K9 August 12, 2016 11:05PM |
Registered: 9 years ago Posts: 1,516 |
Ahhh, here's another thought. The power supply turns on enough power for USB-TTY to not fail, and then turning the actual power switch brings it to a state of awareness. Sad to see this had bad blocks, but here's what I got:
=========
-= Cloud 9 =-
__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ 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
### 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-13 12:25:31 UTC (1471091131)
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: 19/16
UBI: image sequence number: 891834923
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: 19
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 16
ubiformat: 5 bad eraseblocks found, numbers: 1215, 1655, 2283, 2598, 3149
ubifUBI: attaching mtd6 to ubi0k 3749 -- 99 % complete
ormat: formattinUBI: physical eraseblock size: 131072 bytes (128 KiB)
g eraseblock 375UBI: logical eraseblock size: 129024 bytes
0 -- 99 % compleUBI: smallest flash I/O unit: 2048
ubiformat: UBI: sub-page size: 512
formatting eraseUBI: VID header offset: 512 (aligned 512)
block 3751 -- 99UBI: 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: 20/17
UBI: image sequence number: 499669150
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!
ap_failSafeUpdate: Attempt #2 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 2 to download the recovery file!
=========
-= Cloud 9 =-
|
DUUUDES August 12, 2016 11:13PM |
Registered: 9 years ago Posts: 1,516 |
Hey I might have found something. When you
1. Plug in Cisco with power switch still off
2. Tell PuTTY to open serial connection (@ 115200 for me)
3. Hit power switch on the Cisco.
4. Start hitting keys, you stop auto boot!
As an afterthought, I think Ray knew that :-)
YAY! I was helpful! And I only know three chords! Ah hahahaa!
=========
-= Cloud 9 =-
Edited 1 time(s). Last edit at 08/12/2016 11:21PM by JoeyPogoPlugE02.
1. Plug in Cisco with power switch still off
2. Tell PuTTY to open serial connection (@ 115200 for me)
3. Hit power switch on the Cisco.
4. Start hitting keys, you stop auto boot!
As an afterthought, I think Ray knew that :-)
__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ 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>> yreretureetllkrkletjkrle
Unknown command 'yreretureetllkrkletjkrle' - try 'help'
Plasma>>
YAY! I was helpful! And I only know three chords! Ah hahahaa!
=========
-= Cloud 9 =-
Edited 1 time(s). Last edit at 08/12/2016 11:21PM by JoeyPogoPlugE02.
|
Re: Debian on CISCO ON100-K9 August 12, 2016 11:35PM |
Registered: 9 years ago Posts: 1,516 |
bodhi Wrote:
-------------------------------------------------------
> OK so your serial console is working! cool.
> Please post:
- Serial console settings (I can't tell from your post if 11520 or 9600 works).
A: I've stuck with 115200 and it's worked since then
- Serial pins out (is it same as Ray's post?).
A: Yeah the row closest to the edge
- Which header, outside or inside?
A: Both, they're the same contacts. The top part of the pin had a slight blob of solder and I pressed them into place holding the solder iron over the head. One broke away a bit so I re-did that and tacked a bit of solder on the other side. Then just slip the TTY cable ends over it.
- Is the ethernet cable connected? is the router connected to internet?
A. Yes at all times it was plugged into the LAN jack and previous screenshots above are through the router and connected to internet.
- Unplug the internet cable from your router, and then power up. Is serial console still working?
A: Yes here's the results.
Now for a little sleep! Hey Bodhi sorry I initially missed your post, but am happy to reply.
=========
-= Cloud 9 =-
-------------------------------------------------------
> OK so your serial console is working! cool.
> Please post:
- Serial console settings (I can't tell from your post if 11520 or 9600 works).
A: I've stuck with 115200 and it's worked since then
- Serial pins out (is it same as Ray's post?).
A: Yeah the row closest to the edge
- Which header, outside or inside?
A: Both, they're the same contacts. The top part of the pin had a slight blob of solder and I pressed them into place holding the solder iron over the head. One broke away a bit so I re-did that and tacked a bit of solder on the other side. Then just slip the TTY cable ends over it.
- Is the ethernet cable connected? is the router connected to internet?
A. Yes at all times it was plugged into the LAN jack and previous screenshots above are through the router and connected to internet.
- Unplug the internet cable from your router, and then power up. Is serial console still working?
A: Yes here's the results.
__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ 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
### 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-13 12:49:28 UTC (1471092568)
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: 20/17
UBI: image sequence number: 499669150
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: 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: 20
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 17
ubiformat: 5 bad eraseblocks found, numbers: 1215, 1655, 2283, 2598, 3149
ubifUBI: attaching mtd6 to ubi0k 3749 -- 99 % complete
ormat: formattinUBI: physical eraseblock size: 131072 bytes (128 KiB)
g eraseblock 375UBI: logical eraseblock size: 129024 bytes
0 -- 99 % compleUBI: smallest flash I/O unit: 2048
ubiformat: UBI: sub-page size: 512
formatting eraseUBI: VID header offset: 512 (aligned 512)
block 3751 -- 99UBI: 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: 21/18
UBI: image sequence number: 1644597623
UBI: background thread "ubi_bgt0d" started, PID 1274
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
Now for a little sleep! Hey Bodhi sorry I initially missed your post, but am happy to reply.
=========
-= Cloud 9 =-
|
Re: Debian on CISCO ON100-K9 August 13, 2016 12:25AM |
Registered: 9 years ago Posts: 1,516 |
To Bodhi and anyone interested: this is the crude way I used shirt pins, solder-tacked in place from both sides and just slip the TTY-cable over the appropriate pins. Soldering on steel isn't easy (with a 22-watt solder iron!) plus a fly was messing with me trying to solder out in the shed.
=========
-= Cloud 9 =-
Edited 1 time(s). Last edit at 08/13/2016 12:48AM by JoeyPogoPlugE02.
=========
-= Cloud 9 =-
Edited 1 time(s). Last edit at 08/13/2016 12:48AM by JoeyPogoPlugE02.
|
Re: Debian on CISCO ON100-K9 August 13, 2016 01:14AM |
Registered: 9 years ago Posts: 442 |
|
Re: Debian on CISCO ON100-K9 August 13, 2016 02:10AM |
Admin Registered: 13 years ago Posts: 18,580 |
Thanks Ray for serial pins out & Joey for confirmation!
This is interesting:
This might have proven Gravelrash's theory. So stock u-boot must have tried to detect a DHCP before it would run.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 08/13/2016 02:18AM by bodhi.
This is interesting:
Quote
Joey
-4th edit-
I connected it to router with Internet unplugged, got address reservation with router's DHCP. I couldn't quite get MON to show itself but I almost swear I saw it in DHCP list and I couldn't reserve it in time. I don't know about Bonjour but neither Win7 nor OSX snow Leopard can see it on the network, so far.
The lights look healthy, they sequence through stages and ends-up left amber solid and right amber blinking. But I lack a stable way to hold the pins in place, and get pins then, and for sure know what holes, and orientation. Hindsight is 2nd nature but this ain't hindsight.
This might have proven Gravelrash's theory. So stock u-boot must have tried to detect a DHCP before it would run.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 08/13/2016 02:18AM by bodhi.
|
Re: Debian on CISCO ON100-K9 August 13, 2016 08:59AM |
Registered: 9 years ago Posts: 1,037 |
bodhi Wrote:
-------------------------------------------------------
> This might have proven Gravelrash's theory. So
> stock u-boot must have tried to detect a DHCP
> before it would run.
This doesnt surprise me - i work with CI$CO kit often and the one standard thing across all CI$Co kit is, that it there isnt one. Each device range uses differing syntax, parameter behaviour etc...
@all
Well done all thus far!
-------------------------------------------------------
> This might have proven Gravelrash's theory. So
> stock u-boot must have tried to detect a DHCP
> before it would run.
This doesnt surprise me - i work with CI$CO kit often and the one standard thing across all CI$Co kit is, that it there isnt one. Each device range uses differing syntax, parameter behaviour etc...
@all
Well done all thus far!
|
Re: Debian on CISCO ON100-K9 August 13, 2016 05:22PM |
Admin Registered: 13 years ago Posts: 18,580 |
Gravelrash,
OTOH, stock u-boot does not come in to play when we do kwboot. So the fact that I have not been able to kwboot the box must have been caused by either the serial pins out, or the u-boot image being loaded. We know the pins out is correct. So I just need to find an image that can be loaded, or do what Ray did (compile the stock GPL, which might be different from one running in the box).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
OTOH, stock u-boot does not come in to play when we do kwboot. So the fact that I have not been able to kwboot the box must have been caused by either the serial pins out, or the u-boot image being loaded. We know the pins out is correct. So I just need to find an image that can be loaded, or do what Ray did (compile the stock GPL, which might be different from one running in the box).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
