• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 435 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.

DM8148 - PINMUX - EMAC1 RGMII PINS MISSING?

sal anfuso
Prodigy 10 points

Hi -

We are trying to use the PinMux Utility, v2.2.0, to pin out our DM8148 device. 

We require the use of both EMAC0 as RMII and EMAC1 as RGMII. 

I don't seem to be able to get to the EMAC1 pins (as defined in Table 3-7 of  SPRS647B - March 2011– Revised Sept 2011- TMS320DM814x datasheet)  for RGMII when I select EMAC1 in the PinMux Peripheral Interfaces block.  The pins are tied up in the Fcn1 Column of the EMAC(0) PinMux Peripheral Interfaces block.

I was under the impression that I could use both EMAC0 and EMAC1 in these modes.

Is there some pin use rule I am breaking?  I've defined several interfaces, approx. 50 balls, with no conflicts, all green.

Also, is there a way to export the info in the Pin Mux Grid directly to a spreadsheet?

Thanks -

Sal

  • 0
    TI__Expert 6735 points

    Sal:

    I attached a file that you can import into Pin Mux Utility:

    1) Rename from *.dat.txt to *.dat

    2) Place in ... My Documents\Pin Mux Utility\Design1\AM387x-DM814x\ folder

    3) In tool do File -> Open -> Design

    All of the signals you need arre in the EMAC[0] Interface View.    The issue is that some balls using the same mux mode have two signals

    that can be defined by programming registers in the EMAC module in addition to PINCTRL registers.

    For example, in EMAC[0] view J25 is named "EMAC[0]_MRXD[3] / EMAC[1]_RGRXCTL".  The ball in this mux mode can be used as EMAC[0] (G)MII

    or EMAC[1] RGMII.

    4) There is currently not a way to save as a spreadsheet.   It does save C header files.

    Regards,

    Michael T