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.

RTOS/TM4C1294NCPDT: How to check or configure the TI-RTOS to use external XTAL for clock service.

Part Number: TM4C1294NCPDT

Tool/software: TI-RTOS

How to check or configure the TI-RTOS to use external XTAL for clock service for this device?

Where in the documentation made a specific declaration that TI-RTOS used external XTAL (I struggled to find this) and what happens if XTAL is not fitted or badly tuned, how to detect this under CCS debug mode?

Thanks

  • Hi Richard,

     It is in the Boot module. Please see below.

  • So the Clock and Second is actually run by main clock osc 25MHz and SYS CLOCK 120MHz divided down via Timer 0.

    What you suggest there no way to set RTOS CLOCK and RTOS SECOND to XTAL 32KHz without impacting  SYSCLK=120MHz. When I change mainosc to external 32K, it showed SYSCLK = 0MHz via config XCONF.  

    I understood the CLOCK mean date/time or was is actually 120MHz system clock, not sure which. I find documentation on CLOCK in context for the specific device in question bit vague. 

    This means I have to use Hibernate RTC module for clock source (from 32K8 XTAL) with interrupt tap to HWI and forget about the RTOS SECOND and CLOCK as useless for application date/time purpose need?

    Earlier, I also cannot use SYSTICK since it seems to impacts the TI-RTOS based code when I change the SYSTICK value or reset value.  I'm very familiar with SYSTICK from LPC1xxx and other CORTEX based MCU, but I cannot use it for this reason. it seems to be a murky relationship between SYSTICK and RTOS with some open questions. 

    When Boot-Clocking option is not enabled in CONF, what I see are some default values that already implemented, correct?

    R. 

  • Sorry about photo capture download issue, here the correct one that replace 1 of 2 in previous message, 

  • Hi Richard,
    The TI-RTOS has no direct support for hibernation module. If you configure the oscillator source for external 32KHz then it thinks that you want to use the 32KHz as the source for the entire device. If you want to keep 120MHz for the device and only external 32KHz for the RTC module then you will need to call the native TivaWare API such as HibernateClockConfig(HIBERNATE_OSC_LOWDRIVE).