Actions
Forum Thread Details
  • State Not Answered
  • Replies 2 replies
  • Subscribers 363 subscribers
  • Views 452 views
  • Users 0 members are here
Related

Peripherals_Test: xemacps

e14 Contributor

When I slowly step through the Peripherals Test, the "packet" is received before it is send. I believe this because the Rx interrupt handler is called before the Tx interrupt handler.
What am I missing?

Also, the Ethernet is set to Loopback, which I believe means that the ZedBoard never actually transmits anything, it simply enqueues a packet to the PHY, than get it back out. I again believe this because running wireshark on a switch with the ZedBoard, I never see anything.

How do I check what it inside the PHY during debugging?

Any help that someone could offer would be really helpful.

  • 0

    Attempting to debug software that reacts to external events using the single-step debugger is problematic.  I think you will have more luck understanding what is going on if you set breakpoints inside the interrupt handlers, and let the program run until it hits one of the breakpoints.

    You are correct that the PeripheralTest application does not send anything out the ethernet port.  You can view the values of registers in the MAC by checking the address of the device in the memory map, and the locations of the internal registers in the data sheet.   Then use the memory window to dump the contents in hex.

    If you want to use Wireshark to monitor the traffic, I'd suggest using the Echo Server template within the SDK to create a functional ethernet application.  When the target ethernet is connected to your host, you should be able to type characters in telnet/ssh and view the echo in your terminal window, and then capture the traffic in Wireshark to see what the complete packets looked like.

    Ron

  • 0

    If you take a look at the example code for the xemacps ( click on 'Examples' to the right of the ps7_ethernet_0 in the Peripheral Drives section of the system.mss in the SDK ) there is "xemacps_example_util.c". There are functions in this code used to access the PHY.

     

    This code 'detects' the PHY address but if you want to skip that step the PHY on the Zedboard is hard coded to address 0.

     

    -Gary