Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

  • State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 844 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.

AWR2944EVM: Cannot get raw ADC data from DCA1000 to generate bin file

Cherry Zhou
Mastermind 22235 points
Part Number: AWR2944EVM
Other Parts Discussed in Thread: AWR2944, UNIFLASH, DCA1000EVM,

Hi team,

Here's an issue from the customer may need your help:

Issue: Raw data cannot be captured using AWR244EVM with DCA1000 

The customer had referenced this thread and done the following:

1) For two boards: XDS_USB and FTDI connect to PC via data cable, connect network cable and configure IP, and two boards connect 60-row cable. 

2) The awr2944 was burned in 101 mode using uniflash. The burning files are as follows: 

E:\ti\mmwave_mcuplus_sdk_04_03_00_01\mmwave_mcuplus_sdk_04_03_00_01\tools\awr294x\sbl_qspi.release.tiimage

E:\ti\mmwave_mcuplus_sdk_04_03_00_01\mmwave_mcuplus_sdk_04_03_00_01\ti\demo\awr294x\mmw\awr2944_mmw_demoTDM

3) Connect awr2944 in 100 mode with mmWave_Demo_Visualizer/ver/4.3.0/, it can connect successfully and it can be found there's no problem through the test.

4) Power the board back on and connect mmWave_Demo_Visualizer and DCA1000. Execute the following command from the command prompt C:\ti\mmWave_studio_03_00_00_14\mmWaveStudio\PostProc directory (the corresponding AWR294x_Capture has been copied to this directory):

DCA1000EVM_CLI_Control.exe fpga AWR294x_Capture.json

success

DCA1000EVM_CLI_Control.exe start_record AWR294x_Capture.json

success

5) Returns mmWave_Demo_Visualizer/ver/4.3.0 and load the following directory cfg file in plot:

E:\ti\mmWave_mcuplus_SDK_04_03_00_01\mmWave_mcuplus_SDK_04_03_00_01\ti\demo\awr29 4x\mmw\profiles\tdm_awr2944\profile_LVDS

The case here is once the above process was done, you will still see the various graphs in Visualizer. However, after clicking sensor stop, the bin file is not generated in the corresponding location, and the data_Tran_PRG on the DCA1000 stays on solid and does not blink. The generated awr294x__HDR_LogFile shows that no data was captured (with the same capture start time and capture end time).

So how to capture the raw ADC data?

Could you please help check this case? Thanks.

Best Regards,

Cherry

  • 0
    TI__Mastermind 20605 points

    Hi Cherry,

    Is it possible to obtain the info regarding the capture in the .json file?

    Regards,

    Kaushik

  • 0 in reply to Kaushik Gowda
    TI__Mastermind 22235 points

    Hi Kaushik,

    Thanks for your support.

    Do you mean AWR294x_Capture.json file? If so, please see the following:

    {
    "DCA1000Config": {
    "dataLoggingMode": "multi",
    "dataTransferMode": "LVDSCapture",
    "dataCaptureMode": "ethernetStream",
    "lvdsMode": 2,
    "dataFormatMode": 3,
    "packetDelay_us": 10,
    "ethernetConfig": {
    "DCA1000IPAddress": "192.168.33.180",
    "DCA1000ConfigPort": 4096,
    "DCA1000DataPort": 4098
    },
    "ethernetConfigUpdate": {
    "systemIPAddress": "192.168.33.30",
    "DCA1000IPAddress": "192.168.33.180",
    "DCA1000MACAddress": "12.34.56.78.90.12",
    "DCA1000ConfigPort": 4096,
    "DCA1000DataPort": 4098
    },
    "captureConfig": {
    "fileBasePath": "C:\\ti\\",
    "filePrefix": "awr294x_",
    "maxRecFileSize_MB": 1024,
    "sequenceNumberEnable": 1,
    "captureStopMode": "infinite",
    "bytesToCapture": 4000,
    "durationToCapture_ms": 4000,
    "framesToCapture": 40
    },
    "dataFormatConfig": {
    "MSBToggle": 0,
    "reorderEnable": 1,
    "laneFmtMap": 0,
    "dataPortConfig": [
    {
    "portIdx": 0,
    "dataType": "complex"
    },
    {
    "portIdx": 1,
    "dataType": "complex"
    },
    {
    "portIdx": 2,
    "dataType": "complex"
    },
    {
    "portIdx": 3,
    "dataType": "complex"
    },
    {
    "portIdx": 4,
    "dataType": "complex"
    }
    ]
    }
    }
    }

    Thanks and Regards,

    Cherry

  • 0 in reply to Cherry Zhou
    TI__Mastermind 20605 points

    Hi Cherry,

    I would need some additional info here and would also like for the customer to try a few things on their end.

    • Is the customer using an ES1.0 or ES2.0 EVM?
    • Does the customer observe the DCA1000 transfer LED blink before the sensorStop is issued?
    • Can the customer try to configure the number of frames to 1 in both the json config script and the profile_LVDS.cfg and check the behavior?
    • Is it also possible for the customer to ensure that there is no firewall blocking data transfer over the specified UDP port?

    Regards,

    Kaushik

  • 0 in reply to Kaushik Gowda
    TI__Mastermind 22235 points

    Hi Kaushik,

    The customer use C:\ti\mmWave_mcuplus_SDK_04_02_00_01\mmWave_mcuplus_SDK_04_02_00_01\tools\studio_CLI\mmw_CLI_tool\ MmWave_studio_CLI successfully acquired raw data .bin. 

    The imported cfj file is as follows: 

    % ***************************************************************
    % Created for SDK ver:04.01
    % Created using Visualizer ver:4.1.0.0
    % Frequency:77
    % Platform:AWR294X
    % CFG TYPE: LVDS streaming enabled
    % ***************************************************************
    sensorStop
    flushCfg
    dfeDataOutputMode 1
    channelCfg 15 15 0
    adcCfg 2 0
    adcbufCfg -1 1 1 1 1
    lowPower 0 0
    profileCfg 0 77 186 7 57.14 0 0 70 1 256 5209 0 0 30
    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 4
    chirpCfg 2 2 0 0 0 0 0 8
    chirpCfg 3 3 0 0 0 0 0 2
    frameCfg 0 3 16 60 256 100 1 0
    lowPower 0 0
    guiMonitor -1 1 1 0 0 0 1
    cfarCfg -1 0 2 8 4 3 0 15 1
    cfarCfg -1 1 0 4 2 3 1 15 1
    multiObjBeamForming -1 1 0.5
    calibDcRangeSig -1 0 -5 8 256
    clutterRemoval -1 0
    compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
    measureRangeBiasAndRxChanPhase 0 1.5 0.2
    aoaFovCfg -1 -90 90 -90 90
    cfarFovCfg -1 0 0 8.92
    cfarFovCfg -1 1 -1 1.00
    extendedMaxVelocity -1 0
    calibData 0 0 0
    CQRxSatMonitor 0 3 11 121 0
    CQSigImgMonitor 0 127 8
    analogMonitor 0 0
    lvdsStreamCfg -1 0 1 0
    sensorStart

    1) By modifying channelCfg, is the radar configured to a 4-transmit/4-receive state? As configured above, 60 frames get a 7.50MB-size .bin file, is this data correct?

    2) Is there an existing program to parse the raw.bin file generated by the awr2944EVM?

    Thanks and Regards,

    Cherry

  • 0 in reply to Cherry Zhou
    TI__Mastermind 20605 points

    Hi Cherry,

    Good to hear that the customer has been able to progress. Please find my responses below:

    1) By modifying channelCfg, is the radar configured to a 4-transmit/4-receive state? As configured above, 60 frames get a 7.50MB-size .bin file, is this data correct? Yes, this is correct. (2 * 256 * 4 * 4 * 16 * 60 bytes)

    2) Is there an existing program to parse the raw.bin file generated by the awr2944EV? -> Unfortunately, we do not have a program as such at the moment. But it is quite simple to do so using reference for other devices. Would suggest the customer try the same on their end.

    Regards,

    Kaushik

  • 0 in reply to Kaushik Gowda
    TI__Mastermind 22235 points

    Hi Kaushik,

    The bin file currently collected by the 2944 only supports real mode, that is, is it real mode instead of complex mode? 

    Is the number of chrips per frame set by the third bit number of loops of frameCfg 0 3 16 60 256 100 1 0? 

    Thanks and Regards,

    Cherry

  • 0 in reply to Cherry Zhou
    TI__Mastermind 20605 points

    Hi Cherry,

    The bin file currently collected by the 2944 only supports real mode, that is, is it real mode instead of complex mode? -> Yes, there is only real mode supported in 2944.

    Is the number of chrips per frame set by the third bit number of loops of frameCfg 0 3 16 60 256 100 1 0?  -> This refers to the total number of times each of your chirps will be looped (indexed from 0-511)

    Regards,

    Kaushik