The TimerInfo block visualizes timer resource allocation across all peripheral blocks, showing which timers are used, their configuration, and detecting conflicts.
When to use:
When to use:
- Debugging timer conflicts (multiple peripherals requesting same timer)
- Verifying timer allocation before adding new features (check available timers)
- Understanding which peripheral uses which timer resource
- Identifying timer configuration (prescaler, period, mode)
- Documenting timer usage for project handoff or review
โ This block is never harmful:
- Informational utility only โ no simulation or code generation impact
- Add to model for timer resource visualization
- Remove if not needed โ purely a development aid
| 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 Output
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.