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.

AWR6843ISK: Inquiry on Updating Device Configuration for Iterative Frequency Scanning

Part Number: AWR6843ISK


Tool/software:

Dear E2E Team,

I have already set up the device with a hardcoded configuration. Now, I would like to update it to perform environment scanning with a different starting frequency in each iteration.

For example, given a list of desired start frequencies:

float sFreq[10] = {60, 60.2, 60.4, 60.6, ... 62 }

I would like the device to automatically scan sizeof(sFreq) times after initialization and send out the results after each iteration.

Could you please advise on how to implement this functionality?

Thank you in advance for your assistance.

Best regards,

Ramin

  • HI, Ramin:

    You can use per-chirp variation API 

    file:///C:/ti/mmwave_sdk_03_06_02_00-LTS/packages/ti/control/mmwavelink/docs/doxygen/html/structrl_chirp_cfg__t.html

    You can program different RF start frequency variation so that you have different start frequency for different chirps in a frame.  For example, you can have the first M chirps with 60, and next M chirps as 60.2, and etc.  

    Best,

    Zigang

  • However, it will be the same pattern for all the frames.  

    If you want to change the pattern between frames, then you will have to stop the RF front-end, and then reconfigure the RF start frequency through profileCfg, and restart the sensor RF frontend again.

    Best,

    Zigang

  • Hello,

    Thank you for your help and response. As you mentioned, I would like to change the pattern in each frame. For reconfiguring with the desired start frequencies, I have already implemented a Python script using external configuration.

    However, in the hardcoded configuration, placing all contents of the main function within a for loop inside main-mss.c not works because it never returns to the calling function after BIOS_start().

    Could you please advise on the correct placement of the for loop and which parameters or lines need modification in the code?

    I appreciate your time and assistance.

    Best regards,

    Ramin

  • Hi, Ramin:

    if you want to change the configuration for the next frame, you can add the frame Reconfig function inside Dpc_Execute, in the while loop, after DPU_RangeProcHWA_process function.   Basically, you can re-config the chirps after active chirping of the current frame, and the change should be done before the next frame starts. 

    The change itself can be done through calling rl_sensChirpProfTimeCfg function. 

    Best,

    Zigang

  • Hello zigang Yang, 

    Thank you for your assistance. Unfortunately, our EVM board broke down a few days ago, so I am unable to run the updated code. I will get back to you after resolving the hardware issue.