• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 41 subscribers
  • Views 436 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

CC3220: sl_start() returns -2005 error if uart_open/close() called in other thread

CC3220SF: Using TI-RTOS with SimpleLink

Rustem Avkhadiev
Genius 3550 points
Part Number: CC3220SF

Hello!

I've changed Task_sleep() to usleep() and Event_pend/post/construct to sem_t. Now i can't recreate problem with sl_stop().

Is it safe to use Clock_getTicks(), Seconds_set(), Seconds_get() with POSIX and cc3220?

  • 0
    TI__Mastermind 40965 points
    Hi,

    It's great to hear that by removing the TIRTOS sync objects you have fixed the issue with sl_stop() you had previously.

    Looking through the code for the three calls in question (Clock_getTicks(), Seconds_set() and Seconds_get() ), I do not see any cause for concern. I also know that Clock_getTicks() is called during normal operation by the kernel during transitions out of low power mode, so that function is safe for sure. Of course, the only way to be 100% sure that those functions are safe is to perform runtime testing with those functions being used alongside the NWP host driver. However, as there doesn't seem to be any use of TIRTOS-specific sync objects within those function calls they shouldn't cause any issues.

    Let me know if you need more clarification or if you have further questions.

    Regards,
    Michael
  • 0 in reply to Michael Reymond
    Genius 3550 points
    Hello! Thank you very much!