• State
  • Locked Locked
  • Replies 10 replies
  • Subscribers 30 subscribers
  • Views 449 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.

AWR2544LOPEVM: AWR2544LOPEVM: The 1000Base-T1 AUTO PHY(DP83TG720) on the EVB to 100Base-T1 AUTO PHY(DP83TC812)

Kevin Huang2
Prodigy 160 points
Part Number: AWR2544LOPEVM
Other Parts Discussed in Thread: AWR2544, SYSCONFIG, , DP83TG720EVM-MC

Tool/software:

Hi,

I need help to enable DP83TC812 for AWR2544.

Currently I got a new task for the AWR2544, switch the auto phy from 1000Base-T1 DP83TG720 on the EVM to 100Base-T1 DP83TC812.

Previously I had configured the EVM to let the 1000Base-T1 DP83TG720 working with 2544 mmwDemo.

Here I list the modifications I have done to enable the 1000Base-T1 DP83TG720:

1, hardware:

In stall R11 with 0 Ohm resistor.

Move R98, R101, R103, R105, R121, R122, R195, R290, R325, R336, R338, R339, R369, R413

     to R240, R239, R238, R237, R245, R234, R74, R230, R225, R178, R100, R96, R247, R249.

2, software:

run gmake msssyscfg-gui to use the sysconfig gui app to select the "Auto Phy (dp83tg720)", as the <mmwave_mcuplus_sdk_user_guide.pdf>

gmake all, download and run the appimage.

3, connection:

AWR2544LOPEVM -> DP83TG720EVM-MC -> PC. DP83TG720EVM-MC at slave mode.

Result: On PC, I can receive the UDP data, same as the DP83867 (Industrial PHY).

Now what I did try to enable the 100Base-T1 DP83TC812.

All others are exactly unchanged based on above, except:

1, hardware:

    Replace DP83TG720 by DP83TC812.

    Change R11 from 0 Ohm to 10K Ohms.

3, connection:

AWR2544LOPEVM -> 100Base-T1 converter* -> PC.

100Base-T1 converter* Technica engineering 100Base-T1 Media Converter_BCM, at slave mode, FullOut.

However, the modifications do not work.

If I set the 100Base-T1 converter at Master mode:


However it will crush if I run a simple configure as:

The console is dead at here; and wireshark on the PC side shows no data received, same if I configure "frameCfg 0 0 128 10 512 100 1 "

It shouldn't be the data rate too high (128 samples, 1 chirp, 10Hz, cant' work).

By default, the Auto phy should work at Master mode, but based on above screenshot, looks the 100Base-T1 Auto Phy is runing at Slave mode?

-----------------------
I believe on the software side, I need to do some modifications to fit the new Auto Phy, but have no idea which document to reference to.

Could anyone help me out? Thanks a lot!

Regards,

Kaiyu Huang

  • 0
    TI__Genius 11200 points

    Hi Huang,

    Can you try with any default configuration first, In the screenshot you have shared, I could see that in the frame cfg, your chirp start index and chirp end index both are 0, it should be 0 to 3.

    Regards,

    Shruti

  • 0
    TI__Genius 11200 points

    Hi Huang,

    Can you try with any default configuration first, In the screenshot you have shared, I could see that in the frame cfg, your chirp start index and chirp end index both are 0, it should be 0 to 3.

    Regards,

    Shruti

  • 0 in reply to shruti gupta
    Prodigy 160 points

    Hi Shruti,

    Thanks for the suggestion. Here I updated the configure, and the console is alive after the sensorStart. (the 3rd parameter of the frameCfg, number of loops should no less than 4; the 3rd parameter of the procChainCfg should no larger than the chirps)

    But the Wireshark on PC still hasn't show anything. 

    ( I have tested this configure on the 1000Base-T1 2544EVM board, and everything works fine.  The data rate is 4 chirps x 256 samples x 10Hz)

    What I'm worrying about:

    For 1000Base-T1, the EVM is working at master mode, can not work at slave mode.

    Now the 100Base-T1 phy is alive at slave mode without any software change, looks abnormal to me.

    Regards,

    Kaiyu Huang

  • 0 in reply to shruti gupta
    Prodigy 160 points

    Hi Shruti,

    I did another change on the AWR2544LOPEVM: Install R258 to pull up LED_0, which can configure the 100BASE-T1 to master mode through hardware bootstrap.
    However I got the following output on the console (the 100Base-T1 converter on slave mode, which means the DP83TC812 is on master mode):


    Looks like the link keeps up and down. Any suggestions?

    Regards,

    Kaiyu Huang

  • 0 in reply to Kevin Huang2
    TI__Genius 11200 points

    Hi Kevin,

    Kevin Huang2 said:
    Thanks for the suggestion. Here I updated the configure, and the console is alive after the sensorStart. (the 3rd parameter of the frameCfg, number of loops should no less than 4; the 3rd parameter of the procChainCfg should no larger than the chirp

    The frame cfg is still not correct, I would suggest you to send a default cfg present in the SDK first or go over the SDK user guide to see the format of frame cfg. the chirp start and chirp end index both cannot be zero in the frame cfg. 

    Please correct the same and test it.

    Regards,

    Shruti

  • 0 in reply to shruti gupta
    Prodigy 160 points

    Hello Shruti,

    For your suggestion, I just "correct the same and test it"(frameCfg 0 3 4 20 256 100 1 0). Unfortunately, nothing changes --- no data on wireshark.

    As I mentioned above, that configure can work with the 1000Base-T1 2544EVM board --- obviously this configure is not the root of the problem. I tried other configures coming with the SDK at the very beginning, they were not work for the 100Base-T1; then I suspected about the data rate or bandwidth, that's why I reduce the chirp number, and same as the small sampling number. 

    I appreciate your help. Any other suggestions?

    Regards,

    Kaiyu Huang

  • 0
    Prodigy 160 points

    Hi Ti experts,

    I believe the driver of the DP83TC812 is different to the DP83TG720. To enable the DP83TC812 with SDK mmwave_mcuplus_sdk_04_07_00_01(or mmwave_mcuplus_sdk_04_06_00_01) on the AWR2544LOPEVM, what kinds of software and hardware modifications do I need to do? More directly, how to run the 2544 mmw Demo with the DP83TC812 on the EVM?

    Any suggestions are appreciated.

    Regards,

    Kaiyu Huang

  • 0 in reply to Kevin Huang2
    TI__Genius 11200 points

    Hi Kevin,

    Apologies for the delay. You can check the 2944 SDK (C:\ti\mmwave_mcuplus_sdk_04_07_00_01\mcu_plus_sdk_awr294x_10_00_00_07), it has the driver for dp83tc812 PHY. You can take this as reference for your application.

    For hardware modifications, you can check and the schematic of 2944 and 2544 and compare the hardware.

    Regards,

    Shruti

  • 0 in reply to shruti gupta
    Prodigy 160 points

    Hi Shruti,

    Appreciate for the replies. I will take 2944 as reference.

    Regards,

    Kaiyu Huang

  • 0 in reply to Kevin Huang2
    TI__Genius 11200 points

    Hi Kevin,

    Sure, let me know if that works for you.

    Regards,

    Shruti