• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 2076 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.

Problems with 'ethernet_mac'-example on AM335x ICE BOARD (V2.1A)

user4599137
Prodigy 60 points
Other Parts Discussed in Thread: SYSBIOS

Hi,

I have a problem with running the 'ethernet_mac' example on the AM335x ICE BOARD (ReV: 2.1A) in CCS (Version 6.1.2.00015).

At the moment I´m able to build the project, connect to the board and uploading the program to the CortexA8. When the upload finishes the PC stopps in the main-function and I can start the application with Resume. Then I can see that the LED is blinking (green), but I see no Ethernet traffic on both ports.
Also I can see printfs in the terminal (connect to usb COM port) where two IP addresses are shown (192.168.1.3 and 192.168.2.3) When I try to send a ping to this interfaces I can see in wireshark that the board is not responding to the ARP requests from my computer.

Board Configuration:
J18 & J19: Jumper on Pin 2-3

What could be the problem that the board does not send out any ethernet packets (at startup or when receiving ARP-Requests for own IP)?


Thank you



  • 0
    TI__Guru**** 393215 points
    Hi,

    I will ask the industrial team to comment.
  • 0
    TI__Mastermind 39610 points

    Hi, I did a sanity check of Ethernet_mac example from our sysbios_ind_sdk_2.1.1.2 and ping respond OK. Below how I test it:

    - My PC was set to 192.168.1.1 when testing Ethernet_1 port in the board (192.168.1.3)

    - My PC was set to 192.168.2.1 when testing Ethernet_0 port in the board (192.168.2.3)

    Your jumpers are OK. One thing worthy to check is to disable antivirus or firewalls.. in the past I have to disable my corporate antivirus in order to get some type of packets in wireshark..

    Thank you,

    Paula

  • 0 in reply to Paula Carrillo
    Prodigy 60 points

    Hi, thank you for response, but I already tried to disable firewall and antivirus.

    I tried pinging the board on both interfaces, but I never got a response. Furthermore I can see in wireshark log that the board is not responding to the ARP request for the IP resolution:

    I configured my computer also to the IP 192.168.1.1 (SN: 255.255.255.0).

    In terminal I can see that the board should have the IP 192.168.1.3 on one of the two interfaces:

    TI Industrial SDK Version - IASDK 2.1.1.2
    Device name     : AM335X
    Chip Revision   : AM335x [PG2.1]
    ARM Clock rate  : 600 MHz
    SYS/BIOS Ethernet MAC (ICSS) Sample application running

    Interface ID:
            IP Address: 192.168.2.3
            MAC Address: 68:c9:b:e4:c2:c8


    Interface ID:
            IP Address: 192.168.1.3
            MAC Address: 68:c9:b:e4:c2:ca

    So do you have any idea what could be wrong, that the board does not respond to the ARP requests?

    Furthermore I would expect that the board will send out ethernet packets after startup for checking IP conflicts on network, but I can not capture any packet in wireshark after starting the ethernet_mac example. My computer is directly connected to the board, but I also tried using a network hub (no switch) where I should see every packet (wireshark) which was send out from the board. Also I have no problem with sending pings to other devices from my computer.

    Thank you

  • 0 in reply to user4599137
    Expert 1505 points
    Hi.

    Does your ICEv2 board boot the preloaded Ethercat application before you connect through the usb cable?
    Take a look at this discussion, bottom of the page: e2e.ti.com/.../313845

    You could try to modify boot sequence jumper J5, connecting pins 1 and 2. Power cycle the board and retry to test your application.
  • 0 in reply to eugenio
    Prodigy 60 points
    Thank you for your help, changing boot sequence jumper solves the problem. Now I am able to ping both IP address.