• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 860 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.

IWR1843BOOST: IWR1843BOOST Chirp Configuration

Amr Khaled
Prodigy 116 points
Part Number: IWR1843BOOST
Other Parts Discussed in Thread: IWR1843, AWR1843BOOST

I have several related questions to the IWR1843 board chirp configuration:

1- Firstly, in the latest mmWave Sensing Estimator ver 2.2.1 I can't modify the # of Tx antennas as I need to reduce it to 1 instead of 3 to avoid other parameters conflicts "they were configurable in ver 1.3.0"?

2- Secondly, Can we use the Sensing Estimator with the MRR lab or is the generated cfg file uploadable only with the out of the box demo?

3- If it is not possible to upload the Sensing Estimator cfg file directly to the device, how can I utilize this cfg file values in generating an updated image with the required configurations? 

Lastly is this more of a general question:

4- Does the generated cfg overwrite the parameters values from the flashed image or does it need to be re-sent after every power cycle?

Thanks in advance.

  • 0
    TI__Expert 4448 points

    Hello Amr,

    1. Are you using the Advanced Chirp Design and Tuning tab or the Basic Chirp Creation and Design tab? You do not have control over the number of antennas on the Basic side. This is because we keep this side of the tool as simple as possible. You can configure the number of antennas in the Advanced side. To use the Advanced side, either choose values you like in the Basic side, then click SEND TO ADVANCED CHIRP DESIGN, which will move your values from the Basic to the Advanced side - or - start from the Advanced side, copy and paste an existing configuration file into the Configuration I/O box (or click LOAD CONFIG and just select your .cfg file), then hit AUTO-POPULATE, which will parse the file and populate the cells for you.

    2. The config generated from the Basic side is intended for out of the box. Utilize the Advanced side, import the MRR lab config like was mentioned above, and tune your config, then click SAVE CONFIG to get your modified config file back for use in the MRR lab.

    3. You can utilize the SAVE CONFIG button on either the Basic or Advanced Tab. In the case of the Advanced Tab, the output file will ONLY be fully complete if you start from a full file (the case of LOAD CONFIG from a full file or AUTO-POPULATE with a full file's contents pasted into the Configuration I/O box), otherwise it will be a subset of configuration commands (the commands you see in the CLI Commands output box) that get written to the output file. Once, you've gotten your modified and complete CFG file, send that to the device in our typical workflow (described in the lab guide and touched on below).

    4. Configuration files must be sent to the device every-time after a power cycle. This is true whether or not you utilize the Sensing Estimator. You could avoid this by employing a hard-coded configuration, but this would not be optimal if you are testing CFGs and modifying them frequently.

    Regards,
    Luke

  • 0 in reply to Luke Rouleau
    Prodigy 116 points

    Hello Luke,

    Thanks for your support. It helped a lot but I need further clarification in some points.

    - I can't find a config file related to the MRR lab. I searched in the radar_toolbox_1_00_01_07 and mmwave_sdk_03_06_00_00-LTS folders. Can you help guide me where I can find it? or doesn't the MRR lab support the use of config files?

    - How to send the config file to the device? as the MRR GUI visualizer doesn't include this option. Can I use the mmWave Demo Visualizer or is it restricted to OOB demo apps only? also is there another way to do so?

    - Considering I found my optimal config file and want to make this configuration permanent. how to employ the hard-coded configuration mentioned above and which config files and parameters I need to change to reflect the updated parameters?

    Best Regards,

    Amr Khaled

  • 0 in reply to Amr Khaled
    TI__Expert 4448 points

    Hi Amr,

    After looking around myself, I also cannot find the configuration file for the MRR lab, it must be embedded in the GUI. However, I am not on the ADAS team, so I will get the thread looked at by our experts over there and get an answer to your first two points.

    But regarding hard-coded configurations, checkout the Hard-Coded Config Guide, which lives in the Radar Toolbox under [radar_toolbox_root_dir]\source\ti\examples\Fundamentals\Hard_Coded_Config

    Regards,
    Luke

  • 0 in reply to Amr Khaled
    TI__Guru*** 149154 points
    Amr Khaled said:
    - I can't find a config file related to the MRR lab. I searched in the radar_toolbox_1_00_01_07 and mmwave_sdk_03_06_00_00-LTS folders. Can you help guide me where I can find it? or doesn't the MRR lab support the use of config files?

    Hi,

    For the MRR lab, the configuration is hard-coded in the code. It is not possible to use config files with MRR lab.

    The MRR lab was optimized for longer range performance and it is not possible to modify the configuration

    thank you

    Cesar

  • 0 in reply to Cesar
    Prodigy 116 points

    Hi all,

    Okay, thanks for your support.

    I need to change some configuration parameters from the MRR lab to better suit my requirements. I am currently using the latest mmWave Sensing Estimator tool to generate the needed config file but I need to reflect the changed parameters in the code.

    Can I change the defined values in the common files to achieve this? how to know which parameters exactly to change in the code?

    Best Regards,

    Amr Khaled

  • 0 in reply to Amr Khaled
    TI__Guru*** 149154 points

    Hi,

    Changing some parameters may break the code.

    Which parameters do you need to change?

    Using the Sensing Estimator is useful as a first step. However we recommend doing a manual analysis/review after that.

    Thank you

    Cesar

  • 0 in reply to Cesar
    Prodigy 116 points

    I need to change chirp configuration parameters in order to extend maximum range / decrease range resolution / increase velocity in correspondence to the values from the sensing estimator

  • 0 in reply to Amr Khaled
    TI__Guru*** 149154 points

    Are you using the AWR1843BOOST board?

    Based on our experiments the max range is achieved with configuration provided. You will not be able to extend the range  by modifying the chirp configuration.This is a iimitation of EVM, Tx Power and Memory

    Thank you

    Cesar

  • 0 in reply to Cesar
    Prodigy 116 points

    Yes I am using IWR1843BOOST board, at least I need to increase the maximum velocity that can be detected and compromise with the range resolution.

  • +1 in reply to Amr Khaled
    TI__Guru*** 149154 points

    The configuration can be modified in

    lab0007_medium_range_radar\src\common\mrr_config_chirp_design_MRR120.h

    Thank you

    Cesar