CC3220: Is there any issue using the __TI_TIME_USES_64?

Ryan Hunter65

Part Number: CC3220

I found the following article in the TI wiki: Time and Clock RTS Functions

I wanted to utilize the macro __TI_TIME_USES_64 to ensure there is no issue with my internal time functions having issues when EPOCH time rolls over.

When I defined it in my project settings many of the timers from time.h that I was using began operating abnormally. The timers would immediately elapse whereas they operated as intended before defining the 64 bit time.

I was wondering if this is a known issue or if I need to recompile either the CC3220 SDK or something of that nature?

over 7 years ago

0 made4engineering over 7 years ago

TI__Mastermind 27605 points

Hi Ryan,

Is it your intention to not have this handled by the RTOS?

-Aaron

0 Ryan Hunter65 over 7 years ago in reply to made4engineering

Intellectual 470 points

Aaron,

I'm not really sure I understand your question. Are you asking whether I want the CC3220 64/32 bit time selection to not be handled by the RTOS?

--Ryan

0 Sarah P over 7 years ago in reply to Ryan Hunter65

TI__Mastermind 38980 points

Hi Ryan,

How are you initializing your timer? It looks like you're asking about a low level timer function from the compiler, which we don't typically see used with this SDK.

If you're using an TI-RTOS or FreeRTOS, I suggest using a POSIX timer which handles epoch. This timer is part of the RTOS and runs from the system clock. You can find an example of this in the SDK in examples/rtos/CC3220x_LAUNCHXL/demos/cloud_ota/platform.c

You can also use a hardware timer ( dev.ti.com/.../ )

Best regards,
Sarah

0 Ryan Hunter65 over 7 years ago in reply to Sarah P

Intellectual 470 points

Sarah,

I am using the POSIX timers using the functions timer_create and timer_delete. The problem I am seeing is that when I define __TI_TIME_USES_64 in my project all of the POSIX timers that previously worked now elapse almost immediately.

--Ryan