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.

IWR6843ISK-ODS: DCA1000 CLI utility hangs at the end of raw capture (Linux)

Part Number: IWR6843ISK-ODS
Other Parts Discussed in Thread: DCA1000EVM, IWR6843

Hello TI team,

I am currently using the DCA1000 CLI app in order to capture raw data files on Linux. I followed the instruction from mmwaveSDK guide regarding the LVDS streaming settings, and it all works fine and I am able to obtain the bin files with my setup. However, at the very end the DCA1000EVM_CLI_Record application seems to hang and I have to shut it manually (even after waiting for a while):

Start Record command : Success

Record is completed
^Cmake: *** [Makefile:20: record] Interrupt

After the text "Record is completed" I can clearly see the recording LED is still blinking on the DCA1000, which looks like it expects some command to be sent, but it was probably never sent. 

And then if I want to capture more raw data, I get an error about the interface being taken by another process, and the utility cannot even talk to FPGA:

Stop the already running process

And then I have to power cycle, sometimes couple times in order to get rid of the error.

Do you have any ideas what could it be? Is there some command missing that I could add to the main() function?

Also, is there some reference I could refer to regarding the commands for DCA1000 interface, where would it be located?

Thank you.

Best regards,

Victoria

 

  • HI, Victoria:

    Usually there are two methods to stop the capture,

    1) Send the command stop_record command to stop the capture

    DCA1000EVM_CLI_Control.exe stop_record xxx.json

    in this case, usually you will program "captureStopMode" to be "infinite" in your json file

    2) Let the capture end by itself. In this case, usually you will program "captureStopMode" to be "bytes" in your json file

    Let me know whether it helps,

    Zigang

     

  • Hello Zigang,

    I capture based on the duration, for example:

    "captureConfig": {
    "fileBasePath": ".",
    "filePrefix": "iwr6843_capture",
    "maxRecFileSize_MB": 1024,
    "sequenceNumberEnable": 1,
    "captureStopMode": "duration",
    "bytesToCapture": 1025,
    "durationToCapture_ms": 5000,
    "framesToCapture":5
    },

    And indeed my bin file length corresponds to the 5 seconds duration for the chirp config I use. And I can see there are exactly 5 seconds between the text "Start Record" and "Record is completed". It's just it does not seem to end gracefully when the capture is done.

    When the DCA1000 is put into this state, I cannot force it to end the capture with the stop_record as per your suggestion, because it requires I stop the already running process.

    Also, the power-cycle does not always help, and I am not sure how to properly reset my DCA1000 once it's in this state. Often, I power cycle, and get either:

    • Record stopping is initiated. [status -4032] - for query_status
    • Stop the already running process. - for fpga_version

    Any ideas what could it be? Is there any way I can reset DCA1000 manually so that it would not be in the error state?

    Thank you.

    Best regards,

    Victoria

  • Victoria:

    From my personal experience, only the "infinite" and "byte" mode works.

    Best,

    Zigang

  • Zigang, I will try those two suggestions and let you know if it works better. 

    Meanwhile, any idea how to reset DCA1000 from the "Stop the already running process"? The power cycle does not seem to help anymore, and I am not sure how to try to use the DCA1000 for raw captures when it is in this state.

  • Hey Zigang,

    Just thought to let you know I am able to reset the DCA1000 with the fpga_reset command, so it's OK now.

    Also when I tried to use "infinite" mode, it still hangs and I am unable to stop the recording, so I have to manually interrupt. At this point I do not mind, as long as I can reset the FPGA successfully, it is working for me.

    Thank you for your suggestions.

    Regards,

    Victoria