The TimerInfo block visualizes timer resource allocation across all peripheral blocks, showing which timers are used, their configuration, and detecting conflicts.
| Information | Description |
|---|
| Timer Allocation | Which peripheral uses which timer |
| Timer Configuration | Prescaler, period, mode |
| Conflicts | Multiple peripherals requesting same timer |
| Available Timers | Unused timer resources |
Example Display
Timer Resources (dsPIC33AK128MC106):
Timer1: ⚠️ CONFLICT
- MCHP_Interrupt (Hardware Timer mode)
- MCHP_IC1 (Input Capture)
→ Resolve: Use different timer
Timer2: PWM_HS Module
- PWM timebase, Period=1000, Prescaler=1
Timer3: QEI1 Position Measurement
- Speed calculation, Period=65535
Timer4: [Available]
Timer5: [Available]
Usage
- Add TimerInfo block to model
- Double-click to view allocation
- Verify no conflicts exist
- Identify available timers for new features
Timer Conflicts: Must be resolved before code generation. Reconfigure peripheral blocks to use different timers.
See Also
- [MCHP_PortInfo] - GPIO allocation
- [Timer Blocks] - Timer peripheral blocks
