• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 183 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.

AM2634-Q1: Timer enable for multicore project

Perumalsamy A
Prodigy 70 points
Part Number: AM2634-Q1

Tool/software:

We are working on a multicore project where each core has a dedicated task. We need to enable a timer for Core 0. However, when we enable the timer for Core 0, a resource conflict occurs because each core is using its corresponding clock (RTI1, RTI2, RTI3, RTI4). We tried changing the clock to RT0 for all cores, but that also caused a resource conflict.

Could you kindly guide us on how to enable the timer for a specific core? Your support would be greatly appreciated.

  • 0
    TI__Genius 16302 points

    Hi,

    Right now, all the four RTI instances are tied up to each R5F core's "Clock" module (can be checked in the example.syscfg).

    This leads to RTI being completely resource locked and not being able to use it for other purposes. While the Hardware RTI does support having multiple compare outputs, the support is not present in the software RTI driver yet. Unfortunately, this means, in this scenario of all 4 cores being used, with the current SDK offering, RTI cannot be used for other purposes.

    Regards,
    Shaunak

  • 0 in reply to Shaunak Deshpande
    Prodigy 70 points

    Hello Shaunak Deshpande,

    Thank you for your valuable support.

  • 0 in reply to Perumalsamy A
    TI__Genius 16302 points

    Hi,

    I also checked with the development team internally, since this support should be present to use RTI hardware efficiently on the AM263x MCU, we will try to enable he other Compare outputs so RTI can be used for other purposes in the application as well.

    This should be available in the v11.0 SDK around 3Q2025

    Regards.
    Shaunak