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.

AWR1843BOOST: Vehicle Occupancy Mailbox calling periodicity

Part Number: AWR1843BOOST

Hello,

we have the following configuration

profileCfg 0 77 250 10 40 0 0 98 1 64 2200 0 0 40
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 2
frameCfg 0 1 168 0 107 1 0

So:
T1=total_frame_time=((168*2*(40u+250))/1000)ms
T2=time_period_between_frames=107ms


How to calculate the periodicity of calling mailbox read is it T1 ot T2 or T1-T2 ?


  • Hi Saber,

    Let me assume that mailbox periodicity you refering based on MSS core, where at every frame DSS notifies MSS about object result availability.

    Periodicity of mailbox read at MSS is T1+T3; where T3: DSP inter-frame processing time.

    In SDK 3.2 dss_main.c: T3 = outputMsgStats->interFrameProcessingTime;

    Regards,

    Jitendra

  • Hello Jitendra,

    Thanks for your reply.

    Could you please help me how to change T3 value? i'm using SDK 3.1

    Another point in this case what's the effect of changing T2 time or what's the usage?

    Thanks in advance

  • Hi Saber,

    T3 is mainly depends on the processing time taken DSP. This can vary if there are higher sample size or more no. of chirp in a frame and many other factor.

    You need to visit to the source code to trace back the affecting factor to this timing.

    T2 (idle frame time) required to do the inter-frame processing which includes T3 in it and next step to send object data over UART to PC.

    If you reduce T2 time then DSS may hit an assert if this time is not sufficient to do the inter_frame_processing (t3) and UART_send_timing.

    Regards,

    Jitendra