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: SPI Data Capture Example - CLI Error: "SPI ADC Streaming is not enabled"

Part Number: AWRL6432BOOST

Tool/software:

Hello Experts,

I am trying to use the “xWRL6432_Raw_Data_Over_SPI” example from “\radar_toolbox_2_30_00_12\source\ti\examples\Fundamentals” for the AWRL6432BOOST. Following the steps from the user’s guide, I flashed the AWRL with the prebuilt binary. Afterwards I set S1.1 and S1.6 ON to setup the device for SPI transfer. I open the „spi_data_tool_capture.exe“ and select „MotionDetect_SPI_Data_Capture_FTDI.cfg” within “\radar_toolbox_2_30_00_12\source\ti\examples\Fundamentals\xWRL6432_Raw_Data_Over_SPI\chirp_configs\xwrl6432boost”.

The CLI window prints the following:

Choose CFG file in the pop-up window
b'sensorStop 0\n'
b'Done\r\n'
b'mmwDemo:/>channelCfg 7 3 0\n'
b'Done\r\n'
b'mmwDemo:/>chirpComnCfg 8 0 0 128 4 28 0\n'
b'Done\r\n'
b'mmwDemo:/>chirpTimingCfg 6 63 0 75 60\n'
b'Done\r\n'
b'mmwDemo:/>frameCfg 2 0 200 32 350 10\n'
b'Done\r\n'
b'mmwDemo:/>guiMonitor 2 1 0 0 0 1 0 0 0 0 0\n'
b'Done\r\n'
b'mmwDemo:/>sigProcChainCfg 32 2 1 0 4 4 0 15 \n'
b'Done\r\n'
b'mmwDemo:/>cfarCfg 2 8 4 3 0 12.0 0 0.5 0 1 1 1\n'
b'Done\r\n'
b'mmwDemo:/>aoaFovCfg -60 60 -40 40\n'
b'Done\r\n'
b'mmwDemo:/>rangeSelCfg 0.1 12.0\n'
b'Done\r\n'
b'mmwDemo:/>clutterRemoval 1\n'
b'Done\r\n'
b'mmwDemo:/>compRangeBiasAndRxChanPhase 0.0 1.00000 0.00000 -1.00000 0.00000 1.00000 0.00000 -1.00000 0.00000 1.00000 0.00000 -1.00000 0.00000\n'
b'Done\r\n'
b'mmwDemo:/>adcDataSource 0 C:/ti/mmwave_lp_sdk/examples/datapath/common/testBench/major_motion/adc_data_0001_CtestAdc6Ant.bin\n'
b'Done\r\n'
b'mmwDemo:/>adcLogging 2\n'
b'Error: SPI ADC Streaming is not enabled \r\n'
b'mmwDemo:/>lowPowerCfg 0\n'
b'Done\r\n'
b'mmwDemo:/>factoryCalibCfg 1 0 40 0 0x1ff000\n'
b'Done\r\n'
b'mmwDemo:/>mpdBoundaryBox 1 0 1.48 0 1.95 0 3\n'
b'Done\r\n'
b'mmwDemo:/>mpdBoundaryBox 2 0 1.48 1.95 3.9 0 3\n'
b'Done\r\n'
b'mmwDemo:/>mpdBoundaryBox 3 -1.48 0 0 1.95 0 3\n'
b'Done\r\n'
b'mmwDemo:/>mpdBoundaryBox 4 -1.48 0 1.95 3.9 0 3\n'
b'Done\r\n'
b'mmwDemo:/>sensorPosition 0 0 1.44 0 0\n'
b'Done\r\n'
b'mmwDemo:/>minorStateCfg 5 4 40 8 4 30 8 8\n'
b'Done\r\n'
b'mmwDemo:/>majorStateCfg 4 2 30 10 8 80 4 4\n'
b'Done\r\n'
b'mmwDemo:/>clusterCfg 1 0.5 2\n'
b'Done\r\n'
b'mmwDemo:/>profileSwitchCfg 0 25 25\n'
b'Done\r\n'

********** Config Sent Successfully **********
Number of ADC samples:  128
Number of chirps per burst:  2
Number of bursts per frame:  32
Number of frames being captured:  10
Number of RX antennas:  3
Number of TX antennas:  2
**********************************************

"1" for AOP
"2" for FCCSP
Enter Device:
2
Enter Data Type (1 - ADC Data, 2 - RadarCube, 3 - Detection Matrix):
1
Total Size of Data : 49152
FTDI device opened:
{'type': 8, 'id': 67330068, 'description': b'C232HM-DDHSL-0', 'serial': b'FT8KQ45N'}
Starting write loop...

Sensor started successfully. Beginning capture

The “adcLogging 2” CLI command is not accepted even though S1.6 is set to ON (see line 29 above). The generated “data0.txt” file is empty as well. As you can see, the FTDI cable is recognized as well. How can I enable SPI ADC streaming to capture raw ADC data?

Thanks!

- Rene

  • Hi Rene,

    I suspect this might be an issue related to the app image you may be flashing onto the board but I will be able to confirm this in a few days time.

    So I will get back to you but in the mean time could you try to get the project imported and changing the #define SPI_DATA_STREAMING to 1 and SPI_DATA_STREAMING_MODE to 1 (since using the FTDI chip) in the mmw_cli.h file under the mpd_spi_output_xwrL64xx project.

    Project file path: radar_toolbox_2_30_00_12\source\ti\examples\Fundamentals\xWRL6432_Raw_Data_Over_SPI\src\xwrl6432

    Let me know if you run into any trouble during this process.

    Best,

    Vignesh K.

  • Hi Vignesh,

    Thank you for your reply. I've found the macros. However upon building there are errors (see screenshot below). I wasn't able to find the structure ATE_calibData and I wasn't able to see from where this extern is being called from: "extern uint8_t gATECalibDataStorage[]" (mmw_cli.c, line 125) Are they supposed to be in a header file? And if so could you tell me in which header file it should be? I am on CCS 12.8.0.

    Regards,

    - Rene

  • Hi Rene,

    Please give me a few days to look into this issue a little deeper but in the mean time you can make these updates-

    added the following to to mmw_cli.c:
    ```
    extern uint8_t gATECalibDataStorage[];
    uint8_t gATECalibDataStorage[(ATE_CALIB_DATA_LENGTH + 4)] __attribute__((aligned(8))) = {0};

    ```
    added the following to mmw_cli.h:
    ```
    #define ATE_CALIB_DATA_LENGTH (uint8_t)(128U)
    #define ATE_CALIB_DATA_VALID 0x0U
    typedef struct ATE_CalibData_s
    {
    /* Flag to indicate the calibration data is valid */
    uint32_t validityFlag;

    /* Factory Calibration data */
    uint8_t factoryCalData[ATE_CALIB_DATA_LENGTH];

    } ATE_CalibData;
    ```

    This will help with your current issues but I suspect you will see other issues while building your project. I will contact you again in a few days letting you know what I find. Thank you for your patience!

    Best,

    Vignesh K.

  • Hello Vignesh,

    as you already suspected the previous error is cleared, however the current issue seems to be due to memory constraints.

    Thank you for your support,

    - Rene

  • Hey Rene,

    It looks like we are seeing all these issues because there is a mismatch in SDK's between this example project and the latest SDK which we have downloaded. I won't be able to look into this until early next week but if you have time, I would suggest downloading SDK 5.4.0.01 and attempting to run the example there after changing the #define SPI_DATA_STREAMING to 1 and SPI_DATA_STREAMING_MODE to 1 if needed. And any of the other changes that I mentioned.

    No problem if you can't validate this yourself but I will get back to you early next week with some updates on this issue.

    Best,

    Vignesh K.

  • Hi Vignesh,

    installing SDK 5.4.0.01, re-importing the example into CCS and setting SPI_DATA_STREAMING and SPI_DATA_STREAMING_MODE to 1 resolved the issue. I was able to read the raw data file with MATLAB and have it processed accordingly.

    All the best,

    - Rene

  • Hey Rene,

    I am glad that worked! Thank you for verifying this before I could.

    Best,

    Vignesh K.