The following techniques and safety measures can
be useful for improving independence of function when using the TMS320F28P55x real-time MCU:
- Hold peripheral clocks disabled if the available
peripherals are unused (CLK14-Peripheral Clock Gating
(PCLKCR)).
- Hold peripherals in reset if the available peripherals are unused (SYS7-Peripheral Soft Reset (SOFTPRES)).
- Power down the analog component cores if the
cores are not used.
- When possible, separate critical I/O functions by
using non adjacent I/O pins and balls.
- Partition the memory, as per the application requirements, to the respective
processing units and configure the Access Protection Mechanism for Memories for each memory instance,
so that only the permitted initiators have access to memory.
- The Dual Zone Code Security Module
(DCSM) can be used for functional safety as a firewall to protect shared
memories; where functions with different safety integrity levels can be executed from
different security zones (zone1, zone2, and unsecured zone), this mitigates risks
originating due to interference among memories.
- Disabling of the SOC inputs to the ADC can help avoid interference from unused
peripherals that disturb functionality of the ADC. Disabling of unused DMA
trigger sources helps minimize interference caused by unintentional DMA
transfers.
- Disabling unused CLA task trigger
sources and disabling unused DMA trigger sources mitigates risks of interference caused
due to the trigger events.
- To avoid interference from unintentional activity on the debug port of the
MCU, JTAG1-Hardware Disable of
JTAG Port is helpful in preventing this interference.
- Safety applications running on the
CPU can be interfered with by unintentional faulty interrupt events to PIE modules.
PIE7-Maintaining Interrupt Handler for unused interrupts and PIE8- Online Monitoring of
Interrupts and Events detect such interfering failures.
- MCU resources in supporting CPU execution, such as memory, interrupt
controller, and so forth, can be impacted by resources from lower safety-integrity safety
functions coexisting on the same MCU. Safety mechanisms, such as CPU9-External
watchdog, SRAM16 –Information Redundancy
Techniques and SRAM17-CPU handling of Illegal Operation,
Illegal Results and Instruction Trapping, are able to detect such
interference.
- Critical configuration registers can be victim to interference from bus
initiators on the MCU which implements lower safety-integrity functions. These
registers can be protected by SYS1-Multibit Enable Keys
for Control Registers, SYS2-Lock Mechanism for
Control Registers, and SYS8-EALLOW and MEALLOW
Protection for Critical Registers.