* docs(utest): Add standardized documentation for core.irq (irq_tc.c)
Most test cases in `src/utest` lack standardized functional
documentation, as tracked in issue #10895. This leads to high
maintenance costs, difficulty for new contributors, and inefficient
code reviews.
Solution:
This patch adds the full, standardized documentation block to
`src/utest/irq_tc.c`, following the approved template.
The documentation details:
- Test Objectives and tested APIs
- Test Scenarios (for `irq_test` and `interrupt_test`)
- Verification Metrics (the `uassert` criteria)
- Dependencies (Kconfig options and hardware)
- Test Execution command and Expected Results
This makes the test case's purpose and behavior immediately clear
to future maintainers and reviewers.
Relates to #10895
Signed-off-by: lhxj <2743257167@qq.com>
* Update src/utest/irq_tc.c
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
---------
Signed-off-by: lhxj <2743257167@qq.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Setting the send status flag `sndchange` after calling the can->ops->sendmsg function
could lead to a race condition if a transmission timeout occurs, resulting in incorrect state handling.
This patch moves the operation of setting the `sndchange` flag to before the call to can->ops->sendmsg.
This ensures that the mailbox's status is correctly marked as "sending" before the hardware begins transmission,
making the driver's state management more robust and reliable, especially in handling exceptions like timeouts.
Additionally, new macros for CAN filter modes have been added in dev_can.h.
Problem description:
The file 'src/utest/perf/README.md' was incorrectly appearing as a root-level page in the Doxygen documentation output.
Problem analysis:
This file was unintentionally included by the Doxygen build process following commit 7499790. It is an internal README for performance tests and is not intended to be part of the generated documentation.
Solution:
The issue is resolved by explicitly excluding this file from the build. The path '../src/utest/perf/README.md' has been added to the EXCLUDE list in both 'documentation/Doxyfile.1.9.1' and 'documentation/Doxyfile.1.9.8'.
This issue was originally introduced by the following commit:
Commit: 7499790
Title: utest: core: move perf testcase from example to src
Signed-off-by: lhxj <2743257167@qq.com>
The context_gcc.S file was incorrectly marked as cortex-m4 in both the
doxygen comment and .cpu directive, while the IAR and KEIL versions
correctly specify cortex-m33. This file uses ARMv8-M specific features
(PSPLIM register, TrustZone support) that are not available in Cortex-M4.
Changes:
- Update doxygen group from cortex-m4 to cortex-m33
- Change .cpu directive from cortex-m4 to cortex-m33
Requirement: The BSP for the k230 platform in the RT-Thread repository
does not yet have an I2C driver.
Solution: Provide I2C driver for the k230 platform in the RT-Thread
repository.
1. support i2c master mode
Signed-off-by: Ze-Hou <yingkezhou@qq.com>
* feat:[sal][utest] added test cases for the sal api
* improve[net][utestcase]: standardize script construction
* ci[auto utest run]: standardize naming and add sal testcases
* add sal utest auto run configure and standard Information
Fixed implicit type conversion warning in UART driver by correctly
separating clock_name_t and clock_attach_id_t enum types.
Changes:
- Use kCLOCK_Fro12M (clock_name_t) for clock_src field
- Keep kFRO12M_to_LPUARTx (clock_attach_id_t) for clock_attach_id field
- Fix mcx_getc() to use correct status flag kLPUART_RxDataRegFullFlag
This resolves the compiler warning:
"implicit conversion from 'int' to 'clock_name_t' changes value from 16777216 to 0"
Signed-off-by: Yucai Liu 1486344514@qq.com
