Hi,

I have just received my OpenRd Ultimate Dev Kit.

The documentation and software  have  not been upgraded.  The CD
enclosed with the kit appears to be the old original distribution
dated 4th May 2009 rev 1.0.

Therefore NONE of the documentation  matches the Ultimate version, for
example there is no mention of the PCIe connector which sticks 1" out
of the front of the chassis between the debug USB type A and the RS485
RJ45 connectors. The SD card socket being replaced by a micro SD card
socket mounted above the audio sockets.

The 12V 3A power brick supplied in the kit does not have the correct
cable end socket to mate with the chassis connector in the Ultimate.

What is the arcNumber for the Ultimate?, the supplied documentation
only knows about the base and client devices

openrd base arcNumber 2325
openrd client arcNumber 2361
openrd Ultimate arcNumber = ????

The software  and hardware are also May 4th 2009 rev 1, so there is no
layout or schematic for the ULTIMATE. Uboot and Linux kernel supplied
are both ancient.

Please could someone ask GlobalScale or Marvell or Einfochips, or
whoever is responsible for this device now to update the documentation
and the software.

Looking at the GlobalScale website, they do have the correct images
for the Ultimate, but clicking on "documentation" and "software"  on
that page directs me to the openrd.org site, which also does NOT have
the correct versions.

Please tell me I am not going to regret ordering an OpenRd Ultimate,
it appears to be an interesting device, I hope there is continuing
support for it.

regards

Patrick

Hi,

Sorry GTI should send updated documents, i have uploaded file into the
the Files directory hope it will help  -

http://groups.google.com/group/openrd/files?upload=1

I'll address the rest of the issues with GTI

Thank you,
Avi

On May 30, 9:31 am, superpat <patr...@byeslane.org.uk> wrote:

Hello,

Cheers for the new docs Avi - much appreciated!

I too have just taken delivery of an OpenRD-Ultimate dev kit, but I
received even less in that no CD or documentation of any kind was
supplied.

I can also confirm that the power supply provided didn't fit the
socket on the board - it would appear that the centre pin is too large
on the socket. I bought my unit from NewIT in the UK (http://
www.newit.co.uk/)

I had entertainment with the bootloader - I found that recent distros
needed an updated bootloader and bot the updated and supplied uBoot
images kill the ethernet ports. A very helpful chap over on the
PlugComputer forums has managed to build a uBoot image that brings the
device back to life. I had to flash it via OpenOCD (the version
supplied in the OpenRD group file list) as the USB flashing method
failed miserably and obviously TFTP was out of the question:

http://plugcomputer.org/plugforum/index.php?topic=1747.0

I have managed to build a kernel that gets most things right from the
instructions here:

http://groups.google.com/group/openrd/web/add-audio-video-support-to-...

Using the OpenRD-Client archnum again gets everything other than
ethernet working. I've had a poke around in arch/arm/mach-kirkwood/
openrd_client-setup.c and from my limited kernel fiddlings, can only
assume that the following is incorrect:

static struct mv643xx_eth_platform_data openrd_client_ge00_data = {
        .phy_addr       = MV643XX_ETH_PHY_ADDR(8),

I assume the PHY address is incorrect, however I am totally lost at
this stage :-)

I have a bit of a system limping along now having cross-compiled that
GIT kernel with the patches applied, however I'm now stuck with
regards to the ethernet issue - any help would be greatly appreciated!

Many thanks,
Harry.

Additional - the ethernet adaptors are detected and the MAC addresses
are correct, however the link is misdetected:

MV-643xx 10/100/1000 ethernet driver version
1.4
mv643xx_eth smi:
probed
net eth0: port 0 with MAC address 00:50:43:01:54:a4
eth0: link up, 10Mb/sec, half duplex, flow control disabled

This is interesting as it's connected to a gigabit full duplex
switch :-)

After the updated uBoot image, uBoot also correctly identifies the
network as gigabit and uses it quite happily to load the kernel via
TFTP.

Cheers,
Harry

OK - managed to fix Ethernet:

The PHY addresses in arch/arm/mach-kirkwood/openrd_client-setup.c need
changing - new lines are:

static struct mv643xx_eth_platform_data openrd_client_ge00_data = {
        .phy_addr       = MV643XX_ETH_PHY_ADDR(0),

static struct mv643xx_eth_platform_data openrd_client_ge01_data = {
        .phy_addr       = MV643XX_ETH_PHY_ADDR(1),

Cheers,
Harry

Any idea what the ArcNumber of the openrd ultimate is?
Reason for asking is that I do the openrd support in openembedded
(www.openembedded.org). I can try to add openrd ultimate to
openembedded (although I have no way to test it as I only own a client
board).

Best regards, Frans.

Ahh - from http://www.arm.linux.org.uk/developer/machines/download.php

2884 :-D

Cheers,
Harry

Hi,

I' am facing the same problems with the OpenRD Ultimate using the
standard delivered Client distribution.

How can this be fixed in the linux-2.6.22.18 kernel delivered with the
Client?

Regards,

Gerald.

On Jun 3, 3:04 am, cantanko <harry.shepp...@gmail.com> wrote:

Hi Gerald,

I'm sure someone will correct me if I am wrong, but I don't think you can
without compiling, hence why I ended up building a new kernel...

Cheers,
Harry.

On 4 Jun 2010 14:32, "Geraldo" <geraldsess...@eaton.com> wrote:

Hi,

I' am facing the same problems with the OpenRD Ultimate using the
standard delivered Client distribution.

How can this be fixed in the linux-2.6.22.18 kernel delivered with the
Client?

Regards,

Gerald.

On Jun 3, 3:04 am, cantanko <harry.shepp...@gmail.com> wrote:

Hi Harry,

Yes, I know.
I used the sources from the CD delivered with the OpenRD-Client.
I build the 2.6.22.18 kernel and installed it on the Ultimate.
It works except for the Ethernet ports.

According the LspReadme.txt the board specific parameters can be found
in:
2.  Marvell LSP File locations
-------------------------------
    o  KW core directory:
       - /arch/arm/mach-feroceon-kw/...
       - /include/asm-arm/arch-feroceon-kw/...

    o  KW drivers:
       - /arch/arm/plat-feroceon/...

I tried to find the location to change the eth phy address.
But I'm lost.

Could anyone help me on this or should I switch over to the newer
kernel?

Regards,

Gerald.

On Jun 4, 3:34 pm, Harry Sheppard <harry.shepp...@gmail.com> wrote:

Hi Geraldo,

I don't have the sources immediately to hand, but if you grep the
sources for MV643XX that may point you in the right direction... To be
honest I didn't even bother looking at 2.6.22.18 as it was released in
February 2008 - i.e. over two years old now. Thankfully that version
does address the splice() kernel vulnerability that was found, but I
don't know if there are any others that are unpatched...

If you can find in the sources lines similar to the ones posted above
by me for the ethernet fix, changing their address argument and
recompiling should fix it. If I have time, I'll try 2.6.22.18 and see
if I can locate the offending lines.

Cheers,
Harry

Hi Harry,

Maybe it is better to switch over.
Which kernel and u-boot sources did you use?

Regards,

Gerald.

On Jun 7, 9:56 am, Harry Sheppard <harry.shepp...@gmail.com> wrote:

Hi Gerald,

I didn't build the uBoot image myself - I decided I was too much of a
noob to try that :-) Instead, a very obliging chap over on the
PlugComputer forums built one for me - here's the link to the forum
post:

http://plugcomputer.org/plugforum/index.php?topic=1747.0

The sources were pulled from OpenRD's GIT repository and had three
patches applied, plus the fix to re-address the ethernet PHYs.

The walkthrough for building the kernel is here:

http://groups.google.com/group/openrd/web/add-audio-video-support-to-...

...and the change to the PHY addresses is in
arch/arm/mach-kirkwood/openrd_client-setup.c - the modified lines
should read:

static struct mv643xx_eth_platform_data openrd_client_ge00_data = {
       .phy_addr       = MV643XX_ETH_PHY_ADDR(0),

static struct mv643xx_eth_platform_data openrd_client_ge01_data = {
       .phy_addr       = MV643XX_ETH_PHY_ADDR(1),

I believe someone in another thread may now have applied this fix to
the GIT source tree, but I am unsure - probably worth checking it
manually.

Hope that helps :-)

Cheers,
Harry

Additional: the patches to uBoot and the kernel have been done by
someone properly - they are mentioned in this thread:

http://groups.google.com/group/openrd/browse_thread/thread/ed5af0ada2...

I haven't tried this to confirm everything works, however - I know
what I did has now been behaving for the last few days without any
problems :-)

Cheers,
Harry

Hi Avi,

Regarding your post 30th May 2010, regarding

""  I'll address the rest of the issues with GTI ""

GTI still have NOT added or updated ANY information on the Open-Rd.org site
pertaining to the Open-RD Ultimate.

I would have thought seven months would have been enough time for GTI to
post updated drawings and documents.

The CD rom shipping with the Ultimate is STILL V1.0  that does not mention
the Ultimate, (it was released by einfochips BEFORE the Ultimate was
designed!)

None of the documentation / information on this site has been updated since
the two einfochip engineers have stopped posting here.

None of the "open issues" have been looked at.

You are apparently the owner of this site.

Please could we have a statement about the way the Ultimate is to be
supported

many thanks

regards

Patrick

Hi Avi,

My retailer has just sent me a NEW  dev kit for the Ultimate.

This CD is titled "OpenRD Ultimated DEV KIT 2.0"  and does contain
Ultimate documentation

(See my separate post on this)

regards

Patrick

On Jan 5, 11:07 am, superpat <patr...@byeslane.org.uk> wrote: