• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 32 subscribers
  • Views 186 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

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

Batis Chen
Prodigy 100 points
Part Number: AWRL6432BOOST

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 some errors happened during running as below.

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 59\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.25 1.66 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 1500 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'Done\r\n'
b'\n'
INFO [parseFrame.py:114] Invalid TLV type: 1142964559
WARNING [parseFrame.py:103] TLV Header Parsing Failure: Ignored frame due to parsing error
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

Already updated definition for SOC_XWRL64XX.

Another error happened when frame rate set as 35, log is showed below.

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 59\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>frameCfg 2 0 200 128 35 0\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>sigProcChainCfg2 32 32 1 0.4 1.5 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 0 1500 9000 10\n'
b'\n'
b'Done\r\n'
b'\n'
b'mmwDemo:/>lowPowerCfg 0\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'AOA DPU config return error:-30808 \n'
b''

The same CFG works well with SDK 5.4.0.1.

Please help to check this issue.

Thanks.

  • 0
    TI__Expert 8782 points

    Hi,

    The Kick to Open project in SDK 5.5 has a different structure, please see the updated .cfg files in the SDK, as there are new commands that need to be sent.
    Regards,

    Tim

  • 0 in reply to Tim Henderson
    Prodigy 100 points

    Hi Tim,

    I can't find the CFG file for kick to open project in SDK 5.5.0.4.

    Can you provide it to me?

    Thanks.

  • 0 in reply to Batis Chen
    TI__Expert 8782 points

    Hi,

    Please try the following:

    channelCfg 3 3 0
    chirpComnCfg 21 0 0 128 1 34 0
    chirpTimingCfg 8 20 0 102.98 76
    frameCfg 2 0 200 128 70 0
    sigProcChainCfg2 32 32 1 0.25 1.66 25 4 1 1
    cfarCfg 0 8 3 0 0 0 1 0 1 1 0 0
    aoaFovCfg -80 80 -45 45
    rangeSelCfg 0.2 3.4
    cfarMinorMotionCfg 2 8 3 3 8.0 1
    adcDataSource 0 C:/ti/mmwave_lp_sdk/examples/datapath/common/testBench/gesture_recognition_adc_data/radar_data_35frames.bin
    adcLogging 0
    boardTiltAngle 0
    pointCloudEnable 1
    guiMonSel 1 1 0 1
    presenceDetectCfg 0 1500 1600 10
    lowPowerCfg 0
    factoryCalibCfg 1 0 40 0 0x1ff000
    sensorStart 0 0 0 0

  • 0 in reply to Tim Henderson
    Prodigy 100 points

    Hi Tim,

    Another error happened as below and still no data come out.

    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 59\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.25 1.66 25 4 1 1\n'
    b'\n'
    b'Error: Invalid usage of the CLI command\n'
    b'Error -1\r\n'
    b'mmwDemo:/>cfarCfg 0 8 3 0 0 0 1 0 1 1 0 0\n'
    b'\n'
    b"'cfarCfg' is not recognized as a CLI command\r\n"
    b'mmwDemo:/>'
    b'aoaFovCfg -80 80 -45 45\n'
    b'\n'
    b"'aoaFovCfg' is not recognized as a CLI command\r\n"
    b'mmwDemo:/>'
    b'rangeSelCfg 0.2 3.4\n'
    b'\n'
    b"'rangeSelCfg' is not recognized as a CLI command\r\n"
    b'mmwDemo:/>'
    b'cfarMinorMotionCfg 2 8 3 3 8.0 1\n'
    b'\n'
    b"'cfarMinorMotionCfg' is not recognized as a CLI command\r\n"
    b'mmwDemo:/>'
    b'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:/>boardTiltAngle 0\n'
    b'\n'
    b"'boardTiltAngle' is not recognized as a CLI command\r\n"
    b'mmwDemo:/>'
    b'pointCloudEnable 1\n'
    b'\n'
    b"'pointCloudEnable' is not recognized as a CLI command\r\n"
    b'mmwDemo:/>'
    b'guiMonSel 1 1 0 1\n'
    b'\n'
    b"'guiMonSel' is not recognized as a CLI command\r\n"
    b'mmwDemo:/>'
    b'presenceDetectCfg 0 1500 1600 10\n'
    b'\n'
    b'Done\r\n'
    b'\n'
    b'mmwDemo:/>lowPowerCfg 0\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'Doppler DPU config return error:-30701 \n'
    b''
    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

  • 0 in reply to Batis Chen
    TI__Expert 8782 points

    Hi,

    Please wait for a new radar toolbox release in the next week or so. This will have an updated KTO project that works with 5.5.

    In the meantime, are you sure you have flashed the correct demo from 5.5 on here? The errors you are getting suggest that the right project has not been flashed onto the device.

    Regards,

    Tim