AM2632: GPIO Interrupt and related GPIO INT XBAR configuration

MCAL Version : MCAL_AM263X_10.00.00

Hi
We did the configurations in Configurator as below 

in MCU XBar part-  is GPIO Input Xbar and Xbar Output Map right values as I see in Datasheet for A17.

Hi Nidhi,

The below e2e should guide you in this. Though the below one is for syscfg, the identification on GPIO Xbar instance and output is explained here

(3) AM2632: GPIO interrupt - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums

Could you please check this and let me know if you have any further query?

Regards,

Nikhil

Hi Nikhil,

Thanks for sharing the material link and explanation.

With Sysconfig the configurations are tried for GPIO Bank Interrupt as suggested in Forum by Nikhil and its working.

But w.r.t. Using Davinci configurator we would like get support for the same to make it work.

  -We tried similar configuration in Vector Davinci configurator. Also added OsIsr configuration in OS module.

  -We can see the DIO pin value is getting updated but interrupt callback is never getting called.

  -So we would like to understand the dependency when we are shifting the configuration from SysConfig to Vector Da-vinci configurator.

Gunjan, Mudit and Nikhil,

Thanks for the reply on the Forum with links & descriptions. But still the customer needs some additional support on this topic.

 With Sysconfig the configurations are tried for GPIO Bank Interrupt as suggested in Forum by Nikhil above and it's working...

But w.r.t. Using Davinci configurator they would like get support for the same to make it work.

  -They have tried similar configuration in Vector Davinci configurator. Also added OsIsr configuration in OS module.

  -They can see the DIO pin value is getting updated but interrupt callback is never getting called.

  -So they would like to understand the dependency when they are shifting the configuration from SysConfig to Vector Da-vinci configurator.

Following are the configurations in Vector Davinci configuration (for Xbar output and instance, as per corresponding GPIO114 pin)

 MCU module : McuGpioXbarIntrConfiguration

Port Module : PortDioConfig

Thanks,

Chris

Hi 
Any update on this topic please?

It's bit urgent for our project to test few functionalities.

Thanks!

Hi Nidhi,

Sorry for the delay in response.

The MCAL offering from TI is tested on EB Tresos tool, and the configuration on the Vector Davinci configurator is out of the scope of TI's support.

That being said, I am checking internally regarding this in order to find if we could get any reference to the Davinci configurator. 

I see that we have reference documentation for few modules in the MCAL userguide as shown below, 

7. AUTOSAR Integration Guide — Documentation for AM263x

Here we have reference for xbar configuration of ADC and additional ISR configuration for the same below

7. AUTOSAR Integration Guide — Documentation for AM263x 

Can you compare this with your configuration?

Few questions from my end

1. 

Chris Yorkey said:

They can see the DIO pin value is getting updated but interrupt callback is never getting called.

By this do you mean that the ISR is getting called but the interrupt callback registered in the tool is not called?

2. 

Chris Yorkey said:

Also added OsIsr configuration in OS module.

Can you share the screenshot for the same?

Thanks and Regards,

Nikhil Dasan

Hi Nikhil,

Thanks for your continuous support.

Please find below comments for the questions.
1. By this do you mean that the ISR is getting called but the interrupt callback registered in the tool is not called?
Ans : ISR itself not getting called, so the interrupt callback also not getting called.

2. Can you share the screenshot for the same?
Ans : find the OsIsr configuration of OS module.

Can you check the below 2 points at your end?

1. You have selected "Isr Initial Enable interrupt sources" in the above config. I believe this generates an API Os_InitialEnableInterruptSources() which would have to be called at your end in code after the OS starts and before any interrupt occurs. Can you check if you have done the same?

2. If yes, you have mentioned Category_2 as ISR category here. Can you confirm if you have configured the same in the module tab as well?

3. Please confirm if 142 is the correct source number.

Thanks and Regards,

Nikhil Dasan

Checked for the mentioned points.
1. Os_InitialEnableInterruptSources() getting called.
2. In port module selected the type of Interrupt function as CAT2 ISR. 
Is there additional setting required at any other module level?

3. For source number 142, referred the TI Technical reference manual (and also checked with example code present in sdk).

For A17/GPIO114, selected bank-7 and VIM0_0 for GpioXbarIntrCfg

Nidhi Adk said:

Is there additional setting required at any other module level?

For eg, in EB Tresos tool, in ADC module, there is additional config as shown below as highlighted. Is the same present in the module tab on Davinci Configurator?

Nidhi Adk said:

1. Os_InitialEnableInterruptSources() getting called

Where is this being called in the code?

1. For eg, in EB Tresos tool, in ADC module, there is additional config as shown below as highlighted. Is the same present in the module tab on Davinci Configurator?

Yes, similar parameter is present for ADC module and this is also CAT2 in our configuration. 
For DIO module there is no such parameter present.
For Port module its set to CAT2.

2. Where is this being called in the code?
This is getting called after OsStart and during initialization while enabling the interrupt. (Just for reference, Other ISR's for ADC are working fine).

As per the SDK example, using sysconfig i understand that to make GPIO pin as interrupt based modules like 'GPIO - for pin configurations' and 'GPIO INT XBAR - for XBAR output and instance' configurations are required. Similar configurations we did on Davinci configurator along with OsISR. But its not yet working.
Could you please check and confirm for TI AM2632, to make GPIO pin as interrupt based what n all configurations required in MCU (specifically for 'McuGpioXbarIntrConfiguration', 'McuInputXbarChannelTriggerConfiguration' and 'McuXbarChannelTriggerConfiguration' containers), Port and DIO module in Davinci configurator.

From MCU module, do we have to configure 'McuInputXbarChannelTriggerConfiguration' and  'McuXbarChannelTriggerConfiguration' containers as well? If yes, for GPIO PIN 114 what value to be selected?

(Also if you have example for the GPIO pin as interrupt based in EbTresos with MCU, Port, DIO and OS configuration that would also help to analyze.)