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.

IWR1642: The IWR1642 can not transmit at low temperature.

Part Number: IWR1642

Hello,

We made the range meter board with the XI1642WABL.

It operated well at 25 degrees C.

But it did not accept the transmission command at -20 degrees C.

The power supply voltage was OK.

The power supply sequencing was OK.

The CPU of the XI1642WABL operated. And the CPU of the XI1642WABL could communicate with a PC.

What were the other causes?

Best Regards,

Sekiguchi

  • Hello,

    I am working with Mr.Sekiguchi.

    Additional information is shown below.

    We found out 2 types of error occur. (Either one occur.)

    1. MSS recieved "RL_RF_AE_CPUFAULT_SB" from BSS via MMWave_InitCfg.eventFxn.

    2. MMWave_start() return -1.

    Best Regards,

    Oda
  • Hello,

    Things we expect may work differently at temperature difference are calibration.  

    Looking at the mmwave User Guide, we need to trace the execution of each API, looking for the first error code.

    a) you have commented the power supplies are OK, please check them in the -20C environment

    b) if you enable the PMIC_CLKOUT, or the MCU_CLKOUT, following the TRM register programming, you can get a divided PLL output - check for desired frequency

    c) using the section of the mmwave sdk user guide, 5.3.1.2 for xWR1642, you can check each API call, and inspect the return status code, or the check status.  RF calibration (rlRfinitm, RK_RF_AE_INITCALIBSTATUS)

    The status at room temperature, when it works, should match the status at -20C, given the power supply, the 40Mhz clock are OK.

    Regardsl

    Joe Quintal

  • Hello,

    Thank you for your answer.

    We will check those in order.

    First, a) the power supplies were OK in the -20C environment.

    Next, c) we checked "RF Calibration Status". "RX gain calibration" was FAILURE in the -20C environment.

    When "RX gain calibration" is FAILURE, the IWR1642 can not transmit?

    What are the causes that "RX gain calibration" is FAILURE?

    Best Regards,

    Sekiguchi

  • Hello,
    In most cases if there is a calibration failure, we do not actually start the frame, hence we do not see the Tx chirp output.
    You can check the code, or the mmwave SDK User Guide, to see where the calibration status is used.
     
    You should get the calibration status at room, and at -20C and send both status values over e2e, so I can send them to engineering
    For evaluation / debug conditions. 
     
    Also please take a picture of the top of the device, so we can see the PG status (the Errata document has an ES1 or ES2) device difference.
    There is now an IWr1642 ES2 device, this is the production part.
     
    There are several Rx tests, that use the internal Tx to loop back to Rx, the BSS processor expects an Inphase and Quadrature power match, or a specific power level, I need the error code to point to a specific error.
     
    Regards,
    Joe Quintal
     
  • Hello,

    Thank you for your answer.

    We got the calibration status(rlRfInitomplete_t). The values are as follows.

      At room temperature
        calibStatus:0x800017FE
        calibUpdate:0x17FC

      At -20 degrees (when MMWave_start() returns error.)
        calibStatus:0x800013FE
        calibUpdate:0x13FC


    When we got RL_RF_AE_CPUFAULT_SB, we checked the payload(rlCpuFault_t). The values are as follows.

      faultAccType:0xFF
      faultAddr:0x0
      faultAxiErrType:0xFF
      faultErrSrc:0xFF
      faultErrStatus:0xFFFF
      faultLR:0x3C0C4
      faultPrevLR:0x0
      faultRecovType:0xFF
      faultSP:0x800FBF0
      faultSpsr:0x2000011F
      faultType:0x3
      lineNum:0x17DA


    We took a picture of the top of the device.
    Please see the attached file.
    It must be ES1 chip.


    We tried to output from PMIC_CLKOUT pin. but failed.
    Please tell us how to program for output from PMIC_CLKOUT.
    Or is there any sample source?

    Best Regards,

    Oda

  • Hello,
    If you download the dfp Radar Studio package, 5.13.5 discusses the calibration status.
    www.ti.com/.../mmwave-dfp ‘  AWR1xx_Radar_Interface_Control.pdf
    This has more detail for some of the messages and status. 
     
    It appears that bit 10, Rx gain calibration has failed.  I have sent your error report to the designers.
     
    If you wish to work in Tx side for now, See section 5.5.11, clear bit 10 in the One Time calibrations, and scheduled calibrations.
    This will bypass the Rx Gain calibration for now.
     
    I will send an update, when I have a design engineer’s answer.
    Thank you
    Joe Quintal
     
     
  • Hello,
    PMIC Clock registers are described in the Technical Reference Manual (under user guides on iwr1642 web page), if you connect your IWr1642 EVM, with a Devpack (‘www.ti.com/.../MMWAVE-DEVPACK’), to Radar Studio (‘www.ti.com/.../mmwave-dfp’)
    You can use the console window in Radar Studio to see the register writes, and setup the PMIC_Clock_Output enabled, and typically you would divide the PLL 600Mhz clock by 150, or 300, to get a 4 or 2Mhz clock output.  See ClockOutCfg tab.
    Regards,
    Joe Quintal
     
  • The design engineers recommend changing the BSS to dfp version 1.0 and retesting.
    If you download and install the dfp (Radar Studio) version 1.0 or later, "www.ti.com/.../mmwave-dfp"
    you can find the file at, C:\ti\mmwave_dfp_01_00_00_01\firmware\radarss
    Regards,
    Joe Quintal
  • Hello,

    We disabled the Rx Gain calibration.
    The error at MMWave_start() no longer occurs.
    We want to know detail information about the Rx Gain calibration.
    Is there any document about it?


    We used the RadarSS 2.0.0.15. and we retested.
    However, RL_RF_AE_CPUFAULT_SB still occur. The values are as follows.

    faultAccType:FF
    faultAddr:0
    faultAxiErrType:FF
    faultErrSrc:FF
    faultErrStatus:FFFF
    faultLR:FBBE
    faultPrevLR:0
    faultRecovType:FF
    faultSP:800FAD0
    faultSpsr:2000011F
    faultType:3
    lineNum:F1

    Best Regards,
    Oda

  • Hello,

    We could get a divied PLL output from the PMIC_CLKOUT.

    The status at room temperature matched the status at -20C.

    +25C                                                     

    -20C

      

    We are waiting for your response of error code.

    Best Regards,

    Sekiguchi

  • Hello,

    This indicates you don't have a clock problem.

    I sent the error information, you have a receiver gain error.   The bit field for this is shown in the initial and run time calibration mask, and the error code indicates if its not a '1' for the status bit that this bit is in error.

    Please download the "dfp" radar studio package.  In the docs folder there is an AWR1xx_Radar Interface_Control.pdf.

    The calibration masks (what tests are run) is discussed in 5.2.9

    In the CLI commands the Initial and RunTime calibration mask, can be set to 0 for bit 10.  You should then get the Tx output, if there are no other errors.

    The calibration status is discussed in section 5.13.5.  The masked calibrations have to return a '1' to indicated PASS status.

    The designer indicates that downloading the latest DFP package, the new BSS firmware file needs to be compiled and used for your test.

    Regards,

    Joe Quintal

  • Hello,

    e2e.ti.com/.../2551435
    In this report, we tested using the latest DFP package (mmwave_dfp_01_00_00_01, BSS firmware 2.0.0.15).

    we understood how to disable the rx gain calibration.
    we want to know what the rx gain calibration do. and
    we want to know what will happen when the rx gain calibration is disabled.

    Best Regards,
    Oda

  • Hello,

    The Rx Gain calibration is used to adjust for part variation, aging, and device temperature by looping back a Tx internal signal to the Rx.

    There is an internal adjustment for the 2 variable Gain sections covering the LNA gain from 24-48db.

    As suggested in another E2E post, the design engineer indicates if you use a later version of DFP this is supposed to be fixed.

    If you operate without Rx gain calibration, the LNA Rx Gain setting may vary over temperature and device.

    Please try to use a later dfp BSS package and compile and test.

    Regards,

    Joe Quintal

  • Hello,

    We got another trouble as the -20C.
    We got the error and TX output stoped about 0C.
    The IC can transmit, but TX stops in a minute.
    The error is the following.
    MSS recieved "RL_RF_AE_CPUFAULT_SB" from BSS via MMWave_InitCfg.eventFxn.

    When we got RL_RF_AE_CPUFAULT_SB, we checked the payload(rlCpuFault_t). The values are as follows.

    faultAccType:0xFF
    faultAddr:0x0
    faultAxiErrType:0xFF
    faultErrSrc:0xFF
    faultErrStatus:0xFFFF
    faultLR:0x3C0C4
    faultPrevLR:0x0
    faultRecovType:0xFF
    faultSP:0x800FBF0
    faultSpsr:0x2000011F
    faultType:0x3
    lineNum:0x17DA

    What is the cause of the error "CPUFAULT"?

    Best Regards,
    Sekiguchi
  • AWR1xx_Radar_Interface_Control.pdfHello,

    In the radar Studio documentation, there is an ICD document, I will attach it this time.   Under the Initial Self test, and the Repetitive testing there is a bit mask for each test.   Once you know which bit field is failing you can mask it off for temporary testing.   In most cases Radar Subsystem Test errors are handled through BSS firmware upgrades, so downloading the latest dfp package from the TI website , and using the BSS image for your device is needed.

    I have tried to answer this emails 2x already, the answer does not seem to be going through E2E.

    Please look up the Initial calibration command and bit field in the ICD document attached.

    Regards,

    Joe Quintal

  • Hello,
    The RF Init contains the RF Initial calibration, like your other reported case, you need to trace through the calls using the ICD document, the calibration status can be requested. Evaluating the calibration status should have a '1' for success, given your test mask, the bit with a '0' is the error. We need to know the status to advise you further.

    In your description, I assume that the test passes at room temperature. Please step through this to get the calibration status at room temp (reference), then repeat at -20C.

    Regards,
    Joe Quintal
  • Hello,
    In the "dfp" package Docs folder
    dfp download - "www.ti.com/.../mmwave-dfp
    There is a discussion of BSS faults, AWR_RF_CPUFAULT, see Table 5.46, this is not listed as a Fault. Fault_Type = 0xFF
    Please reset, see if its reproducible, and send more information if the mmwave sensor is not performing as expected.

    Regards,
    Joe Quintal
  • When we got the CPUFAULT or the other error, we reset the device.
    However, the payload(rlCpuFault_t) was same value if we got the CPUFAULT.

    We tried another approch. a task blocked the other tasks for a while.
    we fixed this not to block. we tried this for another reason.
    but the CPUFAULT no longer occurs.

    We have some question.
    1) Will blocking the tasks cause the CPUFAULT?
    2) If the temperature is low, does the BSS need more proccesing time ?

    Best Regards,
    Oda

  • Hello,
    If a task is blocked forever, the mailbox eventually times out between the BSS and MSS.

    2) at low temperature, its possible that the BSS needs more time to run calibration. I will ask the designer.

    Regards,
    Joe Quintal