cmu_fc#
Overview#
The cmu_fc example is to demonstrate usage of the SDK cmu_fc driver to check if the target clock frequency is within the threshold range. In this example, the low threshold is specified as the same as the high threshold to trigger a frequency lower than low frequency reference threshold event, which leads to a destructive reset. Then use the optimum high and low threshold to validate the target clock is operating at the correct frequency.
Supported Boards#
FRDM-MCXE31B
Hardware requirements
Type-C USB cable
FRDM-MCXE31B board
Personal Computer
Board settings
No special settings are required.
Prepare the Demo
Connect a type-c USB cable between the host PC and the MCU-Link USB port (J13) on the target board.
Open a serial terminal with the following settings:
115200 baud rate
8 data bits
No parity
One stop bit
No flow control
Download the program to the target board.
Either press the reset button on your board or launch the debugger in your IDE to begin running the demo.
Running the demo
The log below shows the output of the terminal window:
--- Destructive reset test start ---
Destructive reset occurred!
--- CMU FC test start ---
Monitored clock works fine!
FRDM-MCXE32B
Hardware requirements
Type-C USB cable
FRDM-MCXE32B board
Personal Computer
Board settings
No special settings are required.
Prepare the Demo
Connect a type-c USB cable between the host PC and the MCU-Link USB port (J13) on the target board.
Open a serial terminal with the following settings:
115200 baud rate
8 data bits
No parity
One stop bit
No flow control
Download the program to the target board.
Either press the reset button on your board or launch the debugger in your IDE to begin running the demo.
Running the demo
The log below shows the output of the terminal window:
--- Destructive reset test start ---
Destructive reset occurred!
--- CMU FC test start ---
Monitored clock works fine!