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.

Advanced Frame Configuration RunTime Error

Other Parts Discussed in Thread: MMWAVEICBOOST, AWR1843AOP

Hello,

I'm using advanced frame configuration in hardcoded configuration and running in ccs debug mode but I'm getting runtime error in dpm report function task. I've verified the parameters in sensing estimator but still the advance frame configuration is not running in debug mode.

Pleas provide some assistance in this regard.

Thankyou

Ayush

  • Hi,

    Please let us know

    1) What HW platform you are using? Is this a TI Board?

    2) What TI SW release are you using?

    3) What is the error you are seeing?

    Thank you
    Cesar

  • Hi,

    1. I'm using AWR1843AOP sensor board and MMWAVEICBOOST EVM.

    2. I'm using SDK 03_06_00, radar_toolbox 1_20_00_11

    3. I have attached the screenshot below for the error I'm getting. ERROR Number -40112. 

    -Ayush

  • Hi,

    I think there are some issues with the SW updates that were performed

    I recommend reviewing the updates.

    Thank you
    Cesar

  • It is difficult from the error log to identify the exact issue.

    I would configure the number of frames = 1 and step through the mss code to identify where the error occurs

    thank you

    Cesar

  • Hi Cesar,

    I changed the parameters to check for the error and I discovered that by changing the chirp loop parameter in frameCfg, the error didn't occur. The chirp loop I had set earlier which was giving me error was 64 and when I changed the chirp loop parameter to 32 then it started working. 

    I would like to set the chirp loop to 64 for better SNR, could you suggest any changes that I might have to do to be able to run the configuration with 64 chirp loops.

    Thank You,

    Ayush

  • It seems that the issue is that there is not sufficient time to process the higher number of chirps.

    There are several things you can try with the configuration file

    • try lower values for the chirp loop and identify the highest value that works
    • increase the frame duration (in frameCfg)
    • decrease the number of ADC samples (this will have an impact on the max Range)

    Beyond this, further optimizations will be more difficult to perform.

    First one would need to benchmark the code to understand how long time is required

    • for processing
    • for transferring results through the UART to PC

    The demo already provides some benchmarking data. So, you could use that information to start with.

    Thank you

    Cesar