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.

Clock module configuration

Other Parts Discussed in Thread: SYSBIOS

Hi

I am working with latest sysbios running on Cortex M3 MCU. I don't use Clock handles because I have my own collection of software timers driven by my own 1 ms tick, which is independent from Clock tick. So the best idea for me would be to disable completely Clock handles and code managing this functionality, but I still want to use task timeouts for example with Task_sleep(), Semaphore_pend() and all other sysbios functions using timeout parameter.

Is this possible?

I know that setting of BIOS.clockEnabled = false; disables also kernel timeouts functionality, so it is not an option for me.

Gregor

  • Yes. This is possible.

    You just have to make sure that SYS/BIOS isn't using the same timer to drive the Clock module as you're using for your timer services.

    Which M3 device are you using?

    Alan

  • Hi Alan

    I am using LM3S9D90.

    In my current solution I just disabled Clock module with "BIOS.clockEnabled = false;"  and I am using SysTick timer to drive my own timers. Because Clock_tickSource is now NULL I have no timers resource conflict in my project but I faced up with problem which is described in SysBios API doc that

    when BIOS.clockEnabled = false, then "For APIs that take a timeout, values other than NO_WAIT will be equivalent to WAIT_FOREVER. " so it means that timeout function is now 2-state 0/1 function, but I'd like to have timeouts fully operable.

    Gregor

  • Gregor,

    By default, SYS/BIOS does NOT use the SysTick timer to drive the Clock module. It uses one of the 32 bit LM3-device-specific timers.

    So I think it is safe for you to remove the 'BIOS.clockEnabled=false' setting from your config file.

    This will fully enable the Clock module so that timeouts will work.

    Alan