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.

TDA4VH-Q1: GPIO pin external interrupt triggered problem

Part Number: TDA4VH-Q1

To develop GPIO pin external interrupts on the TDA4VH platform, the SDK_RTOS version is 09_00_01_01.

The pins used are WKUP_GPIO0_18 and GPIO0_18 respectively, and the path of the demo program used in SDK_RTOS is: sdk_rtos/pdk_j784s4_09_00_01_04/packages/ti/drv/gpio/test/led_blink/

When WKUP_GPIO0_18 is used, the interrupt can be triggered normally.

When GPIO0_18 is used, the interrupt cannot be triggered, and the Sciclient_rmIrqTranslateIrOutput function returns an exception, retVal=-2, when the route is interrupted.

Description The output resource of J784S4_DEV_GPIOMUX_INTRTR0 does not support mcu1_0 after description in J784S4 Interrupt Management Device Descriptions.

So I run this demo on mcu2_0, because the output resource of J784S4_DEV_GPIOMUX_INTRTR0 can support mcu2_0, modify the interrupt GPIO to GPIO0_18, still the interrupt can not trigger, The Sciclient_rmIrqTranslateIrOutput function returned an abnormal value when interrupting the route, retVal=-2.

How can the demo program trigger the interrupt of GPIO0_18?