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.

RTOS/AWR1642BOOST: Double check TDM configuration

Part Number: AWR1642BOOST
Other Parts Discussed in Thread: MMWAVE-SDK

Tool/software: TI-RTOS

Hello, I am trying to create a simple TDM configuration file. Here are the key lines that I would like to double check:

profileCfg 0 77 20 5 80 0 0 40 1 256 6000 0 0 30
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 2
frameCfg 0 1 64 1 20 1 0

Just so everyone is clear, I want 1 frame to transmit. The frame will have 128 total chirps. 64 chirps from TX1 and 64 chirps from TX2 in a TDM format. The chirps from both TX1 and TX2 will be the same as far as their start frequency, bandwidth, etc. Is this the correct way of implementing such a frame?

  • Hello,

    Based on quick check the set of config parameters achieve what you are intending. I am going to attempt aread through of chirp values,  please see the color coding in params and the explanation to identify the parameter mapping

    profileCfg 0 77 20 5 80 0 0 40 1 256 6000 0 0 30   -->( Chirp Profile # is defined here)
    chirpCfg 0 0 0 0 0 0 0 1   --> (Chrip #to # is defined here and it uses Profile #0 )
    chirpCfg 1 1 0 0 0 0 0 2   --> (Chrip #to # is defined here and it uses Profile #0 )
    frameCfg 0 1 64 1 20 1 0   --> (this Frame uses sequence of chirp  #0 to # and repeats it 64 times  and this frame repeats 1 time )

    Hope this helps with confirming the param values vs intended chirp.

    Explanation of these parameters is included in mmwave SDK user's guide  in  "Configuration (.cfg) File Format" section.

    SDK user's guide can be found in Doc's directory of mmWave SDK isntallation

    Ref:

    User Guide User Guide for MMWAVE-SDK

    Detailed explanation of each of these parameters is included under the mmWave SDK installation's mmWave Link layer module.

    All modules inside the SDK structure have Doc's directory where the details are covered. For example:

    Typical paths:

    Link layer description : file:///C:/ti/mmwave_sdk_01_01_00_02/packages/ti/control/mmwavelink/docs/doxygen/html/index.html

    |-->  Modules    (file:///C:/ti/mmwave_sdk_01_01_00_02/packages/ti/control/mmwavelink/docs/doxygen/html/index.html)

         |--> Sensor   (file:///C:/ti/mmwave_sdk_01_01_00_02/packages/ti/control/mmwavelink/docs/doxygen/html/group___sensor.html)

    |--> <click on required config function >  (e.g. rlSetFrameConfig    :  file:///C:/ti/mmwave_sdk_01_01_00_02/packages/ti/control/mmwavelink/docs/doxygen/html/structrl_frame_cfg__t.html)

    Please let us know if you have more questions.

    Thank you,

    Vaibhav