| Age | Commit message (Collapse) | Author |
|---|
|
- upgraded bsp to v1.10.0
- moved hpm_sdk to rt-thread package
- added support for hpm6p00evk and hpm5e00evk
Signed-off-by: Fan YANG <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Requirement: The BSP for the k230 platform in the RT-Thread repository
does not yet have an RTC driver.
Solution: Provide RTC drivers for the k230 platform in the RT-Thread
repository, implementing timekeeping and alarm functionalities,
with interrupt support for the alarm feature.
Signed-off-by: Ze-Hou <[email protected]>
|
|
utest framework is an optional module and should be
enabled when running utest.
So RT_USING_UTEST should not be enabled by default.
Disable it now.
Signed-off-by: Chen Wang <[email protected]>
|
|
|
|
* [bsp/renesas] add bsp ra4e2-ek
* bsp: Renesas ra4e2-ek bsp support the nano
* fix bsp and SOC_SERIES_R7FA4E2
* remove file R7FA4E2B9.svd
工程未使用此文件，
此文件在renesas bsp中已有一份,此文件可以删除
bsp\renesas\ra4e2-eco\script\R7FA4E2B9.svd
|
|
|
|
|
|
add AD\DA and Flash device
|
|
* [bsp][renesas]add EK-RA2E2 sci_uart support
* [bsp][renesas] add EK-RA2E2 (i2c/spi/adc/pwm/flash/gpio interrupt) support
* [bsp][renesas] comment drv_flash.c and format drv_i2c.c
|
|
[bsp/e906] 添加以BSP方式导入RT-Studio的CDT工程文件
|
|
清理掉无用的拷贝操作
|
|
The names of the utest cases defined in their respective
modules have been updated.
Some utest case names are not yet in their respective modules
because their paths need to be finalized before their unique
names can be determined. Currently, these names do not
appear to conflict with the unified names. These include:
- utest cases still in examples
- bsp/qemu-virt64-riscv/applications/test/test_vector/test_vector.c.
The entire test case should probably be placed in libcpu/risc-v
rather than bsp.
Signed-off-by: Chen Wang <[email protected]>
|
|
More details see PR #10681.
As utest cases are currently moving out of `examples/utest/testcases`
into their own module directories, the naming rule needs to change
accordingly.
Signed-off-by: Chen Wang <[email protected]>
|
|
support.
|
|
|
|
|
|
|
|
|
|
The introduction to Env under the documentation
section of the RTT source code repository is
outdated and unmaintained. We recommend moving the Env
documentation to https://github.com/RT-Thread/env/
for self-maintenance.
Solution:
Direct users to the latest README at https://github.com/RT-Thread/env/.
The Env content under the documentation section of RTT
will not be deleted for now, but will be marked as "outdated".
Signed-off-by: Chen Wang <[email protected]>
|
|
|
|
Similar to PR #10674, `src/scheduler_mp.c` and
`src/scheduler_up.c` also have similar issues.
After investigation, we found: in commit 2c98ce4605
"[HUST CSE][document] Fix some comments, invalid
grouping commands and warnings in Doxygen." This patch
excluded `src/scheduler_mp.c` and `src/scheduler_up.c`
from the Doxygen build and include
`documentation/doxygen/thread.h` (the new file path
after adjustment is `documentation/0.doxygen/core/thread.h`),
placing the Doxygen comments for some functions in this file.
However, this approach has its problems:
- The comments in `documentation/0.doxygen/core/thread.h`
are separated from the source code, making them
difficult to maintain. This also results in the
comments for the newly added functions in
`src/scheduler_mp.c` and `src/scheduler_up.c` not
being updated in a timely manner and failing to
be compiled into Doxygen (becoming HTML).
- For the average programmer, it's unlikely that
they'll consider the `documentation/0.doxygen/`
directory for function declarations and comments,
let alone the need to maintain the Doxygen comments
in that directory. Currently, the header files under
`documentation/0.doxygen/` should strictly be used
only to define Doxygen groups and should not include
Doxygen comments for the code itself. (Similar
issues exist in documentation/0.doxygen/3.hardware.h
and documentation/0.doxygen/core/systeminit.h, which
require further cleanup.)
The solution is similar to PR #10674, where only MP
documentation is generated by default. For functions
defined in MP but not in UP, we use the "@note"
directive in the function's doxygen comment to indicate
whether the function is supported in both UP and MP,
or only in MP.
After implementing this solution, the file
`documentation/0.doxygen/core/thread.h` can be deleted.
Signed-off-by: Chen Wang <[email protected]>
|
|
|
|
|
|
Refer to the issue described in PR #10599. This was a
temporary fix at that time.
After further research, we discovered that this issue
can be addressed using the "@cond" command supported
by Doxygen.
Since we currently do not intend to generate two sets
of documentation for UP and MP when generating Doxygen
documentation, the current solution is to generate only
MP documentation by default. For functions defined in
MP but not in UP, we will use the "@note" command in
the function's Doxygen comment to indicate whether the
function supports both UP and MP, or only MP.
Signed-off-by: Chen Wang <[email protected]>
|
|
* add EK-RA2E2 support
|
|
Signed-off-by: GuEe-GUI <[email protected]>
|
|
|
|
|
|
|
|
|
|
在没有定义FINSH_USING_SYMTAB时编译报错以及IPC及finsh启用时自动选择必要的功能
|
|
|
|
* utest: move testcases of Utest from example to Utest folder
Create unit-test-cases for the Utest framework subsystem
according to "How to add utest cases into RT-Thread for your module." [1]
Link:
https://rt-thread.github.io/rt-thread/page_component_utest.html#autotoc_md804
[1]
The original `components/utilities/utest` directory already has unit
testcases, which are more comprehensive than the testcases in
`examples/utest/testcases/utest/`. Therefore, simply deleted
the test cases in `examples` and used the existing testcases
in the utest framework.
Signed-off-by: Chen Wang <[email protected]>
* utest/utest: rename name and add license text
Signed-off-by: Chen Wang <[email protected]>
---------
Signed-off-by: Chen Wang <[email protected]>
|
|
|
|
Signed-off-by: Chen Wang <[email protected]>
|
|
|
|
|
|
|
|
|
|
The code formatting in the Object Management Markdown document
is misaligned. This issue can be fixed by replacing tabs with spaces.
Signed-off-by: Chen Wang <[email protected]>
|
|
|
|
|
