• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 31 subscribers
  • Views 601 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.

HaCoGen Conflict on MII pin mux

David Wyskiel
Prodigy 155 points

Other Parts Discussed in Thread: HALCOGEN

Hi,

We are targetting the RM46L852PGE device and are trying to configure the EMAC.  With just the MII enabled, there are two pinmux conflicts: MII_RXCLK / MII_RX_AVCLK4 and MII_TX_CLK / MII_TX_AVCLK4.  I can manually disable the second "AV" clocks, clearing the conflict, but need to make sure that this is the right thing to do and that code will be properly generated.  Is it?  If not, what needs to be done?

Also - any pointers to the best way to integrate a TCP/IP stack and a USB stack on this processor would be greatly appreciated.  I did find the link for Micrium and am looking for more information on this topic.

Thanks,

David.

  • 0
    TI__Mastermind 30845 points

    David,

    Let me check on this and get back to you.

    Regards,

    Abhishek

  • 0
    TI__Mastermind 49120 points

    Hi David,

    You don't have to configure the multiplexer on the MII_RXCLK / MII_RX_AVCLk4 or the MII_TXCLK / MII_TX_AVCLK4 terminals. That is, leave these multiplexer controls in their default states. We tried to allow customers to save the additional external clock source for the 25MHz or 50MHz required by the EMAC PHY. However, these TXCLK and RXCLK connections are always required to be inputs driven from the PHY, making the *_AVCLK4 outputs not useful.

    We do also have examples of lwIP stack and a USB host stack on the RM48x wiki. You can refer to these as well as the examples on Micrium's web page.

    Regards, Sunil

  • 0 in reply to Sunil Oak
    TI__Mastermind 49120 points

    David,

    The terminals for MII_RXCLK and MII_TXCLK carry other functions as defaults. So you do need to configure the multiplexer and select the MII_RXCLK and MII_TXCLK functions for the given terminals using the HALCoGen utility. You can deselect the MII_*_AVCLK4 functions if they are shown as already enabled.

    Regards, Sunil

  • 0 in reply to Sunil Oak
    Prodigy 155 points

    Thank you for this detailed, complete answer, and for getting back to us so quickly!

    David.