• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 6059 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.

[FAQ] DCA1000EVM: DCA1000EVM Debug Resources

Cesar
Guru*** 140784 points
Part Number: DCA1000EVM
Other Parts Discussed in Thread: AWR2243BOOST

Attached document provides debug tips for DCA1000 data capture related issues.

1588.DCA1000 Debugging Handbook.pdf.

Here are other relevant FAQ for DCA1000EVM

ADC Data Capture files size larger than 1 GB

 https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/795067/faq-dca1000evm-adc-data-capture-files-size-larger-than-1-gb 

Two AWR2243Boost+DCA1000EVM on same host PC

 https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/936165/faq-awr2243boost-two-awr2243boost-dca1000evm-on-same-host-pc

Synchronizing multiple DCA1000 boards

  https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/902017/faq-dca1000evm-synchronizing-multiple-dca1000-boards
  • 0
    TI__Guru 50240 points

    Hi Cesar,

    This is a useful resource, thank you for posting this!

    Cheers,

    Akash

  • 0
    TI__Guru 69330 points

    Attention everyone:

    DCA1000EVM streams out few chirp data with zero filling:
    We have identified an issue with DCA1000EVM where a few chirp ADC data of frames captured via DCA1000 may contain all zeros, leading to unexpected results during ADC data post-processing. This issue arises from DCA1000EVM inability to convert data from LVDS to Ethernet interface for some chirps, resulting in specific chirps' data streams being filled with zeros. This issue impacts to random chirps across frame capture. This issue is only due to DCA1000EVM while it captures and converts data from LVDS to Ethernet interface. mmWave Sensor sends ADC data correctly over LVDS interface.
    Rate of occurrence of zero chirp data captured is high if chirp duration is short, where chirp to chirp short duration requires faster streaming data rate over LVDS. And later this faster data rate causes faster LVDS to Ethernet conversion at DCA1000EVM FPGA.
    chirp to chirp data generation rate depends on noOfSample and chirp duration. Occurrence of this issue is more when higher noOfSample and shorter chirp duration are used in the RF-front configuration.
    Workaround:
    Capture for multiple frames for specific scenario and during the post-processing, drop that frame data having zero ADC chirp data and rely on next frame data for post-processing. 
    OR 
    user lower noOfSample and longer chirp duration in the RF-Front configuration. 
    These parameters are set in the rlSetProfileConfig API. -   rlProfileCfg_t -> numAdcSamples, rlProfileCfg_t ->  idleTimeConst+ rampEndTime (total chirp duration)
    DCA1000EVM working flow:
    DCA1000EVM receives the ADC data from mmwave sensor via LVDS interface line that is later transmit over Ethernet to PC. DCA1000 has on board FPGA which converts data format from LVDS to Ethernet interface. Faster arrival of data to LVDS interface requires FPGA to convert LVDS->Ethernet faster.