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.

AWR1642BOOST: How to set the <numAdcSamples> to 256 without "DSS Frame Processing Deadline Miss Exception"?

Part Number: AWR1642BOOST
Other Parts Discussed in Thread: DCA1000EVM,

When capturing the raw data from AWR1642BOOST + DCA1000evm,

profileCfg 0 77.5 3 3 56 0 0 8 1 240 5000 0 0 48

The sensor processed very well.

profileCfg 0 77.5 3 3 56 0 0 8 1 256 5000 0 0 48

The message "DSS Frame Processing Deadline Miss Exception" appeared.

Already tried 241, 242, 244, 248, 254, 255 and 272.

The <numAdcSamples> can not set to the number near 256.

Can anyone help me solve this problem? I'm very appreciate for your help! Thank you!

Best regard,

Webb

  • Hi

    The error message indicates that there us not sufficient processing time.

    Please increase the frame time in frameCfg.

    Thank you

    Cesar

  • Hi! Cesar!

    Thank you for your comment!

    Already read mmwave_sdk_user_guide03.pdf provided from TI Team.

    Tried the following configs:

    frameCfg 0 1 16 0 100 1 0

    frameCfg 0 1 16 0 200 1 0

    frameCfg 0 1 16 0 500 1 0

    frameCfg 0 1 16 0 100 1 10

    "Configuration is valid only if the DFE Output Mode is Chirp" appeared with dfeDataOutputMode 3.

    Tried use dfeDataOutputMode 1 but in this mode cannot set the subFrameCfg.

    ----------------------------------------------------------

    When capturing the raw data from AWR1642BOOST + DCA1000evm,

    the "DSS Frame Processing Deadline Miss Exception" comes out with the following configs:

    dfeDataOutputMode 3

    profileCfg 0 77.5 3   3   56  0   0   8      1   256 5000    0   0   48
    profileCfg 1 77.5 3   3   56  0   0   8      1   256 5000    0   0   48

    Is there any suggestion?

    I’m very appreciate for your help! Thank you!

    Best regard,

    Webb

     

  • Hi,

    I would try first the configuration you would like to use with the mmWave SDK demo.

    Not all chirp configurations will work with the demo since there are limitations due to design choices.

    So, if the configuration you would like to use does not work with the demo, this means that you will not be able to use the SDK demo to capture raw data.

    You would have to use mmWave Studio instead.

    thank you

    Cesar

  • Hi! Cesar!

    Thank you for your comment!

    Will try the configuration with mmWave_Demo_Visualizer first.

    And then try mmWave SDK demo and mmWave Studio.

    Hope the processes can work well!

    Best regard,

    Webb