• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 492 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

PROCESSOR-SDK-J7200: CPSW5G Not Work on PSDK 9.07 Release

Jack
Guru 10136 points

Part Number: PROCESSOR-SDK-J7200

Hi TI PSDK Team


A customer is testing the SDK9.07 version released on August 7th.

During the test, we found that the interface of CPSW5G is not working.

Theyt could not see eth1 in the Ifconfig -a command test, please check.

SDK: 9.07

Binary: tisdk default

  • 0
    TI__Guru* 80950 points

    Hi,

    Jack said:
    A customer is testing the SDK9.07 version released on August 7th.

    From SDK 9.0 Onwards Ethernet drivers for CPSWnG will not be enabled by default. 
    We need to add dtb overlay to the uEnv.txt file and boot the SOC.

    For Virtual MAC driver:

    1. Add below device tree overlay in uEnv.txt file and save to load virtual driver in every boot.
    name_overlays="ti/k3-j7200-evm-virt-mac-client.dtbo"

    2. Update the firmware soft link for Main R5F0_0 core (i.e. MCU2_0) with EthFw binary.
    # ln -s /lib/firmware/ti-eth/j7200/app_remoteswitchcfg_server_strip.xer5f j7200-main-r5f0_0-fw

    For Native Linux Driver:
    1. Add device tree overlay in  uEnv.txt file and save to load Native Linux driver in every boot.
    name_overlays="ti/k3-j7200-evm-quad-port-eth-exp.dtbo"


    Best Regards,
    Sudheer

  • 0 in reply to Doredla Sudheer Kumar
    Intellectual 709 points

    HI Sudheer. 

    As you know, we use the default image image on the J7200 EVM.
    Three files are used to boot the EVM board: Tiboot3.bin, tispl.bin, and u-boot.bin. So we don't use uEnv.txt, right?


    j7200-main-r5f0_0-fw -> /lib/firmware/ti-eth/j7200/app_remoteswitchcfg_server_strip.xer5f


    In addition, the simboklic link in j7200-main-r5f0_0-fw is also well established.

    Please tell me how to activate eth1 on j7200.

    root@j7200-evm:/lib/firmware/ti-eth/j7200# cat /sys/kernel/debug/remoteproc/remoteproc*/trace0
Sciclient_boardCfgRm init Passed
DM Built On: Jul  4 2023 18:43:09
Sciserver Version: v2022.01.1.0-REL.PSDK.09.00.00.29-2-gbcadc
RM_PM_HAL Version: REL.PSDK.09.00.00.22
Starting Sciserver..... PASSED
IPC_echo_test (core : mcu1_0) .....
mcu1_0 <--> mcu2_1, Ping- 10000, pong - 10000 completed
=======================================================
            CPSW Ethernet Firmware
=======================================================
Warning: Using 6 MAC address(es) from static pool
ETHFW: Shared multicasts (software fanout):
  01:00:5e:00:00:01
  01:00:5e:00:00:fb
  01:00:5e:00:00:fc
  33:33:00:00:00:01
  33:33:ff:1d:92:c2
  01:80:c2:00:00:00
  01:80:c2:00:00:03
ETHFW: Reserved multicasts:
  01:80:c2:00:00:0e
  01:1b:19:00:00:00
EnetMcm: CPSW_5G on MAIN NAVSS
Mdio_open: MDIO manual mode enabled
PHY 16 is alive
PHY 17 is alive
PHY 18 is alive
PHY 19 is alive
EnetPhy_bindDriver: PHY 16: OUI:0001c1 Model:27 Ver:00 <-> 'vsc8514' : OK
EnetPhy_bindDriver: PHY 17: OUI:0001c1 Model:27 Ver:00 <-> 'vsc8514' : OK
EnetPhy_bindDriver: PHY 18: OUI:0001c1 Model:27 Ver:00 <-> 'vsc8514' : OK
EnetPhy_bindDriver: PHY 19: OUI:0001c1 Model:27 Ver:00 <-> 'vsc8514' : OK

ETHFW Version   : 0.02.00
ETHFW Build Date: Apr 15, 2023
ETHFW Build Time: 12:20:32
ETHFW Commit SHA: 05546b8d

Starting lwIP, local interface IP is dhcp-enabled
Host MAC address: 70:ff:76:1d:92:c3
[LWIPIF_LWIP] Enet LLD netif initialized successfully
[LWIPIF_LWIP_IC] Interface started successfully
[LWIPIF_LWIP_IC] NETIF INIT SUCCESS
[LWIPIF_LWIP_IC] Interface started successfully
[LWIPIF_LWIP_IC] NETIF INIT SUCCESS
Added interface 'br4', IP is 0.0.0.0
CpswProxyServer: Virtual port configuration:
  mpu_1_0 <-> Switch port 0: mpu_1_0_ethswitch-device-0
  mcu_2_1 <-> Switch port 1: mcu_2_1_ethswitch-device-1
  mpu_1_0 <-> MAC port 1: mpu_1_0_ethmac-device-1
  mcu_2_1 <-> MAC port 4: mcu_2_1_ethmac-device-4
CpswProxyServer: initialization completed (core: mcu2_0)
CpswMacPort_checkSgmiiStatus: MAC 3: SGMII link parter config port: link up: 1-Gbps Full-Duplex
Cpsw_handleLinkUp: Port 3: Link up: 1-Gbps Full-Duplex
REMOTE_SERVICE: Init ... !!!
REMOTE_SERVICE: Init ... Done !!!
IPC_echo_test (core : mcu2_1) .....
mcu2_1 <--> mcu1_0, Ping- 10000, pong - 10000 completed

    Best Regards,

    Dongseuk

  • 0 in reply to Kim DongSeuk
    TI__Guru* 80950 points

    Hi,

    Kim DongSeuk said:
    Three files are used to boot the EVM board: Tiboot3.bin, tispl.bin, and u-boot.bin. So we don't use uEnv.txt, right?

    Will use uEnv.txt for any customization like enabling device tree overlays or setting u-boot environment variables and so on..

    If you are using SD boot mode, once after Media card is prepared connect media to PC and update uEnv.txt in boot partition of Media card.

    Or you can enable from U-Boot prompt by stopping at u-boot and run below, but it has to be done in every boot time.
    name_overlays="ti/k3-j7200-evm-virt-mac-client.dtbo"

    Best Regards,
    Sudheer