• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 31 subscribers
  • Views 949 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.

AWR1243: How can I change from S/W triggering to H/W triggering on Radar SDK

Kensuke
Expert 1140 points
Part Number: AWR1243

I'm using Radar-SDK on AWWR1243 + TDA3.

I would like to change the triggering way from SW API based triggering to HW SYNC_IN based triggering.

I know that rlSetAdvFrameConfig.triggerSelect is a parameter of the mode for triggering.

But I'm not sure how to create HW triggering in TDA3.

How do I change/implement the SDK to generate a HW trigger?

If you have any ideas or examples, please let me know.

thank you

  • 0
    TI__Guru*** 149204 points
    Hi,

    We have referred your question to the Radar SDK team

    thank you
    Cesar
  • 0 in reply to Cesar
    TI__Mastermind 24955 points
    Here is a list of actions to take to switch to HW triggering:

    - Find pin on TDA3 schematic that is connected to AWR12 HW SYNC_IN pin

    In TDA3 SW:

    1. Configure the pinmux register to set the pin as GPIO and enable output to SYNC_IN
    2. In GPIO configuration, enable output of the above GPIO line
    3. To change the level of GPIO line, program the GPIO register to set it to 0 or 1
    4. Tie in the GPIO toggling to radar frame start call
    5. Have a timer-based periodic task to start radar frame by toggling GPIO line
    6. Configure AWR12 to HW trigger mode

    Let us know if you have any questions.

    Regards,
    Kyle
  • 0 in reply to Kyle Cousino
    Expert 1140 points
    Thank you for the reply.
    I'm debugging now, but I understood the general procedure.
  • 0 in reply to Kyle Cousino
    Expert 1140 points
    Hi Kyle,

    Does HW triggering start chirp transmission with GPIO toggle? i.e. change GPIO line from 0 to 1, or from 1 to 0
    I'm concerned about whether it is necessary to return to the opposite state after making GPIO line High or Low.
    If so, how long should I keep GPIO status high or low?

    thank you
  • 0 in reply to Kensuke
    TI__Mastermind 24955 points
    I have provided some information on the questions you asked in your previous post.

    I would first suggest looking at the AWR1xxx Radar Interface Control Document. This document is included in our online DFP release. I have posted the link below:

    www.ti.com/.../MMWAVE-DFP

    Specifically, take a look at the HWTRIGGER section.

    To set AWR1243 for external hardware triggering, you will need to make the following changes.

    rlFrameCfg_t.triggerSelect = 0x0002 /* HWTRIGGER */

    This is listed under the rlSetFrameConfig API for our mmWaveLink. The change above will implement the configuration you are looking for.

    Now once you have configured the AWR1243 for external hardware trigger and called "rlSensorStart," the AWR1243 will wait for a pulse on SYNC_IN pin (P4). You would want to make sure you connect the SYNC_IN pin (P4) to the corresponding GPIO pin on the TDA3x device you are planning on using. Only after a pulse has been detected on SYNC_IN will frame transmission being.

    Keep in mind that the periodicity of these pulses should match the following frame parameter: rlFrameCfg_t.framePeriodicity

    If the GPIO pulse is generated earlier than the periodicity of the frames, the GPIO toggle would effectively be ignored and the corresponding chirps will not happen.

    One last quick note, for the AWR1243, the SYNC_IN is always enabled by default. If the HW_Trigger option is selected in the frame config then the device will look for a pulse on this pin to start the frame transmission. Otherwise, SW triggering will selected.

    Regards,
    Kyle
  • 0 in reply to Kyle Cousino
    Expert 1140 points
    Thank you for your great support.
    I got it.