Hi,

I am using a complex gpio as a timer. Before the new release version I used CY_U3P_GPIO_INTR_TIMER_ZERO and it worked as it was supposed to be. With the new release I had to change some configuration of the complex pin. Now I am using CY_U3P_GPIO_INTR_TIMER_THRES and set the values see below.

The release notes of the 1.0 does not say anything about changes at the complex GPIO!

#if OLD_BETA_SDK_FX3
    g_GpioComplexConfig[u8GpioTimerId].intrMode    = CY_U3P_GPIO_INTR_TIMER_ZERO;
    g_GpioComplexConfig[u8GpioTimerId].timerMode   = CY_U3P_GPIO_TIMER_HIGH_FREQ;
    g_GpioComplexConfig[u8GpioTimerId].period      = u32Timer;
#else // NEW_RELEASE
    g_GpioComplexConfig[u8GpioTimerId].intrMode    = CY_U3P_GPIO_INTR_TIMER_THRES;
    g_GpioComplexConfig[u8GpioTimerId].timerMode   = CY_U3P_GPIO_TIMER_HIGH_FREQ;
    g_GpioComplexConfig[u8GpioTimerId].timer       = u32Timer;
    g_GpioComplexConfig[u8GpioTimerId].period      = u32Timer;
    g_GpioComplexConfig[u8GpioTimerId].threshold   = u32Timer;
#endif
 

Which values should be used if I like to have a function to start and stop a timer? The start occurs in application code and the stop occurs in the GPIO interrupt handler.

Thanks

lumpi

Hi,

From which version of Beta to release are you migrating?

Some changes were made from Beta-1 to Beta-2 and are documented in the release notes can you please take a look at it.

Regards,

Anand

Hi Anand,

thanks for your reply, I migrated from the last version BETA 4 to the new Release version.

Because of this I wonder because there were no changes described in the release notes between these versions.

Thanks

Lumpi

Hi Lumpi,

There is no change in the SetComplexConfig API since Beta 2 with this regard. But all input parameters must be initialized. Uninitialized variables can bring in undefined behaviour. Since in the given case, the interrupt generation is based on = CY_U3P_GPIO_INTR_TIMER_THRES the values to be used for initialization for a simple timer is

    g_GpioComplexConfig[u8GpioTimerId].outValue = CyFalse;

    g_GpioComplexConfig[u8GpioTimerId].driveLowEn = CyFalse;

    g_GpioComplexConfig[u8GpioTimerId].driveHighEn = CyFalse;

    g_GpioComplexConfig[u8GpioTimerId].inputEn = CyFalse;

    g_GpioComplexConfig[u8GpioTimerId]. CY_U3P_GPIO_MODE_STATIC;

    g_GpioComplexConfig[u8GpioTimerId].intrMode    = CY_U3P_GPIO_INTR_TIMER_THRES;

    g_GpioComplexConfig[u8GpioTimerId].timerMode   = CY_U3P_GPIO_TIMER_HIGH_FREQ;

    g_GpioComplexConfig[u8GpioTimerId].timer       = 0;

    g_GpioComplexConfig[u8GpioTimerId].period      = u32Timer;

    g_GpioComplexConfig[u8GpioTimerId].threshold   = u32Timer;

CY_U3P_GPIO_INTR_TIMER_THRES based interrupt happens when timer value crosses threshold value. The period value determines when the timer count will be reset to zero. The reset to zero will happen only when the timer values crosses the period value or when it increments over 0xFFFFFFFF. So interrupt will not happen if the threshold is greater than period. Please try this and let me know.

Thanks,

Anand

Hi Anand,

it works fine as you described in the last post.

I already had set up the complex gpio as you described there. Just one change that I had load the u32timer value also into g_GpioComplexConfig[u8GpioTimerId].timer. Now I load this value with 0 as you described and the behaviour is the same.

I think there is now everything fine disregarding the fact, that I really had to do changes as I changed to release version from BETA4.

Thank you very much, regards.

Lumpi