3 Replies Latest reply on Nov 11, 2019 2:41 AM by DheerajP_41

CYW20819/ timeout_ms value in "wiced_rtos_wait_for_event_flags"

YoTa_1693656 Oct 27, 2019 9:25 PM

Hello Cypress IoT team

We evaluate CYW20819 with ModusToolBox for their next products. Let us confirm about timeout_ms in "wiced_rtos_wait_for_event_flags".

wiced_result_t wiced_rtos_wait_for_event_flags ( wiced_event_flags_t * event_flags,

uint32_t flags_to_wait_for,

uint32_t * flags_set,

wiced_bool_t clear_set_flags,

wiced_event_flags_wait_option_t wait_option,

uint32_t timeout_ms

)

・・・

[in] timeout_ms milliseconds to block

[Question]

According to the above description, the unit of timeout_ms is msec.

However, under our evaluation, the unit looks like 10 msec actually. Is it expected behavior?

==example==

timeout_ms = 50

The timeout seems to occur per 500 msec actually. (Not 50msec.)

===========

Thanks,

Yoshinori

1. Re: CYW20819/ timeout_ms value in "wiced_rtos_wait_for_event_flags"

DheerajP_41 Oct 29, 2019 2:56 AM (in response to YoTa_1693656)

Hi Yoshinori Takano,

It seems to be msec only. Not 10msec.
How did you evaluate it? Could you please share your code with me, so that I can take a look at it.

Thanks,
-Dheeraj
Like Show 0 Likes(0)

Actions
2. Re: CYW20819/ timeout_ms value in "wiced_rtos_wait_for_event_flags"

YoTa_1693656 Nov 4, 2019 8:45 PM (in response to DheerajP_41)
Hello Dheeraj-san

We tried to evaluate it with an attachment source code. The timeout value sets 50 msec, we expected that LED1 blinked per 50 mesc. But actual behavior looks like 500 msec. It was observed by oscilloscope.
====
static void threadFunctionBlinkLed(uint32_t arg ){
int count = 1;
for(;;){
uint32_t flagSet;
wiced_rtos_wait_for_event_flags(eventHandleBlinkLed, 1, &flagSet, WICED_TRUE, WAIT_FOR_ANY_EVENT, 50);

count ^= 1;
wiced_hal_gpio_set_pin_output(WICED_GET_PIN_FOR_LED(1), count);
}
}
====

Thanks,
Yoshinori

hal_gpio.c.zip 3.2 K
Like Show 0 Likes(0)

Actions
3. Re: CYW20819/ timeout_ms value in "wiced_rtos_wait_for_event_flags"

DheerajP_41 Nov 11, 2019 2:41 AM (in response to YoTa_1693656)

Hi Yoshinori Takano ,

I could reproduce similar issue at my side regarding the msec timeout. I believe, the issue is with the API which is not accurately setting the timeout. You can workaround by factoring it down to an appropriate value.

We will communicate the issue with our software team and will be fixing it in the future software releases.

Thanks,
-Dheeraj
1 of 1 people found this helpful
Like Show 1 Likes(1)

Actions

Go to original post