Your browser does not support JavaScript! Skip to main content
Free 30-day trial DO-178C Handbook RapiCoupling Preview DO-178C Multicore Training Multicore Resources
Rapita Systems
 

Industry leading verification tools

Rapita Verification Suite (RVS)

RapiTest - Functional testing for critical software RapiCover - Low-overhead coverage analysis for critical software RapiTime - In-depth execution time analysis for critical software RapiTask - RTOS scheduling visualization RapiCoverZero - Zero-footprint coverage analysis RapiTimeZero - Zero-footprint timing analysis RapiTaskZero - Zero-footprint event-level scheduling analysis RVS Qualification Kits - Tool qualification for DO-178 B/C and ISO 26262 projects RapiCouplingPreview - DCCC analysis

Multicore Verification

MACH178 - Multicore Avionics Certification for High-integrity DO-178C projects MACH178 Foundations - Lay the groundwork for A(M)C 20-193 compliance Multicore Timing Solution - Solving the challenges of multicore timing analysis RapiDaemon - Analyze interference in multicore systems

Other

RTBx - The ultimate data logging solution Sim68020 - Simulation for the Motorola 68020 microprocessor

RVS Software Policy

Software licensing Product life cycle policy RVS Assurance issue policy RVS development roadmap

Industry leading verification services

Engineering Services

V&V Services Data Coupling & Control Coupling Object code verification Qualification Training Consultancy Tool Integration Support

Latest from Rapita HQ

Latest news

Rapita partners with Asterios Technologies to deliver solutions in multicore certification
SAIF Autonomy to use RVS to verify their groundbreaking AI platform
RVS 3.22 Launched
Hybrid electric pioneers, Ascendance, join Rapita Systems Trailblazer Partnership Program
View News

Latest from the Rapita blog

What does AMACC Rev B mean for multicore certification?
How emulation can reduce avionics verification costs: Sim68020
Multicore timing analysis: to instrument or not to instrument
How to certify multicore processors - what is everyone asking?
View Blog

Latest discovery pages

Military Drone Certifying Unmanned Aircraft Systems
control_tower DO-278A Guidance: Introduction to RTCA DO-278 approval
Picture of a car ISO 26262
DCCC Image Data Coupling & Control Coupling
View Discovery pages

Upcoming events

IEEE SMC-IT/SCC 2025
2025-07-28
DASC 2025
2025-09-14
DO-178C Multicore In-person Training (Fort Worth, TX)
2025-10-01
DO-178C Multicore In-person Training (Toulouse)
2025-11-04
View Events

Technical resources for industry professionals

Latest White papers

Mitigation of interference in multicore processors for A(M)C 20-193
Sysgo WP
Developing DO-178C and ED-12C-certifiable multicore software
DO178C Handbook
Efficient Verification Through the DO-178C Life Cycle
View White papers

Latest Videos

Requirements traceability with RapiTest and Polarion ALM
How to make AI safe in autonomous systems with SAIF
Rapita Systems - Safety Through Quality
Simulation for the Motorola 68020 microprocessor with Sim68020
View Videos

Latest Case studies

GMV case study front cover
GMV verify ISO26262 automotive software with RVS
Kappa: Verifying Airborne Video Systems for Air-to-Air Refueling using RVS
Supporting DanLaw with unit testing and code coverage analysis for automotive software
View Case studies

Other Resources

 Webinars

 Brochures

 Product briefs

 Technical notes

 Research projects

 Multicore resources

Discover Rapita

Who we are

The company menu

  • About us
  • Customers
  • Locations
  • Partners & Distributors
  • Research projects
  • Contact us
  • Careers
  • Working at Rapita

Industries

  Civil Aviation (DO-178C)   Automotive (ISO 26262)   Military & Defense   Space

US office

+1 248-957-9801
info@rapitasystems.com Rapita Systems, Inc., 41131 Vincenti Ct., Novi, MI 48375, USA

UK office

+44 (0)1904 413945
info@rapitasystems.com Rapita Systems Ltd., Atlas House, Osbaldwick Link Road, York, YO10 3JB, UK

Spain office

+34 93 351 02 05
info@rapitasystems.com Rapita Systems S.L., Parc UPC, Edificio K2M, c/ Jordi Girona, 1-3, Barcelona 08034, Spain
Back to Top Contact Us

How to use the System Clock to extract timing data from a TriCore timer

2013-09-11

infineon tricore microcontroller photograph

We work with many different embedded microcontrollers at Rapita Systems, so it’s useful to understand the need for timers and how to set up and use them. In most systems this involves interacting with several registers and some potentially confusing juggling of clock divisors and the like. However on a TriCore system there is a much easier option.

The TriCore processors have the System Timer (STM) which is a monstrous 56 bits wide. This is very nice if you need an extremely long-running high-precision timer. As one TriCore data sheet notes, this gives 28.56 years at 80MHz.

It starts automatically after reset and cannot be written to - only read from. From our perspective this is a very nice timer to use; timers which are potentially reset or modified by system code that we're not aware of can cause problems.

It's rare that we need more than a 32-bit wide timestamp for our instrumentation (especially when you consider that maximum clock frequencies we're generally encountering are about 200MHz). Using only 32 bits does mean that counter rollover can occur relatively frequently, so this does need to be handled in your code.

Let’s suppose that you want to capture the full 56 bits, without risking a rollover in-between the capture of the upper and lower words. Atomic actions won’t have any effect on timers and pausing timers to complete a read back is overkill. Thankfully Infineon have thought of this. Read a value from STM_TIM0 (the least significant word) and the STM_CAP register will automatically latch the upper 24 bits of the STM timer, to be read back at your leisure e.g.:

unsigned int lowerword, upper_24bits;
lowerword = STM_TIM0.U // dependant on the compiler used (this is TASKING)
uppert_24bits = STM_CAP.U

The default rate of the System Timer depends on the flavor of TriCore that you have. From the user manuals that I’ve seen it will either be fSYS/2 (e.g. in TC1762) or fFPI/2 . This divisor can be modified, which is best done in cstart (the C start up code which executes before the main ( ) function), by setting bits 10:8 (the RMC bit-field) in the STM_CLC register .

These bits have the following effect:

000 No clock input
001 Clock at fSYS
010 Clock at fSYS
011 Clock at fSYS
Etc
111 Clock at fSYS

So for example in cstart you may have the line:

STM_CLC.U = 0x00000100; // set system clock to run at fsys/2

One philosophical point comes to mind on this: if your system experiences timer rollover once every 14 years (if running at 160MHz), the likelihood of residual timing rollover logic faults remaining in the software seems considerably higher than would be the case if rollover happened several times per hour.

Because testing the rollover logic on this device is very difficult, given that there is no way of resetting the timer, other than performing a software reset, this raises the possibility of an entire fleet of systems failing simultaneously at 14.28 years. Instead, should you consider simply using the lower 32 bits and be sure of getting the timer rollover right?

DO-178C webinars

DO178C webinars

White papers


Mitigation of interference in multicore processors for A(M)C 20-193
Sysgo WP
Developing DO-178C and ED-12C-certifiable multicore software
DO178C Handbook
Efficient Verification Through the DO-178C Life Cycle

A Commercial Solution for Safety-Critical Multicore Timing Analysis

Related blog posts

How did the first real-time embedded system also produce the first timing bug?

.
2019-07-16

Unboxing the new RTBx

.
2017-07-25

Optimising for code size might not do what you expect - a GCC and PowerPC example

.
2015-02-09

Lesser used PowerPC instructions

.
2014-02-25

Pagination

  • Current page 1
  • Page 2
  • Page 3
  • Page 4
  • Next page Next ›
  • Last page Last »
  • Solutions
    • Rapita Verification Suite
    • RapiTest
    • RapiCover
    • RapiTime
    • RapiTask
    • MACH178

    • Verification and Validation Services
    • Qualification
    • Training
    • Integration
  • Latest
  • Latest menu

    • News
    • Blog
    • Events
    • Videos
  • Downloads
  • Downloads menu

    • Brochures
    • Webinars
    • White Papers
    • Case Studies
    • Product briefs
    • Technical notes
    • Software licensing
  • Company
  • Company menu

    • About Rapita
    • Careers
    • Customers
    • Distributors
    • Industries
    • Locations
    • Partners
    • Research projects
    • Contact
  • Discover
    • Multicore Timing Analysis
    • Embedded Software Testing Tools
    • Worst Case Execution Time
    • WCET Tools
    • Code coverage for Ada, C & C++
    • MC/DC Coverage
    • Verifying additional code for DO-178C
    • Timing analysis (WCET) & Code coverage for MATLAB® Simulink®
    • Data Coupling & Control Coupling
    • Aerospace Software Testing
    • DO-178C
    • Meeting DO-178C Objectives
    • AC 20-193 and AMC 20-193
    • Meeting A(M)C 20-193 Objectives
    • Certifying eVTOL
    • Certifying UAS

All materials © Rapita Systems Ltd. 2025 - All rights reserved | Privacy information | Trademark notice Subscribe to our newsletter