• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 1091 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.

Original question:

AWRL6432: Request for code snipet of ATE calibration

AWRL6432: How to avoid ATE calibration step for each device

Jack
Mastermind 9105 points
Part Number: AWRL6432
Other Parts Discussed in Thread: IWRL6432,

Hi TI

It is said by Zigang as below. 

<e2e.ti.com/.../4488602

"For the devices that are shipping to customer,  ATE calibration trims is blown in EFUSE and customers are not required to flash ATE calibration binary".

Please let us know more details on this topic. Customer also would like to avoid additional ATE calibration task for each custom board.

When you program the Out of Box Demo image on the empty flash, please include the ATE calibration data and explain in detail how the user does not have to perform ATE calibration separately.
I would like to ask you this question because ATE calibration cannot be performed on all boards when mass-producing products.

Customer would like to remove ATE calibration step in Factory mass-production line. I mean the ATE calibration data need to be stored into specific area when program their application binary.  

Thanks.

Regards, 

Jack

  • 0
    TI__Mastermind 37805 points

    Hi Jack,

    The ATE calibration is done by TI in board manufacturing. Customers do not have to perform it on the IWRL6432. In a previous early product release, some devices needed to be calibrated, but this is no longer the case.

    Best,

    Nate

  • 0 in reply to Nathan Block
    Mastermind 9105 points

    Hi Nathan.

    I understand that since MMWAVE_L_SDK_05_02_00_02 it has been changed to not perform ATE calibration by device.
    I'm inquiring about this.

    Sources included in that version still reference ATE Calibration data.
    For example, mmw_demo/motion_and_presense_detection.

    It appears that motion_detect.c is trying to import ATE calibration data from Flash while invoking MmwDemo_calibInit().
    Failure to retrieve data from Flash will result in assert.
    If it is read from Flash, it is understood that the application developer, not the TI, should perform ATE calibration on a device-by-device basis. I wonder if it's fused inside IWRL6432.

    Please tell me how not to perform ATE calibration based on motion_and_presense_detection.

    If We need to do ATE Cal, please answer if it is correct to read from the eFUSED ROM area.

    Hence Customer need not to consider ATE calibration process more on thier custom project too. right?

    Please explain the case when customer would assemble their custom board with a new IWRL6432 IC and empty flash memory.

    Thanks.

    Best Regards, 

    Jack

  • 0 in reply to Jack
    TI__Mastermind 37805 points

    Hi Jack,

    ATE calibration data should be burned into memory by default by TI. Customers may need to modify the compRangeBiasAndRxChanPhase on a device-by-device basis, but they should not need to modify the ATE calibration.

    Best,

    Nate

  • 0 in reply to Nathan Block
    Mastermind 9105 points

    Hi Nate

    Thanks for your kind answer.

    BTW, A customer is still seeing the failure from their L6432BOOT EVM kit.

    Plese see the failure log below.

    • Test Device : AWRL6432BOOST
    • Test Firmware : 
    • C:\ti\MMWAVE_L_SDK_05_02_00_02\examples\mmw_demo\motion_and_presence_detection\prebuilt_binaries\motion_and_presence_detection_demo.release.appimage
    • Etc : Full erase before firmware downloading
    • failure log

    Please load and rerun ATE Calirbation application!
sensorStart 0 0 0 0
Error: mmWave Control Initialization failed [Error code -205787070] [errorLevel 2] [mmWaveErrorCode -3141] [subsysErrorCode 15376]
Error: Boot Calibration failure
Error: mmWave factory calibration failed
Error: mmWave Open failed [Error code: -3121 Subsystem: 0]
Error -1

    The issue is reproducible as it's pre-launch device attached in EVM.  The related question is from below.

    AWRL6432: Need API or Interface for ATE calibration. - Sensors forum - Sensors - TI E2E support forums

    Could you please let us know how to avoid this assert failure after Flash full erase on the latest SDK 5.2 as it seems still trying to access ATE cal value stored in Flash?

    In the RTM version of L6432, is the ATE cal value programmed in the Sensor internal ROM and shipped? I was asked to re-confirm that Customer don't need to program it separately on the external Flash. Please answer me.

    Regards, 

    Jack

  • 0 in reply to Jack
    TI__Expert 8802 points

    Hi Jack,

    Nate is out today, but as far as I'm aware yes the RTM L6432 devices will have the ATE calibration values burned into the device.

    For the customer who needs the ATE calibration from the pre-launch device. They need to flash (in flashing mode) the ATE calibration binary from MMWAVE_L_SDK_05_02_00_02\tools\Ate_Calibration\xwrL64xx, and then switch it into functional mode for a few seconds. After that, the device should have ATE calibration values and they can reset, go back to flashing mode, and flash whatever binary they wish.

    Regards,

    Tim