For timing functions on the TM990 microcomputer platform, where can timing support be obtained, and what are common approaches to implement timing in such systems?

Introduction / Context:
Microcomputer and embedded platforms commonly provide timing through a mix of hardware peripherals and software techniques. Hardware timers deliver precise periodic interrupts and capture/compare features, while software-based timing can be adequate for non-critical delays. Understanding both methods is important for scheduling tasks, measuring intervals, and generating real-time events.

Given Data / Assumptions:

• We consider a classic microcomputer platform (TM990 family).
• Typical CPU boards include at least one timer/counter peripheral or can be paired with a timer module.
• Software timing uses instruction cycles and calibrated delay loops or tick interrupts.

Concept / Approach:

Hardware timers provide accurate, low-jitter timing and can drive periodic interrupts for operating system ticks or time-base generation. Software timing, while less precise, is simple and may suffice for coarse delays or prototyping. Many development boards expose a timer on the standard CPU board and also allow users to implement timing in software, giving flexibility between precision and simplicity.

Step-by-Step Solution:

Verification / Alternative check:

Legacy manuals and common embedded practices align: boards with standard timers plus software delays are both widely used across microcomputer systems.

Why Other Options Are Wrong:

“External timer only” ignores built-in timer availability and software strategies.

“Hardware only” excludes valid software methods.

“Software only” disregards precision and jitter constraints solved by hardware timers.

Common Pitfalls:

Relying on busy-wait loops in multi-task systems can starve other tasks; prefer timer interrupts and proper schedulers for scalable designs.

Final Answer:

Both hardware timing on the CPU board and software timing are possible