• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 405 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

onetime runtime calibration timing constrains

Joseph Hanna
Intellectual 410 points
Other Parts Discussed in Thread: AWR2944

Hello,

kindly need to ask some questions regarding onetime runtime calibration please.


1- Are there any timing constrain that i should take in consideration when i'm triggering the runtime calibration before triggering the frame?
 (i tried to trigger the calibration before triggering the frame by 10 and 20 msec, it works fine, but if i tried by 30 msec it didn't work. it seems i should trigger the calibration before triggering the frame by short time)

2- if yes, how can i calculate this constrain? and if no, why it only works in case of 10 or 20 msec only, or just before frame triggering?

3- if i enabled reporting while triggering the runtime calibration, then i must receive the report in a synch event even if there is no thing to calibrate?
   (i just want to make sure not to trigger another calibration while the first is not finished)

4- if it will send me back the report even if there is no thing to calibrate, how can i differentiate between the report sent by my trigger and the one sent automatically due to the by default enabled runtime calibration?

5- are there any cases where i trigger a runtime calibration and i don't receive the report?



Thank you so much


 

  • 0
    TI__Mastermind 32665 points

    Hi Joseph,

    1) My understanding is that we are talking about API AWR_RUN_TIME_CALIBRATION_CONF_AND_TRIGGER_SB. There are no such restrictions on the use of this API. When you say it does not work can you let us know what is error code you are getting?

    2) Please let us know about the error code which you get when you issue the API earlier.

    3) If you issue this API then Calibrations which are enabled in one time mask field will be performed. If you have disabled, all the run time calibrations then also APLL and Synth Calibrations will be performed, and reports will be sent out via async event if reporting is enabled.

    4) Only two reports APLL and Synth will be sent over if everything else is disabled. In your report if you are only receiving the report for these two then you can differentiate. Also, you can disable the reporting if you do not want the report.

    5) If you disable the reporting then you will not receive the reports even for the APLL and Synth calibrations. The calibrations will be performed but reports will not be sent over.

    Thanks,

    Pradipta.

  • 0 in reply to Pradipta Bandyopadhyay
    Intellectual 410 points

    HI Pradipta,

    Thank you for your replay.

    1) - yes we are talking about AWR_RUN_TIME_CALIBRATION_CONF_AND_TRIGGER_SB.

        - No error code come from the API, it always return zero.

        - I mean by not working that i can not see the report in the async event (i've enabled reporting).

        - Also there is no timing failed report comes in the async event.

        - I see the report in the async event only if i called the runtime calibration just before triggering the frame or before triggering the frame by 0->20 msec.

        - I just wondering why it only works only under these conditions, i just need to do the calibrations whenever i called the API, what do you think the issue?

    2) error code is always zero.

    3) , 4) , 5) understood.

    Thank you.

       

     

  • 0 in reply to Joseph Hanna
    TI__Mastermind 32665 points

    Hi Joseph,

    I will need to implement your use case on the bench once to test it out. I will also try calling the API before the frame triggering. By Friday i will try to provide an update on this. 

    Thanks,

    Pradipta.

  • 0 in reply to Pradipta Bandyopadhyay
    Intellectual 410 points

    Hi Pradipta,

    Thank you so much for that, i'll wait your replay.

    Thanks

  • 0 in reply to Joseph Hanna
    TI__Mastermind 32665 points

    Hi Joseph,

    I ran the test on the bench. I tried calling the AWR_RUN_TIME_CALIBRATION_CONF_AND_TRIGGER_SB. I called it way before the frame configuration and sensor start API. I was able to receive the report. 

    I will suggest you download the latest SDK from the ti.com and it has an example test where we show usage of most of the radarSS  APIs (In the AWR2944 DFP package). You can use this example as reference to dorm your code or use the same as it is. 

    The only condition on the API is that the profiles need to be configured before calling this API. 

    Thanks,

    Pradipta.

  • 0 in reply to Pradipta Bandyopadhyay
    Intellectual 410 points

    Hi Pradipta,

    - kindly asking about (the profiles need to be configured before calling this API), Is it means (rlSetFrameConfig) or (rlSetProfileConfig) API?

    - as i call (rlSetProfileConfig) API only once at the beginning while calling (rlSetFrameConfig) before every frame.


    - and i noticed that AWR_RUN_TIME_CALIBRATION_CONF_AND_TRIGGER_SB API works only if i called it after rlSetFrameConfig API and doesn't work if i called it before.

    Thank you.

  • 0 in reply to Joseph Hanna
    Intellectual 410 points

    Hello Pradipta,

    Kindly asking if there any updates?

    Thank you.

  • 0 in reply to Joseph Hanna
    TI__Mastermind 32665 points

    Hi,

    The profile should be set before calling this API. (rlSetProfileConfig)

    The API programming sequence (IN the ICD) shows that calling the  AWR_RUN_TIME_CALIBRATION_CONF_AND_TRIGGER_SB API  after rlSetFrameConfig API is the correct sequence. So you can follow this sequencing.

    I hope you were able to find our example test code in the below path. 

    ti\mmwave_mcuplus_sdk_04_04_00_01\mmwave_dfp_02_04_08_01\ti\control\mmwavelink\test

    This has a reference implementation of all the APIs. I have used the same code base and made minor modifications to test the run time calibrations.

    Thanks,

    Pradipta.