AWR2243: Cascade example design: cannot connect to TDA

Glen DesBouillons II

Part Number: AWR2243

Hello i am working with the AWR2243 Cascade EVM. I am trying to use the mmwavelink_cascade_example project to control the radar chips from a serial console rather than the mmwave_studi GUI. When i run the .exe program file the board connects and runs through the script properly. However, when i compile the code and run the .exe that is created when building the code in visual studios i get an error that the board is unable to connect to the TDA device, make sure board is connected to network. Execution failed. I have not made any code changes, just built the project in visual studios and tried to run it.

I am working on porting this example and its supporting libraries to run on a linux machine and want to be able to check the expected outputs of functions to ensure my ported code is working properly.

The host machine has the proper static ip as mentioned in the cascade user guide, all is hooked up correctly and functions properly once i use the gui to confirm nothing is broken on the hardware side.

Thank you in advance.

over 5 years ago

0 Cesar over 5 years ago

TI__Guru*** 148804 points

Hi,

We have to check with mmwavelink team and get back to you

thank you

Cesar

0 Jitendra Gupta over 5 years ago

TI__Guru 69960 points

Hello Glen,

You may need to restart the board if it doesn't connect (after first connection with exe).

Regards,

Jitendra

0 Glen DesBouillons II over 5 years ago in reply to Jitendra Gupta

Intellectual 520 points

Jitendra

Do you mean run the .exe, then press the reset button on the board without closing the exe terminal? I have tried resetting the board with the .exe termial open and it returns the same error.

Thank you for the suggestion

0 robert hoff over 5 years ago in reply to Jitendra Gupta

Intellectual 390 points

Hi Jitendra,

We've tried restarting several times and we consistently get the results that Glen detailed above. Do you have any other ideas why we may be seeing this behavior?

Thanks,

Robert

0 Jitendra Gupta over 5 years ago

TI__Guru 69960 points

Hello Glen,

Which version of Visual Studio you are using, given example was written in Visual Studio 2017 version? I'm not sure if changing of the version is impacting this flow.

And what about another cascade example (mmWaveLink_Cascade_Monitoring). Does that also behave the same way?

Try to change build mode to 'Release' in Visual Studio.

Regards,

Jitendra

0 Glen DesBouillons II over 5 years ago in reply to Jitendra Gupta

Intellectual 520 points

Jitendra

I am using Visual studio 2019, but i downloaded 2017 and tried to run the exact same code without modifications and it still fails in the same way. I also tried different build modes release or debug in both versions of visual studio and it all fails with the same error code.

The .exe that come pre built with the dfp download still functions.

See the attached image for the error code. This behavior is consistent across all builds.

Any other suggestions is appreciated

Thanks

0 Jitendra Gupta over 5 years ago in reply to Glen DesBouillons II

TI__Guru 69960 points

Hello,

Looks like something wrong with the underline library for network connection.

We provide ethernetLib in the mmwave studio package, could you include that VS project to your example project and rebuild and try

<mmwave studio>\mmWaveStudio\ReferenceCode\EthernetLib\SourceCode\vs

This way we can find more lower layer cause of issue. Although it is strange as same application works at my end even with rebuild.

Regards,

Jitendra

0 Glen DesBouillons II over 5 years ago in reply to Jitendra Gupta

Intellectual 520 points

Jitendra

I have this library included and it is has been rebuilt. perhaps i have messed up a setting some where along the way. would it be possible to get a copy of the projects you are working with, with all of the proper settings and test them as they are known working and im having difficulties debugging this issue?

0 Glen DesBouillons II over 5 years ago in reply to Jitendra Gupta

Intellectual 520 points

hello,

I am still trying to debug the software. I have moved passed the ethernet connect, but now it is failing at the mmwlDevicePowerOn function in the mmwavelink lib. The device power on fails with -8 meaning there is a timeout error. what is the response that the software is waiting on and how can i find it to make this software function properly? any updates on why the built project does not function properly? The pre built .exe also fails in the same way every once in a while. Do you see this behavior too?

Thank you

0 Glen DesBouillons II over 5 years ago in reply to Glen DesBouillons II

Intellectual 520 points

This is the prebuilt executable and this is where it fails on the built code as well. I have tried power cycling the board using the reset button and any other previously suggested solution.

Thank you

0 Jitendra Gupta over 5 years ago in reply to Glen DesBouillons II

TI__Guru 69960 points

Hello,

Could you try building in 'release' mode in the visual studio and with Studio version 2017

I tried default DFP cascade example with VS 2017 in release mode and it worked as expected.

Attached is the original example file.

mmWaveLink_Cascade_Example.zip

0 Glen DesBouillons II over 5 years ago in reply to Jitendra Gupta

Intellectual 520 points

Jitendra

Hello i have done this build with visual studios 2017 in 'release' mode and have the same performance. The board connects to the ethernet then fails the device power on, returning error code (-8), corresponding to a timeout error. i have tried stepping through the code in the visual studios debugger and it times out during the power on device function, then the rest of the code is useless when the chips are not powered on or configured. I can use the mmwaveStudio gui to run the setup and triggering of the chirps to confirm that the hardware is not the issue. mmwaveStudio GUI works as expected without issues.

Thanks

0 Glen DesBouillons II over 5 years ago in reply to Glen DesBouillons II

Intellectual 520 points

This is the console output when running the .exe built in vs 2017 in release mode. how can i check to make sure that the device reset is happening if that is the issue or why the device power on is timing out?

Thank you for the help it is appreciated

0 Jitendra Gupta over 5 years ago in reply to Glen DesBouillons II

TI__Guru 69960 points

Closing this thread now as we are connected offline.

Sensors

Sensors forum

AWR2243: Cascade example design: cannot connect to TDA