| Age | Commit message (Collapse) | Author |
|---|
|
Co-authored-by: BernardXiong <[email protected]>
|
|
Co-authored-by: BernardXiong <[email protected]>
|
|
|
|
* 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 <[email protected]>
* Update src/utest/irq_tc.c
Co-authored-by: Copilot <[email protected]>
---------
Signed-off-by: lhxj <[email protected]>
Co-authored-by: Copilot <[email protected]>
|
|
|
|
times.
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
* Initial plan
* Remove vbus component and related code
Co-authored-by: BernardXiong <[email protected]>
---------
Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: BernardXiong <[email protected]>
|
|
* [bsp] [stm32] 添加鹿小班STM32H723开发板的BSP
* fix(bsp): 修正链接脚本中的拼写错误并启用环境变量配置
修复链接脚本中'excetion'拼写错误为'execution'
启用rtconfig.py中的环境变量配置选项
* fix(bsp): 重新添加开发板IAR、GCC链接脚本
链接脚本中包含了所有寄存器，除flash与主sarm外其余寄存器已注释
* refactor(bsp): 移除冗余的SOC_STM32H723ZGT6配置选项
|
|
|
|
�起,无法区分
|
|
|
|
|
|
enable stream mode
|
|
[bsp][gd32][serial_v2] 增加 GD32F5 支持
|
|
|
|
(RT-Thread#10888)
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 <[email protected]>
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
(#10869)
Resolve issue #10857
Signed-off-by: Ze-Hou <[email protected]>
|
|
* Initial plan
* Add CI results comment workflow
Co-authored-by: supperthomas <[email protected]>
* Improve CI results comment formatting and PR detection
Co-authored-by: supperthomas <[email protected]>
* Add documentation for CI results comment feature
Co-authored-by: supperthomas <[email protected]>
* Add ToolsCI and pkgs_test to monitored workflows
Co-authored-by: supperthomas <[email protected]>
* Add immediate CI status comment via direct workflow integration
Co-authored-by: supperthomas <[email protected]>
---------
Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: supperthomas <[email protected]>
|
|
|
|
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 <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
义 (#10859)
* [BSP][renesas][rsoc][fix]:移除HAL_Drivers/config/ra2a1,add pwm configuration items
* 在pwm_config里新增对BSP_USING_PWM10到BSP_USING_PWM12的定义
|
|
|
|
|
|
|
|
example could not enable DHCP.
|
|
有关
|
|
|
|
Signed-off-by: Yonggang Luo <[email protected]>
|
|
|
|
|
|
* 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 [email protected]
|
