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

PHY set up, and interacting with the "gem"

Former Member

I am trying to configure the PHY in an ethernet packet manipulating program that I am writing.
According to the technical reference manual (Zynq-7000 AP SoC Technical Reference Manual), before I begin configuring bits on the PHY maintenance register I need to wait for it to become idle ("gem.net_status[phy_mgmt_idle]=1").

However, I cannot simply do "while(gem.net_status[phy_mgmt_idle]!=1){sleep(1);print("waiting for idle
");}
because gem is not an object in my program.

Where do I go to find the documentation about how to interact gem?

Parents
  • 0

    As discussed in an earlier thread you take a look at the example code for the xemacps there are functions in this code used to access the PHY registers: http://zedboard.org/content/peripheralstest-xemacps

     

    These routines are written at a higher level of abstraction and are taking care of the low level 'bit banging' of the physical interface you are referring to from the TRM so that you can just call these functions and read or write the PHY registers. You can follow the code down level by level to see this by looking at function calls like 'XEmacPs_PhyRead' and 'XEmacPs_PhyWrite'  within the functions like XEmacPsDetectPHY used in the example code. These functions use lower level function calls like XEmacPs_WriteReg and XEmacPs_ReadReg which are directly accessing the registers referred to in the TRM.

     

    -Gary

Reply
  • 0

    As discussed in an earlier thread you take a look at the example code for the xemacps there are functions in this code used to access the PHY registers: http://zedboard.org/content/peripheralstest-xemacps

     

    These routines are written at a higher level of abstraction and are taking care of the low level 'bit banging' of the physical interface you are referring to from the TRM so that you can just call these functions and read or write the PHY registers. You can follow the code down level by level to see this by looking at function calls like 'XEmacPs_PhyRead' and 'XEmacPs_PhyWrite'  within the functions like XEmacPsDetectPHY used in the example code. These functions use lower level function calls like XEmacPs_WriteReg and XEmacPs_ReadReg which are directly accessing the registers referred to in the TRM.

     

    -Gary

Children
No Data