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.

IWR1443BOOST: Unable to capture data with mmWave Studio CLI or DCA1000EVM CLI

Part Number: IWR1443BOOST
Other Parts Discussed in Thread: DCA1000EVM, UNIFLASH, AWR2243

Hello Team,

I'm posting on behalf of my customer who are trying to capture raw ADC data using IWR1443BOOST and DCA1000EVM for further processing. Please see below:

We have been trying to capture raw ADC data using IWR1443BOOST and DCA1000EVM for further processing. When using the mmWave Studio (02.01.01.00) GUI, we are able to connect to the board and capture data most of the time; however, our experimental setup requires being able to control the process using a script so that it can be operated without manual configuration. When attempting to automate this process, we have encountered the following set of issues:

1. mmWave Studio CLI using the attached "mmwaveconfig.txt" (from mmWave Platform 1.2.1) is not able to load the desired configuration and instead produces the error shown below. This occurs for both boards preloaded with "mmwave_Studio_cli_xwr14xx.bin" and with initially empty SFLASH.

================= mmWave Studio CLI Application ====================Configuring mmWave Sensor Device over SPI...====================== SPI Mode of Operation ======================Device map 1 : SOP 4 mode successfulDevice map 1 : Device reset successfulrlDeviceEnable Callback is called by mmWaveLink for Device Index [0]mmWave Device Power on failed for deviceMap 1 with error -8[ERROR] During Device Configuration [-8]=========== mmWave Studio CLI Application: Exit ===========

2. When attempting to flash the RadarSS and MSS binaries provided with mmWave Studio using UniFlash, we get the header below. Since these binaries are supposed to be dedicated to this board, what could be the cause of this error?

[17.12.2021, 17:22:50] [INFO] Cortex_R4_0: Checking file C:/ti/mmwave_studio_02_01_01_00/rf_eval_firmware/radarss/xwr12xx_xwr14xx_radarss.bin for correct header for IWR1443.[17.12.2021, 17:22:50] [INFO] Cortex_R4_0: Header of C:/ti/mmwave_studio_02_01_01_00/rf_eval_firmware/radarss/xwr12xx_xwr14xx_radarss.bin file indicates it is not a valid file to flash to IWR1443: 0x43525052[17.12.2021, 17:22:50] [ERROR] Cortex_R4_0: !!! Aborting flashing of specified files!!!

3. When trying to use "DCA1000EVM_CLI_Control.exe" from the mmWave Studio with "configFile_chirp3500MHz.json" we get "Start Record command : Success", but no data is produced, even when we provide the configuration commands directly over the Application/User UART port.

4. Due to the very large number of cables connecting the DCA1000EVM to the computer, we would like to replace the PC with a Raspberry Pi to easily move the entire assembly between locations. Since there is no Linux version of mmWave Studio, we would like to ask what the recommended data capture approach for Linux-based systems is?

attachemnt.zip

Thanks in advance.

Regards,

Renan

  • Hi Renan, 

    I will look into these issues for you.  If possible, could you tell me who the customer is and what their application is?

    Thanks,

    Brennan

  • Hello Brennan,

    Good day, please see my customer response below:

    We are researching intelligent methods of data processing, with a focus on vital signs detection and human action classification. We want to use IWR1443BOOST purely as a data source without any onboard processing and have (at this time) prepared a configuration with 28 unique chirps defined based on 4 profies. Ideally, we would like to reach a "one click" approach where we can start the measurement session by pressing a button on a Raspberry Pi so that we can easily move between different locations and participants.

    Regards,

    Renan

  • Hi Renan, 

    Before diving into your previous questions, I want to address something the customer said in your most recent reply:

    "We want to use IWR1443BOOST purely as a data source without any onboard processing"

    We have offerings for this: the AWR2243 is a front-end only sensor that might be of interest for the customer.  However, if they have already decided on the 1443, that can be used as a data source with mmWave studio and the DCA1000.

    1) The error code they received indicates that the device failed to send a response.  Can you ensure that they have set all the parameters correctly in the mmWaveConfig.txt file?  Refer them to the mmWave studio CLI Developer's Guide.

    2) Make sure the device is in flashing mode before attempting to flash the device.  Always power cycle between SOP modes.

    https://www.ti.com/lit/ds/symlink/iwr1443.pdf?ts=1640709548677&ref_url=https%253A%252F%252Fwww.google.com%252F

    See: section 6.8

    In addition, if they are not looking to debug the application, they only need to flash the binary located at:

    C:\ti\mmwave_platform_1_2_1\tools\studio_cli\src\pre-built-Binaries\mmwave_Studio_cli_xwr14xx.bin

    3) Refer to these past e2e threads for information on this:

    https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1010050/dca1000evm-use-command-line-for

    They may not ever be starting the actual sensor, and are only starting the DCA1000.  

    4) DCA1000EVM does work on linux without the direct usage of mmWave Studio application. Please follow the instructions described in "TI_DCA1000EVM_CLI_Software_UserGuide.pdf". You can find this document in the following directory 'C:\ti\mmwave_studio_02_01_01_00\mmWaveStudio\ReferenceCode\DCA1000\Docs'.  The document describes how to build the source and execute on linux machines. 

    What is offered here is a command line interface tool. It will simply record the data from the DCA1000 into a .bin file. Post-processing tools targeted for linux would have to be developed on your own. 

    Please see the following thread for more information on this: https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/968875/dca1000evm-extract-real-time-data-to-linux

    It mentions where to find the source code, directions on how to compile, etc.

    Regards,

    Brennan