• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 558 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.

XEVMK2LX: Packet is not comming out from interface eth0 or eth1

Gautam Shah90
Genius 3815 points

Part Number: XEVMK2LX

Hi,

We have TI lamarr chipset board with three ethernet interface "Eth0, Eth1, Mgmt"
We are running LTE stack on this board" L3 run on ARM, L2 & L1 on DSP".

All communication is configured through eth0 interface.

Syslib version 3.0.9

After L3, L2, & L1 process up, system work normaly. I am able to ping other node of the network from my board eth0 interface.

Once UE attach happen & I run UDP data from UE in uplink, network get blocked "L2 using fast path to transmit GTPU packet from enodeb to MME"  

No packet is going out "Not from ARM or DSP, ping to other node from ARM got stopped, Fapi packet log coming from enodeb is also stopped". Still packet can be received by board but TX got bloacked.

MGMT interface RX/TX still working maybe because as it doesn't use Lamarr switch "As per my understanding"

Can you please help me to find out, what goes wrong with system?

From where I can start my debugging? How I can check the netcp packet stats?

Thanks.

  • 0
    TI__Guru* 95265 points

    Hi,

    66AK2L has 4 SGMII ports, so ETH0, ETH1 and Mgmt should use the same K2L switch. In the K2L user guide http://www.ti.com/lit/ug/spruhz3a/spruhz3a.pdf, Ethernet Switch Module, are you able to find out in the statistics that there is no packet counter increment on Tx side?

    What is the TI Ethernet driver Tx/Rx packets?

    Once UE attach happen & I run UDP data from UE in uplink =====>is this an application use Eth0? Or does this use packet DMA? has CPPI and QMSS usage?

    Regards, Eric

  • 0 in reply to lding
    Genius 3815 points

    Thanks Eric for you response.

    Regarding you Query, the response are as inline.

     are you able to find out in the statistics that there is no packet counter increment on Tx side

    Gautam: Yes, I am using mirror port to capture all packet coming out from board. Its 100% confirmed no packet coming out from board.

    What is the TI Ethernet driver Tx/Rx packets?

    Gautam: Can you please tell me, how I can capture it. I captured the PA status at DSP level but it doesn't showing any abnormal behavior before or after issue happened.

    Once UE attach happen & I run UDP data from UE in uplink =====>is this an application use Eth0? Or does this use packet DMA? has CPPI and QMSS usage?

    Gautam: UE "Cell phone", is connected with board, over the air. UE transmit its data in uplink, enodeb received it on radio interface, after this L1 process this data & send to L2, L2 have fast path interface with EPC "other node in network", L2 use fast path "CPPI, QMSS" to transmit this data using eth0 interface toward EPC.

    When the above process happen, all of sudden network get block. The TX from arm & dsp, both got stopped. 

    I hope, I provided the required information.

    I can attach CCS with my system, so if you need any register information, I can provide that too.

    Please let me know if you need any other information.

    Thanks.

  • 0 in reply to Gautam Shah90
    TI__Guru* 95265 points

    Hi,

    Thanks for the information! What is the TI software used in this infrastructure and version number? I meant what software is used to configure QMSS, CPPI, PA etc, and send the packets out of the EMAC port?

    Edit: sorry I saw you mentioned SYSLIB 3.0.9, was any TI MCSDK PDK package used in the integration? Do you have any unit test for the packet interface? Trying to understand if some packages worked before, what changes broke it? The support for SYSLIB is limited.  

    Regards, Eric

  • 0 in reply to lding
    Genius 3815 points

    Hi Eric,

    Thanks for your kind support. We found the cause of this abnormal behavior.

    In our system, at boot up time, we run some diagnosis procedure to check the System/hardware health, something like as below

    Power On Self Test
    POST external memory ... PASSED
    POST EMIF NAND read ... PASSED
    POST EMAC TEST for port 0 ... Port doesn't have mdio - test skipped
    POST DSP0 Test ... PASSED
    POST DSP1 Test ... PASSED
    POST DSP2 Test ... PASSED
    POST DSP3 Test ... PASSED
    POST ARM CORE 1 Test ... PASSED
    POST MARCONI0 Test ... bmc_cmd_send failure PASSED
    POST MARCONI1 Test ... PASSED
    SF: Detected N25Q128A with page size 64 KiB, total 16 MiB
    Test complete
    backhaul_link_status:0
    Hit ctrl+c key to stop autoboot:  0
    Unmounting UBIFS volume k2l-evm-rootfs!

    We observed that if we disable the interface diagnosis test, system is working fine.

    Currently our System team is looking in this test procedure. 

    Thanks for your kind help. will update this ticket with our further findings or you can close it for now.

    Thanks.