Hi,
we are using am578 SDK ti-processor-sdk-linux-am57xx-evm-03.02.00.05-Linux-x86-Install.bin
In our custom board we connected PRUSS2 ethernet to micrel ethernet driver IC. we connected rx,tx data lines clocks and ctl signals
I changed the DTS file as below:
/* Dual-MAC Ethernet application node on PRU-ICSS2 */
pruss2_eth {
compatible = "ti,am57-prueth";
pruss = <&pruss2>;
sram = <&ocmcram1>;
interrupt-parent = <&pruss2_intc>;
pruss2_emac0: ethernet-mii0 {
phy-handle = <&pruss2_eth0_phy>;
phy-mode = "mii";
/*interrupts = <20>, <22>;
interrupt-names = "rx", "tx";
/* Filled in by bootloader */
local-mac-address = [00 00 00 00 00 00];
};
pruss2_emac1: ethernet-mii1 {
phy-handle = <&pruss2_eth1_phy>;
phy-mode = "mii";
/*interrupts = <21>, <23>;
interrupt-names = "rx", "tx";
/* Filled in by bootloader */
local-mac-address = [00 00 00 00 00 00];
};
};
&pruss2 {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&pru2_mii_pins_default>;
/*dual_emac;*/
pru2_0: pru0@4b2b4000 {
mboxes=<&mailbox4 &mbox_pru2_0>;
status = "okay";
};
pru2_1: pru1@4b2b8000 {
mboxes=<&mailbox4 &mbox_pru2_1>;
status = "okay";
};
&pruss2_mdio {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&pru2_mii_davinci_mdio_pins_default>;
pruss2_eth0_phy: ethernet-phy@5 {
reg = <5>;
dual_emac_res_vlan = <3>;
};
pruss2_eth1_phy: ethernet-phy@6 {
reg = <6>;
dual_emac_res_vlan = <4>;
};
};
we used physical address of 5 and 6
we included ti,am572x-beagle-x15 in pru_rproc.c
the log is as follows regarding pru ethernet
[ 2.318576] prueth pruss2_eth: unable to get pruss handle
[ 2.532482] ti-pruss 4b280000.pruss: creating PRU cores and other child platform devices
[ 2.586488] davinci_mdio 4b2b2400.mdio: davinci mdio revision 1.6
[ 2.586491] libphy: 4b2b2400.mdio: probed
[ 2.591095] davinci_mdio 4b2b2400.mdio: phy[5]: device 4b2b2400.mdio:05, driver Micrel KSZ9031 Gigabit PHY
[ 2.591101] davinci_mdio 4b2b2400.mdio: phy[6]: device 4b2b2400.mdio:06, driver Micrel KSZ9031 Gigabit PHY
[ 2.592507] remoteproc4: 4b2b4000.pru0 is available
[ 2.592512] remoteproc4: Note: remoteproc is still under development and considered experimental.
[ 2.592515] remoteproc4: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[ 2.592583] pru-rproc 4b2b4000.pru0: PRU rproc node /ocp/pruss@4b280000/pru0@4b2b4000 probed successfully
[ 2.592756] remoteproc5: 4b2b8000.pru1 is available
[ 2.592759] remoteproc5: Note: remoteproc is still under development and considered experimental.
[ 2.592763] remoteproc5: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[ 2.592831] pru-rproc 4b2b8000.pru1: PRU rproc node /ocp/pruss@4b280000/pru1@4b2b8000 probed successfully
[ 2.593758] remoteproc4: Direct firmware load for ti-pruss/am57xx-pru0-prueth-fw.elf failed with error -2
[ 2.593765] remoteproc4: failed to load ti-pruss/am57xx-pru0-prueth-fw.elf
[ 2.593815] remoteproc5: Direct firmware load for ti-pruss/am57xx-pru1-prueth-fw.elf failed with error -2
[ 2.593821] remoteproc5: failed to load ti-pruss/am57xx-pru1-prueth-fw.elf
what else to be changed
Regards,
Kumari
