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.
Tool/software: Linux
Dear TI support team,
we've seen in the release notes for the processor SDK 06.00 that U-Boot now supports use of the PRU ethernet ports.
We've tested this following the instructions from the documentation (http://software-dl.ti.com/processor-sdk-linux/esd/docs/06_00_00_07/linux/Foundational_Components_U-Boot.html#booting-linux-from-the-network) and it works with the bottom ethernet port on the base board itself.
We didn't manage to get this running with one of the ports on the IDK board, nor did we manage to get this to work on our own custom hardware. We modified the setenv lines from the documentation to use rprocs 0 and 1 and also changed ethact to pruss0_eth, but so far haven't been able to get this to work. On our custom hardware only ICSSG0 and ICSSG1 are connected to PHYs.
The documentation states that "Only PRU-ICSSG port of the base board (ICSSG2) is supported for net boot.". Is there a reason for this limitation?
Regards,
Dominic
Hello Dominic,
The driver supports ICSSG0, ICSSG1, and ICSSG2. For now, TI is only publishing ICSSG2 support to the broad market.
I have not tested it, but I think you should be able to enable ICSSG0 and ICSSG1 on the IDK board by doing this:
Revert the u-boot commit cfe135d1cbd939b192e6ab1958cd61b6327e1934 . We have information on getting the u-boot sources in the u-boot general information section. Rebuild u-boot.
Let me know if this works for you, or if additional steps need to be taken.
Regards,
Nick
Hello Nick,
we got the ICSSG0 ethernet ports on our own hardware to work with the U-Boot driver.
Since we didn't have an environment to rebuild U-Boot for the SDK readily available we gave our own hardware another try, and basically the only thing that we missed was that originally we didn't want to use DHCP so we removed the "dhcp" call from the init_icssg2 command (between rproc start and stop). With that we didn't get the PRU ethernet to work.
It looks like there needs to be some network communication between rproc start/stop, then you can later use the start_icssg2/stop_icssg2 calls to enable networking when needed.
Regards,
Dominic