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.

TDA4VM: Could not send boardcasts within VLAN

Part Number: TDA4VM


Hi Experts,

We are working on a TDA4 platform and willing to do the following:

    - to config a VLAN and make apps communicating within the VLAN.

but when we added the VLAN config by modifing the startup code for switch, we found that although the VLAN config exists in the switch's entry table, and we confirmed that the communication within that VLAN is valid, we found that outside boardcast packets could not be seen on the A72 side(tried tcpdump on A72 side), which means the outside ARP boardcast could not reach to the A72 side, thus the communication will fail until the A72 sends ARP boardcast to outside. And this happens to other boardcast packets too, which is required by one of our apps.

From our point of view, the switch on the TDA4 platform is blocking the outside boardcast packets. We noticed that in cpsw startup codes, a multi-cast entry with addr "ffff ffff ffff" is added for boardcasting, so we tried to add samilar multi-cast entry for the VLAN we configured but the outside boardcasts are still being blocked.

So we are wondering, if we want to enable the boardcasting from outside to inside within a VLAN, what should we check or what should we do to config the switch?

Thank you very much!

  • Hi,

    Can you clarify the following things for me :

    • Which SDK are you using?
    • Which CPSW are you using? Is it MCU CPSW 2G or MAIN CPSW 9G?
    • How are you configuring VLAN interfaces?

    Regards,
    Tanmay

  • Hi Tanmay,

    Thanks for your reply. For your questions:

    1, We are using SDK 8.2;

    2, It is the CPSW 9G being used;

    3, We referenced the code in EthHwInterVlan_setOpenPrms and directly modified the vlan config under the port configs. We checked the ALE entries and found that vlan configs are present after that. 

    So any other configs could be missed by us?

    Thanks you.

    Regards.

  • Hi,

    Inter VLAN is used to move data around inside CPSW between different ports and it actually sometimes interfere with the external VLAN. For Inter-VLAN, VLAN IDs are stripped at ingress and egress. Can you take a look at this and see if it resolves your issue. Addidng VLAN interfaces for ethfw is somewhat involved process. 

    The latest SDK, SDK 8.4 has support for CPSW9G enabled from A72. So it has a native linux driver for ethernet like used with CPSW2G. With that, you can linux user space tools to configure interfaces. You can also consider this option.

    Regards,
    Tanmay

  • Hi Tanmay,

    Sorry for late reply while we are busy on other issues.

    Come back to you again because we found the patch "add vlan entry" mentioned in that link seems not working porperly with SDK 8.2, we could not add vlan config with that, the static config function has not been called for some reason. Woule you please help to confirm if that is applicable for SDK 8.2?

    Btw, would you please explain more about how broadcast packets been treated within vlan? I think for normal network switches, broadcasts are very normal operations which doesn't need any special config.

    We also noticed that a config called "policer" has been used for vlan config, would you also please explain how a "policer" would be used?

    thank you very much!

    Best regards

  • Hi,

    I believe I suggested a solution by disabling the INTERCORE_ETH_SUPPORT flag in ethfw. Can you confirm that the issue is resolved?

    Regards,
    Tanmay

  • Hi Tanmay,

    Thanks for your support. We now can confirm that the issue is resolved for now.

    As mentioned that "as long as you do not use multicore multicast it should be fine", we would like to know if we use the multicore multicast feature in the future, what would happen if we keep this flag disabled?

    Thank you very much!

    Best regards

  • Hi,

    we would like to know if we use the multicore multicast feature in the future, what would happen if we keep this flag disabled?

    To properly use the multicore multicast functionality, an addition interface has to added to linux. That will take care of the issue.

    Regards,
    Tanmay