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.

AWR2544LOPEVM: Enabling Automotive Ethernet (non master) in mmw_cli demo software

Part Number: AWR2544LOPEVM
Other Parts Discussed in Thread: AWR2544, SYSCONFIG

Tool/software:

Hello,

Goal: Enable Slave mode on AWR2544EVMLOP with Automotive Ethernet PHY.

 

We've successfully modified our AWR2544EVMLOP physically to enable Automotive Ethernet PHY using TI instructions.

I've built the C:\ti\mmwave_mcuplus_sdk_04_06_01_02\mmwave_mcuplus_sdk_04_06_01_02\ti\demo\awr2544\mmw\ demo software using gmake as per the SDK with MakeFiles instructions. This works with the Industrial PHY as expected. 

I've then successfully modified the sysConfig component of Industrial PHY for project MMW_CLI to use the Automotive Ethernet component instead and rebuilt. This was then flashed successfully to the board for QSPI boot mode. This boots fine as shown below when my automotive ethernet adapter is set to slave mode, connecting to the default master mode on the awr2544evm.

I then changed the sysconfig component of the MDIO to disable "Set as Master" to try and get the AWR2544EVM to act as slave.

However, the application no longer continues to the cpsw_handleLinkUp stage after printing the Host MAC address as seen below:

I've verified my test setup by loading back on the master version just to be sure, and it indeed still works, but slave mode on awr2544 does not. I tried setting the Disable state machine on open (and separately manual MDIO mode) as a guess, but this yielded the same above result.

Are there other modifications I need to make to the mmw cli demo source or sysconfig to enable slave mode on the awr2544?

Thank you for your time,

-Ross B

  • Hi Ross,

    Can you clarify the following things - 

    1. which example project you are working on here?

    2. can you put a breakpoint in the code and see where exactly you are getting stuck?

    3. Have you configured your adapter in slave mode after changing the device configuration as slave? If you are using two connecting devices, one must be set to master and the other to slave mode. Both cannot be in master or slave mode.

    4. Instead of this project, can you take any standard example from our SDK which works in the default scenario (device - as a master and converter/adapter - as a slave) and then try to reproduce your issue there. That will be a good starting point for us for further debugging.

    Regards,

    Shruti

  • Hi Shruti,

    In response:

    1. This is the Millimeter Wave (mmw) Demo for AWR2544 located at this installation path for the awr2544:

    C:\ti\mmwave_mcuplus_sdk_04_06_01_02\mmwave_mcuplus_sdk_04_06_01_02\ti\demo\awr2544\mmw\

    It's the demo used in the out of box + visualizer for the awr2544, capable of processing commands from the command line over Serial. This was built successfully using MakeFiles, and flashed.

    2. I'm fairly confident that the Cpsw_waitForLinkUp() is the current blocking call, waiting for negotiation to take place on the automotive ethernet PHY. This can be seen in the above print out of CpSw_handleLinkUp occurring on the working setup (awr2544 master, host adapter slave), but not in the second broken case (awr2544 slave, host adapter master). I will verify with a breakpoint and report back.

    3.  The AWR2544EVM works fine as master connected to a slave host adapter. The problem is it seems to be still in master mode even after changing the sysConfig component "set as Master." I'm wondering if there's additional steps with this mmw demo software or the board itself to enable slave mode.

    4. Ok I will try another ethernet demo, then try to change the same sysConfig component, and report back with results.

    Thank you,

    -Ross