- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Hi
I would like to know if the CPSW configuration support two different PHY mode on the same CPSW ?
Our Hardware engineer connected the Atheros 8031 and SMSC LAN8710 to our Sitara processor.
/var/log/dmesg:[ 1.220301] davinci_mdio 4a101000.mdio: phy[2]: device 4a101000.mdio:02, driver SMSC LAN8710/LAN8720
/var/log/dmesg:[ 1.220315] davinci_mdio 4a101000.mdio: phy[4]: device 4a101000.mdio:04, driver Atheros 8031 ethernet
I am trying to configure the DTS in order to have both PHY working, one on ETH0 and one on ETH1 but I dont know how to proceed.
I have reused the cpsw_emac section of the am335x-evm-sk and the Atheros started to work, but for the SMSC LAN8710 I used the cpsw_emac section of the bone-common.dtsi and I dont see link on eth1
is there some one which can guide me about those two questions ?
1. Is this design can work ?
2. if Yes, how the cpsw_emac DTS section should look like ?
3. How the pin definition cpsw_default: should look like ?
4. Is the dual_emac mode has to be enabled ?
thanks in advance
Part Number: PROCESSOR-SDK-AM335X
Tool/software: Linux
Hi,
I need help to debug my issue.
I have read dozen of threads on configuring RGMII and MII on U-boot and DTS in the TI forum, I have tried all of them, nothing is helping.
My issue is as following:
Our board is based EVMSK for everything except the ETH1 which is SMSC LAN8710 (used in the design of BBB).
My DTS is as following:
cpsw_default: cpsw_default {
pinctrl-single,pins = <
/* Slave 1 */
0x114 (PIN_OUTPUT_PULLDOWN | MUX_MODE2) /* mii1_txen.rgmii1_tctl */
0x118 (PIN_INPUT_PULLDOWN | MUX_MODE2) /* mii1_rxdv.rgmii1_rctl */
0x11c (PIN_OUTPUT_PULLDOWN | MUX_MODE2) /* mii1_txd3.rgmii1_td3 */
0x120 (PIN_OUTPUT_PULLDOWN | MUX_MODE2) /* mii1_txd2.rgmii1_td2 */
0x124 (PIN_OUTPUT_PULLDOWN | MUX_MODE2) /* mii1_txd1.rgmii1_td1 */
0x128 (PIN_OUTPUT_PULLDOWN | MUX_MODE2) /* mii1_txd0.rgmii1_td0 */
0x12c (PIN_OUTPUT_PULLDOWN | MUX_MODE2) /* mii1_txclk.rgmii1_tclk */
0x130 (PIN_INPUT_PULLDOWN | MUX_MODE2) /* mii1_rxclk.rgmii1_rclk */
0x134 (PIN_INPUT_PULLDOWN | MUX_MODE2) /* mii1_rxd3.rgmii1_rd3 */
0x138 (PIN_INPUT_PULLDOWN | MUX_MODE2) /* mii1_rxd2.rgmii1_rd2 */
0x13c (PIN_INPUT_PULLDOWN | MUX_MODE2) /* mii1_rxd1.rgmii1_rd1 */
0x140 (PIN_INPUT_PULLDOWN | MUX_MODE2) /* mii1_rxd0.rgmii1_rd0 */
0x78 ( PIN_INPUT | MUX_MODE1 ) /* (U18) gpmc_be1n.gmii2_col */
0x70 ( PIN_INPUT | MUX_MODE1 ) /* (T17) gpmc_wait0.gmii2_crs */
0x74 ( PIN_INPUT | MUX_MODE1 ) /* (U17) gpmc_wpn.gmii2_rxer */
/* Slave 2 */
0x40 (PIN_OUTPUT_PULLDOWN | MUX_MODE1) /* gpmc_a0.gmii2_tctl */
0x44 (PIN_INPUT_PULLDOWN | MUX_MODE1) /* gpmc_a1.gmii2_rctl */
0x48 (PIN_OUTPUT_PULLDOWN | MUX_MODE1) /* gpmc_a2.gmii2_td3 */
0x4c (PIN_OUTPUT_PULLDOWN | MUX_MODE1) /* gpmc_a3.gmii2_td2 */
0x50 (PIN_OUTPUT_PULLDOWN | MUX_MODE1) /* gpmc_a4.gmii2_td1 */
0x54 (PIN_OUTPUT_PULLDOWN | MUX_MODE1) /* gpmc_a5.gmii2_td0 */
0x58 (PIN_OUTPUT_PULLDOWN | MUX_MODE1) /* gpmc_a6.gmii2_tclk */
0x5c (PIN_INPUT_PULLDOWN | MUX_MODE1) /* gpmc_a7.gmii2_rclk */
0x60 (PIN_INPUT_PULLDOWN | MUX_MODE1) /* gpmc_a8.gmii2_rd3 */
0x64 (PIN_INPUT_PULLDOWN | MUX_MODE1) /* gpmc_a9.gmii2_rd2 */
0x68 (PIN_INPUT_PULLDOWN | MUX_MODE1) /* gpmc_a10.gmii2_rd1 */
0x6c (PIN_INPUT_PULLDOWN | MUX_MODE1) /* gpmc_a11.gmii2_rd0 */
>;
};
&mac {
pinctrl-names = "default", "sleep";
pinctrl-0 = <&cpsw_default>;
pinctrl-1 = <&cpsw_sleep>;
dual_emac = <0>;
status = "okay";
};
&davinci_mdio {
pinctrl-names = "default", "sleep";
pinctrl-0 = <&davinci_mdio_default>;
pinctrl-1 = <&davinci_mdio_sleep>;
status = "okay";
};
&cpsw_emac0 {
phy_id = <&davinci_mdio>, <4>;
phy-mode = "rgmii-txid";
};
&cpsw_emac1 {
phy_id = <&davinci_mdio>, <5>; // the PHY IS 0x02 in the design, but we changed the PHY ADDR to 0x5 during our test
phy-mode = "mii";
};
The result is that I see LINK UP on eth1 but no ping and no traffic is getting out neither received and suddenly the KERNEL reports a WARNING which also made ETH0 not working anymore.
[ 632.563942] device eth0 entered promiscuous mode
[ 632.612187] device eth0 left promiscuous mode
[ 640.634085] device eth1 entered promiscuous mode
[ 648.024063] ------------[ cut here ]------------
[ 648.024160] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:303 dev_watchdog+0x2a4/0x2c8()
[ 648.024185] NETDEV WATCHDOG: eth0 (cpsw): transmit queue 0 timed out
[ 648.024204] Modules linked in: bluetooth ipv6 omap_rng rng_core rtc_omap omap_wdt uio_pdrv_genirq uio vs88ut_fpga(O)
[ 648.024312] CPU: 0 PID: 0 Comm: swapper Tainted: G O 4.1.19-kramer-bone20-tisdk_vs88ut-001 #30
[ 648.024333] Hardware name: Generic AM33XX (Flattened Device Tree)
[ 648.024351] Backtrace:
[ 648.024417] [<c0012af8>] (dump_backtrace) from [<c0012d18>] (show_stack+0x18/0x1c)
[ 648.024437] r7:c08225ec r6:0000012f r5:00000009 r4:00000000
[ 648.024501] [<c0012d00>] (show_stack) from [<c063fd80>] (dump_stack+0x20/0x28)
[ 648.024553] [<c063fd60>] (dump_stack) from [<c0036704>] (warn_slowpath_common+0x7c/0xb4)
[ 648.024593] [<c0036688>] (warn_slowpath_common) from [<c0036774>] (warn_slowpath_fmt+0x38/0x40)
[ 648.024613] r8:ffffffff r7:c08eb6eb r6:c08baad0 r5:00000000 r4:c08225b0
[ 648.024675] [<c0036740>] (warn_slowpath_fmt) from [<c058a934>] (dev_watchdog+0x2a4/0x2c8)
[ 648.024695] r3:cd9bf800 r2:c08225b0
[ 648.024719] r4:cd9bf800
[ 648.024769] [<c058a690>] (dev_watchdog) from [<c00766dc>] (call_timer_fn+0x2c/0xa4)
[ 648.024788] r9:c08baad0 r8:00200200 r7:00000000 r6:c08ade38 r5:c058a690 r4:00000101
[ 648.024858] [<c00766b0>] (call_timer_fn) from [<c0076b68>] (run_timer_softirq+0x234/0x2d4)
[ 648.024877] r6:c08ade38 r5:c0900b40 r4:cd9bfa38
[ 648.024935] [<c0076934>] (run_timer_softirq) from [<c0039668>] (__do_softirq+0xec/0x218)
[ 648.024953] r10:00000101 r9:40000001 r8:c08eed80 r7:c08ac000 r6:c08eed84 r5:00000001
[ 648.024999] r4:00000000
[ 648.025038] [<c003957c>] (__do_softirq) from [<c0039a3c>] (irq_exit+0xa8/0x100)
[ 648.025057] r10:00000001 r9:c08ae110 r8:cd806000 r7:00000001 r6:00000000 r5:c08c4954
[ 648.025102] r4:00000000
[ 648.025149] [<c0039994>] (irq_exit) from [<c0068874>] (__handle_domain_irq+0x58/0xb0)
[ 648.025167] r5:c08c4954 r4:00000000
[ 648.025210] [<c006881c>] (__handle_domain_irq) from [<c0009470>] (omap_intc_handle_irq+0xbc/0xcc)
[ 648.025228] r9:c08ae110 r8:00000000 r7:00000044 r6:c08adf20 r5:c0916940 r4:c08c4bc0
[ 648.025300] [<c00093b4>] (omap_intc_handle_irq) from [<c0645240>] (__irq_svc+0x40/0x74)
[ 648.025323] Exception stack(0xc08adf20 to 0xc08adf68)
[ 648.025358] df20: 00000001 00000000 00000000 c001ffa0 c08ac000 c08ae110 00000000 00000000
[ 648.025392] df40: 00000000 c08ae110 00000001 c08adf74 c08adf78 c08adf68 c00101fc c0010200
[ 648.025414] df60: 60000013 ffffffff
[ 648.025430] r7:c08adf54 r6:ffffffff r5:60000013 r4:c0010200
[ 648.025504] [<c00101c8>] (arch_cpu_idle) from [<c00603a0>] (cpu_startup_entry+0x194/0x214)
[ 648.025542] [<c006020c>] (cpu_startup_entry) from [<c063cbe4>] (rest_init+0x78/0x90)
[ 648.025560] r7:c08ae000
[ 648.025611] [<c063cb6c>] (rest_init) from [<c0868c8c>] (start_kernel+0x354/0x3c4)
[ 648.025629] r5:c08ee000 r4:c08ee050
[ 648.025675] [<c0868938>] (start_kernel) from [<80008078>] (0x80008078)
[ 648.025697] ---[ end trace c818a663baccaf67 ]---
[ 677.197982] device eth1 left promiscuous mode
So, I need guidance to debug and how to check the validity of the PHY, it can be in u-boot or Linux, I have debugged the PHY register in both of them the issue remain the same.
I almost sure the issue is somewhere in the hardware design, but I need your help to find the root cause.
BTW, Strangely, when I declare "rgmii" for the ETH1, things starts to work but some packets are dropped..... very strange, the PHY is physically configured and connected using MII.....I am lost !
Any direction, advice is welcome ,
thank you very much in advance.
