• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 265 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Compiler/AWR1642BOOST: Configuration not compiling due to unforeseen chirp requirements?

George Denove
Expert 1435 points
Part Number: AWR1642BOOST
Other Parts Discussed in Thread: AWR1642

Tool/software: TI C/C++ Compiler

Hi,

I posted something similar in the sensor forum, but I now realize this may be more of a code forum question rather than a sensor forum question. Please see below:

While I understand that the DCA1000 collects the raw ADC data, I think there is something special about how many chirps (or cycles of chirps * # of chirps) described in the CLI Script under subframeCfg that the AWR is looking for. When I tried the "wrong" script below on the online demoVisualizer, I remember getting an error in regards to DSS_main.c, line 2021. The working one worked.

I state the above because the attached working CLI script (that transmits 16 chirps per subframe) works when I run it on the AWR1642, but the CLI Script that transmits anything other than 16 (or a multiple of that) does not load correctly. I am trying to figure out why.

Where do you think this hang up could be occurring? I was thinking somewhere in the DSS that requires a certain amount of chirps (for the velocity calculation), but I am not sure.

Working CLI Script:

Fullscreen MIMO_multistatic_device2_sdk20_ver3.txt Download 
sensorStop
flushCfg
dfeDataOutputMode 3
channelCfg 15 1 0
adcCfg 2 1
adcbufCfg -1 0 0 1 0
profileCfg 0 77 7 7 160 0 0 20 1 512 6200 0 0 30
profileCfg 1 77 7 7 160 0 32 20 1 512 6200 0 0 30
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 1
chirpCfg 2 2 1 0 0 0 0 1
chirpCfg 3 3 1 0 0 0 0 1
bpmCfg -1 0 0 1
advFrameCfg 4 0 80 1 0
subFrameCfg 0 0 0 1 16 50 0 1 1 50
subFrameCfg 1 0 1 1 16 50 0 1 1 50
subFrameCfg 2 0 2 1 16 50 0 1 1 50
subFrameCfg 3 0 3 1 16 50 0 1 1 50
lowPower 0 1
guiMonitor -1 1 1 1 0 0 1
cfarCfg -1 0 0 8 4 4 0 2560
cfarCfg -1 1 0 4 2 3 0 2560
peakGrouping -1 1 1 1 1 255
multiObjBeamForming -1 1 0.5
calibDcRangeSig -1 0 -5 8 256
extendedMaxVelocity -1 0
clutterRemoval -1 0
compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
measureRangeBiasAndRxChanPhase 0 1.5 0.2
nearFieldCfg -1 0 0 0
CQRxSatMonitor 0 3 5 123 0
CQSigImgMonitor 0 127 4
analogMonitor 0 0
lvdsStreamCfg -1 0 1 0
sensorStart

 

Not working CLI Script:

(Everything is the same except that there is now 15 chirps rather than 16. Ideally, I would like it to only work with one chirp and collect that raw ADC data).

Fullscreen MIMO_multistatic_device2_sdk20_ver4.txt Download 
sensorStop
flushCfg
dfeDataOutputMode 3
channelCfg 15 1 0
adcCfg 2 1
adcbufCfg -1 0 0 1 0
profileCfg 0 77 7 7 160 0 0 20 1 512 6200 0 0 30
profileCfg 1 77 7 7 160 0 32 20 1 512 6200 0 0 30
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 1
chirpCfg 2 2 1 0 0 0 0 1
chirpCfg 3 3 1 0 0 0 0 1
bpmCfg -1 0 0 1
advFrameCfg 4 0 80 1 0
subFrameCfg 0 0 0 1 15 50 0 1 1 50
subFrameCfg 1 0 1 1 15 50 0 1 1 50
subFrameCfg 2 0 2 1 15 50 0 1 1 50
subFrameCfg 3 0 3 1 15 50 0 1 1 50
lowPower 0 1
guiMonitor -1 1 1 1 0 0 1
cfarCfg -1 0 0 8 4 4 0 2560
cfarCfg -1 1 0 4 2 3 0 2560
peakGrouping -1 1 1 1 1 255
multiObjBeamForming -1 1 0.5
calibDcRangeSig -1 0 -5 8 256
extendedMaxVelocity -1 0
clutterRemoval -1 0
compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
measureRangeBiasAndRxChanPhase 0 1.5 0.2
nearFieldCfg -1 0 0 0
CQRxSatMonitor 0 3 5 123 0
CQSigImgMonitor 0 127 4
analogMonitor 0 0
lvdsStreamCfg -1 0 1 0
sensorStart

Thank you!

George

  • 0
    TI__Guru 69960 points

    Hello George,

    Do you want to capture only raw data or your intention is to let AWR1642 do the processing as well?

    In case you want to just capture the raw ADC data from AWR1642 then better to use mmWave Studio to capture the data.

    Although mmw demo provides an option to stream adc data over LVDS but meanwhile it does the processing also. Thus configuration you provide depends on processing algo as well that why you are getting error from dss_main.c.

    Please provide the exact SDK version and the code snippet (if you modified dss_main.c) when it hits the error with non-working configuration.

     

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    Expert 1435 points

    Hi Jitendra,

    Yes, I only want to collect raw ADC data with no AWR1642 processing. 

    How do I change my configuration to not depend on the processing algorithms? 

    And I figured out where in DSS_main the above  CLI script does not work. It is because you require a number of chirps that is multiple of 2, 4, 8, etc. 

    Therefore, I have commented these sections out. 

    Now I am having trouble figuring out how to just transmit 1 chirp per subframe. As seen in this forum:

    Any advice on how to do this would be greatly appreciated. Can I just transmit one per subframe in the mmWave Studio? If so, can I load that image on to the AWR1642. The user guide for mmWave studio solely talks about the GUI and I need to flash it on the AWR since they will be remote.

    Thank you!

  • 0 in reply to George Denove
    Expert 1435 points

    I figured out a work around, thank you!