• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 30 subscribers
  • Views 442 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.

Original question:

RTOS/AWR1642BOOST: HW Trigger Configuration Issue

RTOS/AWR1642BOOST: HW Trigger Configuration Issue

Samuel Miller99
Expert 1005 points
Part Number: AWR1642BOOST

Tool/software: TI-RTOS

Reposting for clarity. Still confused on this issue.

Jitendra,

I apologize for the continued problem, but I am still not getting results that I would expect for the HW trigger on the AWR1642BOOST ES2.0. I resorted to the demo visualizer for the ease of viewing changes. Here is the configuration script I would load each time:

sensorStop

flushCfg

dfeDataOutputMode 1

channelCfg 15 3 0

adcCfg 2 1

adcbufCfg -1 0 0 1 0

profileCfg 0 77 429 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 2

frameCfg 0 1 16 0 100 2 0

lowPower 0 1

guiMonitor -1 1 1 0 0 0 1

cfarCfg -1 0 0 8 4 4 0 5120

cfarCfg -1 1 0 4 2 3 0 5120

peakGrouping -1 1 1 1 1 255

multiObjBeamForming -1 1 0.5

clutterRemoval -1 0

calibDcRangeSig -1 0 -5 8 256

extendedMaxVelocity -1 0

bpmCfg -1 0 0 1

lvdsStreamCfg -1 0 0 0

nearFieldCfg -1 0 0 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

CQRxSatMonitor 0 3 5 123 0

CQSigImgMonitor 0 127 4

analogMonitor 1 1

sensorStart

After the sensorStart command, I provided a continuous waveform to the J6-[9] SYNC_IN pin that has an high period of 6ms (active frame is ~8ms) and has a low period of 94ms (adding together to equal the 100ms frame periodicity). Still, there was no observable changes in the mmWave demo visualizer output graphs. I am not sure what I am doing wrong.  Below is the verified waveform and pin connections. I appreciate your help!

  • 0
    TI__Guru*** 141504 points
    Hi

    Will get back to you rarly next week.

    Thank you
    Cesar
  • 0 in reply to Cesar
    TI__Guru*** 141504 points
    Hi,

    Based on mmWave SDK UG, the hardware trigger option is not supported in the SDK oob demo.

    Did you modify the code to support it?

    Thank you
    Cesar
  • 0 in reply to Cesar
    Expert 1005 points
    My apologies, I meant to say that I tried the hardware trigger with the capture demo v1.1, not the oob demo. I don't recall reading that the HW trigger is not supported in the capture demo, but maybe I'm wrong? If so, you mentioned 'changing the code', do you mean rewriting the C files that comprise the oob demo? Thanks for the help.
  • 0 in reply to Samuel Miller99
    TI__Guru*** 141504 points

    If you are using the capture demo, hw triggering should be supported. Please note that the SDK 1.1 which includes capture demo is not a lts release and only limited support is provided for the capture demo.

    Regarding the SYNC_IN signal please note that the SYNC_IN pulse periodicity should be >= (programmed frame periodicity + trigger delay). Below is the figure showing the timing .