• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 97 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: Need help with the configuration file settings to download to the EVM

Dave Peters
Prodigy 30 points
Part Number: AWR2544LOPEVM
Other Parts Discussed in Thread: AWR2544

Tool/software:

I am trying to change settings in a configuration file to download to the 2544 EVM.  I have a configuration file that was sent by TI that loads correctly and I can get the raw data in a '.bin' file.  However when I change the profile config and/or the channelcfg I cannot get the the raw data.

I've been searching through the documentation for clear details of the argument settings but I have had no luck.  The best source I've used is a MatLab example that parses the data.  I was able to read my config file into that and it will produce the correct radarParam(the structure in MatLab).

I'm attaching the original Ti file and my modified file.  Initially I am just trying to change the Tx/Rx antennas, the bandwidth, start frequency.  I'm using the default parameters in mmWaveStudio as a reference.  I will attach screenshots of those as well.

Thank you,

Daveprofile_3d_3Azim_1ElevTx_DDM_LVDS_awr2544_1Xmode.cfg

drp_3d_3Azim_1ElevTx_DDM_LVDS_awr2544_1Xmode.cfg

  • 0
    TI__Expert 3490 points

    Hello,

    Several questions,

    "I am trying to change settings in a configuration file to download to the 2544 EVM.  I have a configuration file that was sent by TI that loads correctly and I can get the raw data in a '.bin' file.  However when I change the profile config and/or the channelcfg I cannot get the the raw data."

    For this question is this being done in studio?

    If you want details on each argument and their parameter I would refer to the SDK user guide at this path. 

    file:///C:/ti/mmwave_mcuplus_sdk_04_07_01_03/mmwave_mcuplus_sdk_04_07_01_03/docs/mmwave_mcuplus_sdk_user_guide.pdf

    Here is an example screenshot showing parameter info

    I am also a little unclear on your desired use case. Do you want to capture this data with studio? or with the board in functional mode and the usage of the DCA CLI commands?

    These clarifications will be useful for future debug.

    Best,

    Gabriel

  • 0 in reply to Gabriel Gigliotti
    Prodigy 30 points

    Thank you for the response.

    I am using CLI commands and a Comport to connect to the unit.  

    I'll look for that document.  I'll try to compare what I set in mmWave Studio to what I put in the file.

    My use case is to capture the data with the DCA CLI commands.  For now I'm trying to change the bandwidth, the start frequency and the number transmitters and receivers.  My test setup is just a simple mount in an anechoic chamber with a 1m square piece of steel at 3m distance.

    My goal would be to have that automated to make multiple measurements.

    Thanks,

    Dave

  • 0 in reply to Dave Peters
    TI__Expert 3490 points

    Hello,

    If I understand correctly you were able to collect adc data with the original config, but once you changed certain config parameters ( Tx/Rx antennas, the bandwidth, start frequency) you were no longer able to collect data.

    This is not a data collection issue, this an issue with the board. Most likely these changes are causing an error or assert in the SDK OOB code as in it is not an accepted configuration.

    So, if you require these config changes I recommended doing everything via studio to verify that these changes will work. When working with studio the board is in development mode so nothing flashed will affect the config. You are essentially providing all the firmware and the configuration. IF you're not familiar with the process of connecting to the board, loading the firmware, configuring the board, and capturing data on studio then please refer to this document in studio. Start at section 6 and it will spell out the steps to do.

    mmwave_studio_user_guide.pdf

    If the config is not accepted with the OOB SDK project then there is nothing you can do. There are programmed safeguards in the OOB demo to ensure functionality with only certain confiigs and I do foresee changing the starting frequency, etc. will be an issue. Please try this with studio first.

    Best,

    Gabriel