• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 102 subscribers
  • Views 969 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Linux/66AK2H14: PHYless ethernet

Gabor Kocsis67
Prodigy 80 points
Part Number: 66AK2H14

Tool/software: Linux

Hello Everybody,

We have made our custom board based on three of 66ak2h14 SoC. We want them to boot via transceiverless Ethernet that provided on our board by another Soc.

At the first round we try to bring them up from a QSPI flash. The U-Boot runs correctly from flash but we can't bring up the network. This U-Boot version uses the DeviceTree.

We have checked the SerDes signals between the DSP Soc and the Ethernet provider Soc and we have found a communication between them. We haven't decoded this communication,

but it seemed to be a negotiation dialogue.

In the DeviceTree we have set the fixed-link type connections

My question is we have to set other than fixed-link type connections in the DeviceTree for transceiverless Ethernet and have to modify the source code of U-Boot.

In the U-Boot environment we have set the ethaddr,  eth1addr, ethprime, ethact variables.

Thanks in advance,

Gabor

  • 0
    TI__Guru**** 161600 points
    Hi,

    Which Processor SDK Linux are you using?

    Best Regards,
    Yordan
  • 0 in reply to Yordan Kovachev
    Prodigy 80 points
    Hi,
    We 're using the mcsdk_linux_3_00_03_15.
    But we haven't got to the Linux yet, we try to bring up the network at U-Boot level. Our U-Boot version is 2018.07-rc2. I downloaded it on 11th of July.

    Best regards,
    Gabor
  • 0 in reply to Gabor Kocsis67
    TI__Guru 50170 points
    Hi, Gabor,

    U-boot device tree support is only in Processor SDK, therefore it is not recommended to mix Processor SDK u-boot with MCSDK.
    Though Processsor SDK is evolved from MCSDK, but a lot of things changed. The code may not be compatible.

    As for PHY-less Ethernet in U-boot, we have not tried it in u-boot, but in kernel. Please refer to the "Note" in NetCP User's Guide on how to enable all 8 ports on K2E.

    software-dl.ti.com/.../Foundational_Components_Kernel_Drivers.html

    In K2E, we have 2 ports (eth0, eth1) exposed on 2 PHYs on the EVM, 2 MAC_to_MAC ports (eth2, eth3, PHY-less) to AMC Break-out-Card, and 4 MAC_to_MAC ports (eth4-7) to RTM BoC. You didn't mention what the fixed-link type is, but in the document, it is set to 2 (LINK_TYPE_SGMII_MAC_TO_MAC_FORCED_MODE). On K2H, there are only 2 MAC_MAC ports to the AMC connector.

    Since we never tried to enable MAC_MAC port in u-boot and booting from the PHY-less ports, I am not sure what changes needed in u-boot. You may want to try it and see if it works.

    Rex
  • 0 in reply to Rex Chang
    Prodigy 80 points

    Hi Rex,

    Thank you for your answer. I was able to set up the PHYless Ethernet at U-Boot level. The DSP chip (66ak2h14) gets IP address via DHCP. But the tftpboot doesn't work at all . What can the problem be ?

    I tried both kind of u-boot to see if they work. I experienced the same with them, the DHCP works well with both of u-boots, the chip gets an IP address, but it can't download any file.

    Best regards,

    Gabor

  • 0 in reply to Gabor Kocsis67
    TI__Guru 50170 points
    Gabor,

    Can you ping both way? I suspect it may have something to do with uboot ethact variable. The K2HK EVM has 4 Ethernet ports (port 0 - 3) with K2HK_EMAC, K2HK_EMAC1, K2HK_EMAC2, K2HK_EMAC3 interface names. Try setting to EMAC2 or EMAC3 to see if it helps. If not, you may need to debug a bit using wireshark to see if any packets in and out of the port.

    Rex
  • 0 in reply to Rex Chang
    Prodigy 80 points
    No, the ping doesn't work. If I use the K2HK_EMAC the DHCP works as I mentioned. If I try any other interface, the DHCP doesn't work either.
  • 0 in reply to Gabor Kocsis67
    TI__Guru 50170 points
    Hi, Gabor,

    It doesn't make sense that DHCP works but not TFTP. Is there any way you can capture the traffic to see what packets are in and out of the port for both DHCP and TFTP and verify the IP address is truely from DHCP through this port?

    Rex