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.

AWRL1432BOOST: error when running kick to open project with SDK 5.5.0.2

Part Number: AWRL1432BOOST
Other Parts Discussed in Thread: AWRL1432

Tool/software:

Hi Expert,

I am testing \ti\radar_toolbox_2_10_00_04\source\ti\examples\Kick_to_Open project with SDK 5.5.0.2 and found error happened during running as below.

INFO [gui_core.py:192] Data COM Port found: COM3
INFO [gui_core.py:183] CLI COM Port found: COM4
INFO [gui_parser.py:233] Connected (one port) with baud rate 1250000
line=UseDSPhotoViewerAsDefault=1

[ExplorerProps.Add()]prop=UseDSPhotoViewerAsDefault, value=1

[GetSecuType]c:\, error=3

[GetSecuType]c:\, error=3

[GetSecuType]d:\, error=3

[GetSecuType]d:\, error=3

[GetSecuType]w:\, error=123

[GetSecuType]w:\, error=123

[GetSecuType]z:\, error=123

[GetSecuType]z:\, error=123

b'channelCfg 3 3 0\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>chirpComnCfg 21 0 0 128 1 34 0\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>chirpTimingCfg 8 20 0 102.98 76\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>frameCfg 2 0 200 128 70 0\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>sigProcChainCfg2 32 32 1 0.4 1.2 25\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>adcDataSource 0 C:/ti/mmwave_lp_sdk/examples/datapath/common/testBench/gesture_recognition_adc_data/radar_data_6432_100framesS.bin\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>adcLogging 0\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>presenceDetectCfg 1 800 1600 10\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>lowPowerCfg 1\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>factoryCalibCfg 1 0 40 0 0x1ff000\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>sensorStart 0 0 0 0\n'
b'\n'
b'Error: mmWave Control Initialization failed [Error code -205848574] [errorLevel 2] [mmWaveErrorCode -3141] [subsysErrorCode 0]\n'
b'Error: Boot Calibration failure\n'
ERROR [gui_parser.py:153] ERROR: No data detected on COM Port, read timed out
ERROR [gui_parser.py:154] Be sure that the device is in the proper mode, and that the cfg you are sending is valid

Please help to check this issue.

Thanks.

  • Hi,

    I'm wondering if you are potentially using an older silicon revision of the device that is not compatible with SDK 5.5.0.2. The errata document below lists how to find the package marking that indicates the silicon revision. I've included the specific decoder for the AWRL1432 silicon revision markings below.

    https://www.ti.com/lit/pdf/swrz138

    ES1.0 = 791

    ES1.1 = 791A

    ES2.0 = 843B

    Thanks,

    Clinton

  • Hi Clinton,

    It is XAL1432 / BA / 44zcs79 / 843B marked in the chip.

    What SDK version should I use for kick to open project with this EVM?

    It is functional when prebuild image of presence and motion detection refreshed. 

    Batis Chen

  • Hi,

    The latest SDK version, which you are using (5.5.0.2) is the right one for this device. Could you use the latest radar toolbox version 2.20.0.5 as well? This will match the SDK version for the KTO demo. Let us know if the error persists or changes.

    Thanks,

    Clinton

  • Hi Clinton,

    By using toolbox version 2.20.0.5 with SDK 5.5.0.2, KTO demo can run correctly.

    But we got another issue.

    We have 2 AWRL1432 EVMs, EVM1 has very good recognition rate about 99% up, but the other one is not and only about 70%.

    Our test environment: sensor height 40 cm (Z axis), kick distance 30~60 cm (toes to sensor)(Y axis)

    Test result of 5 positions (+20cm, +10cm, 0cm, -10cm, -20cm) (X axis) (kick 10 times)(from left to right, 0cm means in front of sensor)

    EVM No.1: 100%, 100%, 100%, 100%, 100%

    EVM No.2: 0%, 70%, 70%, 90%, 70%

    The FW is the same on both EVMs.

    Can you help to clarify what is going on on EVM No.2?

    Is it possible that we can get a replacement for EVM No.2?

  • Hi,

    Have you measured and set the specific range bias and phase compensation parameters for the board which is not performing well? Please take a look at section "3.2.6 Range Bias and Phase Compensation Configuration" in the document listed below. Please perform the procedure there and let us know how this affects your results.

    C:/ti/MMWAVE_L_SDK_05_05_00_02/docs/Motion_Presence_Detection_Demo_Tuning_Guide.pdf

    Thanks,

    Clinton