TI中文支持网板子是自己的板子，套用OMAPL138_LCDK的SDK开发
硬件没问题，使用别人以前编译好的UBOOT 网络能PING通，但是那个没有源码 无法改功能
SDK ti-processor-sdk-linux-omapl138-lcdk-05.01.00.11
UBOOT 版本 u-boot-2018.01+gitAUTOINC+cdb1cc0a9e-gcdb1cc0a9e
omapl138_lcdk.h文件里面的改动
#undef CONFIG_MII (这个CONFIG_MII打开也试过，现象没区别)
#define CONFIG_DRIVER_TI_EMAC_USE_RMII
#define CONFIG_DRIVER_TI_EMAC_RMII_NO_NEGOTIATE
omapl138_lcdk.c文件里面的改动
改PINMUX
#ifdef CONFIG_DRIVER_TI_EMAC
static const struct pinmux_config emac_pins[] = {
{ pinmux(14), 8, 2 }, /* RMII_TXD[1] */
{ pinmux(14), 8, 3 }, /* RMII_TXD[0] */
{ pinmux(14), 8, 4 }, /* RMII_TXEN */
{ pinmux(14), 8, 5 }, /* RMII_RXD[1] */
{ pinmux(14), 8, 6 }, /* RMII_RXD[0] */
{ pinmux(14), 8, 7 }, /* RMII_RXER */
{ pinmux(15), 0, 0 }, /* RMII_MHz_50_CLK */
{ pinmux(15), 8, 1 }, /* RMII_CRS_DV */
{ pinmux(4), 8, 0 },
{ pinmux(4), 8, 1 }
};
#endif /* CONFIG_DRIVER_TI_EMAC */
这里mode_sel也选了RMII
#ifdef CONFIG_DRIVER_TI_EMAC
if (davinci_configure_pin_mux(emac_pins, ARRAY_SIZE(emac_pins)) != 0)
return 1;
davinci_emac_mii_mode_sel(HAS_RMII);
#endif /* CONFIG_DRIVER_TI_EMAC */
UBOOT 里面
ipaddr=192.168.15.107
主机IP是100
ping 192.168.15.100
+ emac_close
+ emac_ch_teardown
– emac_ch_teardown
– emac_close
+ emac_open
– emac_open
Using DaVinci-EMAC device
+ emac_close
+ emac_ch_teardown
– emac_ch_teardown
+ emac_ch_teardown
– emac_ch_teardown
– emac_close
Abort
ping failed; host 192.168.15.100 is not alive
mii命令信息
mii device
MII devices: 'DP83848 @ 0x01'Current device: 'DP83848 @ 0x01'
mii dump 1 0
0. (3100) — PHY control register —
(8000:0000) 0.15 = 0 reset
(4000:0000) 0.14 = 0 loopback
(2040:2000) 0. 6,13 = b01 speed selection = 100 Mbps
(1000:1000) 0.12 = 1 A/N enable
(0800:0000) 0.11 = 0 power-down
(0400:0000) 0.10 = 0 isolate
(0200:0000) 0. 9 = 0 restart A/N
(0100:0100) 0. 8 = 1 duplex = full
(0080:0000) 0. 7 = 0 collision test enable
(003f:0000) 0. 5- 0 = 0 (reserved)
=> mii dump 1 1
1. (786d) — PHY status register —
(8000:0000) 1.15 = 0 100BASE-T4 able
(4000:4000) 1.14 = 1 100BASE-X full duplex able
(2000:2000) 1.13 = 1 100BASE-X half duplex able
(1000:1000) 1.12 = 1 10 Mbps full duplex able
(0800:0800) 1.11 = 1 10 Mbps half duplex able
(0400:0000) 1.10 = 0 100BASE-T2 full duplex able
(0200:0000) 1. 9 = 0 100BASE-T2 half duplex able
(0100:0000) 1. 8 = 0 extended status
(0080:0000) 1. 7 = 0 (reserved)
(0040:0040) 1. 6 = 1 MF preamble suppression
(0020:0020) 1. 5 = 1 A/N complete
(0010:0000) 1. 4 = 0 remote fault
(0008:0008) 1. 3 = 1 A/N able
(0004:0004) 1. 2 = 1 link status
(0002:0000) 1. 1 = 0 jabber detect
(0001:0001) 1. 0 = 1 extended capabilities
=> mii dump 1 2
2. (2000) — PHY ID 1 register —
(ffff:2000) 2.15- 0 = 8192 OUI portion
=> mii dump 1 3
3. (5c90) — PHY ID 2 register —
(fc00:5c00) 3.15-10 = 23 OUI portion
(03f0:0090) 3. 9- 4 = 9 manufacturer part number
(000f:0000) 3. 3- 0 = 0 manufacturer rev. number
=> mii dump 1 4
4. (01e1) — Autonegotiation advertisement register —
(8000:0000) 4.15 = 0 next page able
(4000:0000) 4.14 = 0 (reserved)
(2000:0000) 4.13 = 0 remote fault
(1000:0000) 4.12 = 0 (reserved)
(0800:0000) 4.11 = 0 asymmetric pause
(0400:0000) 4.10 = 0 pause enable
(0200:0000) 4. 9 = 0 100BASE-T4 able
(0100:0100) 4. 8 = 1 100BASE-TX full duplex able
(0080:0080) 4. 7 = 1 100BASE-TX able
(0040:0040) 4. 6 = 1 10BASE-T full duplex able
(0020:0020) 4. 5 = 1 10BASE-T able
(001f:0001) 4. 4- 0 = 1 selector = IEEE 802.3
=> mii dump 1 5
5. (4de1) — Autonegotiation partner abilities register —
(8000:0000) 5.15 = 0 next page able
(4000:4000) 5.14 = 1 acknowledge
(2000:0000) 5.13 = 0 remote fault
(1000:0000) 5.12 = 0 (reserved)
(0800:0800) 5.11 = 1 asymmetric pause able
(0400:0400) 5.10 = 1 pause able
(0200:0000) 5. 9 = 0 100BASE-T4 able
(0100:0100) 5. 8 = 1 100BASE-X full duplex able
(0080:0080) 5. 7 = 1 100BASE-TX able
(0040:0040) 5. 6 = 1 10BASE-T full duplex able
(0020:0020) 5. 5 = 1 10BASE-T able
(001f:0001) 5. 4- 0 = 1 selector = IEEE 802.3
高手给提供点思路，我卡住了，谢谢
Shine：
我这边转不了，请到omap论坛咨询https://e2echina.ti.com/question_answer/dsp_arm/omap_l1x/
