TI中文支持网hi guys:
We are using AM335x and IP101AH. We port the u-boot from evm BSP. Now the problem is net interface doesn't work.
I ran #dhcp or #ping. there was always timeout and retry. I found there was no packet sent out.
What we have done:
1.change the pinmux, use beagle bone pin-mux. support {rmii1_pin_mux, PROFILE_ALL, DEV_ON_BASEBOARD} in beaglebone.
2.change the MII_SEL register to 0x4D. We use RMII1 & PEF_CLK FORM CHIPIN.
After this steps, I can't think out what else I should do. but the net interface kept not working.Then I noticed this structure:
static struct cpsw_slave_data cpsw_slaves[] = { { .slave_reg_ofs = 0x208, .sliver_reg_ofs = 0xd80, .phy_id = 0, }, { .slave_reg_ofs = 0x308, .sliver_reg_ofs = 0xdc0, .phy_id = 1, }, };
I wonder what is its what's the phy_id stand for? I once thought maybe slave_reg_ofs need modify, but I don't know what value it should be if it need change.
I find a topic when I was in despair. It says swap the phy_id value overcome the problem:
static struct cpsw_slave_data cpsw_slaves[] = { { .slave_reg_ofs = 0x208, .sliver_reg_ofs = 0xd80, .phy_id = 1, }, { .slave_reg_ofs = 0x308, .sliver_reg_ofs = 0xdc0, .phy_id = 0, }, };
Gary Wu：
你好！可以确认下你的PHY的设置。一般会有PHY_ID的三个管脚进行上下拉来决定PHY的ID
zai Jonathan：
回复 Gary Wu:
你好，
1. 这个PHY_ID的三个管脚是从哪里可以找到？
2. 还有就是这个配置这个是否会影响到驱动和slave的匹配。
Yaoming Qin：
回复 zai Jonathan:
这个可以看phy的spec
zai Jonathan：
回复 Yaoming Qin:
TRM or icplus datasheet
zai Jonathan：
回复 Yaoming Qin:
hi : Yao ming Qin
icplus ip101a已经OK了，谢谢你！
