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.

AM2631-Q1: AM263x Sysconfig: Need to disable Clock module.

Part Number: AM2631-Q1
Other Parts Discussed in Thread: SYSCONFIG

Hello,

SDK states that Clock module is always enabled with any other module. Not quite sure why is there such a constraint. I want to use SDK drivers that do not need Clock and use Sysconfig to configure them.  I also do not need another interrupt that I have no use for.

How do I disable auto creation of Clock module and reclaim one of RTI modules for my application and remove unneeded interupt?

Regards,
Eugene

  • Hi Eugene,

    ARM R5F does not have its own systick and relies on external timers such as RTI to generate systick or heartbeat for the system. The RTI0 is by default reserved in the SDK for doing this. With this architecture, it is not possible to run the system without an RTI0 generating system heartbeat.

    The DPL layer used in SDK provides clocking support via certain APIs, which require RTI ISR to maintain gClockCtrl.ticks and process timer callbacks and without it there would be no time reference in the system

    Regards,
    Shaunak

  • Hello Shaunak,

    I see that not all SDK/DLP API require cocking support. What are those "certain APIs" that require clocking support? Could you please list them? If I do not use those that require Clock why then I am forced to sacrifice RTI instance and have interrupt that I do not need?

    There should be a way to remove Clock module and its required HW resource when it is not needed? Don't you think?

    Regards,

    Eugene

  • Hi Eugene,

    What are those "certain APIs" that require clocking support?

    All the ClockP APIs, Timer APIs. To summarize, 

    1. System Tick - ClockP_init() configures RTI0 for periodic interrupts
    2. ClockP_Object Callbacks - Timer-driven callback execution depends on RTI0 interrupts
    3. Timing Infrastructure - TimerP uses RTI0 counters for measuring elapsed time
    4. Sleep/Delay Operations - Even ClockP_sleep() depends on RTI counter readings

    If I do not use those that require Clock why then I am forced to sacrifice RTI instance and have interrupt that I do not need?

    I do understand exactly what the blocker here is. Ideally if no clocking task is used, the RTI0 in NoRTOS should not be locked.

    There should be a way to remove Clock module and its required HW resource when it is not needed? Don't you think?

    I do agree, but unfortunately the current SDK architecture does not support it. RTI0 is ALWAYS initialized (unconditionally in clock_init.c.xdt for AM263x) BUT it does almost nothing if you don't use ClockP APIs. I will talk internally to the SDK team to see if this is possible/feasible.

    Regards,
    Shaunak

  • Hi Shaunak,

    Similar constraint is with FreeRTOS port. FreeRTOS Timer is optional feature and yet SDK port forces user to have it.

    Regards,

    Eugene

  • Hi Eugene,

    I have this conversation on-going with the team internally, i will get back soon. Im tracking the bugs internally (TI Internal links):

    https://jira.itg.ti.com/browse/MCUSDK-15337

    https://jira.itg.ti.com/browse/MCUSDK-15824

    https://jira.itg.ti.com/browse/MCUSDK-15825

    Regards,
    Shaunak