• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1]
1  Linux Stuff / Linux distributions / Re: Sheevaplug Factory Images on: August 09, 2013, 03:58:45 AM
Thanks for this. Marvell appears not to have uploaded anything onto the downloads section of this website, so it's good to see something.

Can you let me know from where this has been sourced ?

2  Linux Stuff / Linux distributions / Re: [Debian SheevaPlug] smbd panic after upgrade from Squeeze to Wheezy on: August 09, 2013, 03:55:28 AM
As I can't believe that nobody else did an upgrade Squeeze to Wheezy and obviously re missing feedback did not run into the smbd issue, may I ask you to share your upgrade procedure with us, please!?

Well, I intend to upgrade over the next few days, so will let you know how I fare with this.

Assuming I can locate a "known to work" new uBoot that seems to be required. For some reason Marvell has not published anything on the downloads area of this site.
3  Hardware and U-Boot firmware / Hardware / Re: Query regarding using USB -> Molex (modded for SheevaPlug) on: November 17, 2010, 03:27:22 AM
The header on my board looks as if it is a JST XH series type. I haven't physically tested it against a real JST XH plug. (Yet).

If I'm right, RS Components part numbers are:

Header:  543-2733 (on the board).

Plug housing: 353-1636
Terminals: 353-1591

I had to slice a "floppy disk power connector" about to remove surplus plastic before being able to fit it in. It regularly fell out, though, because there was no locking mechanism.

4  General Category / General Discussion / Re: BootROM firmware on: October 19, 2010, 02:20:50 PM
Ok, there is difference in the UART boot management (I think that I discovered a bug in my fimrware).
That maybe explains why I cannot enter in Debug/Boot mode with UART (device is stopped) on my Dockstar.


Did you get any further with this ? I, too, cannot enter UART Debug/Boot mode - but this with my SheevaPlug. 88F6281 A0. Bootrom version 1.11. I cannot see which firmware version you have.

The system just seems to stay "stopped". Anything I download, whether it be a valid bootrom/xmodem signature or just a load of nonsense, just stops the system. Nothing comes back up the line.  Sad

I have noticed that the voltage on the TX line seems to stay at its start-up value of about 3.1V and never moves on. I think I expect it to hit 3.3V when the UART switches in, and I am having a thought that perhaps the 6281 is failing to switch the pin from its start-up sampling role over to UART use. But I don't really believe it, I expect I have made a mistake somewhere.

And then I discovered your post. Perhaps there is problem with the chip after all...
5  Hardware and U-Boot firmware / Hardware / Re: My Modified SheevaPlug part II on: September 14, 2010, 06:07:38 AM
Thank you so much. The seeds of an autumn/winter project begin to germinate.

I had no idea that one could acquire pre-crimped leads. Perfect.
6  Hardware and U-Boot firmware / Hardware / Re: mini usb-Port on: September 06, 2010, 05:14:31 PM
There maybe something to be found here:


Being paranoid, I am wondering if some kind of opto-isolation would be necessary/advisable as well. I don't have the practical knowledge to know.
7  Hardware and U-Boot firmware / Hardware / Re: My Modified SheevaPlug part II on: September 06, 2010, 04:51:33 PM
I had been mulling on this today, and then discovered your post.

I have obtained the mating 4 and 6 pin connectors and some precrimped sockets

Would you be able to provide part # ?

Is there any use for a RS232 serial connection on the Sheevplug?

Not quite an answer to your question, but a direct connection to the UART might just provide an alternative way of booting the plug from scratch in the absence of OpenOCD. OpenOCD did not work properly on my Mac PPC when I last tried it, due to some unfortunate big/little endian issues in the code. So I am reluctant to proceed with OpenOCD right now. The plan would be to exploit the BootROM Firmware Boot Sequence as described in Marvell's "88F6281, 88F6192, and 88F6180 Functional Specifications" document. (But it might turn out easier to audit the OpenOCD code.  Smiley )

... J6... This is obviously designed for a TWI or I2C  bus connection...

One possibility would be to use the I2C to connect up a simple low power LED "status" display. Ideally one that could be powered off the I2C power line (3.3V might be a problem). I did notice that some pre-built modules have an I2C interface built in. There appears to be I2C support in the kernel, although for a different board. Perhaps it could be tweaked into action for the plug.

Pages: [1]