Hi, We have a design based on the DM8148 and a BCM5461 Gigabit PHY. we use RGMII mode in our design.
Our problem is that the ethernet interface appears to can not work in u-boot. in u-boot we use cmd ping
ping 10.33.0.69link up on port 0, speed 100, full duplexUsing cpsw deviceping failed; host 10.33.0.69 is not alive
We think we have the PHY hooked up correctly . Is there ang special seting for BCM5461. thankssteve
Hello,
We have the same issue. We are using a DM8148 and a LSI ET1011C Gigabit PHY. We also using the RGMII mode in our design.
Any idea about what we are missing? Do we need to modify some drivers?
Thank you!
Kefil
Steve,Can you tell me which PSP/SDK software version your u-boot is based from?
When you mentioned that you have the PHY hooked up correctly, have you verified that all the clocks are good?One of the things to check would also be the GMII_SEL register (TRM 3.2.43 offset 0x48140650) as well as the pin muxing.
Regards,Benoit
If my reply answers your question then please click on the "Verify Answer" button.
Hi,
we use TI814X-LINUX-PSP-04.01.00.07 and PG2.1 SI,all the clocks are good.
GMII_SEL register is 0x30a.
I'm using a BCM54610 and had similar issues with it, see: http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/716/t/155890.aspx
Steve,
Given the information so far I assumed you have re-used the ti814x/evm.c code to setup the GMII_SEL and pinmux which being a PG2.1 silicon would sets it up for RGMII mode.Kyle's suggestion to disable the CPRGMII Internal Delay Mode is the next step. Try setting GMII_SEL to 0x33A.And see if that helps.
Stephen Turner
AudioScience, Inc
Kefil,
We are using the ET1011C as well and are having trouble getting an IP address. Did you ever get it to work properly? If so, do you mind sharing what change you had to make?
Many thanks,
-Ben
Did anyone using the ETC1011C have any issues getting it to work with the kernel once things were working correctly in u-boot. We have made the necessary changes to to boot over tftp. However, the system fails to send anything out onto the network when trying to use DHCP when booting the kernel to get NFS.
We are using Kernel 2.6.37. It fails with the following:
PHY 0:00 not foundCPSW phy found : id is : 0x282f014Sending DHCP requests .PHY: 0:01 - Link is Up - 100/Full.PHY: 0:01 - Link is DownPHY: 0:01 - Link is Up - 100/Full.... timed out!IP-Config: Retrying forever (NFS root)...PHY 0:00 not foundCPSW phy found : id is : 0x282f014Sending DHCP requests .PHY: 0:01 - Link is Up - 100/Full..... timed out!IP-Config: Retrying forever (NFS root)...PHY 0:00 not foundCPSW phy found : id is : 0x282f014Sending DHCP requests .PHY: 0:01 - Link is Up - 100/Full.
Thanks,
Mark
Yes,
We were able to make it work. The issue was hardware. Make sure that your hardware is configured properly to include the RGMII interface (BTMODE[9] on TI8148).
Regards,
Thank you for your answer. Right after I posted I found that there was another hard-coded phy id in the kernel as well as uboot. Problem solved!
We are using DM8148 processor on our board. We are using EMAC1 for our Ethernet interface . The data rate transfer happens only for 100Mbps.When we try setting our PC to 1000Mbps using mii-tool eth0 -r command and then do dhcp , auto negotiation happens and the speed will be reduced to 100Mbps automatically and the data transfer takes place. Same is the problem with 10Mbps. Our PC supports 10/100/1000Mbps speed.
Please can someone help us on this?
Thanks
Prakash
Hi Mark,
We met the same issue in kernel as yours, and we can do DHCP in uboot env, but can not get DHCP response, and see the same log file you posted here.
So we would like to know the details about the hard-coded phy id part. Does that mean the phy id is duplicated and not same with want you want? If the "CPSW phy found : id is : 0x282f014" is the right phy id you used?
Perry
We fixed the issue.
we need to change the GMII_SEL value in cpsw_probe() function, from 0x33a to 0x30a, add the internal delay.