• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 97 subscribers
  • Views 677 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AM3352: Features of the 3-port CPSW

Gopher79
Expert 1125 points
Part Number: AM3352
1) Does it support ingress rate limiting for unicast packets?
2) Any detailed documentation about CPSW 3-Port switch at user-level? 
Considering the information given in latest CPSW wiki: 
"In switch mode added VLAN will be subscribed to all the ports, in Dual EMAC mode added VLAN will be subscribed to host port and the respective slave ports."
3) Can both Ethernet ports have an independent VLAN configuration in switch mode?
4) Broadcast storm protection?

Regards

Yakir

  • 0
    TI__Guru**** 393215 points
    The Ethernet experts have been notified. They will respond here.
  • 0 in reply to Biser Gatchev-XID
    TI__Mastermind 40080 points
    Ingress rate limiting only affects broadcast and multicast packets. The quote you listed from the wiki along with the TRM for the part is the current documentation available.

    It is possible to add VLANs as the wiki describes in switch mode. Could you describe what you would like setup?

    Could you describe the type application you want to put on the AM3552?

    There is not any HW support that detects a broadcast storm. There is the ability to reject unicast addresses in the ALE of the CPSW but the current Linux driver does not support setting the block feature.

    How do you see the AM3352 in your application being subjected to a broadcast storm? For example is this in isolated network with bridges?
  • 0 in reply to Schuyler Patton
    Expert 1125 points

    About the rate limiting. I am bring the capability description from the HW we currently use with our other product,

    Please specify what out of the above is/isn't supported. Cheers

    VLANs

    Nothing special about what we do. We define the user port 3 as radio's RF interface. Then, on each port we configure it to carry 1-15 vlans (trunked).

    VLANs ID can related to 1,2 or to both ports.

    Port tagging: alternatively, we set port 1 or 2 to work in access mode - where the traffic to the port is untagged and the switch tags or untags it on egress.  

    Broadcast Storm

    Understood.