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

AWR2243: Cascade example design: cannot connect to TDA

Glen DesBouillons II
Intellectual 520 points
Part Number: AWR2243

Hello, 

I am working with the awr2243 cascade evaluation board and the TDAxx dsp board. when running the software provided in the dfp mmwave_dfp_02_01_05_03, the provided software does not connect to the tda board via ethernet. when debugging the TDA_StartTraceACK is rarely changes from 0 to 1, thus the ethernetConnect function fails and the program rarely runs sucessfully. maybe 1 out of 10 runs.

The baord is connected to the correct power supply and i have tried power cycling the board many times. this is an issue across multiple computers. The Static ip is set and all setup steps have been followed correctly in the mmw user guide. 

Thank you in advance

  • 0
    TI__Mastermind 31680 points

    Hello Glen,

    Is your cascade board with AWR2243 ES1.1 silicon? or ES1.0 silicon revision?

    First of all, do you see the correct number of COM ports in the device manager when you switch on the cascade board? Do you see the lights glowing up?

    Regards,

    Ishita

  • 0 in reply to Ishita Kochar
    Intellectual 520 points

    Ishita, 

    I have the ES1.0 board. 

    When connected i can see the correct com ports in the device manager. Which lights are you referring to? I can see the lights on the ethernet connector as well as the nrst lights and power lights. 

    Thank you

  • 0 in reply to Glen DesBouillons II
    TI__Mastermind 31680 points

    Hello Glen,

    Thankyou for your response. Yes, I meant the same LEDs.

    Are you able to see the tera term log running as soon as you connect the board to you PC?

    And just to clarify, are you trying to connect your board with mmWave studio and is this what are you haven't been able to achieve?

    If that is the case, we do have a FAQ page which tries to address this concern. You might want to take a look at it :

     

    Let me know if I got it wrong.

    Regards,

    Ishita

  • 0 in reply to Ishita Kochar
    Intellectual 520 points

    Ishita,

    Yes i am able to see tera term on start up. No i am using the mmwavestudio gui, i am using the example software and running it in visual studios. C:\ti\mmwave_dfp_02_01_05_03\ti\example\mmWaveLink_Cascade_Example

  • 0 in reply to Glen DesBouillons II
    TI__Mastermind 31680 points

    Hello Glen

    I think you mean to say that you're not using mmWave Studio GUI.

    When you're running the mmWave link example, where exactly is it getting stuck? Can you maybe demonstrate your problem with the help of some screenshots for us to understand it better. I suppose you're not able to connect to the TDA board. 

    Usually in these type of situations, we suggest a trial run with mmWave studio first. This eliminates some basic TDA connection related concerns and helps us narrow down some possible causes.

    Regards,

    Ishita

  • 0 in reply to Ishita Kochar
    Intellectual 520 points

    Correct. I am NOT using the mmwave sutido gui. 

    In the example software's eternet lib, there is a function called ethernetConnect. Inside of that function there is a while loop waiting for TDA_StartTraceACK to be signalled from 0 to 1. a thread is created to run the function Network_waitConnect, in that function is where the variable is set but rarely happens. I have tested with mmwave studio gui and been able to connect to ethernet without problems, but when running the software it does not connect.

  • 0 in reply to Glen DesBouillons II
    TI__Mastermind 31680 points

    Hello Glen,

    Can you try to ping TDA2XX IP address from PC to verify if the network connection is proper?

    Also, at the terminal screen, check if apps.out process is running. You can refer to Section 13 (mmWave studio cascade user guide) for instructions on how to check this.

    Again, I feel it would be better if you could try connecting with mmWave studio first.

    Regards,

    Ishita