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.
Hi,
TI currently provides GESI (Gateway Ethernet Expansion board) and QSGMII two ways for users to use CPSW9G.
Our attempt to use QSGMII was a failure, even if we already use the binary files compiled by TI.
I used to ask questions about QSGMII in TIi as bellow.
e2e.ti.com/.../903480
We next want to try to use CPSW9G with GESI, but we are worried that it cannot be used in our environment as QSGMII.
So I would like to ask if I want to try to use GESI under PSDK6.2, what needs to be modified?
Allen,
I'll review further your referenced post on QSGMII and see if we can make progress there. As noted in that thread, we are not supporting QSGMII directly in SDK 6.2 and need to patch the release to bring up the QSGMII SerDes interface.
For the GESI card, we have support directly with the SDK6.2 release, so you should be able to get it working quickly.
The Ethernet Firmware is configured for use with the GESI card, and demos are included in the Processor SDK RTOS Automotive package (fromhttps://www.ti.com/tool/PROCESSOR-SDK-DRA8X-TDA4X ).
See http://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/ethfw/docs/user_guide/ethfw_c_ug_top.html#ethfw_c_ug_ethfw_demos for a description of the included demos with the package.
Please do let me know if you are facing a specific issue with the initialization and we can address.
Best regards,
Dave
Hi Dave,
Thank you for your continued support of the QSGMII issue. If we can do something to help clarify the issue, let us know.
For the support of GESI under SDK6.2, you have posted a link.
software-dl.ti.com/.../ethfw_c_ug_top.html
I don’t know much about the following statement from TI in the link.
TI:
Note: If building the Ethernet Firmware for integration in Linux, please uncomment below in CPSW LLD's makefile located at <PDK_PATH>/packages/ti/drv/cpsw/cpsw_component.mk:
#CPSW_CFLAGS += -DSDK_6_2_CORE_SDK_IMAGE
This change is required to avoid board-level settings conflicts with Linux bootloader.
Which image will be affected, when I uncomment #CPSW_CFLAGS += -DSDK_6_2_CORE_SDK_IMAGE?
Isn't the source code for Ethfw all under the folder (ethfw/ethremotecfg/server)?
Allen,
The Ethernet Firmware can be be loaded and run as a standalone RTOS application on the R5F cores. For this, the application itself is responsible to configure the system firmware through the SciClient.
If you are loading through Linux, then Linux is responsible for the system firmware configuration through rm-cfg, and the Ethernet Firmware needs to be compiles to exclude this.
Best regards,
Dave
Hi Dave,
The following is our current environment on the sd card.
root@j7-evm:/lib/firmware# realpath j7-main-r5f0_0-fw
/lib/firmware/app_remoteswitchcfg_server.xer5f
Our current boot message displays the message as bellow,
so should it be considered to load ethfw through Linux?
boot message:
remoteproc remoteproc4: Booting fw image j7-main-r5f0_0-fw, size 9837804
After uncomment the CPSW_CFLAGS bellow, and then recompiling, which image should I replace with compiled image on the SD card?
#CPSW_CFLAGS += -DSDK_6_2_CORE_SDK_IMAGE
for example : app_remoteswitchcfg_server.xer5f ?
Allen,
Yes, the remoteproc message indicates the loading of the R5F firmware from Linux. And you are correct that the app_remoteswitchcfg_server.xer5f should be what is loaded.
Best regards,
Dave
Hi Dave,
Please help me to answer another question.
After uncomment the CPSW_CFLAGS bellow, and then recompiling, which image should I replace with compiled image on the SD card?
#CPSW_CFLAGS += -DSDK_6_2_CORE_SDK_IMAGE
for example : app_remoteswitchcfg_server.xer5f ?
Allen,
Yes, you want to replace the app_remoteswitchcfg_server.xer5f image.
Best regards,
Dave