RTOS/AM6548: TI EMAC driver using on bare metal AM65x R5F MCU

Hi Sergei,

This is forwarded to the R5F experts, however due to the holidays, responses may be delayed.

Best Regards,
Yordan

Sergei,

Let me try and set this up at my end so I can confirm or try to reproduce this issue. Can you clarify that you are setting up the EVM and CCS such that the SYSFW/DMSC firmware is loaded before you run the example? Does the example work for you on the A53 but only fail from the R5F?

 In addition to the EMAC driver code, there is also a EMAC diagnostic code that tests the PHY Setup and EMAC setup on the EVM. Have you tried this on your EVM to see there is no HW issue?

Regards,

Rahul

Hello, Rahul!

Firstly, thank you for your answer and help!

1. Yes, I have set up the EVM and CSS and load SYSFW/DMSC firmware, following the instructions ‘Advanced AM65x Debug Setup with DMSC Firmware Load’ witch are described here:
software-dl.ti.com/.../index_how_to_guides.html

2. I have not tried to execute the examples on the A53 core. But the thing is that the examples work properly on R5F, but only in scope of their tests.

3. I have not tried to run EMAC diagnostic tests, but we have brought up Linux kernel on A53, and the Linux is able to send ARP packets to the Ethernet through the CPSW port and the ICSS-G ports. I can capture the packets by Wireshark on my host PC. That’s why I can realize that AM6548 SoC on the EVM board is connected to the PHY chips of each port correctly and HW works well.

Rahul, my problem is that I cannot set up any of the ports using TI EMAC driver to sent a Ethernet packet to network.

The Emac_Cpsw_TestApp is a loopback test inside the CPSW switch, and it does not send any packets to the port 6.

The Emac_Icssg_TestApp sends only a test packet from one ICSS-G port to other ICSS-G port. The test at the beginning waits for link-up on the port 4 and port 5. And after the links are upped it sents the test packet from port 4 to port 5. I tried to deceive the test for capturing the test pack on my host PC. But the attempt was fail. I connected port 5 to port 6 to give the test an ability to detect link-up on port 5, and the port 4 I connected to the host PC for catching the test packet by Wireshark. So, I could not catch up it. Also, the initialization for the test uploads ‘rtu_test0_bin.h’ and ‘rtu_test1_bin.h’ files to the on SoC RTUs. Might the reason that I cannot send a packet to the ICSS-G port be that the firmwares for RTUs are for the test only?

Thus, using the setting for the test I cannot set up the the TI EMAC driver to send Ethernet packets to the network. And I am interested in do you have an initialization sequence for EMAC driver and associated peripherals such as UDMA, MDIO, PHY, PRU, RTU, and etc. to initialize the SoC for sending packets out? It may be any port either CPSW or ICSS-G.

Please help me to solve the problem, or show a direction what I have to do.

Hi,

There are also NIMU test examples that communicate with outside world:
\packages\ti\binary\NIMU_Cpsw_ExampleApp
\packages\ti\binary\NIMU_Icssg_ExampleApp

They can run on A53 or R5F. Can you try that? Also, those examples run standalone, which means you can't run Linux on A53.

Regards, Eric

Hello, Eric.

Thank you for these examples! Yes, of course I'm going to try that.

Any news?

Regards, Eric

Hello, Eric.

I'm sorry, no news yet. We had holidays in Russia and I couldn't check the test. And also, after the holidays I got sick. So, I hope I will be fine on Monday and continue my investigation. In any case I let you know about the result.

Part Number: AM6548

Tool/software: TI-RTOS

Hello, TI.

I am still continue working on setting up the TI EMAC driver on TMDX654IDKEVM AM65x Industrial Development Kit, and still can’t receive or send an Ethernet packet to the network. Having examined the NIMU test for CPSW, I saw that the test could communicate with my laptop answering the ICMP packets. Also, I researched the test setting and configured my software and the TI EMAC driver used by the software exactly how the NIMU test does. However it didn’t help me to use the TI EMAC driver.

I have run up the NIMU test under debugger, and assign all C source files to have ability to set breakpoints and to do debugging the test step by step. And currently I have a question. The TI EMAC driver uses the TI UDMA driver, which uses the TI INTA (Interrupt Aggregator) driver. So, having this sequence the TI EMAC driver for receiving a packet sets up the TI UDMA driver, and the TI UDMA driver sends an interrupt function within a settings to TI INTA driver. Therefore, when an Ethernet packet received, the TI UDMA driver ISR function is called, and the function does some other steps to complete the packet receiving.

Under debugging I have seen that the ISR function is called in the NIMU test, but I cannot repeat this in my software. The the NIMU test is executed under TI RTOS, my software uses ‘nonos’ source code provided by TI PDK and executed on bare metal. May the different be in it? And what do I have to initialize more to see that the ISR function is called on bare metal using the ‘nonos’ source code? May the TI RTOS do some additional HW initialization for TI EMAC driver works?

Hello, Eric.

Thank you! Yes, I saw source code of the diagnostic test and also tried the settings of the TI EMAC driver from it for my project. The settings did not force the driver to be working as well. But I have not executed the test. Ok, I am going to execute the test and also to take a look at it under debugger to realize step by step what it does. Please give me some time for that and I will return to you with an answer.