* Linux w/ML403 PLB TEMAC
@ 2007-02-12 16:12 Glenn.G.Hart
2007-02-12 16:33 ` Rick Moleres
` (2 more replies)
0 siblings, 3 replies; 14+ messages in thread
From: Glenn.G.Hart @ 2007-02-12 16:12 UTC (permalink / raw)
To: linuxppc-embedded
I am trying to get Linux up on my ML403 board with the PLB TEMAC with
SGDMA. I am almost there and am not sure where to go now. I have seen
many posts on this from Robert, Ming, and Rick. Hopefully somebody know
the answer. Since I am going to detail how I got to where I am it can be
somewhat of a guide for others (unless I am doing something really wrong).
1. I started with Linux 2.6.19 from kernel.org. I copied over the
xparameters_ml40x.h file to xparameters_ml403.h in
arch/ppc/platforms/4xx/xparameters. Setting up my kernel configuration and
downloading to the board everything worked OK. ** I did not have the TEMAC
configured or as part of my PPC project.
2. Next I created a new PPC with the PLB TEMAC and applied all four kernel
patches from PAULUS
(http://source.mvista.com/~ank/paulus-powerpc/20060309/). A couple of the
files did not patch completely, so I had to do it by hand. Recompiling the
kernel (with the TEMAC configured to on) I now had network support.
3. The speed of the network was very poor. I wanted to implement DMA for
the TEMAC. I created a new PPC with BSB using DMA on the TEMAC. Kernel
recompilied without a problem, but upon starting the kernel I got:
[ 3.813223] Oops: machine check, sig: 7 [#1]
[ 3.864368] NIP: C00E7B08 LR: C00E1640 CTR: 00000000
[ 3.923854] REGS: c01c4f50 TRAP: 0202 Not tainted (2.6.19)
[ 3.992778] MSR: 00029030 <EE,ME,IR,DR> CR: 88000028 XER: 20000000
[ 4.069670] TASK = c052ab70[1] 'swapper' THREAD: c052e000
[ 4.132247] GPR00: C00E1640 C052FE10 C052AB70 00000000 00000068 C5002200
C04A242C 00000001
[ 4.233281] GPR08: 00000000 C04A2304 C5002010 11111111 28000028 FFFFCD64
FFFF0000 FFFF0000
[ 4.334318] GPR16: 0B6654D8 FFFF0000 FFFF0000 FFFF0000 FFFF0000 FFFF0000
FFFF0000 FFFF0000
[ 4.435353] GPR24: C017E890 00000000 C04A22D8 C017EA00 C017E9C8 C017E888
C04A2260 C04A22D8
[ 4.538579] NIP [C00E7B08] XPacketFifoV200a_Initialize+0x74/0x7c
[ 4.610762] LR [C00E1640] XTemac_ConfigureFifoAccess+0x28/0x9c
[ 4.680752] Call Trace:
[ 4.710037] [C052FE10] [C000ADD8] __ioremap+0xe8/0x14c (unreliable)
[ 4.785448] [C052FE20] [C00E1640] XTemac_ConfigureFifoAccess+0x28/0x9c
[ 4.863880] [C052FE30] [C00DFCF8] Initialize+0x3c/0xd0
[ 4.925647] [C052FE40] [C00DF354] xtenet_probe+0x14c/0x5fc
[ 4.991581] [C052FEB0] [C00D6B38] really_probe+0x84/0x154
[ 5.056472] [C052FED0] [C00D6D04] driver_probe_device+0xdc/0xfc
[ 5.127613] [C052FEF0] [C00D6E68] __driver_attach+0x88/0xf4
[ 5.194588] [C052FF10] [C00D5CC0] bus_for_each_dev+0x54/0x94
[ 5.262604] [C052FF40] [C00D6EF8] driver_attach+0x24/0x34
[ 5.327496] [C052FF50] [C00D63E8] bus_add_driver+0x68/0x1b8
[ 5.394471] [C052FF70] [C00D744C] driver_register+0x98/0xac
[ 5.461446] [C052FF80] [C01BBC00] xtenet_init+0x18/0x28
[ 5.524358] [C052FF90] [C0002454] init+0xb0/0x288
[ 5.580917] [C052FFF0] [C0004EA0] kernel_thread+0x44/0x60
[ 5.645794] Instruction dump:
[ 5.681427] 38000000 901f3694 91690004 90a90008 91490000 3800000a
7c0004ac 900a0000
[ 5.775062] 80010014 38600000 83e1000c 7c0803a6 <38210010> 4e800020
2c030000 7c0802a6
[ 5.875957] Kernel panic - not syncing: Attempted to kill init!
Going back through previous posts I found that I need to upgrade the kernel
driver for the DMA and TEMAC to V3.
4. From EDK 8.2.02i SP2.4+0 I copied the files from the BSP to the kernel
using the following steps.
a. Copied the files from linux\drivers\net\xilinx_temac of the BSP
to drivers/net/xilinx_temac of the kernel preserving the Makefile from the
kernel.
b. To adapter.c I remove the #include xilinx_devices.h and added
#include linux/platform_devices.h and #include platforms/4xx/virtex.h
c. To adapter.c I changed all instances of CHECKSUM_HW to
CHECKSUM_PARTIAL
d. To the Makefile in linux/drivers/net/xilinux_temac I added
xtemac_stats.o
e. I removed the #include xparameters.h from xtemac.h
f. Copied the files from linux\drivers\xilinx_common of the BSP to
drivers/xilinx_edk of the kernel.
g. In the drivers/xililnx_edk Makefile I removed the line containing
xdma_channel.o xdma_channel_sg.o
h. In the drivers/xililnx_edk Makefile I commented out the line with
xlinx_syms.o
5. Recompiled the kernel I everything was OK. Starting the kernel
everything looked OK:
[ 3.758994] XTemac: using sgDMA mode.
[ 3.803211] XTemac: using TxDRE mode
[ 3.846160] XTemac: using RxDRE mode
[ 3.889186] XTemac: buffer descriptor size: 32768 (0x8000)
[ 3.956476] XTemac: (buffer_descriptor_init) phy: 0x4a8000, virt:
0xff100000, size: 0x8000
[ 4.069678] eth0: Xilinx TEMAC #0 at 0x81200000 mapped to 0xC5000000,
irq=0
[ 4.153560] eth0: XTemac id 1.0f, block id 5, type 8
6. I am using busybox 1.2.1 which worked fine previously configuring the
network. Now when I execute ifconfig I get the following problem:
[ 12.228721] eth0: XTemac: Options: 0xb8f2
[ 24.197749] eth0: XTemac: Not able to set the speed to 1000 (status:
0x148)
[ 34.215593] eth0: XTemac: Not able to set the speed to 100 (status:
0x148)
[ 44.232349] eth0: XTemac: Not able to set the speed to 10 (status:
0x148)
[ 44.313727] eth0: XTemac: could not negotiate speed
[ 44.372226] eth0: XTemac: Send Threshold = 16, Receive Threshold = 2
[ 44.448421] eth0: XTemac: Send Wait bound = 1, Receive Wait bound = 1
# [ 57.180152] eth0: XTemac: PHY Link carrier lost.
Anybody have an suggestions?
Thanks,
Glenn
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: Linux w/ML403 PLB TEMAC
2007-02-12 16:12 Linux w/ML403 PLB TEMAC Glenn.G.Hart
@ 2007-02-12 16:33 ` Rick Moleres
2007-02-12 16:48 ` Ming Liu
2007-04-04 7:19 ` Leonid
2 siblings, 0 replies; 14+ messages in thread
From: Rick Moleres @ 2007-02-12 16:33 UTC (permalink / raw)
To: Glenn.G.Hart, linuxppc-embedded
Glenn,
Make sure that hard_temac_v3_00_a is being used in your hardware design
for the ML403 board (BSB defaults to hard_temac_v3_00_b, which doesn't
work well for PHY communication on the ML403 board).
Then, take a look at my post on this mailing list from 2/8/07 where I
included a new adapter.c that has a bit better PHY address detection and
auto-negotiation. You may not need it, but you can see the changes.
Thanks,
Rick
-----Original Message-----
From: linuxppc-embedded-bounces+moleres=3Dxilinx.com@ozlabs.org
[mailto:linuxppc-embedded-bounces+moleres=3Dxilinx.com@ozlabs.org] On
Behalf Of Glenn.G.Hart@us.westinghouse.com
Sent: Monday, February 12, 2007 9:13 AM
To: linuxppc-embedded@ozlabs.org
Subject: Linux w/ML403 PLB TEMAC
I am trying to get Linux up on my ML403 board with the PLB TEMAC with
SGDMA. I am almost there and am not sure where to go now. I have seen
many posts on this from Robert, Ming, and Rick. Hopefully somebody know
the answer. Since I am going to detail how I got to where I am it can
be
somewhat of a guide for others (unless I am doing something really
wrong).
1. I started with Linux 2.6.19 from kernel.org. I copied over the
xparameters_ml40x.h file to xparameters_ml403.h in
arch/ppc/platforms/4xx/xparameters. Setting up my kernel configuration
and
downloading to the board everything worked OK. ** I did not have the
TEMAC
configured or as part of my PPC project.
2. Next I created a new PPC with the PLB TEMAC and applied all four
kernel
patches from PAULUS
(http://source.mvista.com/~ank/paulus-powerpc/20060309/). A couple of
the
files did not patch completely, so I had to do it by hand. Recompiling
the
kernel (with the TEMAC configured to on) I now had network support.
3. The speed of the network was very poor. I wanted to implement DMA
for
the TEMAC. I created a new PPC with BSB using DMA on the TEMAC. Kernel
recompilied without a problem, but upon starting the kernel I got:
[ 3.813223] Oops: machine check, sig: 7 [#1]
[ 3.864368] NIP: C00E7B08 LR: C00E1640 CTR: 00000000
[ 3.923854] REGS: c01c4f50 TRAP: 0202 Not tainted (2.6.19)
[ 3.992778] MSR: 00029030 <EE,ME,IR,DR> CR: 88000028 XER: 20000000
[ 4.069670] TASK =3D c052ab70[1] 'swapper' THREAD: c052e000
[ 4.132247] GPR00: C00E1640 C052FE10 C052AB70 00000000 00000068
C5002200
C04A242C 00000001
[ 4.233281] GPR08: 00000000 C04A2304 C5002010 11111111 28000028
FFFFCD64
FFFF0000 FFFF0000
[ 4.334318] GPR16: 0B6654D8 FFFF0000 FFFF0000 FFFF0000 FFFF0000
FFFF0000
FFFF0000 FFFF0000
[ 4.435353] GPR24: C017E890 00000000 C04A22D8 C017EA00 C017E9C8
C017E888
C04A2260 C04A22D8
[ 4.538579] NIP [C00E7B08] XPacketFifoV200a_Initialize+0x74/0x7c
[ 4.610762] LR [C00E1640] XTemac_ConfigureFifoAccess+0x28/0x9c
[ 4.680752] Call Trace:
[ 4.710037] [C052FE10] [C000ADD8] __ioremap+0xe8/0x14c (unreliable)
[ 4.785448] [C052FE20] [C00E1640]
XTemac_ConfigureFifoAccess+0x28/0x9c
[ 4.863880] [C052FE30] [C00DFCF8] Initialize+0x3c/0xd0
[ 4.925647] [C052FE40] [C00DF354] xtenet_probe+0x14c/0x5fc
[ 4.991581] [C052FEB0] [C00D6B38] really_probe+0x84/0x154
[ 5.056472] [C052FED0] [C00D6D04] driver_probe_device+0xdc/0xfc
[ 5.127613] [C052FEF0] [C00D6E68] __driver_attach+0x88/0xf4
[ 5.194588] [C052FF10] [C00D5CC0] bus_for_each_dev+0x54/0x94
[ 5.262604] [C052FF40] [C00D6EF8] driver_attach+0x24/0x34
[ 5.327496] [C052FF50] [C00D63E8] bus_add_driver+0x68/0x1b8
[ 5.394471] [C052FF70] [C00D744C] driver_register+0x98/0xac
[ 5.461446] [C052FF80] [C01BBC00] xtenet_init+0x18/0x28
[ 5.524358] [C052FF90] [C0002454] init+0xb0/0x288
[ 5.580917] [C052FFF0] [C0004EA0] kernel_thread+0x44/0x60
[ 5.645794] Instruction dump:
[ 5.681427] 38000000 901f3694 91690004 90a90008 91490000 3800000a
7c0004ac 900a0000
[ 5.775062] 80010014 38600000 83e1000c 7c0803a6 <38210010> 4e800020
2c030000 7c0802a6
[ 5.875957] Kernel panic - not syncing: Attempted to kill init!
Going back through previous posts I found that I need to upgrade the
kernel
driver for the DMA and TEMAC to V3.
4. From EDK 8.2.02i SP2.4+0 I copied the files from the BSP to the
kernel
using the following steps.
a. Copied the files from linux\drivers\net\xilinx_temac of the
BSP
to drivers/net/xilinx_temac of the kernel preserving the Makefile from
the
kernel.
b. To adapter.c I remove the #include xilinx_devices.h and added
#include linux/platform_devices.h and #include platforms/4xx/virtex.h
c. To adapter.c I changed all instances of CHECKSUM_HW to
CHECKSUM_PARTIAL
d. To the Makefile in linux/drivers/net/xilinux_temac I added
xtemac_stats.o
e. I removed the #include xparameters.h from xtemac.h
f. Copied the files from linux\drivers\xilinx_common of the BSP
to
drivers/xilinx_edk of the kernel.
g. In the drivers/xililnx_edk Makefile I removed the line
containing
xdma_channel.o xdma_channel_sg.o
h. In the drivers/xililnx_edk Makefile I commented out the line
with
xlinx_syms.o
5. Recompiled the kernel I everything was OK. Starting the kernel
everything looked OK:
[ 3.758994] XTemac: using sgDMA mode.
[ 3.803211] XTemac: using TxDRE mode
[ 3.846160] XTemac: using RxDRE mode
[ 3.889186] XTemac: buffer descriptor size: 32768 (0x8000)
[ 3.956476] XTemac: (buffer_descriptor_init) phy: 0x4a8000, virt:
0xff100000, size: 0x8000
[ 4.069678] eth0: Xilinx TEMAC #0 at 0x81200000 mapped to 0xC5000000,
irq=3D0
[ 4.153560] eth0: XTemac id 1.0f, block id 5, type 8
6. I am using busybox 1.2.1 which worked fine previously configuring
the
network. Now when I execute ifconfig I get the following problem:
[ 12.228721] eth0: XTemac: Options: 0xb8f2
[ 24.197749] eth0: XTemac: Not able to set the speed to 1000 (status:
0x148)
[ 34.215593] eth0: XTemac: Not able to set the speed to 100 (status:
0x148)
[ 44.232349] eth0: XTemac: Not able to set the speed to 10 (status:
0x148)
[ 44.313727] eth0: XTemac: could not negotiate speed
[ 44.372226] eth0: XTemac: Send Threshold =3D 16, Receive Threshold =
=3D 2
[ 44.448421] eth0: XTemac: Send Wait bound =3D 1, Receive Wait bound =
=3D 1
# [ 57.180152] eth0: XTemac: PHY Link carrier lost.
Anybody have an suggestions?
Thanks,
Glenn
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: Linux w/ML403 PLB TEMAC
2007-02-12 16:12 Linux w/ML403 PLB TEMAC Glenn.G.Hart
2007-02-12 16:33 ` Rick Moleres
@ 2007-02-12 16:48 ` Ming Liu
2007-04-04 7:19 ` Leonid
2 siblings, 0 replies; 14+ messages in thread
From: Ming Liu @ 2007-02-12 16:48 UTC (permalink / raw)
To: Glenn.G.Hart; +Cc: linuxppc-embedded
Dear Glenn,
>3. The speed of the network was very poor. I wanted to implement DMA for
>the TEMAC. I created a new PPC with BSB using DMA on the TEMAC. Kernel
>recompilied without a problem, but upon starting the kernel I got:
In fact, the old cores of TEMAC(plb_temac 2.00 & hard_temac 1.00) also
support DMA. But of course the 3.00 cores are prefered because of other
improved features.
>6. I am using busybox 1.2.1 which worked fine previously configuring the
>network. Now when I execute ifconfig I get the following problem:
>[ 12.228721] eth0: XTemac: Options: 0xb8f2
>[ 24.197749] eth0: XTemac: Not able to set the speed to 1000 (status:
>0x148)
>[ 34.215593] eth0: XTemac: Not able to set the speed to 100 (status:
>0x148)
>[ 44.232349] eth0: XTemac: Not able to set the speed to 10 (status:
>0x148)
>[ 44.313727] eth0: XTemac: could not negotiate speed
>[ 44.372226] eth0: XTemac: Send Threshold = 16, Receive Threshold = 2
>[ 44.448421] eth0: XTemac: Send Wait bound = 1, Receive Wait bound = 1
># [ 57.180152] eth0: XTemac: PHY Link carrier lost.
I also had such a problem before. To solve such a problem most quickly, you
can just specify a fixed speed (like 1000Mbps) in adapter.c file. In this
file, after the line of "/* Get current link speed */ (around L378) and
"phylinkspeed = (RegValue & MARVELL_88E1111_LINKSPEED_MARK)>>
MARVELL_88E1111_LINKSPEED_SHIFT;", I just add and specify the speed as
"phylinkspeed = MARVELL_88E1111_LINKSPEED_1000M;" Of course with this
method, the speed cannot be auto-negotiated any more.
Another hints: I remember that there is another post from Rick on the
updated "adapter.c" a few days ago. Maybe that could solve your problem. I
didn't try that before. So if you will try, pls let us know the result. :)
BR
Ming
_________________________________________________________________
享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: Linux w/ML403 PLB TEMAC
2007-02-12 16:12 Linux w/ML403 PLB TEMAC Glenn.G.Hart
2007-02-12 16:33 ` Rick Moleres
2007-02-12 16:48 ` Ming Liu
@ 2007-04-04 7:19 ` Leonid
2007-04-04 8:21 ` Andrei Konovalov
2 siblings, 1 reply; 14+ messages in thread
From: Leonid @ 2007-04-04 7:19 UTC (permalink / raw)
To: linuxppc-embedded
Is Paulus' patch http://source.mvista.com/~ank/paulus-powerpc/20060309/
for TEMAC the best one or somebody has better suggestion?
Thanks,
Leonid.=20
-----Original Message-----
From: linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org
[mailto:linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org] On =
Behalf
Of Glenn.G.Hart@us.westinghouse.com
Sent: Monday, February 12, 2007 8:13 AM
To: linuxppc-embedded@ozlabs.org
Subject: Linux w/ML403 PLB TEMAC
I am trying to get Linux up on my ML403 board with the PLB TEMAC with
SGDMA. I am almost there and am not sure where to go now. I have seen
many posts on this from Robert, Ming, and Rick. Hopefully somebody know
the answer. Since I am going to detail how I got to where I am it can
be
somewhat of a guide for others (unless I am doing something really
wrong).
1. I started with Linux 2.6.19 from kernel.org. I copied over the
xparameters_ml40x.h file to xparameters_ml403.h in
arch/ppc/platforms/4xx/xparameters. Setting up my kernel configuration
and
downloading to the board everything worked OK. ** I did not have the
TEMAC
configured or as part of my PPC project.
2. Next I created a new PPC with the PLB TEMAC and applied all four
kernel
patches from PAULUS
(http://source.mvista.com/~ank/paulus-powerpc/20060309/). A couple of
the
files did not patch completely, so I had to do it by hand. Recompiling
the
kernel (with the TEMAC configured to on) I now had network support.
3. The speed of the network was very poor. I wanted to implement DMA
for
the TEMAC. I created a new PPC with BSB using DMA on the TEMAC. Kernel
recompilied without a problem, but upon starting the kernel I got:
[ 3.813223] Oops: machine check, sig: 7 [#1]
[ 3.864368] NIP: C00E7B08 LR: C00E1640 CTR: 00000000
[ 3.923854] REGS: c01c4f50 TRAP: 0202 Not tainted (2.6.19)
[ 3.992778] MSR: 00029030 <EE,ME,IR,DR> CR: 88000028 XER: 20000000
[ 4.069670] TASK =3D c052ab70[1] 'swapper' THREAD: c052e000
[ 4.132247] GPR00: C00E1640 C052FE10 C052AB70 00000000 00000068
C5002200
C04A242C 00000001
[ 4.233281] GPR08: 00000000 C04A2304 C5002010 11111111 28000028
FFFFCD64
FFFF0000 FFFF0000
[ 4.334318] GPR16: 0B6654D8 FFFF0000 FFFF0000 FFFF0000 FFFF0000
FFFF0000
FFFF0000 FFFF0000
[ 4.435353] GPR24: C017E890 00000000 C04A22D8 C017EA00 C017E9C8
C017E888
C04A2260 C04A22D8
[ 4.538579] NIP [C00E7B08] XPacketFifoV200a_Initialize+0x74/0x7c
[ 4.610762] LR [C00E1640] XTemac_ConfigureFifoAccess+0x28/0x9c
[ 4.680752] Call Trace:
[ 4.710037] [C052FE10] [C000ADD8] __ioremap+0xe8/0x14c (unreliable)
[ 4.785448] [C052FE20] [C00E1640]
XTemac_ConfigureFifoAccess+0x28/0x9c
[ 4.863880] [C052FE30] [C00DFCF8] Initialize+0x3c/0xd0
[ 4.925647] [C052FE40] [C00DF354] xtenet_probe+0x14c/0x5fc
[ 4.991581] [C052FEB0] [C00D6B38] really_probe+0x84/0x154
[ 5.056472] [C052FED0] [C00D6D04] driver_probe_device+0xdc/0xfc
[ 5.127613] [C052FEF0] [C00D6E68] __driver_attach+0x88/0xf4
[ 5.194588] [C052FF10] [C00D5CC0] bus_for_each_dev+0x54/0x94
[ 5.262604] [C052FF40] [C00D6EF8] driver_attach+0x24/0x34
[ 5.327496] [C052FF50] [C00D63E8] bus_add_driver+0x68/0x1b8
[ 5.394471] [C052FF70] [C00D744C] driver_register+0x98/0xac
[ 5.461446] [C052FF80] [C01BBC00] xtenet_init+0x18/0x28
[ 5.524358] [C052FF90] [C0002454] init+0xb0/0x288
[ 5.580917] [C052FFF0] [C0004EA0] kernel_thread+0x44/0x60
[ 5.645794] Instruction dump:
[ 5.681427] 38000000 901f3694 91690004 90a90008 91490000 3800000a
7c0004ac 900a0000
[ 5.775062] 80010014 38600000 83e1000c 7c0803a6 <38210010> 4e800020
2c030000 7c0802a6
[ 5.875957] Kernel panic - not syncing: Attempted to kill init!
Going back through previous posts I found that I need to upgrade the
kernel
driver for the DMA and TEMAC to V3.
4. From EDK 8.2.02i SP2.4+0 I copied the files from the BSP to the
kernel
using the following steps.
a. Copied the files from linux\drivers\net\xilinx_temac of the
BSP
to drivers/net/xilinx_temac of the kernel preserving the Makefile from
the
kernel.
b. To adapter.c I remove the #include xilinx_devices.h and added
#include linux/platform_devices.h and #include platforms/4xx/virtex.h
c. To adapter.c I changed all instances of CHECKSUM_HW to
CHECKSUM_PARTIAL
d. To the Makefile in linux/drivers/net/xilinux_temac I added
xtemac_stats.o
e. I removed the #include xparameters.h from xtemac.h
f. Copied the files from linux\drivers\xilinx_common of the BSP
to
drivers/xilinx_edk of the kernel.
g. In the drivers/xililnx_edk Makefile I removed the line
containing
xdma_channel.o xdma_channel_sg.o
h. In the drivers/xililnx_edk Makefile I commented out the line
with
xlinx_syms.o
5. Recompiled the kernel I everything was OK. Starting the kernel
everything looked OK:
[ 3.758994] XTemac: using sgDMA mode.
[ 3.803211] XTemac: using TxDRE mode
[ 3.846160] XTemac: using RxDRE mode
[ 3.889186] XTemac: buffer descriptor size: 32768 (0x8000)
[ 3.956476] XTemac: (buffer_descriptor_init) phy: 0x4a8000, virt:
0xff100000, size: 0x8000
[ 4.069678] eth0: Xilinx TEMAC #0 at 0x81200000 mapped to 0xC5000000,
irq=3D0
[ 4.153560] eth0: XTemac id 1.0f, block id 5, type 8
6. I am using busybox 1.2.1 which worked fine previously configuring
the
network. Now when I execute ifconfig I get the following problem:
[ 12.228721] eth0: XTemac: Options: 0xb8f2
[ 24.197749] eth0: XTemac: Not able to set the speed to 1000 (status:
0x148)
[ 34.215593] eth0: XTemac: Not able to set the speed to 100 (status:
0x148)
[ 44.232349] eth0: XTemac: Not able to set the speed to 10 (status:
0x148)
[ 44.313727] eth0: XTemac: could not negotiate speed
[ 44.372226] eth0: XTemac: Send Threshold =3D 16, Receive Threshold =
=3D 2
[ 44.448421] eth0: XTemac: Send Wait bound =3D 1, Receive Wait bound =
=3D 1
# [ 57.180152] eth0: XTemac: PHY Link carrier lost.
Anybody have an suggestions?
Thanks,
Glenn
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Linux w/ML403 PLB TEMAC
2007-04-04 7:19 ` Leonid
@ 2007-04-04 8:21 ` Andrei Konovalov
0 siblings, 0 replies; 14+ messages in thread
From: Andrei Konovalov @ 2007-04-04 8:21 UTC (permalink / raw)
To: Leonid; +Cc: linuxppc-embedded
Hi Leonid,
Please note that the 20060309 patch (i.e. of March 9, 2006)
is for v2.x of PLB TEMAC; the one using SGDMA version 2 IOW.
The most recent v3.xx PLB TEMAC IP from EDK 8.2.02 uses SGDMA version 3.
Guess this is what made the kernel to crash when Glenn tried
the new design with the PLB TEMAC (step 3 in his email below).
The step 5 problem was probably due to XC4VFX12 engineering
samples (all ML403 use the engineering samples AFAIK)
could not work with HARD TEMAC IP version 3.00.b. For ML403 one need
to set the HARD TEMAC IP version to 3.00.a in xps. Then
TEMAC should work OK.
Thanks,
Andrei
Leonid wrote:
> Is Paulus' patch http://source.mvista.com/~ank/paulus-powerpc/20060309/
> for TEMAC the best one or somebody has better suggestion?
>
> Thanks,
>
> Leonid.
>
> -----Original Message-----
> From: linuxppc-embedded-bounces+leonid=a-k-a.net@ozlabs.org
> [mailto:linuxppc-embedded-bounces+leonid=a-k-a.net@ozlabs.org] On Behalf
> Of Glenn.G.Hart@us.westinghouse.com
> Sent: Monday, February 12, 2007 8:13 AM
> To: linuxppc-embedded@ozlabs.org
> Subject: Linux w/ML403 PLB TEMAC
>
> I am trying to get Linux up on my ML403 board with the PLB TEMAC with
> SGDMA. I am almost there and am not sure where to go now. I have seen
> many posts on this from Robert, Ming, and Rick. Hopefully somebody know
> the answer. Since I am going to detail how I got to where I am it can
> be
> somewhat of a guide for others (unless I am doing something really
> wrong).
>
> 1. I started with Linux 2.6.19 from kernel.org. I copied over the
> xparameters_ml40x.h file to xparameters_ml403.h in
> arch/ppc/platforms/4xx/xparameters. Setting up my kernel configuration
> and
> downloading to the board everything worked OK. ** I did not have the
> TEMAC
> configured or as part of my PPC project.
>
> 2. Next I created a new PPC with the PLB TEMAC and applied all four
> kernel
> patches from PAULUS
> (http://source.mvista.com/~ank/paulus-powerpc/20060309/). A couple of
> the
> files did not patch completely, so I had to do it by hand. Recompiling
> the
> kernel (with the TEMAC configured to on) I now had network support.
>
> 3. The speed of the network was very poor. I wanted to implement DMA
> for
> the TEMAC. I created a new PPC with BSB using DMA on the TEMAC. Kernel
> recompilied without a problem, but upon starting the kernel I got:
> [ 3.813223] Oops: machine check, sig: 7 [#1]
> [ 3.864368] NIP: C00E7B08 LR: C00E1640 CTR: 00000000
> [ 3.923854] REGS: c01c4f50 TRAP: 0202 Not tainted (2.6.19)
> [ 3.992778] MSR: 00029030 <EE,ME,IR,DR> CR: 88000028 XER: 20000000
> [ 4.069670] TASK = c052ab70[1] 'swapper' THREAD: c052e000
> [ 4.132247] GPR00: C00E1640 C052FE10 C052AB70 00000000 00000068
> C5002200
> C04A242C 00000001
> [ 4.233281] GPR08: 00000000 C04A2304 C5002010 11111111 28000028
> FFFFCD64
> FFFF0000 FFFF0000
> [ 4.334318] GPR16: 0B6654D8 FFFF0000 FFFF0000 FFFF0000 FFFF0000
> FFFF0000
> FFFF0000 FFFF0000
> [ 4.435353] GPR24: C017E890 00000000 C04A22D8 C017EA00 C017E9C8
> C017E888
> C04A2260 C04A22D8
> [ 4.538579] NIP [C00E7B08] XPacketFifoV200a_Initialize+0x74/0x7c
> [ 4.610762] LR [C00E1640] XTemac_ConfigureFifoAccess+0x28/0x9c
> [ 4.680752] Call Trace:
> [ 4.710037] [C052FE10] [C000ADD8] __ioremap+0xe8/0x14c (unreliable)
> [ 4.785448] [C052FE20] [C00E1640]
> XTemac_ConfigureFifoAccess+0x28/0x9c
> [ 4.863880] [C052FE30] [C00DFCF8] Initialize+0x3c/0xd0
> [ 4.925647] [C052FE40] [C00DF354] xtenet_probe+0x14c/0x5fc
> [ 4.991581] [C052FEB0] [C00D6B38] really_probe+0x84/0x154
> [ 5.056472] [C052FED0] [C00D6D04] driver_probe_device+0xdc/0xfc
> [ 5.127613] [C052FEF0] [C00D6E68] __driver_attach+0x88/0xf4
> [ 5.194588] [C052FF10] [C00D5CC0] bus_for_each_dev+0x54/0x94
> [ 5.262604] [C052FF40] [C00D6EF8] driver_attach+0x24/0x34
> [ 5.327496] [C052FF50] [C00D63E8] bus_add_driver+0x68/0x1b8
> [ 5.394471] [C052FF70] [C00D744C] driver_register+0x98/0xac
> [ 5.461446] [C052FF80] [C01BBC00] xtenet_init+0x18/0x28
> [ 5.524358] [C052FF90] [C0002454] init+0xb0/0x288
> [ 5.580917] [C052FFF0] [C0004EA0] kernel_thread+0x44/0x60
> [ 5.645794] Instruction dump:
> [ 5.681427] 38000000 901f3694 91690004 90a90008 91490000 3800000a
> 7c0004ac 900a0000
> [ 5.775062] 80010014 38600000 83e1000c 7c0803a6 <38210010> 4e800020
> 2c030000 7c0802a6
> [ 5.875957] Kernel panic - not syncing: Attempted to kill init!
>
> Going back through previous posts I found that I need to upgrade the
> kernel
> driver for the DMA and TEMAC to V3.
>
> 4. From EDK 8.2.02i SP2.4+0 I copied the files from the BSP to the
> kernel
> using the following steps.
> a. Copied the files from linux\drivers\net\xilinx_temac of the
> BSP
> to drivers/net/xilinx_temac of the kernel preserving the Makefile from
> the
> kernel.
> b. To adapter.c I remove the #include xilinx_devices.h and added
> #include linux/platform_devices.h and #include platforms/4xx/virtex.h
> c. To adapter.c I changed all instances of CHECKSUM_HW to
> CHECKSUM_PARTIAL
> d. To the Makefile in linux/drivers/net/xilinux_temac I added
> xtemac_stats.o
> e. I removed the #include xparameters.h from xtemac.h
>
> f. Copied the files from linux\drivers\xilinx_common of the BSP
> to
> drivers/xilinx_edk of the kernel.
> g. In the drivers/xililnx_edk Makefile I removed the line
> containing
> xdma_channel.o xdma_channel_sg.o
> h. In the drivers/xililnx_edk Makefile I commented out the line
> with
> xlinx_syms.o
>
> 5. Recompiled the kernel I everything was OK. Starting the kernel
> everything looked OK:
> [ 3.758994] XTemac: using sgDMA mode.
> [ 3.803211] XTemac: using TxDRE mode
> [ 3.846160] XTemac: using RxDRE mode
> [ 3.889186] XTemac: buffer descriptor size: 32768 (0x8000)
> [ 3.956476] XTemac: (buffer_descriptor_init) phy: 0x4a8000, virt:
> 0xff100000, size: 0x8000
> [ 4.069678] eth0: Xilinx TEMAC #0 at 0x81200000 mapped to 0xC5000000,
> irq=0
> [ 4.153560] eth0: XTemac id 1.0f, block id 5, type 8
>
> 6. I am using busybox 1.2.1 which worked fine previously configuring
> the
> network. Now when I execute ifconfig I get the following problem:
> [ 12.228721] eth0: XTemac: Options: 0xb8f2
> [ 24.197749] eth0: XTemac: Not able to set the speed to 1000 (status:
> 0x148)
> [ 34.215593] eth0: XTemac: Not able to set the speed to 100 (status:
> 0x148)
> [ 44.232349] eth0: XTemac: Not able to set the speed to 10 (status:
> 0x148)
> [ 44.313727] eth0: XTemac: could not negotiate speed
> [ 44.372226] eth0: XTemac: Send Threshold = 16, Receive Threshold = 2
> [ 44.448421] eth0: XTemac: Send Wait bound = 1, Receive Wait bound = 1
> # [ 57.180152] eth0: XTemac: PHY Link carrier lost.
>
> Anybody have an suggestions?
>
> Thanks,
> Glenn
>
>
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: Linux w/ML403 PLB TEMAC
2007-04-09 16:35 Jarek
@ 2007-04-10 5:57 ` Leonid
0 siblings, 0 replies; 14+ messages in thread
From: Leonid @ 2007-04-10 5:57 UTC (permalink / raw)
To: Jarek, linuxppc-embedded
Sorry, I cannot tell. I didn't experience your problem, but then I don't
run ML403 precisely, my board is different. I had problem with MDIO, but
it appeared it just wasn't connected in our design.
Leonid.
-----Original Message-----
From: linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org
[mailto:linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org] On =
Behalf
Of Jarek
Sent: Monday, April 09, 2007 9:36 AM
To: linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
Hello folks,
I have been working for a while on bringing up PLB Temac on ml403. I
have followed all steps presented by Glenn, but unfortunately I have
stacked in one place. I hope that maybe one of you due to your experince
can give me some advice. I use systemace for mounting rfs and I have
patched my kernel with Paulus Temac patches. Kernel compiles without any
problem. As i said i followed Glenn's steps for configuring kernel with
plb/temac. The only difference I have noticed is that I use root file
system on a flash card. After booting the kernel from flash card I got
the following output:
loaded at: 00400000 0052013C
board data at: 0051E124 0051E13C
relocated to: 004040B8 004040D0
zimage at: 00404E45 0051DFC1
avail ram: 00521000 04000000
Linux/PPC load: console=3DttyS0,9600 root=3D/dev/xsa3 rw =
init=3D/sbin/init
Uncompressing Linux...done.
Now booting the kernel
[ 0.000000] Linux version 2.6.20 (butanowi@amandla) (gcc version
4.0.2) #3 Mon Apr 9 16:44:13 CEST 2007
[ 0.000000] Xilinx ML403 Reference System (Virtex-4 FX)
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0 -> 16384
[ 0.000000] Normal 16384 -> 16384
[ 0.000000] early_node_map[1] active PFN ranges
[ 0.000000] 0: 0 -> 16384
[ 0.000000] Built 1 zonelists. Total pages: 16256
[ 0.000000] Kernel command line: console=3DttyS0,9600 =
root=3D/dev/xsa3 rw
init=3D/sbin/init
[ 0.000000] Xilinx INTC #0 at 0x41200000 mapped to 0xFDFFE000
[ 0.000000] PID hash table entries: 256 (order: 8, 1024 bytes)
[ 0.000430] Console: colour dummy device 80x25
[ 0.001581] Dentry cache hash table entries: 8192 (order: 3, 32768
bytes)
[ 0.003395] Inode-cache hash table entries: 4096 (order: 2, 16384
bytes)
[ 0.036070] Memory: 62476k available (1840k kernel code, 488k data,
96k init, 0k highmem)
[ 0.221232] Mount-cache hash table entries: 512
[ 0.232180] NET: Registered protocol family 16
[ 0.269606] NET: Registered protocol family 2
[ 0.361155] IP route cache hash table entries: 1024 (order: 0, 4096
bytes)
[ 0.363365] TCP established hash table entries: 2048 (order: 1, 8192
bytes)
[ 0.363868] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.364143] TCP: Hash tables configured (established 2048 bind 1024)
[ 0.364229] TCP reno registered
[ 0.401242] JFS: nTxBlock =3D 488, nTxLock =3D 3908
[ 0.408340] SGI XFS with no debug enabled
[ 0.411933] io scheduler noop registered
[ 0.412037] io scheduler deadline registered (default)
[ 0.517700] Serial: 8250/16550 driver $Revision: 1.90 $ 1 ports, IRQ
sharing disabled
[ 0.524846] serial8250.0: ttyS0 at MMIO 0x40401003 (irq =3D 2) is a
16550A
[ 2.444102] RAMDISK driver initialized: 1 RAM disks of 4096K size
1024 blocksize
[ 2.536064] xsa: xsa1 xsa2 xsa3
[ 2.602624] XTemac: using sgDMA mode.
[ 2.646747] XTemac: not using TxDRE mode
[ 2.694037] XTemac: using RxDRE mode
[ 2.737007] XTemac: buffer descriptor size: 32768 (0x8000)
[ 2.804113] XTemac: (buffer_descriptor_init) phy: 0x3c00000, virt:
0xff100000, size: 0x8000
[ 3.004280] XTemac: Could not alloc TX buffer 168 (9032 bytes).
Cleaning up.
[ 3.093984] XTemac: Could not allocate TX buffers.
[ 3.156274] xilinx_temac: probe of xilinx_temac.0 failed with error
-5
[ 3.236276] mice: PS/2 mouse device common for all mice
[ 3.299587] TCP cubic registered
[ 3.338772] NET: Registered protocol family 1
[ 3.391288] NET: Registered protocol family 17
[ 3.495078] EXT2-fs warning: mounting unchecked fs, running e2fsck is
recommended
[ 3.586449] VFS: Mounted root (ext2 filesystem).
[ 3.642764] Freeing unused kernel memory: 96k init
serial console detected. Disabling virtual terminals.
init started: BusyBox v0.60.2 (2004.04.30-17:49+0000) multi-call binary
I have a problem with TxDRE: XTemac: not using TxDRE mode
[ 3.004280] XTemac: Could not alloc TX buffer 168 (9032 bytes).
Cleaning up.
[ 3.093984] XTemac: Could not allocate TX buffers.
Is it a problem related to my hardware design??=20
Looking for a help:-( or hint. I do not know what is the problem related
to.
Regards
Jaroslaw Butanowicz
> I have just learnt that MDIO lines are not connected in our design...
that explains everything... thanks a lot.
>=20
> Leonid.
>=20
> -----Original Message-----
> From: Rick Moleres [mailto:Rick.Moleres@xilinx.com]=20
> Sent: Wednesday, April 04, 2007 5:00 PM
> To: Leonid; linuxppc-embedded@ozlabs.org
> Subject: RE: Linux w/ML403 PLB TEMAC
>=20
>=20
> Leonid,
>=20
> If it's not the ML403 board and the FX part is CES4 or later (read
this at the bottom of the FX chip), then you will need
hard_temac_v3_00_b to get the MDIO access working properly.
>=20
> If this is pre-CES4 silicon, then hard_temac_v3_00_a is the right
version and there may be an issue with the MDIO signal connectivity in
your design (? just guessing). You can also try to hardcode the PHY
address (gmii_addr) and see if the speed detection works at that point -
but my guess is it won't.
>=20
> -Rick
>=20
> -----Original Message-----
> From: Leonid [mailto:Leonid@a-k-a.net]=20
> Sent: Wednesday, April 04, 2007 5:50 PM
> To: Rick Moleres; linuxppc-embedded@ozlabs.org
> Subject: RE: Linux w/ML403 PLB TEMAC
>=20
> Hi, Rick:
>=20
> We have both in our design and both are 3.00a. I'm not sure why - I'll
ask our HW folks.=20
>=20
> I have actually managed (just 30 minutes ago) to bring up network
interface but I have commented out all accesses to PHY in your adapter.c
and I set speed to 1000 always (see my adapter.c attached). Without
these changes packets are not transmitted out of board.
>=20
> This is probably some issue in my EDK project.
>=20
> I'm not using ML403 actually but another proprietary board, based on
Virtex
> 4 (69FX) FPGA.
>=20
> Thanks,
>=20
> Leonid.
>=20
> -----Original Message-----
> From: Rick Moleres [mailto:Rick.Moleres@xilinx.com]=20
> Sent: Wednesday, April 04, 2007 4:41 PM
> To: Leonid; Glenn.G.Hart@us.westinghouse.com;
linuxppc-embedded@ozlabs.org
> Subject: RE: Linux w/ML403 PLB TEMAC
>=20
> Leonid,
>=20
> You mentioned that the TEMAC version if v3.00a. Is this the plb_temac
version or the hard_temac version, or both?
>=20
> -Rick
>=20
> -----Original Message-----
> From: linuxppc-embedded-bounces+moleres=3Dxilinx.com@ozlabs.org
[mailto:linuxppc-embedded-bounces+moleres=3Dxilinx.com@ozlabs.org] On
Behalf Of Leonid
> Sent: Wednesday, April 04, 2007 4:14 PM
> To: Glenn.G.Hart@us.westinghouse.com; linuxppc-embedded@ozlabs.org
> Subject: RE: Linux w/ML403 PLB TEMAC
>=20
> I have investigated little bit more. Receive is working actually, but
transmit doesn't. What can it be?
>=20
> -----Original Message-----
> From: linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org
[mailto:linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org] On =
Behalf
Of Leonid
> Sent: Wednesday, April 04, 2007 12:06 PM
> To: Glenn.G.Hart@us.westinghouse.com; linuxppc-embedded@ozlabs.org
> Subject: RE: Linux w/ML403 PLB TEMAC
>=20
> I have precisely the same problem you have described:
>=20
> [ 0.430515] XTemac: using FIFO direct interrupt driven mode.
> [ 0.437461] eth%d: XTemac: No PHY detected. Assuming a PHY at
address 0
> [ 0.445295] eth0: Xilinx TEMAC #0 at 0x02000000 mapped to
0xC3000000, irq=3D0
> [ 0.452256] eth0: XTemac id 1.0f, block id 5, type 8
> [ 0.458665] tun: Universal TUN/TAP device driver, 1.6
> [ 0.463712] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
> [ 0.471106] mice: PS/2 mouse device common for all mice
> [ 0.476339] TCP cubic registered
> [ 0.479615] NET: Registered protocol family 1
> [ 0.484032] NET: Registered protocol family 17
> [ 0.992599] eth0: XTemac: Options: 0xb8f2
> [ 12.955691] eth0: XTemac: Not able to set the speed to 1000
(status: 0x0)
> [ 22.928615] eth0: XTemac: Not able to set the speed to 100 (status:
0x0)
> [ 32.901449] eth0: XTemac: Not able to set the speed to 10 (status:
0x0)
> [ 32.907976] eth0: XTemac: could not negotiate speed
> [ 33.921626] IP-Config: Complete:
> [ 33.924635] device=3Deth0, addr=3D192.168.0.223,
mask=3D255.255.255.0, gw=3D192.168.0.1,
> [ 33.932418] host=3DLM200, domain=3D, nis-domain=3D(none),
> [ 33.937715] bootserver=3D192.168.0.141,
rootserver=3D192.168.0.141, rootpath=3D
> [ 33.946230] Looking up port of RPC 100003/2 on 192.168.0.141
> [ 34.916694] eth0: XTemac: PHY Link carrier lost.
>=20
> My TEMAC core version is 3.00.a and low level code I'm using is
working in u-boot wi
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: Linux w/ML403 PLB TEMAC
@ 2007-04-09 16:35 Jarek
2007-04-10 5:57 ` Leonid
0 siblings, 1 reply; 14+ messages in thread
From: Jarek @ 2007-04-09 16:35 UTC (permalink / raw)
To: linuxppc-embedded
Hello=20folks,
I=20have=20been=20working=20for=20a=20while=20on=20bringing=20up=20PLB=20=
Temac=20on=20ml403.=20I=20have=20followed=20all=20steps=20presented=20by=20=
Glenn,=20but=20unfortunately=20I=20have=20stacked=20in=20one=20place.=20I=
=20hope=20that=20maybe=20one=20of=20you=20due=20to=20your=20experince=20c=
an=20give=20me=20some=20advice.=20I=20use=20systemace=20for=20mounting=20=
rfs=20and=20I=20have=20patched=20my=20kernel=20with=20Paulus=20Temac=20pa=
tches.=20Kernel=20compiles=20without=20any=20problem.=20As=20i=20said=20i=
=20followed=20Glenn's=20steps=20for=20configuring=20kernel=20with=20plb/t=
emac.=20The=20only=20difference=20I=20have=20noticed=20is=20that=20I=20us=
e=20root=20file=20system=20on=20a=20flash=20card.=20After=20booting=20the=
=20kernel=20from=20flash=20card=20I=20got=20the=20following=20output:
loaded=20at:=20=20=20=20=2000400000=200052013C
board=20data=20at:=200051E124=200051E13C
relocated=20to:=20=20004040B8=20004040D0
zimage=20at:=20=20=20=20=2000404E45=200051DFC1
avail=20ram:=20=20=20=20=2000521000=2004000000
Linux/PPC=20load:=20console=3DttyS0,9600=20root=3D/dev/xsa3=20rw=20init=3D=
/sbin/init
Uncompressing=20Linux...done.
Now=20booting=20the=20kernel
[=20=20=20=200.000000]=20Linux=20version=202.6.20=20(butanowi@amandla)=20=
(gcc=20version=204.0.2)=20#3=20Mon=20Apr=209=2016:44:13=20CEST=202007
[=20=20=20=200.000000]=20Xilinx=20ML403=20Reference=20System=20(Virtex-4=20=
FX)
[=20=20=20=200.000000]=20Zone=20PFN=20ranges:
[=20=20=20=200.000000]=20=20=20DMA=20=20=20=20=20=20=20=20=20=20=20=20=20=
0=20->=20=20=20=2016384
[=20=20=20=200.000000]=20=20=20Normal=20=20=20=20=20=2016384=20->=20=20=20=
=2016384
[=20=20=20=200.000000]=20early=5Fnode=5Fmap[1]=20active=20PFN=20ranges
[=20=20=20=200.000000]=20=20=20=20=200:=20=20=20=20=20=20=20=200=20->=20=20=
=20=2016384
[=20=20=20=200.000000]=20Built=201=20zonelists.=20=20Total=20pages:=20162=
56
[=20=20=20=200.000000]=20Kernel=20command=20line:=20console=3DttyS0,9600=20=
root=3D/dev/xsa3=20rw=20init=3D/sbin/init
[=20=20=20=200.000000]=20Xilinx=20INTC=20#0=20at=200x41200000=20mapped=20=
to=200xFDFFE000
[=20=20=20=200.000000]=20PID=20hash=20table=20entries:=20256=20(order:=20=
8,=201024=20bytes)
[=20=20=20=200.000430]=20Console:=20colour=20dummy=20device=2080x25
[=20=20=20=200.001581]=20Dentry=20cache=20hash=20table=20entries:=208192=20=
(order:=203,=2032768=20bytes)
[=20=20=20=200.003395]=20Inode-cache=20hash=20table=20entries:=204096=20(=
order:=202,=2016384=20bytes)
[=20=20=20=200.036070]=20Memory:=2062476k=20available=20(1840k=20kernel=20=
code,=20488k=20data,=2096k=20init,=200k=20highmem)
[=20=20=20=200.221232]=20Mount-cache=20hash=20table=20entries:=20512
[=20=20=20=200.232180]=20NET:=20Registered=20protocol=20family=2016
[=20=20=20=200.269606]=20NET:=20Registered=20protocol=20family=202
[=20=20=20=200.361155]=20IP=20route=20cache=20hash=20table=20entries:=201=
024=20(order:=200,=204096=20bytes)
[=20=20=20=200.363365]=20TCP=20established=20hash=20table=20entries:=2020=
48=20(order:=201,=208192=20bytes)
[=20=20=20=200.363868]=20TCP=20bind=20hash=20table=20entries:=201024=20(o=
rder:=200,=204096=20bytes)
[=20=20=20=200.364143]=20TCP:=20Hash=20tables=20configured=20(established=
=202048=20bind=201024)
[=20=20=20=200.364229]=20TCP=20reno=20registered
[=20=20=20=200.401242]=20JFS:=20nTxBlock=20=3D=20488,=20nTxLock=20=3D=203=
908
[=20=20=20=200.408340]=20SGI=20XFS=20with=20no=20debug=20enabled
[=20=20=20=200.411933]=20io=20scheduler=20noop=20registered
[=20=20=20=200.412037]=20io=20scheduler=20deadline=20registered=20(defaul=
t)
[=20=20=20=200.517700]=20Serial:=208250/16550=20driver=20$Revision:=201.9=
0=20$=201=20ports,=20IRQ=20sharing=20disabled
[=20=20=20=200.524846]=20serial8250.0:=20ttyS0=20at=20MMIO=200x40401003=20=
(irq=20=3D=202)=20is=20a=2016550A
[=20=20=20=202.444102]=20RAMDISK=20driver=20initialized:=201=20RAM=20disk=
s=20of=204096K=20size=201024=20blocksize
[=20=20=20=202.536064]=20=20xsa:=20xsa1=20xsa2=20xsa3
[=20=20=20=202.602624]=20XTemac:=20using=20sgDMA=20mode.
[=20=20=20=202.646747]=20XTemac:=20not=20using=20TxDRE=20mode
[=20=20=20=202.694037]=20XTemac:=20using=20RxDRE=20mode
[=20=20=20=202.737007]=20XTemac:=20buffer=20descriptor=20size:=2032768=20=
(0x8000)
[=20=20=20=202.804113]=20XTemac:=20(buffer=5Fdescriptor=5Finit)=20phy:=20=
0x3c00000,=20virt:=200xff100000,=20size:=200x8000
[=20=20=20=203.004280]=20XTemac:=20Could=20not=20alloc=20TX=20buffer=2016=
8=20(9032=20bytes).=20Cleaning=20up.
[=20=20=20=203.093984]=20XTemac:=20Could=20not=20allocate=20TX=20buffers.=
[=20=20=20=203.156274]=20xilinx=5Ftemac:=20probe=20of=20xilinx=5Ftemac.0=20=
failed=20with=20error=20-5
[=20=20=20=203.236276]=20mice:=20PS/2=20mouse=20device=20common=20for=20a=
ll=20mice
[=20=20=20=203.299587]=20TCP=20cubic=20registered
[=20=20=20=203.338772]=20NET:=20Registered=20protocol=20family=201
[=20=20=20=203.391288]=20NET:=20Registered=20protocol=20family=2017
[=20=20=20=203.495078]=20EXT2-fs=20warning:=20mounting=20unchecked=20fs,=20=
running=20e2fsck=20is=20recommended
[=20=20=20=203.586449]=20VFS:=20Mounted=20root=20(ext2=20filesystem).
[=20=20=20=203.642764]=20Freeing=20unused=20kernel=20memory:=2096k=20init=
serial=20console=20detected.=20=20Disabling=20virtual=20terminals.
init=20started:=20=20BusyBox=20v0.60.2=20(2004.04.30-17:49+0000)=20multi-=
call=20binary
I=20have=20a=20problem=20with=20TxDRE:=20XTemac:=20not=20using=20TxDRE=20=
mode
[=20=20=20=203.004280]=20XTemac:=20Could=20not=20alloc=20TX=20buffer=2016=
8=20(9032=20bytes).=20Cleaning=20up.
[=20=20=20=203.093984]=20XTemac:=20Could=20not=20allocate=20TX=20buffers.=
Is=20it=20a=20problem=20related=20to=20my=20hardware=20design??=20
Looking=20for=20a=20help:-(=20or=20hint.=20I=20do=20not=20know=20what=20i=
s=20the=20problem=20related=20to.
Regards
Jaroslaw=20Butanowicz
>=20I=20have=20just=20learnt=20that=20MDIO=20lines=20are=20not=20connecte=
d=20in=20our=20design...=20that=20explains=20everything...=20thanks=20a=20=
lot.
>=20
>=20Leonid.
>=20
>=20-----Original=20Message-----
>=20From:=20Rick=20Moleres=20[mailto:Rick.Moleres@xilinx.com]=20
>=20Sent:=20Wednesday,=20April=2004,=202007=205:00=20PM
>=20To:=20Leonid;=20linuxppc-embedded@ozlabs.org
>=20Subject:=20RE:=20Linux=20w/ML403=20PLB=20TEMAC
>=20
>=20
>=20Leonid,
>=20
>=20If=20it's=20not=20the=20ML403=20board=20and=20the=20FX=20part=20is=20=
CES4=20or=20later=20(read=20this=20at=20the=20bottom=20of=20the=20FX=20ch=
ip),=20then=20you=20will=20need=20hard=5Ftemac=5Fv3=5F00=5Fb=20to=20get=20=
the=20MDIO=20access=20working=20properly.
>=20
>=20If=20this=20is=20pre-CES4=20silicon,=20then=20hard=5Ftemac=5Fv3=5F00=5F=
a=20is=20the=20right=20version=20and=20there=20may=20be=20an=20issue=20wi=
th=20the=20MDIO=20signal=20connectivity=20in=20your=20design=20(?=20just=20=
guessing).=20=20You=20can=20also=20try=20to=20hardcode=20the=20PHY=20addr=
ess=20(gmii=5Faddr)=20and=20see=20if=20the=20speed=20detection=20works=20=
at=20that=20point=20-=20but=20my=20guess=20is=20it=20won't.
>=20
>=20-Rick
>=20
>=20-----Original=20Message-----
>=20From:=20Leonid=20[mailto:Leonid@a-k-a.net]=20
>=20Sent:=20Wednesday,=20April=2004,=202007=205:50=20PM
>=20To:=20Rick=20Moleres;=20linuxppc-embedded@ozlabs.org
>=20Subject:=20RE:=20Linux=20w/ML403=20PLB=20TEMAC
>=20
>=20Hi,=20Rick:
>=20
>=20We=20have=20both=20in=20our=20design=20and=20both=20are=203.00a.=20I'=
m=20not=20sure=20why=20-=20I'll=20ask=20our=20HW=20folks.=20
>=20
>=20I=20have=20actually=20managed=20(just=2030=20minutes=20ago)=20to=20br=
ing=20up=20network=20interface=20but=20I=20have=20commented=20out=20all=20=
accesses=20to=20PHY=20in=20your=20adapter.c=20and=20I=20set=20speed=20to=20=
1000=20always=20(see=20my=20adapter.c=20attached).=20Without=20these=20ch=
anges=20packets=20are=20not=20transmitted=20out=20of=20board.
>=20
>=20This=20is=20probably=20some=20issue=20in=20my=20EDK=20project.
>=20
>=20I'm=20not=20using=20ML403=20actually=20but=20another=20proprietary=20=
board,=20based=20on=20Virtex
>=204=20(69FX)=20FPGA.
>=20
>=20Thanks,
>=20
>=20Leonid.
>=20
>=20-----Original=20Message-----
>=20From:=20Rick=20Moleres=20[mailto:Rick.Moleres@xilinx.com]=20
>=20Sent:=20Wednesday,=20April=2004,=202007=204:41=20PM
>=20To:=20Leonid;=20Glenn.G.Hart@us.westinghouse.com;=20linuxppc-embedded=
@ozlabs.org
>=20Subject:=20RE:=20Linux=20w/ML403=20PLB=20TEMAC
>=20
>=20Leonid,
>=20
>=20You=20mentioned=20that=20the=20TEMAC=20version=20if=20v3.00a.=20=20Is=
=20this=20the=20plb=5Ftemac=20version=20or=20the=20hard=5Ftemac=20version=
,=20or=20both?
>=20
>=20-Rick
>=20
>=20-----Original=20Message-----
>=20From:=20linuxppc-embedded-bounces+moleres=3Dxilinx.com@ozlabs.org=20[=
mailto:linuxppc-embedded-bounces+moleres=3Dxilinx.com@ozlabs.org]=20On=20=
Behalf=20Of=20Leonid
>=20Sent:=20Wednesday,=20April=2004,=202007=204:14=20PM
>=20To:=20Glenn.G.Hart@us.westinghouse.com;=20linuxppc-embedded@ozlabs.or=
g
>=20Subject:=20RE:=20Linux=20w/ML403=20PLB=20TEMAC
>=20
>=20I=20have=20investigated=20little=20bit=20more.=20Receive=20is=20worki=
ng=20actually,=20but=20transmit=20doesn't.=20What=20can=20it=20be?
>=20
>=20-----Original=20Message-----
>=20From:=20linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org=20[ma=
ilto:linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org]=20On=20Beha=
lf=20Of=20Leonid
>=20Sent:=20Wednesday,=20April=2004,=202007=2012:06=20PM
>=20To:=20Glenn.G.Hart@us.westinghouse.com;=20linuxppc-embedded@ozlabs.or=
g
>=20Subject:=20RE:=20Linux=20w/ML403=20PLB=20TEMAC
>=20
>=20I=20have=20precisely=20the=20same=20problem=20you=20have=20described:=
>=20
>=20[=20=20=20=200.430515]=20XTemac:=20using=20FIFO=20direct=20interrupt=20=
driven=20mode.
>=20[=20=20=20=200.437461]=20eth%d:=20XTemac:=20No=20PHY=20detected.=20=20=
Assuming=20a=20PHY=20at=20address=200
>=20[=20=20=20=200.445295]=20eth0:=20Xilinx=20TEMAC=20#0=20at=200x0200000=
0=20mapped=20to=200xC3000000,=20irq=3D0
>=20[=20=20=20=200.452256]=20eth0:=20XTemac=20id=201.0f,=20block=20id=205=
,=20type=208
>=20[=20=20=20=200.458665]=20tun:=20Universal=20TUN/TAP=20device=20driver=
,=201.6
>=20[=20=20=20=200.463712]=20tun:=20(C)=201999-2004=20Max=20Krasnyansky=20=
<maxk@qualcomm.com>
>=20[=20=20=20=200.471106]=20mice:=20PS/2=20mouse=20device=20common=20for=
=20all=20mice
>=20[=20=20=20=200.476339]=20TCP=20cubic=20registered
>=20[=20=20=20=200.479615]=20NET:=20Registered=20protocol=20family=201
>=20[=20=20=20=200.484032]=20NET:=20Registered=20protocol=20family=2017
>=20[=20=20=20=200.992599]=20eth0:=20XTemac:=20Options:=200xb8f2
>=20[=20=20=2012.955691]=20eth0:=20XTemac:=20Not=20able=20to=20set=20the=20=
speed=20to=201000=20(status:=200x0)
>=20[=20=20=2022.928615]=20eth0:=20XTemac:=20Not=20able=20to=20set=20the=20=
speed=20to=20100=20(status:=200x0)
>=20[=20=20=2032.901449]=20eth0:=20XTemac:=20Not=20able=20to=20set=20the=20=
speed=20to=2010=20(status:=200x0)
>=20[=20=20=2032.907976]=20eth0:=20XTemac:=20could=20not=20negotiate=20sp=
eed
>=20[=20=20=2033.921626]=20IP-Config:=20Complete:
>=20[=20=20=2033.924635]=20=20=20=20=20=20=20device=3Deth0,=20addr=3D192.=
168.0.223,=20mask=3D255.255.255.0,=20gw=3D192.168.0.1,
>=20[=20=20=2033.932418]=20=20=20=20=20=20host=3DLM200,=20domain=3D,=20ni=
s-domain=3D(none),
>=20[=20=20=2033.937715]=20=20=20=20=20=20bootserver=3D192.168.0.141,=20r=
ootserver=3D192.168.0.141,=20rootpath=3D
>=20[=20=20=2033.946230]=20Looking=20up=20port=20of=20RPC=20100003/2=20on=
=20192.168.0.141
>=20[=20=20=2034.916694]=20eth0:=20XTemac:=20PHY=20Link=20carrier=20lost.=
>=20
>=20My=20TEMAC=20core=20version=20is=203.00.a=20and=20low=20level=20code=20=
I'm=20using=20is=20working=20in=20u-boot=20wi
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: Linux w/ML403 PLB TEMAC
2007-04-05 0:00 ` Rick Moleres
@ 2007-04-05 18:04 ` Leonid
0 siblings, 0 replies; 14+ messages in thread
From: Leonid @ 2007-04-05 18:04 UTC (permalink / raw)
To: Rick Moleres, linuxppc-embedded
I have just learnt that MDIO lines are not connected in our design... =
that explains everything... thanks a lot.
Leonid.
-----Original Message-----
From: Rick Moleres [mailto:Rick.Moleres@xilinx.com]=20
Sent: Wednesday, April 04, 2007 5:00 PM
To: Leonid; linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
Leonid,
If it's not the ML403 board and the FX part is CES4 or later (read this =
at the bottom of the FX chip), then you will need hard_temac_v3_00_b to =
get the MDIO access working properly.
If this is pre-CES4 silicon, then hard_temac_v3_00_a is the right =
version and there may be an issue with the MDIO signal connectivity in =
your design (? just guessing). You can also try to hardcode the PHY =
address (gmii_addr) and see if the speed detection works at that point - =
but my guess is it won't.
-Rick
-----Original Message-----
From: Leonid [mailto:Leonid@a-k-a.net]=20
Sent: Wednesday, April 04, 2007 5:50 PM
To: Rick Moleres; linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
Hi, Rick:
We have both in our design and both are 3.00a. I'm not sure why - I'll =
ask our HW folks.=20
I have actually managed (just 30 minutes ago) to bring up network =
interface but I have commented out all accesses to PHY in your adapter.c =
and I set speed to 1000 always (see my adapter.c attached). Without =
these changes packets are not transmitted out of board.
This is probably some issue in my EDK project.
I'm not using ML403 actually but another proprietary board, based on =
Virtex
4 (69FX) FPGA.
Thanks,
Leonid.
-----Original Message-----
From: Rick Moleres [mailto:Rick.Moleres@xilinx.com]=20
Sent: Wednesday, April 04, 2007 4:41 PM
To: Leonid; Glenn.G.Hart@us.westinghouse.com; =
linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
Leonid,
You mentioned that the TEMAC version if v3.00a. Is this the plb_temac =
version or the hard_temac version, or both?
-Rick
-----Original Message-----
From: linuxppc-embedded-bounces+moleres=3Dxilinx.com@ozlabs.org =
[mailto:linuxppc-embedded-bounces+moleres=3Dxilinx.com@ozlabs.org] On =
Behalf Of Leonid
Sent: Wednesday, April 04, 2007 4:14 PM
To: Glenn.G.Hart@us.westinghouse.com; linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
I have investigated little bit more. Receive is working actually, but =
transmit doesn't. What can it be?
-----Original Message-----
From: linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org =
[mailto:linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org] On =
Behalf Of Leonid
Sent: Wednesday, April 04, 2007 12:06 PM
To: Glenn.G.Hart@us.westinghouse.com; linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
I have precisely the same problem you have described:
[ 0.430515] XTemac: using FIFO direct interrupt driven mode.
[ 0.437461] eth%d: XTemac: No PHY detected. Assuming a PHY at =
address 0
[ 0.445295] eth0: Xilinx TEMAC #0 at 0x02000000 mapped to 0xC3000000, =
irq=3D0
[ 0.452256] eth0: XTemac id 1.0f, block id 5, type 8
[ 0.458665] tun: Universal TUN/TAP device driver, 1.6
[ 0.463712] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 0.471106] mice: PS/2 mouse device common for all mice
[ 0.476339] TCP cubic registered
[ 0.479615] NET: Registered protocol family 1
[ 0.484032] NET: Registered protocol family 17
[ 0.992599] eth0: XTemac: Options: 0xb8f2
[ 12.955691] eth0: XTemac: Not able to set the speed to 1000 (status: =
0x0)
[ 22.928615] eth0: XTemac: Not able to set the speed to 100 (status: =
0x0)
[ 32.901449] eth0: XTemac: Not able to set the speed to 10 (status: =
0x0)
[ 32.907976] eth0: XTemac: could not negotiate speed
[ 33.921626] IP-Config: Complete:
[ 33.924635] device=3Deth0, addr=3D192.168.0.223, =
mask=3D255.255.255.0, gw=3D192.168.0.1,
[ 33.932418] host=3DLM200, domain=3D, nis-domain=3D(none),
[ 33.937715] bootserver=3D192.168.0.141, =
rootserver=3D192.168.0.141, rootpath=3D
[ 33.946230] Looking up port of RPC 100003/2 on 192.168.0.141
[ 34.916694] eth0: XTemac: PHY Link carrier lost.
My TEMAC core version is 3.00.a and low level code I'm using is working =
in u-boot without problems. I use Rick's adapter and also tried Ming's =
trick to set hardcoded speed value but with no success.
I suspect something is configured wrong - phys is not detected:
[ 0.437461] eth%d: XTemac: No PHY detected. Assuming a PHY at =
address 0
Leonid.
-----Original Message-----
From: linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org =
[mailto:linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org] On =
Behalf Of Glenn.G.Hart@us.westinghouse.com
Sent: Wednesday, February 14, 2007 6:48 AM
To: linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
Ming/Rick,
I tried setting the speed to 1000 as below, but it did not change the
result. I also tried Rick's new adapter.c with the same results. =
Changing
the hard_temac_v3_b to hard_temac_v3_a was the change I needed.
Unfortunately, the speed of the network is much slower now. I switched =
to
DMA and then changed the Linux drivers for the DMA & TEMAC v2 to v3.
I have my own program to test performance. It seems everything is so =
slow
it does not every complete to give me the statistics. My ping are also
slower. I used to be able to ping my computer and get 0.6-0.7 ms times.
With the DMA and TEMAC v3 I am now getting 1.8 ms times.
I am now not sure if it is my build or my PPC design. For the PPC =
design I
have a minimum PPC with OPB-RS232, PLB-DDR, and PLB-TEMAC. I use all =
the
defaults from BSB except I check use interrupt on the RS232 and TEMAC.
Any suggestions?
Thanks,
Glenn
=
=20
(Embedded "Ming Liu" <eemingliu@hotmail.com>@ozlabs.org =
=20
image moved 02/12/2007 11:48 AM =
=20
to file: =
=20
pic04169.pcx) =
=20
=
=20
=
=20
Sent by:
=
linuxppc-embedded-bounces+glenn.g.hart=3Dus.westinghouse.com@ozlabs.org
To: Glenn.G.Hart@us.westinghouse.com
cc: linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
Security Level:? Internal
Dear Glenn,
>3. The speed of the network was very poor. I wanted to implement DMA =
for
>the TEMAC. I created a new PPC with BSB using DMA on the TEMAC. =
Kernel
>recompilied without a problem, but upon starting the kernel I got:
In fact, the old cores of TEMAC(plb_temac 2.00 & hard_temac 1.00) also
support DMA. But of course the 3.00 cores are prefered because of other
improved features.
>6. I am using busybox 1.2.1 which worked fine previously configuring =
the
>network. Now when I execute ifconfig I get the following problem:
>[ 12.228721] eth0: XTemac: Options: 0xb8f2
>[ 24.197749] eth0: XTemac: Not able to set the speed to 1000 (status:
>0x148)
>[ 34.215593] eth0: XTemac: Not able to set the speed to 100 (status:
>0x148)
>[ 44.232349] eth0: XTemac: Not able to set the speed to 10 (status:
>0x148)
>[ 44.313727] eth0: XTemac: could not negotiate speed
>[ 44.372226] eth0: XTemac: Send Threshold =3D 16, Receive Threshold =
=3D 2
>[ 44.448421] eth0: XTemac: Send Wait bound =3D 1, Receive Wait bound =
=3D 1
># [ 57.180152] eth0: XTemac: PHY Link carrier lost.
I also had such a problem before. To solve such a problem most quickly, =
you
can just specify a fixed speed (like 1000Mbps) in adapter.c file. In =
this
file, after the line of "/* Get current link speed */ (around L378) and
"phylinkspeed =3D (RegValue & MARVELL_88E1111_LINKSPEED_MARK)>>
MARVELL_88E1111_LINKSPEED_SHIFT;", I just add and specify the speed as
"phylinkspeed =3D MARVELL_88E1111_LINKSPEED_1000M;" Of course with this
method, the speed cannot be auto-negotiated any more.
Another hints: I remember that there is another post from Rick on the
updated "adapter.c" a few days ago. Maybe that could solve your problem. =
I
didn't try that before. So if you will try, pls let us know the result. =
:)
BR
Ming
_________________________________________________________________
=CF=ED=D3=C3=CA=C0=BD=E7=C9=CF=D7=EE=B4=F3=B5=C4=B5=E7=D7=D3=D3=CA=BC=FE=CF=
=B5=CD=B3=A1=AA MSN Hotmail=A1=A3 http://www.hotmail.com
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: Linux w/ML403 PLB TEMAC
[not found] <406A31B117F2734987636D6CCC93EE3C013E20B0@ehost011-3.exch011.intermedia.net>
@ 2007-04-05 0:00 ` Rick Moleres
2007-04-05 18:04 ` Leonid
0 siblings, 1 reply; 14+ messages in thread
From: Rick Moleres @ 2007-04-05 0:00 UTC (permalink / raw)
To: Leonid, linuxppc-embedded
Leonid,
If it's not the ML403 board and the FX part is CES4 or later (read this =
at the bottom of the FX chip), then you will need hard_temac_v3_00_b to =
get the MDIO access working properly.
If this is pre-CES4 silicon, then hard_temac_v3_00_a is the right =
version and there may be an issue with the MDIO signal connectivity in =
your design (? just guessing). You can also try to hardcode the PHY =
address (gmii_addr) and see if the speed detection works at that point - =
but my guess is it won't.
-Rick
-----Original Message-----
From: Leonid [mailto:Leonid@a-k-a.net]=20
Sent: Wednesday, April 04, 2007 5:50 PM
To: Rick Moleres; linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
Hi, Rick:
We have both in our design and both are 3.00a. I'm not sure why - I'll =
ask our HW folks.=20
I have actually managed (just 30 minutes ago) to bring up network =
interface but I have commented out all accesses to PHY in your adapter.c =
and I set speed to 1000 always (see my adapter.c attached). Without =
these changes packets are not transmitted out of board.
This is probably some issue in my EDK project.
I'm not using ML403 actually but another proprietary board, based on =
Virtex
4 (69FX) FPGA.
Thanks,
Leonid.
-----Original Message-----
From: Rick Moleres [mailto:Rick.Moleres@xilinx.com]=20
Sent: Wednesday, April 04, 2007 4:41 PM
To: Leonid; Glenn.G.Hart@us.westinghouse.com; =
linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
Leonid,
You mentioned that the TEMAC version if v3.00a. Is this the plb_temac =
version or the hard_temac version, or both?
-Rick
-----Original Message-----
From: linuxppc-embedded-bounces+moleres=3Dxilinx.com@ozlabs.org =
[mailto:linuxppc-embedded-bounces+moleres=3Dxilinx.com@ozlabs.org] On =
Behalf Of Leonid
Sent: Wednesday, April 04, 2007 4:14 PM
To: Glenn.G.Hart@us.westinghouse.com; linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
I have investigated little bit more. Receive is working actually, but =
transmit doesn't. What can it be?
-----Original Message-----
From: linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org =
[mailto:linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org] On =
Behalf Of Leonid
Sent: Wednesday, April 04, 2007 12:06 PM
To: Glenn.G.Hart@us.westinghouse.com; linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
I have precisely the same problem you have described:
[ 0.430515] XTemac: using FIFO direct interrupt driven mode.
[ 0.437461] eth%d: XTemac: No PHY detected. Assuming a PHY at =
address 0
[ 0.445295] eth0: Xilinx TEMAC #0 at 0x02000000 mapped to 0xC3000000, =
irq=3D0
[ 0.452256] eth0: XTemac id 1.0f, block id 5, type 8
[ 0.458665] tun: Universal TUN/TAP device driver, 1.6
[ 0.463712] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 0.471106] mice: PS/2 mouse device common for all mice
[ 0.476339] TCP cubic registered
[ 0.479615] NET: Registered protocol family 1
[ 0.484032] NET: Registered protocol family 17
[ 0.992599] eth0: XTemac: Options: 0xb8f2
[ 12.955691] eth0: XTemac: Not able to set the speed to 1000 (status: =
0x0)
[ 22.928615] eth0: XTemac: Not able to set the speed to 100 (status: =
0x0)
[ 32.901449] eth0: XTemac: Not able to set the speed to 10 (status: =
0x0)
[ 32.907976] eth0: XTemac: could not negotiate speed
[ 33.921626] IP-Config: Complete:
[ 33.924635] device=3Deth0, addr=3D192.168.0.223, =
mask=3D255.255.255.0, gw=3D192.168.0.1,
[ 33.932418] host=3DLM200, domain=3D, nis-domain=3D(none),
[ 33.937715] bootserver=3D192.168.0.141, =
rootserver=3D192.168.0.141, rootpath=3D
[ 33.946230] Looking up port of RPC 100003/2 on 192.168.0.141
[ 34.916694] eth0: XTemac: PHY Link carrier lost.
My TEMAC core version is 3.00.a and low level code I'm using is working =
in u-boot without problems. I use Rick's adapter and also tried Ming's =
trick to set hardcoded speed value but with no success.
I suspect something is configured wrong - phys is not detected:
[ 0.437461] eth%d: XTemac: No PHY detected. Assuming a PHY at =
address 0
Leonid.
-----Original Message-----
From: linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org =
[mailto:linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org] On =
Behalf Of Glenn.G.Hart@us.westinghouse.com
Sent: Wednesday, February 14, 2007 6:48 AM
To: linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
Ming/Rick,
I tried setting the speed to 1000 as below, but it did not change the
result. I also tried Rick's new adapter.c with the same results. =
Changing
the hard_temac_v3_b to hard_temac_v3_a was the change I needed.
Unfortunately, the speed of the network is much slower now. I switched =
to
DMA and then changed the Linux drivers for the DMA & TEMAC v2 to v3.
I have my own program to test performance. It seems everything is so =
slow
it does not every complete to give me the statistics. My ping are also
slower. I used to be able to ping my computer and get 0.6-0.7 ms times.
With the DMA and TEMAC v3 I am now getting 1.8 ms times.
I am now not sure if it is my build or my PPC design. For the PPC =
design I
have a minimum PPC with OPB-RS232, PLB-DDR, and PLB-TEMAC. I use all =
the
defaults from BSB except I check use interrupt on the RS232 and TEMAC.
Any suggestions?
Thanks,
Glenn
=
=20
(Embedded "Ming Liu" <eemingliu@hotmail.com>@ozlabs.org =
=20
image moved 02/12/2007 11:48 AM =
=20
to file: =
=20
pic04169.pcx) =
=20
=
=20
=
=20
Sent by:
=
linuxppc-embedded-bounces+glenn.g.hart=3Dus.westinghouse.com@ozlabs.org
To: Glenn.G.Hart@us.westinghouse.com
cc: linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
Security Level:? Internal
Dear Glenn,
>3. The speed of the network was very poor. I wanted to implement DMA =
for
>the TEMAC. I created a new PPC with BSB using DMA on the TEMAC. =
Kernel
>recompilied without a problem, but upon starting the kernel I got:
In fact, the old cores of TEMAC(plb_temac 2.00 & hard_temac 1.00) also
support DMA. But of course the 3.00 cores are prefered because of other
improved features.
>6. I am using busybox 1.2.1 which worked fine previously configuring =
the
>network. Now when I execute ifconfig I get the following problem:
>[ 12.228721] eth0: XTemac: Options: 0xb8f2
>[ 24.197749] eth0: XTemac: Not able to set the speed to 1000 (status:
>0x148)
>[ 34.215593] eth0: XTemac: Not able to set the speed to 100 (status:
>0x148)
>[ 44.232349] eth0: XTemac: Not able to set the speed to 10 (status:
>0x148)
>[ 44.313727] eth0: XTemac: could not negotiate speed
>[ 44.372226] eth0: XTemac: Send Threshold =3D 16, Receive Threshold =
=3D 2
>[ 44.448421] eth0: XTemac: Send Wait bound =3D 1, Receive Wait bound =
=3D 1
># [ 57.180152] eth0: XTemac: PHY Link carrier lost.
I also had such a problem before. To solve such a problem most quickly, =
you
can just specify a fixed speed (like 1000Mbps) in adapter.c file. In =
this
file, after the line of "/* Get current link speed */ (around L378) and
"phylinkspeed =3D (RegValue & MARVELL_88E1111_LINKSPEED_MARK)>>
MARVELL_88E1111_LINKSPEED_SHIFT;", I just add and specify the speed as
"phylinkspeed =3D MARVELL_88E1111_LINKSPEED_1000M;" Of course with this
method, the speed cannot be auto-negotiated any more.
Another hints: I remember that there is another post from Rick on the
updated "adapter.c" a few days ago. Maybe that could solve your problem. =
I
didn't try that before. So if you will try, pls let us know the result. =
:)
BR
Ming
_________________________________________________________________
=CF=ED=D3=C3=CA=C0=BD=E7=C9=CF=D7=EE=B4=F3=B5=C4=B5=E7=D7=D3=D3=CA=BC=FE=CF=
=B5=CD=B3=A1=AA MSN Hotmail=A1=A3 http://www.hotmail.com
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: Linux w/ML403 PLB TEMAC
2007-04-04 22:13 ` Leonid
@ 2007-04-04 23:40 ` Rick Moleres
0 siblings, 0 replies; 14+ messages in thread
From: Rick Moleres @ 2007-04-04 23:40 UTC (permalink / raw)
To: Leonid, Glenn.G.Hart, linuxppc-embedded
Leonid,
You mentioned that the TEMAC version if v3.00a. Is this the plb_temac =
version or the hard_temac version, or both?
-Rick
-----Original Message-----
From: linuxppc-embedded-bounces+moleres=3Dxilinx.com@ozlabs.org =
[mailto:linuxppc-embedded-bounces+moleres=3Dxilinx.com@ozlabs.org] On =
Behalf Of Leonid
Sent: Wednesday, April 04, 2007 4:14 PM
To: Glenn.G.Hart@us.westinghouse.com; linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
I have investigated little bit more. Receive is working actually, but =
transmit doesn't. What can it be?
-----Original Message-----
From: linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org =
[mailto:linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org] On =
Behalf Of Leonid
Sent: Wednesday, April 04, 2007 12:06 PM
To: Glenn.G.Hart@us.westinghouse.com; linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
I have precisely the same problem you have described:
[ 0.430515] XTemac: using FIFO direct interrupt driven mode.
[ 0.437461] eth%d: XTemac: No PHY detected. Assuming a PHY at =
address 0
[ 0.445295] eth0: Xilinx TEMAC #0 at 0x02000000 mapped to 0xC3000000, =
irq=3D0
[ 0.452256] eth0: XTemac id 1.0f, block id 5, type 8
[ 0.458665] tun: Universal TUN/TAP device driver, 1.6
[ 0.463712] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 0.471106] mice: PS/2 mouse device common for all mice
[ 0.476339] TCP cubic registered
[ 0.479615] NET: Registered protocol family 1
[ 0.484032] NET: Registered protocol family 17
[ 0.992599] eth0: XTemac: Options: 0xb8f2
[ 12.955691] eth0: XTemac: Not able to set the speed to 1000 (status: =
0x0)
[ 22.928615] eth0: XTemac: Not able to set the speed to 100 (status: =
0x0)
[ 32.901449] eth0: XTemac: Not able to set the speed to 10 (status: =
0x0)
[ 32.907976] eth0: XTemac: could not negotiate speed
[ 33.921626] IP-Config: Complete:
[ 33.924635] device=3Deth0, addr=3D192.168.0.223, =
mask=3D255.255.255.0, gw=3D192.168.0.1,
[ 33.932418] host=3DLM200, domain=3D, nis-domain=3D(none),
[ 33.937715] bootserver=3D192.168.0.141, =
rootserver=3D192.168.0.141, rootpath=3D
[ 33.946230] Looking up port of RPC 100003/2 on 192.168.0.141
[ 34.916694] eth0: XTemac: PHY Link carrier lost.
My TEMAC core version is 3.00.a and low level code I'm using is working =
in u-boot without problems. I use Rick's adapter and also tried Ming's =
trick to set hardcoded speed value but with no success.
I suspect something is configured wrong - phys is not detected:
[ 0.437461] eth%d: XTemac: No PHY detected. Assuming a PHY at =
address 0
Leonid.
-----Original Message-----
From: linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org =
[mailto:linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org] On =
Behalf Of Glenn.G.Hart@us.westinghouse.com
Sent: Wednesday, February 14, 2007 6:48 AM
To: linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
Ming/Rick,
I tried setting the speed to 1000 as below, but it did not change the
result. I also tried Rick's new adapter.c with the same results. =
Changing
the hard_temac_v3_b to hard_temac_v3_a was the change I needed.
Unfortunately, the speed of the network is much slower now. I switched =
to
DMA and then changed the Linux drivers for the DMA & TEMAC v2 to v3.
I have my own program to test performance. It seems everything is so =
slow
it does not every complete to give me the statistics. My ping are also
slower. I used to be able to ping my computer and get 0.6-0.7 ms times.
With the DMA and TEMAC v3 I am now getting 1.8 ms times.
I am now not sure if it is my build or my PPC design. For the PPC =
design I
have a minimum PPC with OPB-RS232, PLB-DDR, and PLB-TEMAC. I use all =
the
defaults from BSB except I check use interrupt on the RS232 and TEMAC.
Any suggestions?
Thanks,
Glenn
=
=20
(Embedded "Ming Liu" <eemingliu@hotmail.com>@ozlabs.org =
=20
image moved 02/12/2007 11:48 AM =
=20
to file: =
=20
pic04169.pcx) =
=20
=
=20
=
=20
Sent by:
=
linuxppc-embedded-bounces+glenn.g.hart=3Dus.westinghouse.com@ozlabs.org
To: Glenn.G.Hart@us.westinghouse.com
cc: linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
Security Level:? Internal
Dear Glenn,
>3. The speed of the network was very poor. I wanted to implement DMA =
for
>the TEMAC. I created a new PPC with BSB using DMA on the TEMAC. =
Kernel
>recompilied without a problem, but upon starting the kernel I got:
In fact, the old cores of TEMAC(plb_temac 2.00 & hard_temac 1.00) also
support DMA. But of course the 3.00 cores are prefered because of other
improved features.
>6. I am using busybox 1.2.1 which worked fine previously configuring =
the
>network. Now when I execute ifconfig I get the following problem:
>[ 12.228721] eth0: XTemac: Options: 0xb8f2
>[ 24.197749] eth0: XTemac: Not able to set the speed to 1000 (status:
>0x148)
>[ 34.215593] eth0: XTemac: Not able to set the speed to 100 (status:
>0x148)
>[ 44.232349] eth0: XTemac: Not able to set the speed to 10 (status:
>0x148)
>[ 44.313727] eth0: XTemac: could not negotiate speed
>[ 44.372226] eth0: XTemac: Send Threshold =3D 16, Receive Threshold =
=3D 2
>[ 44.448421] eth0: XTemac: Send Wait bound =3D 1, Receive Wait bound =
=3D 1
># [ 57.180152] eth0: XTemac: PHY Link carrier lost.
I also had such a problem before. To solve such a problem most quickly, =
you
can just specify a fixed speed (like 1000Mbps) in adapter.c file. In =
this
file, after the line of "/* Get current link speed */ (around L378) and
"phylinkspeed =3D (RegValue & MARVELL_88E1111_LINKSPEED_MARK)>>
MARVELL_88E1111_LINKSPEED_SHIFT;", I just add and specify the speed as
"phylinkspeed =3D MARVELL_88E1111_LINKSPEED_1000M;" Of course with this
method, the speed cannot be auto-negotiated any more.
Another hints: I remember that there is another post from Rick on the
updated "adapter.c" a few days ago. Maybe that could solve your problem. =
I
didn't try that before. So if you will try, pls let us know the result. =
:)
BR
Ming
_________________________________________________________________
=CF=ED=D3=C3=CA=C0=BD=E7=C9=CF=D7=EE=B4=F3=B5=C4=B5=E7=D7=D3=D3=CA=BC=FE=CF=
=B5=CD=B3=A1=AA MSN Hotmail=A1=A3 http://www.hotmail.com
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: Linux w/ML403 PLB TEMAC
2007-04-04 19:05 ` Leonid
@ 2007-04-04 22:13 ` Leonid
2007-04-04 23:40 ` Rick Moleres
0 siblings, 1 reply; 14+ messages in thread
From: Leonid @ 2007-04-04 22:13 UTC (permalink / raw)
To: Glenn.G.Hart, linuxppc-embedded
I have investigated little bit more. Receive is working actually, but =
transmit doesn't. What can it be?
-----Original Message-----
From: linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org =
[mailto:linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org] On =
Behalf Of Leonid
Sent: Wednesday, April 04, 2007 12:06 PM
To: Glenn.G.Hart@us.westinghouse.com; linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
I have precisely the same problem you have described:
[ 0.430515] XTemac: using FIFO direct interrupt driven mode.
[ 0.437461] eth%d: XTemac: No PHY detected. Assuming a PHY at =
address 0
[ 0.445295] eth0: Xilinx TEMAC #0 at 0x02000000 mapped to 0xC3000000, =
irq=3D0
[ 0.452256] eth0: XTemac id 1.0f, block id 5, type 8
[ 0.458665] tun: Universal TUN/TAP device driver, 1.6
[ 0.463712] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 0.471106] mice: PS/2 mouse device common for all mice
[ 0.476339] TCP cubic registered
[ 0.479615] NET: Registered protocol family 1
[ 0.484032] NET: Registered protocol family 17
[ 0.992599] eth0: XTemac: Options: 0xb8f2
[ 12.955691] eth0: XTemac: Not able to set the speed to 1000 (status: =
0x0)
[ 22.928615] eth0: XTemac: Not able to set the speed to 100 (status: =
0x0)
[ 32.901449] eth0: XTemac: Not able to set the speed to 10 (status: =
0x0)
[ 32.907976] eth0: XTemac: could not negotiate speed
[ 33.921626] IP-Config: Complete:
[ 33.924635] device=3Deth0, addr=3D192.168.0.223, =
mask=3D255.255.255.0, gw=3D192.168.0.1,
[ 33.932418] host=3DLM200, domain=3D, nis-domain=3D(none),
[ 33.937715] bootserver=3D192.168.0.141, =
rootserver=3D192.168.0.141, rootpath=3D
[ 33.946230] Looking up port of RPC 100003/2 on 192.168.0.141
[ 34.916694] eth0: XTemac: PHY Link carrier lost.
My TEMAC core version is 3.00.a and low level code I'm using is working =
in u-boot without problems. I use Rick's adapter and also tried Ming's =
trick to set hardcoded speed value but with no success.
I suspect something is configured wrong - phys is not detected:
[ 0.437461] eth%d: XTemac: No PHY detected. Assuming a PHY at =
address 0
Leonid.
-----Original Message-----
From: linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org =
[mailto:linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org] On =
Behalf Of Glenn.G.Hart@us.westinghouse.com
Sent: Wednesday, February 14, 2007 6:48 AM
To: linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
Ming/Rick,
I tried setting the speed to 1000 as below, but it did not change the
result. I also tried Rick's new adapter.c with the same results. =
Changing
the hard_temac_v3_b to hard_temac_v3_a was the change I needed.
Unfortunately, the speed of the network is much slower now. I switched =
to
DMA and then changed the Linux drivers for the DMA & TEMAC v2 to v3.
I have my own program to test performance. It seems everything is so =
slow
it does not every complete to give me the statistics. My ping are also
slower. I used to be able to ping my computer and get 0.6-0.7 ms times.
With the DMA and TEMAC v3 I am now getting 1.8 ms times.
I am now not sure if it is my build or my PPC design. For the PPC =
design I
have a minimum PPC with OPB-RS232, PLB-DDR, and PLB-TEMAC. I use all =
the
defaults from BSB except I check use interrupt on the RS232 and TEMAC.
Any suggestions?
Thanks,
Glenn
=
=20
(Embedded "Ming Liu" <eemingliu@hotmail.com>@ozlabs.org =
=20
image moved 02/12/2007 11:48 AM =
=20
to file: =
=20
pic04169.pcx) =
=20
=
=20
=
=20
Sent by:
=
linuxppc-embedded-bounces+glenn.g.hart=3Dus.westinghouse.com@ozlabs.org
To: Glenn.G.Hart@us.westinghouse.com
cc: linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
Security Level:? Internal
Dear Glenn,
>3. The speed of the network was very poor. I wanted to implement DMA =
for
>the TEMAC. I created a new PPC with BSB using DMA on the TEMAC. =
Kernel
>recompilied without a problem, but upon starting the kernel I got:
In fact, the old cores of TEMAC(plb_temac 2.00 & hard_temac 1.00) also
support DMA. But of course the 3.00 cores are prefered because of other
improved features.
>6. I am using busybox 1.2.1 which worked fine previously configuring =
the
>network. Now when I execute ifconfig I get the following problem:
>[ 12.228721] eth0: XTemac: Options: 0xb8f2
>[ 24.197749] eth0: XTemac: Not able to set the speed to 1000 (status:
>0x148)
>[ 34.215593] eth0: XTemac: Not able to set the speed to 100 (status:
>0x148)
>[ 44.232349] eth0: XTemac: Not able to set the speed to 10 (status:
>0x148)
>[ 44.313727] eth0: XTemac: could not negotiate speed
>[ 44.372226] eth0: XTemac: Send Threshold =3D 16, Receive Threshold =
=3D 2
>[ 44.448421] eth0: XTemac: Send Wait bound =3D 1, Receive Wait bound =
=3D 1
># [ 57.180152] eth0: XTemac: PHY Link carrier lost.
I also had such a problem before. To solve such a problem most quickly, =
you
can just specify a fixed speed (like 1000Mbps) in adapter.c file. In =
this
file, after the line of "/* Get current link speed */ (around L378) and
"phylinkspeed =3D (RegValue & MARVELL_88E1111_LINKSPEED_MARK)>>
MARVELL_88E1111_LINKSPEED_SHIFT;", I just add and specify the speed as
"phylinkspeed =3D MARVELL_88E1111_LINKSPEED_1000M;" Of course with this
method, the speed cannot be auto-negotiated any more.
Another hints: I remember that there is another post from Rick on the
updated "adapter.c" a few days ago. Maybe that could solve your problem. =
I
didn't try that before. So if you will try, pls let us know the result. =
:)
BR
Ming
_________________________________________________________________
=CF=ED=D3=C3=CA=C0=BD=E7=C9=CF=D7=EE=B4=F3=B5=C4=B5=E7=D7=D3=D3=CA=BC=FE=CF=
=B5=CD=B3=A1=AA MSN Hotmail=A1=A3 http://www.hotmail.com
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: Linux w/ML403 PLB TEMAC
2007-02-14 14:47 Glenn.G.Hart
2007-02-14 15:10 ` Ming Liu
@ 2007-04-04 19:05 ` Leonid
2007-04-04 22:13 ` Leonid
1 sibling, 1 reply; 14+ messages in thread
From: Leonid @ 2007-04-04 19:05 UTC (permalink / raw)
To: Glenn.G.Hart, linuxppc-embedded
I have precisely the same problem you have described:
[ 0.430515] XTemac: using FIFO direct interrupt driven mode.
[ 0.437461] eth%d: XTemac: No PHY detected. Assuming a PHY at =
address 0
[ 0.445295] eth0: Xilinx TEMAC #0 at 0x02000000 mapped to 0xC3000000, =
irq=3D0
[ 0.452256] eth0: XTemac id 1.0f, block id 5, type 8
[ 0.458665] tun: Universal TUN/TAP device driver, 1.6
[ 0.463712] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 0.471106] mice: PS/2 mouse device common for all mice
[ 0.476339] TCP cubic registered
[ 0.479615] NET: Registered protocol family 1
[ 0.484032] NET: Registered protocol family 17
[ 0.992599] eth0: XTemac: Options: 0xb8f2
[ 12.955691] eth0: XTemac: Not able to set the speed to 1000 (status: =
0x0)
[ 22.928615] eth0: XTemac: Not able to set the speed to 100 (status: =
0x0)
[ 32.901449] eth0: XTemac: Not able to set the speed to 10 (status: =
0x0)
[ 32.907976] eth0: XTemac: could not negotiate speed
[ 33.921626] IP-Config: Complete:
[ 33.924635] device=3Deth0, addr=3D192.168.0.223, =
mask=3D255.255.255.0, gw=3D192.168.0.1,
[ 33.932418] host=3DLM200, domain=3D, nis-domain=3D(none),
[ 33.937715] bootserver=3D192.168.0.141, =
rootserver=3D192.168.0.141, rootpath=3D
[ 33.946230] Looking up port of RPC 100003/2 on 192.168.0.141
[ 34.916694] eth0: XTemac: PHY Link carrier lost.
My TEMAC core version is 3.00.a and low level code I'm using is working =
in u-boot without problems. I use Rick's adapter and also tried Ming's =
trick to set hardcoded speed value but with no success.
I suspect something is configured wrong - phys is not detected:
[ 0.437461] eth%d: XTemac: No PHY detected. Assuming a PHY at =
address 0
Leonid.
-----Original Message-----
From: linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org =
[mailto:linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org] On =
Behalf Of Glenn.G.Hart@us.westinghouse.com
Sent: Wednesday, February 14, 2007 6:48 AM
To: linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
Ming/Rick,
I tried setting the speed to 1000 as below, but it did not change the
result. I also tried Rick's new adapter.c with the same results. =
Changing
the hard_temac_v3_b to hard_temac_v3_a was the change I needed.
Unfortunately, the speed of the network is much slower now. I switched =
to
DMA and then changed the Linux drivers for the DMA & TEMAC v2 to v3.
I have my own program to test performance. It seems everything is so =
slow
it does not every complete to give me the statistics. My ping are also
slower. I used to be able to ping my computer and get 0.6-0.7 ms times.
With the DMA and TEMAC v3 I am now getting 1.8 ms times.
I am now not sure if it is my build or my PPC design. For the PPC =
design I
have a minimum PPC with OPB-RS232, PLB-DDR, and PLB-TEMAC. I use all =
the
defaults from BSB except I check use interrupt on the RS232 and TEMAC.
Any suggestions?
Thanks,
Glenn
=
=20
(Embedded "Ming Liu" <eemingliu@hotmail.com>@ozlabs.org =
=20
image moved 02/12/2007 11:48 AM =
=20
to file: =
=20
pic04169.pcx) =
=20
=
=20
=
=20
Sent by:
=
linuxppc-embedded-bounces+glenn.g.hart=3Dus.westinghouse.com@ozlabs.org
To: Glenn.G.Hart@us.westinghouse.com
cc: linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
Security Level:? Internal
Dear Glenn,
>3. The speed of the network was very poor. I wanted to implement DMA =
for
>the TEMAC. I created a new PPC with BSB using DMA on the TEMAC. =
Kernel
>recompilied without a problem, but upon starting the kernel I got:
In fact, the old cores of TEMAC(plb_temac 2.00 & hard_temac 1.00) also
support DMA. But of course the 3.00 cores are prefered because of other
improved features.
>6. I am using busybox 1.2.1 which worked fine previously configuring =
the
>network. Now when I execute ifconfig I get the following problem:
>[ 12.228721] eth0: XTemac: Options: 0xb8f2
>[ 24.197749] eth0: XTemac: Not able to set the speed to 1000 (status:
>0x148)
>[ 34.215593] eth0: XTemac: Not able to set the speed to 100 (status:
>0x148)
>[ 44.232349] eth0: XTemac: Not able to set the speed to 10 (status:
>0x148)
>[ 44.313727] eth0: XTemac: could not negotiate speed
>[ 44.372226] eth0: XTemac: Send Threshold =3D 16, Receive Threshold =
=3D 2
>[ 44.448421] eth0: XTemac: Send Wait bound =3D 1, Receive Wait bound =
=3D 1
># [ 57.180152] eth0: XTemac: PHY Link carrier lost.
I also had such a problem before. To solve such a problem most quickly, =
you
can just specify a fixed speed (like 1000Mbps) in adapter.c file. In =
this
file, after the line of "/* Get current link speed */ (around L378) and
"phylinkspeed =3D (RegValue & MARVELL_88E1111_LINKSPEED_MARK)>>
MARVELL_88E1111_LINKSPEED_SHIFT;", I just add and specify the speed as
"phylinkspeed =3D MARVELL_88E1111_LINKSPEED_1000M;" Of course with this
method, the speed cannot be auto-negotiated any more.
Another hints: I remember that there is another post from Rick on the
updated "adapter.c" a few days ago. Maybe that could solve your problem. =
I
didn't try that before. So if you will try, pls let us know the result. =
:)
BR
Ming
_________________________________________________________________
=CF=ED=D3=C3=CA=C0=BD=E7=C9=CF=D7=EE=B4=F3=B5=C4=B5=E7=D7=D3=D3=CA=BC=FE=CF=
=B5=CD=B3=A1=AA MSN Hotmail=A1=A3 http://www.hotmail.com
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: Linux w/ML403 PLB TEMAC
2007-02-14 14:47 Glenn.G.Hart
@ 2007-02-14 15:10 ` Ming Liu
2007-04-04 19:05 ` Leonid
1 sibling, 0 replies; 14+ messages in thread
From: Ming Liu @ 2007-02-14 15:10 UTC (permalink / raw)
To: Glenn.G.Hart; +Cc: linuxppc-embedded
Hi Glenn,
>I have my own program to test performance. It seems everything is so slow
>it does not every complete to give me the statistics. My ping are also
>slower. I used to be able to ping my computer and get 0.6-0.7 ms times.
>With the DMA and TEMAC v3 I am now getting 1.8 ms times.
I am also struggling with the speed issue. :) Rick is the expert and I am
also asking him on this problem.
For your problem, I suggest you to use a general test software like netperf
first. Then it can bypass the problem in your own test program.
In my system, the ping speed is also slow. From board to pc is 2.1ms and
from pc to board is 1.8ms.
>I am now not sure if it is my build or my PPC design. For the PPC design
I
>have a minimum PPC with OPB-RS232, PLB-DDR, and PLB-TEMAC. I use all the
>defaults from BSB except I check use interrupt on the RS232 and TEMAC.
This should not be a problem because the platform is so common.
BR
Ming
_________________________________________________________________
与联机的朋友进行交流，请使用 MSN Messenger: http://messenger.msn.com/cn
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: Linux w/ML403 PLB TEMAC
@ 2007-02-14 14:47 Glenn.G.Hart
2007-02-14 15:10 ` Ming Liu
2007-04-04 19:05 ` Leonid
0 siblings, 2 replies; 14+ messages in thread
From: Glenn.G.Hart @ 2007-02-14 14:47 UTC (permalink / raw)
To: linuxppc-embedded
[-- Attachment #1: Type: text/plain, Size: 4065 bytes --]
Ming/Rick,
I tried setting the speed to 1000 as below, but it did not change the
result. I also tried Rick's new adapter.c with the same results. Changing
the hard_temac_v3_b to hard_temac_v3_a was the change I needed.
Unfortunately, the speed of the network is much slower now. I switched to
DMA and then changed the Linux drivers for the DMA & TEMAC v2 to v3.
I have my own program to test performance. It seems everything is so slow
it does not every complete to give me the statistics. My ping are also
slower. I used to be able to ping my computer and get 0.6-0.7 ms times.
With the DMA and TEMAC v3 I am now getting 1.8 ms times.
I am now not sure if it is my build or my PPC design. For the PPC design I
have a minimum PPC with OPB-RS232, PLB-DDR, and PLB-TEMAC. I use all the
defaults from BSB except I check use interrupt on the RS232 and TEMAC.
Any suggestions?
Thanks,
Glenn
(Embedded "Ming Liu" <eemingliu@hotmail.com>@ozlabs.org
image moved 02/12/2007 11:48 AM
to file:
pic04169.pcx)
Sent by:
linuxppc-embedded-bounces+glenn.g.hart=us.westinghouse.com@ozlabs.org
To: Glenn.G.Hart@us.westinghouse.com
cc: linuxppc-embedded@ozlabs.org
Subject: RE: Linux w/ML403 PLB TEMAC
Security Level:? Internal
Dear Glenn,
>3. The speed of the network was very poor. I wanted to implement DMA for
>the TEMAC. I created a new PPC with BSB using DMA on the TEMAC. Kernel
>recompilied without a problem, but upon starting the kernel I got:
In fact, the old cores of TEMAC(plb_temac 2.00 & hard_temac 1.00) also
support DMA. But of course the 3.00 cores are prefered because of other
improved features.
>6. I am using busybox 1.2.1 which worked fine previously configuring the
>network. Now when I execute ifconfig I get the following problem:
>[ 12.228721] eth0: XTemac: Options: 0xb8f2
>[ 24.197749] eth0: XTemac: Not able to set the speed to 1000 (status:
>0x148)
>[ 34.215593] eth0: XTemac: Not able to set the speed to 100 (status:
>0x148)
>[ 44.232349] eth0: XTemac: Not able to set the speed to 10 (status:
>0x148)
>[ 44.313727] eth0: XTemac: could not negotiate speed
>[ 44.372226] eth0: XTemac: Send Threshold = 16, Receive Threshold = 2
>[ 44.448421] eth0: XTemac: Send Wait bound = 1, Receive Wait bound = 1
># [ 57.180152] eth0: XTemac: PHY Link carrier lost.
I also had such a problem before. To solve such a problem most quickly, you
can just specify a fixed speed (like 1000Mbps) in adapter.c file. In this
file, after the line of "/* Get current link speed */ (around L378) and
"phylinkspeed = (RegValue & MARVELL_88E1111_LINKSPEED_MARK)>>
MARVELL_88E1111_LINKSPEED_SHIFT;", I just add and specify the speed as
"phylinkspeed = MARVELL_88E1111_LINKSPEED_1000M;" Of course with this
method, the speed cannot be auto-negotiated any more.
Another hints: I remember that there is another post from Rick on the
updated "adapter.c" a few days ago. Maybe that could solve your problem. I
didn't try that before. So if you will try, pls let us know the result. :)
BR
Ming
_________________________________________________________________
享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
[-- Attachment #2: pic04169.pcx --]
[-- Type: application/octet-stream, Size: 128 bytes --]
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2007-04-10 5:57 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-02-12 16:12 Linux w/ML403 PLB TEMAC Glenn.G.Hart
2007-02-12 16:33 ` Rick Moleres
2007-02-12 16:48 ` Ming Liu
2007-04-04 7:19 ` Leonid
2007-04-04 8:21 ` Andrei Konovalov
2007-02-14 14:47 Glenn.G.Hart
2007-02-14 15:10 ` Ming Liu
2007-04-04 19:05 ` Leonid
2007-04-04 22:13 ` Leonid
2007-04-04 23:40 ` Rick Moleres
[not found] <406A31B117F2734987636D6CCC93EE3C013E20B0@ehost011-3.exch011.intermedia.net>
2007-04-05 0:00 ` Rick Moleres
2007-04-05 18:04 ` Leonid
2007-04-09 16:35 Jarek
2007-04-10 5:57 ` Leonid
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.