This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM6422: change ethernet to switch mode

Part Number: AM6422


Tool/software:

Hi team,

This is post on customer's behalf.

Is there a way just change DTS file to  achieve switch mode?

we want to use netifd.service to config our bridge and ip address, the devlink command seems doesn't work after run netifd service.

Regards,

  • Hello Ying Zhou,

    we want to use netifd.service to config our bridge and ip address, the devlink command seems doesn't work after run netifd service.

    Can you point me to what specific devlink command is not working and what the log is showing when this devlink command is used?

    What SDK version is the customer using?

    Is this on a custom designed board or a TI AM64x EVM?

    Is there a way just change DTS file to  achieve switch mode?

    Is configuring switch mode for PRU_ICSSG Ethernet interfaces or CPSW Ethernet interfaces?

    Please note with the latest SDK, a DTS configuration is not necessary to configure switch mode, see below

    CPSW Ethernet: https://software-dl.ti.com/processor-sdk-linux/esd/AM64X/latest/exports/docs/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW3g.html#multi-port-switch-mode

    PRU_ICSSG Ethernet: https://software-dl.ti.com/processor-sdk-linux/esd/AM64X/latest/exports/docs/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/PRU_ICSSG_Ethernet_Switch.html

    -Daolin

  • Hi Daolin,

    Thanks for your support.

    There is customer's response, please support further , thank you so much.

    I am using TI AM64x EVM, I want to cofigure switch mode on CPSW ethernet interfaces.

    In emac-only mode, we config ethernet by using /etc/config/network:

    config interface 'lan'
            option type 'bridge'
            option ifname 'eth0 eth1'
            option proto 'static'
            option ipaddr '192.168.1.101'
            #option gateway '172.16.88.1'
            option netmask '255.255.255.0'
            option ip6assign '60'
            option stp '1'
            option rstp '1'

    but when I convert it to switch mode by run command:

    devlink dev param set platform/8000000.ethernet name switch_mode value true cmode runtime

    the log shows:

    but the ethernet doesn't work.

     I would be really appreciate if you have any suggestions, thank you.

    By the way, I try to cancel the uci network config, reboot the machine, and run the script below, it works.

    #!/bin/bash
    
    ip link set dev eth0 down
    ip link set dev eth1 down
    sleep 1
    ip link set dev eth0 up
    ip link set dev eth1 up
    sleep 2
    devlink dev param set platform/8000000.ethernet name switch_mode value true cmode runtime
    sleep 1
    ip link add name br0 type bridge
    ip link set dev br0 type bridge ageing_time 1000
    sleep 1
    ip link set dev eth0 master br0
    ip link set dev eth1 master br0
    ip link set dev br0 type bridge stp_state 1
    ip link set dev br0 up
    bridge vlan add dev br0 vid 1 self
    bridge vlan add dev br0 vid 1 pvid untagged self
    #udhcpc -i br0
    ip addr add 192.168.1.101/24 dev br0

    But I can't run this script every time, I still want to use uci to config my network,  

    Maybe it has some thing to do in the order of running devlink and netifd.service, maybe the uci config should add something, I don't know.

    Regards,

  • Hello Ying Zhou,

    Thanks for sharing the customer's response, if it makes it easier for you and the customer, we could move this thread to the public E2E forum for them to respond directly, let me know if this would work for you/what you think.

    But I can't run this script every time, I still want to use uci to config my network,  

    Maybe it has some thing to do in the order of running devlink and netifd.service, maybe the uci config should add something, I don't know.

    It sounds like you are running the devlink command after configuring the bridge and ip address with this netifd.service. As you mentioned, I think devlink must be run in the same order as in the script you shared (i.e. before the bridge setup). 

    A couple of suggestions

    1. Is it possible to try running the devlink command before netifd.service starts? I'm not sure netifd.service is a daemon that automatically starts upon boot up, if so, maybe configure the devlink command to run as a systemd type service before netifd.service is run?

    2. Since it sounds like your goal is to automate the switch mode setup, likely to be configured upon boot up, perhaps, instead of using this netifd.service, you could write a custom systemd service to start the script you shared automatically upon boot up?

    -Daolin

  • Hi Daolin,

    Thank you for your support, I've moved the post to a public forum, you can communicate directly with the customer, please wait for the customer's reply

    Regards,

    Katherine

  • 1、I have tried run devlink command as a service, put it before or after netifd.service, but it can't work, unfortunately, the eth port can't work completely.

    2、I can't run the whole script as a service, beacause I want use uci(/etc/config/network) to config my eth tool.

  • Hello Zitong, 

    1、I have tried run devlink command as a service, put it before or after netifd.service, but it can't work, unfortunately, the eth port can't work completely.

    I'm not very familiar with the netifd.service, one question is are you sure the configurations you made in /etc/config/network are equivalent to the below script commands used to configure the bridge interface, especially the vid configurations below?

    ip link add name br0 type bridge
    ip link set dev br0 type bridge ageing_time 1000
    sleep 1
    ip link set dev eth0 master br0
    ip link set dev eth1 master br0
    ip link set dev br0 type bridge stp_state 1
    ip link set dev br0 up
    bridge vlan add dev br0 vid 1 self <- vid configuration
    bridge vlan add dev br0 vid 1 pvid untagged self <- vid configuration
    #udhcpc -i br0
    ip addr add 192.168.1.101/24 dev br0

    As a note, TI can help with issues related to TI-specific drivers, but when it comes to application specific issues, including how to enable switch mode with netifd.service, this is more out of the scope of TI support, since netifd.service is not something we specifically show examples of how to use.

    -Daolin

  • By the way, I want to know is the devlink command the only method to convert eth to switch mode?

  • I also have a question, when the devlink command is executed, the eth port should change to switch mode in hardware theoretically. But why do we need to set eth0 and eth1 to bridge? 

  • Hello Zitong, 

    I want to know is the devlink command the only method to convert eth to switch mode?

    To my knowledge, this is what we indicate in our SDK documentation to use to configure hardware switch. If you skip using devlink, you can still configure a switch with the other commands in the sequence; however, the switch would be functioning in software rather than hardware. Software switching means that each Ethernet packet would need to pass through more Network layers resulting in larger switching latency as compared to a hardware switch.

    when the devlink command is executed, the eth port should change to switch mode in hardware theoretically. But why do we need to set eth0 and eth1 to bridge? 

    eth0 and eth1 interfaces still need to be added to the br0 interface (essentially br0 is like a virtual interface) so that there is an interface for upper layer interfacing. Please see the response here for more details: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1463803/processor-sdk-am62x-how-to-use-cpsw3g-in-hw-switch-mode-using-linux/5618583#5618583

    -Daolin

  • hello Daolin, after I run the command devlink xxx, I run netifd.service. I got some kernel log maybe useful, can you have a look, and find out what problem it has?

    $ [  125.299745] br-lan: port 2(eth1) entered disabled state
    [  125.305154] br-lan: port 1(eth0) entered disabled state
    [  125.311538] device eth1 left promiscuous mode
    [  125.318464] br-lan: port 2(eth1) entered disabled state
    [  125.324415] br-lan: port 2(eth1) failed to delete vlan 1: -ENOENT
    [  125.336207] ------------[ cut here ]------------
    [  125.340839] WARNING: CPU: 1 PID: 624 at net/bridge/br_vlan.c:433 __vlan_group_free+0x4c/0x54
    [  125.349282] Modules linked in:
    [  125.352337] CPU: 1 PID: 624 Comm: netifd Not tainted 6.1.33-g40c32565ca #1
    [  125.359200] Hardware name: Texas Instruments AM642 EVM (DT)
    [  125.364759] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
    [  125.371708] pc : __vlan_group_free+0x4c/0x54
    [  125.375970] lr : nbp_vlan_flush+0x40/0x90
    [  125.379973] sp : ffff80000a623bc0
    [  125.383276] x29: ffff80000a623bc0 x28: ffff000000f38000 x27: 0000000000000000
    [  125.390405] x26: 0000000000000000 x25: 0000aaaadbd90d88 x24: 0000aaaadbd90d88
    [  125.397532] x23: 0000000000000000 x22: ffff000001165000 x21: ffff000003d79940
    [  125.404659] x20: ffff000003d0e200 x19: ffff000003d0e200 x18: ffffffffffffffff
    [  125.411786] x17: ffff800036b2f000 x16: ffff800008008000 x15: 0000000000000079
    [  125.418913] x14: 0000000000000100 x13: 0000000000000001 x12: 0000000000000000
    [  125.426039] x11: 0000000000000001 x10: 00000000000009b0 x9 : ffff80000a6239c0
    [  125.433166] x8 : ffff000000f38a10 x7 : ffff000003f9fe00 x6 : 0000000000000000
    [  125.440293] x5 : 00000000410fd030 x4 : 0000000000000000 x3 : ffff80000a623bc0
    [  125.447419] x2 : 0000000000000000 x1 : ffff0000015f5e18 x0 : ffff000003d0e310
    [  125.454547] Call trace:
    [  125.456985]  __vlan_group_free+0x4c/0x54
    [  125.460900]  nbp_vlan_flush+0x40/0x90
    [  125.464555]  del_nbp+0xcc/0x2dc
    [  125.467693]  br_dev_delete+0x44/0xb0
    [  125.471263]  br_del_bridge+0x2c/0x54
    [  125.474831]  br_ioctl_stub+0x1ac/0x3b0
    [  125.478574]  br_ioctl_call+0x70/0xc0
    [  125.482148]  sock_ioctl+0x2f8/0x350
    [  125.485630]  __arm64_sys_ioctl+0xa8/0xf0
    [  125.489548]  invoke_syscall+0x48/0x114
    [  125.493295]  el0_svc_common.constprop.0+0x44/0xfc
    [  125.497992]  do_el0_svc+0x30/0xd0
    [  125.501302]  el0_svc+0x2c/0x84
    [  125.504357]  el0t_64_sync_handler+0xbc/0x140
    [  125.508618]  el0t_64_sync+0x18c/0x190
    [  125.512273] ---[ end trace 0000000000000000 ]---
    [  125.517234] ------------[ cut here ]------------
    [  125.521864] WARNING: CPU: 1 PID: 624 at net/bridge/br_switchdev.c:280 nbp_switchdev_del+0xb4/0xdc
    [  125.530745] Modules linked in:
    [  125.533800] CPU: 1 PID: 624 Comm: netifd Tainted: G        W          6.1.33-g40c32565ca #1
    [  125.542138] Hardware name: Texas Instruments AM642 EVM (DT)
    [  125.547697] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
    [  125.554646] pc : nbp_switchdev_del+0xb4/0xdc
    [  125.558910] lr : br_switchdev_port_unoffload+0x78/0x90
    [  125.564042] sp : ffff80000a6239c0
    [  125.567345] x29: ffff80000a6239c0 x28: ffff000000f38000 x27: 0000000000000000
    [  125.574473] x26: 0000000000000000 x25: 0000aaaadbd90d88 x24: ffff8000095676d0
    [  125.581600] x23: ffff000001165000 x22: ffff000003d79000 x21: 0000000000000000
    [  125.588727] x20: 0000000000000000 x19: ffff0000015eb400 x18: ffffffffffffffff
    [  125.595854] x17: ffff800036b2f000 x16: ffff800008008000 x15: 0000000000000000
    [  125.602981] x14: ffff8000095f6520 x13: 0000000000000040 x12: 0000000000000228
    [  125.610109] x11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000
    [  125.617235] x8 : ffff80000a623ad8 x7 : ffff8000095676d0 x6 : ffff000000f38000
    [  125.624362] x5 : ffff000000f38000 x4 : 0000000000000000 x3 : 0000000000000000
    [  125.631488] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0000015eb400
    [  125.638616] Call trace:
    [  125.641054]  nbp_switchdev_del+0xb4/0xdc
    [  125.644971]  br_switchdev_blocking_event+0x60/0xb0
    [  125.649755]  blocking_notifier_call_chain+0x6c/0xa0
    [  125.654626]  switchdev_bridge_port_unoffload+0x6c/0xd4
    [  125.659757]  am65_cpsw_netdevice_event+0xd8/0x150
    [  125.664459]  raw_notifier_call_chain+0x54/0x74
    [  125.668893]  call_netdevice_notifiers_info+0x58/0xac
    [  125.673853]  __netdev_upper_dev_unlink+0xa0/0x210
    [  125.678550]  netdev_upper_dev_unlink+0x30/0x60
    [  125.682984]  del_nbp+0x180/0x2dc
    [  125.686207]  br_dev_delete+0x44/0xb0
    [  125.689776]  br_del_bridge+0x2c/0x54
    [  125.693344]  br_ioctl_stub+0x1ac/0x3b0
    [  125.697087]  br_ioctl_call+0x70/0xc0
    [  125.700659]  sock_ioctl+0x2f8/0x350
    [  125.704142]  __arm64_sys_ioctl+0xa8/0xf0
    [  125.708059]  invoke_syscall+0x48/0x114
    [  125.711804]  el0_svc_common.constprop.0+0x44/0xfc
    [  125.716502]  do_el0_svc+0x30/0xd0
    [  125.719811]  el0_svc+0x2c/0x84
    [  125.722865]  el0t_64_sync_handler+0xbc/0x140
    [  125.727126]  el0t_64_sync+0x18c/0x190
    [  125.730784] ---[ end trace 0000000000000000 ]---
    [  125.735665] device eth0 left promiscuous mode
    [  125.742555] br-lan: port 1(eth0) entered disabled state
    [  125.748501] br-lan: port 1(eth0) failed to delete vlan 1: -ENOENT
    [  125.760181] ------------[ cut here ]------------
    [  125.764817] WARNING: CPU: 1 PID: 624 at net/bridge/br_vlan.c:433 __vlan_group_free+0x4c/0x54
    [  125.773258] Modules linked in:
    [  125.776311] CPU: 1 PID: 624 Comm: netifd Tainted: G        W          6.1.33-g40c32565ca #1
    [  125.784647] Hardware name: Texas Instruments AM642 EVM (DT)
    [  125.790207] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
    [  125.797155] pc : __vlan_group_free+0x4c/0x54
    [  125.801417] lr : nbp_vlan_flush+0x40/0x90
    [  125.805420] sp : ffff80000a623bc0
    [  125.808723] x29: ffff80000a623bc0 x28: ffff000000f38000 x27: 0000000000000000
    [  125.815851] x26: 0000000000000000 x25: 0000aaaadbd90d88 x24: 0000aaaadbd90d88
    [  125.822978] x23: 0000000000000000 x22: ffff000001163000 x21: ffff000003d79940
    [  125.830105] x20: ffff000003f9de00 x19: ffff000003f9de00 x18: 0000000000000000
    [  125.837232] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000
    [  125.844359] x14: 0000000000000066 x13: 0000000000000001 x12: 0000000000000000
    [  125.851485] x11: 0000000000000001 x10: 00000000000009b0 x9 : ffff80000a6239c0
    [  125.858611] x8 : ffff000000f38a10 x7 : ffff000003f9fe00 x6 : 0000000000000000
    [  125.865738] x5 : 00000000410fd030 x4 : 0000000000000000 x3 : ffff80000a623bc0
    [  125.872865] x2 : 0000000000000000 x1 : ffff0000015fa218 x0 : ffff000003f9df10
    [  125.879993] Call trace:
    [  125.882430]  __vlan_group_free+0x4c/0x54
    [  125.886345]  nbp_vlan_flush+0x40/0x90
    [  125.890000]  del_nbp+0xcc/0x2dc
    [  125.893137]  br_dev_delete+0x44/0xb0
    [  125.896706]  br_del_bridge+0x2c/0x54
    [  125.900274]  br_ioctl_stub+0x1ac/0x3b0
    [  125.904016]  br_ioctl_call+0x70/0xc0
    [  125.907589]  sock_ioctl+0x2f8/0x350
    [  125.911071]  __arm64_sys_ioctl+0xa8/0xf0
    [  125.914989]  invoke_syscall+0x48/0x114
    [  125.918736]  el0_svc_common.constprop.0+0x44/0xfc
    [  125.923433]  do_el0_svc+0x30/0xd0
    [  125.926743]  el0_svc+0x2c/0x84
    [  125.929796]  el0t_64_sync_handler+0xbc/0x140
    [  125.934057]  el0t_64_sync+0x18c/0x190
    [  125.937713] ---[ end trace 0000000000000000 ]---
    [  125.942721] ------------[ cut here ]------------
    [  125.947351] WARNING: CPU: 1 PID: 624 at net/bridge/br_switchdev.c:280 nbp_switchdev_del+0xb4/0xdc
    [  125.956231] Modules linked in:
    [  125.959287] CPU: 1 PID: 624 Comm: netifd Tainted: G        W          6.1.33-g40c32565ca #1
    [  125.967624] Hardware name: Texas Instruments AM642 EVM (DT)
    [  125.973183] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
    [  125.980131] pc : nbp_switchdev_del+0xb4/0xdc
    [  125.984397] lr : br_switchdev_port_unoffload+0x78/0x90
    [  125.989528] sp : ffff80000a6239c0
    [  125.992832] x29: ffff80000a6239c0 x28: ffff000000f38000 x27: 0000000000000000
    [  125.999960] x26: 0000000000000000 x25: 0000aaaadbd90d88 x24: ffff8000095676d0
    [  126.007087] x23: ffff000001163000 x22: ffff000003d79000 x21: 0000000000000000
    [  126.014214] x20: 0000000000000000 x19: ffff0000015ebc00 x18: ffffffffffffffff
    [  126.021341] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000
    [  126.028467] x14: ffff8000095f6520 x13: 0000000000000040 x12: 0000000000000228
    [  126.035594] x11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000
    [  126.042720] x8 : ffff80000a623ad8 x7 : ffff8000095676d0 x6 : ffff000000f38000
    [  126.049847] x5 : ffff000000f38000 x4 : 0000000000000000 x3 : 0000000000000000
    [  126.056974] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0000015ebc00
    [  126.064101] Call trace:
    [  126.066539]  nbp_switchdev_del+0xb4/0xdc
    [  126.070457]  br_switchdev_blocking_event+0x60/0xb0
    [  126.075241]  blocking_notifier_call_chain+0x6c/0xa0
    [  126.080112]  switchdev_bridge_port_unoffload+0x6c/0xd4
    [  126.085244]  am65_cpsw_netdevice_event+0xd8/0x150
    [  126.089946]  raw_notifier_call_chain+0x54/0x74
    [  126.094380]  call_netdevice_notifiers_info+0x58/0xac
    [  126.099341]  __netdev_upper_dev_unlink+0xa0/0x210
    [  126.104037]  netdev_upper_dev_unlink+0x30/0x60
    [  126.108471]  del_nbp+0x180/0x2dc
    [  126.111695]  br_dev_delete+0x44/0xb0
    [  126.115264]  br_del_bridge+0x2c/0x54
    [  126.118832]  br_ioctl_stub+0x1ac/0x3b0
    [  126.122575]  br_ioctl_call+0x70/0xc0
    [  126.126148]  sock_ioctl+0x2f8/0x350
    [  126.129630]  __arm64_sys_ioctl+0xa8/0xf0
    [  126.133547]  invoke_syscall+0x48/0x114
    [  126.137293]  el0_svc_common.constprop.0+0x44/0xfc
    [  126.141990]  do_el0_svc+0x30/0xd0
    [  126.145300]  el0_svc+0x2c/0x84
    [  126.148353]  el0t_64_sync_handler+0xbc/0x140
    [  126.152614]  el0t_64_sync+0x18c/0x190
    [  126.156272] ---[ end trace 0000000000000000 ]---
    [  126.176164] ------------[ cut here ]------------
    [  126.180804] WARNING: CPU: 1 PID: 624 at net/bridge/br_vlan.c:433 __vlan_group_free+0x4c/0x54
    [  126.189247] Modules linked in:
    [  126.192300] CPU: 1 PID: 624 Comm: netifd Tainted: G        W          6.1.33-g40c32565ca #1
    [  126.200637] Hardware name: Texas Instruments AM642 EVM (DT)
    [  126.206196] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
    [  126.213145] pc : __vlan_group_free+0x4c/0x54
    [  126.217406] lr : br_vlan_flush+0x40/0x90
    [  126.221323] sp : ffff80000a623b10
    [  126.224626] x29: ffff80000a623b10 x28: ffff00003fdd454c x27: ffff800008ab4c80
    [  126.231755] x26: ffff000003c11c00 x25: dead000000000100 x24: dead000000000122
    [  126.238882] x23: ffff000003d79000 x22: ffff000007262880 x21: ffff800009558020
    [  126.246009] x20: ffff000003d12400 x19: ffff000003d12400 x18: 0000000000000000
    [  126.253136] x17: 0000000000000000 x16: 0000000000000000 x15: 000000000000001b
    [  126.260263] x14: 00000000000003c1 x13: 0000000000000000 x12: 0000000000000003
    [  126.267390] x11: 0000000000000000 x10: 00000000000009b0 x9 : ffff80000a623910
    [  126.274516] x8 : ffff000000f38a10 x7 : ffff000003f9fe00 x6 : 0000000000000000
    [  126.281643] x5 : 00000000410fd030 x4 : 0000000000000000 x3 : ffff80000a623b10
    [  126.288769] x2 : 0000000000000000 x1 : ffff00000197ee18 x0 : ffff000003d12510
    [  126.295898] Call trace:
    [  126.298335]  __vlan_group_free+0x4c/0x54
    [  126.302250]  br_vlan_flush+0x40/0x90
    [  126.305818]  br_dev_uninit+0x30/0x60
    [  126.309387]  unregister_netdevice_many+0x43c/0x744
    [  126.314174]  unregister_netdevice_queue+0x90/0xd0
    [  126.318869]  br_dev_delete+0x94/0xb0
    [  126.322438]  br_del_bridge+0x2c/0x54
    [  126.326007]  br_ioctl_stub+0x1ac/0x3b0
    [  126.329750]  br_ioctl_call+0x70/0xc0
    [  126.333323]  sock_ioctl+0x2f8/0x350
    [  126.336806]  __arm64_sys_ioctl+0xa8/0xf0
    [  126.340723]  invoke_syscall+0x48/0x114
    [  126.344470]  el0_svc_common.constprop.0+0x44/0xfc
    [  126.349167]  do_el0_svc+0x30/0xd0
    [  126.352477]  el0_svc+0x2c/0x84
    [  126.355531]  el0t_64_sync_handler+0xbc/0x140
    [  126.359791]  el0t_64_sync+0x18c/0x190
    [  126.363448] ---[ end trace 0000000000000000 ]---
    [  126.490103] am65-cpsw-nuss 8000000.ethernet eth0: Link is Down
    [  126.509013] am65-cpsw-nuss 8000000.ethernet eth0: PHY [8000f00.mdio:01] driver [TI DP83822] (irq=POLL)
    [  126.518381] am65-cpsw-nuss 8000000.ethernet eth0: configuring for phy/rmii link mode
    [  126.533604] br-lan: port 1(eth0) entered blocking state
    [  126.539036] br-lan: port 1(eth0) entered disabled state
    [  126.547195] device eth0 entered promiscuous mode
    [  126.603591] am65-cpsw-nuss 8000000.ethernet eth1: Link is Down
    [  126.623331] am65-cpsw-nuss 8000000.ethernet eth1: PHY [8000f00.mdio:00] driver [TI DP83822] (irq=POLL)
    [  126.632774] am65-cpsw-nuss 8000000.ethernet eth1: configuring for phy/rmii link mode
    [  126.650593] br-lan: port 2(eth1) entered blocking state
    [  126.655983] br-lan: port 2(eth1) entered disabled state
    [  126.665195] device eth1 entered promiscuous mode
    [  126.675333] br-lan: port 2(eth1) entered blocking state
    [  126.680612] br-lan: port 2(eth1) entered listening state
    [  127.523761] br-lan: port 2(eth1) entered disabled state
    [  127.587666] am65-cpsw-nuss 8000000.ethernet eth0: Link is Up - 10Mbps/Full - flow control off
    [  127.596300] br-lan: port 1(eth0) entered blocking state
    [  127.601538] br-lan: port 1(eth0) entered listening state
    [  127.651734] br-lan: port 2(eth1) entered blocking state
    [  127.657014] br-lan: port 2(eth1) entered listening state
    [  127.657036] am65-cpsw-nuss 8000000.ethernet eth1: Link is Up - 10Mbps/Full - flow control off
    [  129.635113] br-lan: port 1(eth0) entered learning state
    [  129.699097] br-lan: port 2(eth1) entered learning state
    [  131.683099] br-lan: port 1(eth0) entered forwarding state
    [  131.688561] br-lan: topology change detected, propagating
    [  131.694924] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
    [  131.747108] br-lan: port 2(eth1) entered forwarding state
    [  131.752562] br-lan: topology change detected, propagating

  • Hello Zitong,

    Daolin is out of the office for the rest of March. Feel free to ping the thread in early April if you have not received a response.

    Regards,

    Nick

  • Hi,

    I will discuss this with the development team and post tomorrow or Thursday with an update on possible next steps.

    Best Regards,

    Schuyler

  • Hi Schuyler,

    In addition, after the eth config to switch mode, I try to link eth down and up, the time that eth port recover takes nearly 1 minute, is this we expected?

  • Hi,

    I am not sure if this expected I will have to further discuss this with the developer.

    Concerning the question of enabling the switch/bridge mode in DTS this used to be the method in earlier devices but was changed a few years ago. Bridge configuration involves a virtualization process to create the bridge interface.  We will take a look if this possible.

    We are also looking at the error you have reported.

    Best Regards,

    Schuyler

  • Hi Schuyler

    May I ask if you have further updates here? Thanks

    Zekun

  • Hi Zekun, 

    I apologize for the delay, I will check again with the developer.

    Best Regards,

    Schuyler

  • Hi Schuyler

    From Dallin’s feedback, it seems that this issue is more like an application layer issue. Do you have any further feedback about this one? 
    Regards

    Zekun

  • As discussed in person, customer have succeed to switch mode, so close this one.

    Regards

    Zekun

  • In addition, after the eth config to switch mode, I try to link eth down and up, the time that eth port recover takes nearly 1 minute, is this we

    Hello Zitong

         in your system, if the RSTP protocol is enabled, this protocol will impact the network up time,

         please try to disable RSTP protocol if it is enabled, 

          connect 2 PC to the CPSW-3g port to do the test

    Regards

        Semon