• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 33 subscribers
  • Views 179 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.

MSP432E401Y: Force Link Enable

Mike_d
Intellectual 1000 points
Part Number: MSP432E401Y

Hi,

Using one of the TIRTOS network service examples, is there a way to force the Ethernet active without a physical link?

Also, can it be forced to 10 Mbps or 100 Mbps?

Regards,

-Mike

  • 0
    TI__Guru 56685 points

    Hello Mike,

    Sorry for the late response here. We still have unstable power conditions in Texas which have caused delays in responses. We are starting to warm back up as we head through the weekend. This should lead to more stable power next week. Please allow us until next week to look into your question and give you a response. 

  • 0
    TI__Genius 12650 points

    Posting the response that was provided offline. The below responses reference files in the MSP432E SDK (simplelink_msp432e4_sdk_4_20_00_12).

    • The PHY is configured in the function EMACPHYConfigSet:

    • This function is called from EMACMSP432E4_emacStart in EMACMSP432E4.c

    • These are some of the options for config parameter:

    • By default, the TI Drivers are using EMAC_PHY_CONFIG (shown above) which is defined as 100M with auto-negotiation in EMACMSP432E4.c as:

    • While that is not a parameter that can be reconfigured using TI Drivers, the function is called from a library.

    • As such, we can simply override the file by adding EMACMSP432E4.c (from ~SDK\source\ti\drivers\emac) to the project and modify it manually:

    • After adding that source file to the project it is necessary to pre-define __MSP432E401Y__ to build the file. You can add this in the project build options like this:

    • Building the project and examining the map file shows that the linker now calls the function directly from the .c file, not the library: