• State
  • Replies 5 replies
  • Subscribers 30 subscribers
  • Views 125 views
  • Users 0 members are here
Support feedback
Options
Options
Related

AWR6843AOP: Question about Calibration in xWR6843AOP SDK 3.5.4

ChaoChin Huang
Prodigy 220 points
Part Number: AWR6843AOP
Other Parts Discussed in Thread: IWR6843

Tool/software:

I am currently working with the xWR6843AOP platform, SDK version 3.5.00.04.


I flashed the binary file located at:


C:\ti\mmwave_sdk_03_05_00_04\packages\ti\demo\xwr64xx\mmw\xwr64xxAOP_mmw_demo.bin

For visualization, I used mmWave_Demo_Visualizer 3.5.0 with the configuration file profile_3d_aop.cfg and default value. 


In the Visualizer’s Advanced Command tab, I entered the command:

measureRangeBiasAndRxChanPhase 1 1.0 0.2

However, the system responded with a message indicating that the command is not supported.

I recall that this procedure used to work in the past. Could you please advise if I may have missed a step, or if I am using the wrong file for this SDK version?

Thank you for your support.

Best regards,

Chris.

  • 0
    TI__Mastermind 40495 points

    Hi, Chris:

    SDK users guide and Doxygen documentation all indicate that measureRangeBiasAndRxChanPhase should be supported.  Millimeter Wave (mmw) Demo for XWR64XX/XWR68xx/XWR68XXAOP

    Can you add the measureRangeBiasAndRxChanPhase CLI directly to profile_3d_aop.cfg and see whether you will be able to run the visualize successfully.

    Best,
    Zigang

  • 0 in reply to zigang Yang
    Prodigy 220 points

    Hello,

    I have a question about the recommended calibration process for our IWR6843 boards. Since every board requires individual calibration, I need to know how to properly execute the measureRangeBiasAndRxChanPhase command and write the results using compRangeBiasAndRxChanPhase within the HCC architecture.

    If a direct CLI method is not available in the HCC framework, I am considering the following alternative approach. Could you please validate if this is the correct procedure?

    1. First, load the OOB.bin (Out-of-Box demo) to perform the measureRangeBiasAndRxChanPhase measurement and generate the calibration data.

    2. Then, use a flash API to write this calibration data to a specific, reserved block in the external flash memory.

    3. Finally, flash our mass-production binary, which will be programmed to read the calibration data from that location in flash during initialization.

    Could you please advise on the best practice or the recommended method for implementing this per-device calibration for production?

    Thank you for your guidance.

  • 0 in reply to ChaoChin Huang
    TI__Mastermind 40495 points

    Hi, there:

    Sorry for the delay.  Your proposal looks good to me.  Factory calibration follows a similar procedure.  

    Best,

    Zigang

  • 0 in reply to zigang Yang
    Prodigy 220 points

    I have a question that I’d like your help with. For the compRangeBiasAndRxChanPhase parameters, is there a recommended flash memory storage address (for example, 0x5008_0000)? Also, which flash API should I use if I want to store the calibration values right after performing calibration?

    Additionally, in the mass production program, where should I modify the storage location of compRangeBiasAndRxChanPhase in flash memory, so that during program loading the calibration values from flash memory can be properly restored into the internal RAM of the IWR6843?

  • 0 in reply to ChaoChin Huang
    TI__Mastermind 40495 points

    Hi, there:

    Please give me some time to find the answer.  Will get back to you early next week.

    Best,

    Zigang