* [components][clock_time] Refactor time subsystem around clock_time Introduce the clock_time core with clock source/event separation, high-resolution scheduling, and boot-time helpers, plus clock_timer adapters for timer peripherals. Remove legacy ktime/cputime/hwtimer implementations and migrate arch and BSP time paths to the new subsystem while keeping POSIX time integration functional. Update drivers, Kconfig/SConscript wiring, documentation, and tests; add clock_time overview docs and align naming to clock_boottime/clock_hrtimer/clock_timer. * [components][clock_time] Use BSP-provided clock timer frequency on riscv64 * [risc-v] Use runtime clock timer frequency for tick and delays * [bsp] Add clock timer frequency hooks for riscv64 boards * [bsp] Update Renesas RA driver doc clock_timer link * [bsp] Sync zynqmp-r5-axu4ev rtconfig after config refresh * [bsp][rk3500] Update rk3500 clock configuration * [bsp][hpmicro] Add rt_hw_us_delay hook and update board delays * [bsp][stm32l496-st-nucleo] enable clock_time for hwtimer sample in ci * [bsp][hpmicro] Fix rtconfig include scope for hpm6750evk Move rtconfig.h include outside the ENET_MULTIPLE_PORT guard for hpm6750evk and hpm6750evk2 so configuration macros are available regardless of ENET settings. * [bsp][raspi3] select clock time for systimer * [bsp][hpm5300evk] Trim trailing blank line * [bsp][hpm5301evklite] Trim trailing blank line * [bsp][hpm5e00evk] Trim trailing blank line * [bsp][hpm6200evk] Trim trailing blank line * [bsp][hpm6300evk] Trim trailing blank line * [bsp][hpm6750evk] Trim trailing blank line * [bsp][hpm6750evk2] Trim trailing blank line * [bsp][hpm6750evkmini] Trim trailing blank line * [bsp][hpm6800evk] Trim trailing blank line * [bsp][hpm6e00evk] Trim trailing blank line * [bsp][nxp] switch lpc178x to gcc and remove mcx timer source * [bsp][stm32] fix the CONFIG_RT_USING_CLOCK_TIME issue. * [docs][clock_time] add clock time documentation * [docs][clock_time] Update clock time subsystem documentation - Update device driver index to use correct page reference - Clarify upper layer responsibilities in architecture overview - Update README to describe POSIX/libc, Soft RTC, and device driver usage - Refine architecture diagram with improved layout and color scheme - Remove obsolete clock_timer.md file * [kernel][utest] Trim trailing space * [clock_time] Fix hrtimer wrap handling * [clock_time] fix the static rt_inline issue * [clock_time] fix the rt_clock_hrtimer_control result issue
NXP FRDM-MCXC444 Introduction
Overview
The FRDM-MCXC444 is NXP's official low-cost evaluation board based on the MCX C444 MCU. It is designed for rapid prototyping and features a compact and scalable form factor. The board provides industry-standard headers for easy access to the MCU's I/O pins and supports the MCUXpresso development environment.
Key features of the FRDM-MCXC444 include:
- SLCD functionality
- Arduino-compatible expansion headers
- MCUXpresso IDE support
The appearance of the board is shown in the figure below:
The common on-board resources for this board are listed below:
For more details on the development board, please refer to NXP official website。
Preparation
To run sample programs on the FRDM-MCXC444 board, you need to make the following preparations:
-
Development Environment
Keil V5 with MCXC444 package installed.
-
Source Code Acquisition
Visit https://github.com/RT-Thread/rt-thread and download the latest stable release zip package from the Assets section.
-
Hardware Connection
Use a USB cable to connect the USB port of the development board to your PC.
NXP's official hands-on tutorial for the FRDM-MCXC444 can be found at here
Run the First Sample Program
Compile and Download
Please note!!!
Before performing the compilation process, please first open the ENV and execute the following command (this command is used to pull the necessary libraries; otherwise, the compilation will not be successful):
pkgs --update
- Navigate to the
rt-thread\bsp\nxp\mcxc\frdm-mcxc444folder. - Open the project file in Keil.
- Compile the project.
- Click the download button to flash the firmware to the development board.
Execute the compilation. After it, click the download button to download the firmware to the development board. Then, the program will start running automatically, observe the program running status.
Tip: The default configuration of the project uses CMSIS-DAP to download the program. And then click the Download button to download the program to the development board.
Run
If it does not run automatically, press the reset button to restart the board and observe the actual effect of the LEDs on the board. After normal operation, the LEDs will blink periodically, as shown in the following figure:
After downloading the program, it should start running automatically. If not, press the reset button on the board.
Connect the board's serial port to your PC and open a serial terminal with the following settings:
- Baud rate: 115200
- Data bits: 8
- Stop bits: 1
- Parity: None
Reset the device, and you should see the RT-Thread startup information in the serial terminal:
\ | /
- RT - Thread Operating System
/ | \ 5.2.0 build Sep 4 2024 10:46:13
2006 - 2024 Copyright by RT-Thread team
using armclang, version: 6190004
NXP MCXC444
msh >
Keep Learning
Completed RT-Thread Quickstart! Click here for Kernel Learning .





