• State Resolved
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 6 replies
  • Subscribers 32 subscribers
  • Views 502 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.

IWRL6432: GPIO Pin Keeps Interrupting - SDK 5.4 (ES2.0)

Alperen Halal
Prodigy 30 points
Part Number: IWRL6432

We are testing our custom PCB’s with latest SDK (MMWAVE_L_SDK_05_04_00_01) and CCS (Version: 12.5.0.00007) right now.

We have problem with GPIO interrupts. We were reading a signal with GPIO interrupt on dev kit (IWRL6432BOOST) without any problem and our algorithm was working without any problems.

When we first tried to test our PCBs with the code from dev kit we encounter some problems. We were able to upload our code to the flash, but it was not running.

Later we find out that dev kit has ES1.0 silicon and the new IC’s were ES2.0.

Therefore, we updated our SDK version from 5.3 to 5.4 and tested the demo (motion and presence detection) and it is working fine.

 

Then, we started to transfer the algorithm to SDK 5.4, but we are encountering some problems.

When radar part of the demo (motion and presence detection) starts, GPIO interrupt occurs continuously, even though the line is stable and always high. So we cannot use GPIO interrupt to read the signal.

Later we tried gpio interrupt example (from SDK 5.4 examples folder) to check if we have any problems on the PCB/hardware but it is working without any problems alone.

Is there anyone encountered such problem and have the solution? Thanks in advance.

*Algorithm:

-Sending semaphore from GPIO ISR (trigger type: both edges)

-Taking semaphore on a task and saving GPIO pin state and current ticks value.

  • 0
    TI__Mastermind 23177 points

    Hello,

    We will get back to you next week, apologies for the delay.

    Best Regards,

    Pedrhom

  • 0 in reply to Pedrhom Nafisi
    Prodigy 20 points

    Hello Mr. Nafisi,

    Is there any update?

  • 0
    TI__Mastermind 21071 points

    Hello, 

    Sorry about the delayed response here. I first just want to make sure I understand the issue. Is it correct that the GPIO interrupt example from the driver examples is working as expected but when adding the GPIO interrupt functionality to the presence and motion detection example, you are seeing issues for both the TI EVM and your custom design? 

    Best Regards,

    Josh

  • 0 in reply to Josh Dye
    Prodigy 30 points

    Hello,

    Your understanding is correct about GPIO interrupt functionality, it does not work with the detection example.

    - TI EVM have early silicon ES1.0 version (791).

    - Custom design have ES2.0 version (791B).

    SDK_5.03 > examples > mmw_demo: these examples only works with TI EVM (ES1.0)

    SDK_5.04 > examples > mmw_demo: these examples only works with Custom Design (ES2.0)

    I tried "SDK_5.04 > examples > drivers > gpio > gpio_led_blink" on TI EVM. It is working fine, but the mmw_demo examples are still not working from newest SDK_5.04 on old silicon ES1.0.

    This case is also true for SDK_5.03 mmw_demo examples, they are not working on the new silicon ES2.0.

    With SDK_5.03 mmw_demo examples, I had no such problem on TI EVM. The examples works fine with the additional GPIO interrupt functionality.

    TI EVM:

    On TI EVM, using pin B12 "DCA_LP_SPI_MOSI" to capture interrupt.

    This pin is directly connected from IC to header.

    Thanks and best regards.

  • 0 in reply to Alperen Halal
    TI__Mastermind 21071 points

    Hi,

    Thank you for the confirmation and further explanation. We are still looking into this issue. Will try to provide an update in the next couple of days. Thank you for your patience.

    Best Regards,

    Josh

  • 0
    Prodigy 30 points

    Hello,

    We solved this issue with Mr. Peake.

    Thank you all for your support.

    Solution if anyone facing the same issue.

    From the source code of motion and presence demo:

    1- Commented all the stuff about LED toggle.

    2- Disabled low power mode ("lowPowerCfg 0").

    3- Quick Eval/Start is used.

    Not sure which of the above solved the issue exactly, but we have no problem right now.