Linux/TMDXIDK5728: PRU Ethernet

Is it possible to contact your developer to see if they can supply more instructions for this issue? We are rush in fixing this problem. Any idea or sugggestion from your developer will be helpful. Thanks a lot

I was told that your am5728idk board harware should support 4 pru-Eth ports without any issue, the only thing need to do is the software change. Please confirm if this information is correct or not.

If the above sentence is correct, then all my work should continue, otherwise I am wasting my time. I am trying to change the software  to make the am5728idk board work for 3 pru-eth and 1 Gigabite ports.

so far I changed the pin-mux in u-boot, and changed the dts files. What I did is disbaling the Gigabite port 1 and enabling pruss1-port1 (another pruss1-port0 I don't need). The results I got is the pruss1-port1 can get physical link up if connected to the network. But it never can go through any ethernet traffic. The fiurther check shows that the interrupt for rx and tx never fired.

Here is the dts file am57xx-idsk-common.dtsi file related change ( The other changes I think should be ok, such as the mdio interrupt, I saw the pruss1-port1 mdio interrupts did fired).

        pruss1_eth: pruss1_eth {
                status = "okay";
                compatible = "ti,am57-prueth";
                pruss = <&pruss1>;
                sram = <&ocmcram1>;
                interrupt-parent = <&pruss1_intc>;
                /*rx-queue-size = /bits/ 16 <254 134 134 254 48>;*/ /* RED */
                /*rx-queue-size = /bits/ 16 <194 194 194 194 48>;*/ /* EMAC */
                /* map is lowpcp-to->hipcp where val 3=q4, 2=q3, 1=q2, 0=q1 */
                /*pcp-rxq-map = /bits/ 8 <3 3 2 2 1 1 0 0>;*/

                pruss1_emac0: ethernet-mii0 {
                        phy-handle = <&pruss1_eth0_phy>;
                        phy-mode = "mii";
                        interrupts = <20>, <22>, <23>;
                        interrupt-names = "rx", "tx", "ptp_tx";
                        /* Filled in by bootloader */
                        local-mac-address = [00 00 00 00 00 00];
                        /*tx-queue-size = /bits/ 16 <97 97 97 97 48>;*/
                };

               pruss1_emac1: ethernet-mii1 {
                        phy-handle = <&pruss1_eth1_phy>;
                        phy-mode = "mii";
                        interrupts = <21>, <23>, <24>;
                        interrupt-names = "rx", "tx", "ptp_tx";
                        /* Filled in by bootloader */
                        local-mac-address = [00 00 00 00 00 00];
                        /*tx-queue-size = /bits/ 16 <97 97 97 97 48>;*/
                };
        };

This peice of dts code I copied from the pruss2 directly, only change the corresponding pruss2 to be pruss1. And leave  all the interupts the same number with the pruss2, I think they are the same, but not sure, please confirm.

If the above setup for pruss1 are correct, why the 20, 21 , 22, 23 interrupts fired for pruss2 ports correctly and never fired for pruss1 ports?

Ok, I understood. But We are trying to fix it ourselves and need some clue from you.

For the previouse posting,am5728idk,  the interrupts 20, 21, 22, 23, 24 work fine for RUSS2 2 cores, but not wokring for PRUSS1. Why 20,21, 22,23,24 interupts numbers used here for all the PRUSS, I couldn't find any documentation say why use these interrupt numbers, please explain how it works.(The 5718 idk use 20, 21, 22, 23, 24 interrupts for PRUSS1 and PRUSS2). And I figured out that these 5 interrupts not go through your crossbar interupt mapping.

And please give some clue how to fix it, either in software or in hardware as well?