Thanks for the reply.
The driver which we are using for the ethernet is provided by Xilinx.
In the Linux kernel source, it is located in net/xilinx_enet
directory. We are attaching the adapter file for the driver provided
by Xilinx for the ethernet.
When we gave a first try, it showed two ethernet
Hi all,
I'm debugging my board with MPC 8540 and marvell 88e designed on it.
I'm sure the hardware connection is correct, and the phy's ID could be read
through terminal port. But anyway, phy can not work. I wonder if it is the
driver's problem? Since the Gianfar Ethernet Controller Version
Hi all,
I'm debugging my board with MPC 8540 and marvell 88e
designed on it.
I'm sure the hardware connection is correct, and the phy's ID
could be read
through terminal port. But anyway, phy can not work. I wonder
Are you sure the hardware is no problem?
Can you successfully tftp
thank you
-- next part --
An HTML attachment was scrubbed...
URL:
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060608/ba9d9a50/attachment.htm
Hello everyone,
Now I am trying to cross-compile the driver for a customed FIFO peripheral
in my design. My embedded platform is Xilinx ML403 development board
(Virtex4) and the host linux is suse 64-bit. I use the cross-compiler to
compile the driver source files provided by Xilinx EDK. But
On Thursday 08 June 2006 15:27, Ming Liu wrote:
My embedded linux kernel version is 2.4.26. My compiler is
powerpc-405-linux-gnu-gcc 3.4.1. I don't know how the version mismatch
happened. Shall I change another cross-compiler version? I will appreciate
a lot if someone could tell me how to
Thanks for your telling first.
The easiest way is usually to put the driver in your source tree
and compile everything together. That also makes it easier to
distribute the complete source tree to your users.
Sorry that I am a novice in Linux. I don't know how can I put the driver in
my source
All,
I've been attempting to get a 2.6 version running on the Xilinx ML403 and
only really need the ethernet and compact flash devices at this point. I've
tried versions from mvista, kernel.org, etc; all only have the serial8250
device enabled. Obviously adding devices is a lot of work
On Thursday 08 June 2006 15:52, Ming Liu wrote:
The easiest way is usually to put the driver in your source tree
and compile everything together. That also makes it easier to
distribute the complete source tree to your users.
Sorry that I am a novice in Linux. I don't know how can I put the
Shantanu,
Can you post the xemac_g.c file in the xilinx_enet directory? Also,
which version of the EDK are you using? There was a bug in EDK 7.x that
prevented multiple Ethernet interfaces from working properly.
It would also be helpful to see xparameters_ml300.h from the
Dear Arnd,
Thanks a lot for your help. Now I have solved the problem of version
mismatch. The reason is I haven't include the sentence of #define MODULE.
However the problem of unresolved symbol XIo_In32 and XIo_Out32 still
exists. I will try to solve it following your suggestion. If any
There seems to be a conflict between two sections of the 5200 User manual.
In section 7.3 where port_config is documented the PSC3 configuration
bits (20:23)
defined as:
= All PSC3 pins are GPIOs
0001 = USB2 on PSC3, no GPIOs available, see Note 3
001X = Reserved
0100 = UART functionality
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
-- next part --
An embedded and charset-unspecified text was scrubbed...
Name: mpc5200_ts_spi.h
Url:
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060608/2eda994d/attachment.txt
On Jun 8, 2006, at 02:43, ? ?? wrote:
Hi all,
I'm debugging my board with MPC 8540 and marvell 88e designed
on it.
I'm sure the hardware connection is correct, and the phy's ID could
be read
through terminal port. But anyway, phy can not work. I wonder if it
is the
driver's
On 6/8/06, rakirtley at bellsouth.net rakirtley at bellsouth.net wrote:
All,
I've been attempting to get a 2.6 version running on the Xilinx ML403 and
only really need the ethernet and compact flash devices at this point. I've
tried versions from mvista, kernel.org, etc; all only have
I'm trying to port a 2.6 kernel to a V2Pro-based board that I've got. I
get the following output when trying to boot:
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
VFS: Cannot open root device NULL or unknown-block(0,0)
Please append a correct root= boot option
On 6/8/06, Chris Dumoulin cdumoulin at ics-ltd.com wrote:
I'm trying to port a 2.6 kernel to a V2Pro-based board that I've got. I
get the following output when trying to boot:
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
VFS: Cannot open root device NULL or
On Jun 8, 2006, at 12:51, Guo Jaffe wrote:
Hi Andy,
Thank you for your information. So the driver is not the issue, but
better to upgraded.
I will check the board once more. The PHY doesn't work because the
8bit bus between MAC and PHY is locked(TX_EN and RX_DV all disabled
from
Thanks John. I actually decided not to sleep last night and figured all of
that out, including the documentation conflict, and now I'm working. I
wasn't even sure my post work, I didn't receive it, but maybe the sender is
left out. I should've slept and waited for your reply.
I'm still a
I am using the linux kernel 2.6.15 and initrd ramdisk image from ELDK
4.0. Currently, I seem to be able to boot without errors, but after the
root filesystem is mounted, things just stop.
I'm guessing that my problems are related to the setup of the RFS, and
more specifically, my inittab file.
On 6/8/06, Chris Dumoulin cdumoulin at ics-ltd.com wrote:
I am using the linux kernel 2.6.15 and initrd ramdisk image from ELDK
4.0. Currently, I seem to be able to boot without errors, but after the
root filesystem is mounted, things just stop.
I'm guessing that my problems are related to
I have encountered one of the rare instances where I need/want more
debugging resources than an LED on an IO port.
I am looking for some recommendations as well as understanding of
the lighter weight debugging tools that are available.
I am dealing with a Xilinx V4 PPC405 FPGA. It
I was hoping to be able to bring up gdb, download an elf file to
the
target and step through a program to see where it is going off the
rails.
Assuming you have the Xilinx EDK tools installed, there is a program
called xmd that acts as a standalone debugger or can communicate with
gdb
23 matches
Mail list logo
