AM5716: can AM5716 support HW MAC address filter function on PRUSS network port？

Hello,

Due to bandwidth, I will not be able to get to your question until next week.

Please see the following thread for reference in case it is helpful: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/885461/am5708-mac-filtering-in-the-pru-icss-driver

This was from an earlier SDK but it still might be enabled on the 6.03 SDK

Thank you for your patience.

-Josue

Hello,

On the 6.03 SDK, I have no found pruss1_port0_mc_mask, pruss1_port1_mc_mask?

Hello Victor,

Have you read through the following documentation https://software-dl.ti.com/processor-sdk-linux/esd/docs/06_03_00_106/linux/Industrial_Protocols_HSR_PRP.html#multicast-filtering?"

Also see https://software-dl.ti.com/processor-sdk-linux/esd/docs/06_03_00_106/linux/Industrial_Protocols_HSR_PRP.html#network-storm-prevention

-Josue

Hello Josue Zamitiz-Ayala,

problem：

The DSP1 core crashed in a network storm. Preliminary location: When the PRUICSS_pruEnable enabled network port was detected during restart, the DSP1 core died directly without any further action;

PRUICSS_pruEnable(ICSS_EMAC_testPruIcssHandle2, ICSS_EMAC_PORT_1-1); //
PRUICSS_pruEnable(ICSS_EMAC_testPruIcssHandle2, ICSS_EMAC_PORT_2-1); //

Two network storm control programme:

1.MAC address filtering method

  GOOSE single network port connection is not a problem, will not crash, and can process data normally; But when both network ports are connected to the network cable, an error message may occur and the device may restart, or it may not restart but the network port cannot receive data.

When both network ports are connected and restarted directly with an error message, the error message is as follows:

2. Traffic control

  Only when eth0 is set for traffic control, and only when eth0 is connected to a network cable, the real-time core will not die, but the received data still has abnormalities. In other situations, the real-time core still crashes directly, such as setting traffic control for EHT1 and connecting Ethernet cable to eth1 port.

The above are two possible solutions. Please help track the current issues
1. Please confirm if there are any issues with the added code
2. If the code is correct, please continue to track the existing issues

Victor,

Can you please describe the exact procedure you are doing, specifically the topology differences described in the following cases:

1.

victor_thor said:

GOOSE single network port connection is not a problem, will not crash, and can process data normally; But when both network ports are connected to the network cable,

• Please include block diagrams and the specific firmware that is being used.
• Is this your own PRUSS application?

2.

victor_thor said:

Only when eth0 is set for traffic control, and only when eth0 is connected to a network cable

• Please include block diagrams and the specific firmware that is being used.
• Is this your own PRUSS application?

-Josue

ETH3 is GOOSE port1, ETH4 is GOOSE port0

Switch, with one Ethernet cable connected to both ends of the switch, forming a loop

GOOSE single network port ：

Connect only one Ethernet cable from the switch to the device，For example, only linking to ETH3 or ETH4.

GOOSE double network port ：

ETH3 and ETH4 are both linked.

What firmwares are you using? Are they TI defaullt FWs or your own?

not default, we have modified some of the code and recompiled it to generate.

Victor,

So the FW you are modifying is DSP FW and not PRU FW?

Josue Zamitiz-Ayala,

Are you saying these two firmware， /lib/firmware/ti-pruss/am57xx-pru0-prueth-fw.elf and  /lib/firmware/ti-pruss/am57xx-pru1-prueth-fw.elf ?

Victor,

Yes, that is what I am referring to, are these the firmwares that are modified? 

What I want to understand is which core are you using to control the PRU cores. Are you using the C66 to control the PRUs?

Can you also confirm what operating system you are utilizing? I have been under the presumption that you are using Linux and I might be wrong.

And the pictures you shared do not clearly show how the relationships in ethernet connections. Can you please make a block diagram?

-Josue