| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Replace standard string and memory functions with RT-Thread's rt-prefixed
equivalents where available:
- strcpy -> rt_strcpy
- strncpy -> rt_strncpy
- strcmp -> rt_strcmp
- strncmp -> rt_strncmp
- strlen -> rt_strlen
- strstr -> rt_strstr
- memcpy -> rt_memcpy
- memcmp -> rt_memcmp
Functions like strcat, strchr remain unchanged as RT-Thread does not provide
rt-prefixed versions.
|
|
修复accept在错误执行过程中返回无效socket问题
|
|
|
|
for idle harts
Add explanatory comments for the utest of smp_assigned_idle_cores.
Signed-off-by: Mengchen Teng <[email protected]>
|
|
Currently, this utest cannot determine whether threads are evenly distributed
across idle harts by observing the result of list_thread(). This is because
the presence of rt_thread_delay(5); causes all other threads to be in the
suspended state when thread information is printed. For example, if RT_CPUS_NR=4,
T0 executes list_thread() to print information, while T1~T3 are in hibernation
and thus it is impossible to observe which hart they are running on.
Solution:Here, the completion judgment condition has been modified. For example,
when RT_CPUS_NR=4, only RT_CPUS_NR-1 threads will be created (i.e., T0 to T2),
because running the utest occupies one hart. The execution is judged as completed
when finish_flag=0x0007, and the thread running the utest will call list_thread()
to print the information. Observe whether T0 to T2 are running on different
harts simultaneously.
Signed-off-by: Mengchen Teng <[email protected]>
|
|
truncation #10943
|
|
Signed-off-by: Ze-Hou <[email protected]>
|
|
Signed-off-by: Ze-Hou <[email protected]>
|
|
by improper priority configuration. (#10956)
|
|
by improper priority configuration.
|
|
mtsafe_kprint_tc #10945
|
|
|
|
|
|
|
|
Signed-off-by: Ze-Hou <[email protected]>
|
|
* [fix][utest] correct spelling of ''pref_test' to 'perf_test'
|
|
|
|
Requirement: The BSP for the k230 platform in the RT-Thread repository does not yet have an spi driver.
Solution: Provide spi driver for the k230 platform in the RT-Thread repository.
- Supports SPI0(OSPI) controller with 1/2/4/8 data lines.
- Supports SPI1(QSPI0) and SPI2(QSPI1) controllers with 1/2/4 data lines.
- Implements DMA-based transfers for OSPI, QSPI, and DSPI modes.
- Falls back to standard IRQ-driven transfers for legacy SPI mode (single line).
- Updates documentation in bsp/README.md
Signed-off-by: ChuanN-sudo <[email protected]>
|
|
Signed-off-by: ChuanN-sudo <[email protected]>
|
|
Add Doxygen-style comments for the lwp shared memory public APIs
in components/lwp/lwp_shm.c and the related control structure.
This change is documentation-only and does not modify any runtime
behavior or logic.
Signed-off-by: ibvqeibob <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Signed-off-by: Ze-Hou <[email protected]>
|
|
Signed-off-by: Ze-Hou <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
* List of RT-Thread BSP Support Additions.
|
|
Can use rt_ktime_cputimer_getfrq() / RT_TICK_PER_SECOND instead.
|
|
(#10919)
* Initial plan
* [libcpu][cortex-a] Improve FPU stack initialization implementation
Co-authored-by: BernardXiong <[email protected]>
* [libcpu][cortex-a] Replace FPU init loop with rt_memset
Co-authored-by: BernardXiong <[email protected]>
---------
Co-authored-by: copilot-swe-agent[bot] <[email protected]>
Co-authored-by: BernardXiong <[email protected]>
|
|
* [utest]: [signal]:Standardized function comment blocks have been added.
Added comments to the utest for the signal module, including: test purpose,
usage scenarios, dependency configurations, expected outcomes, and expected
behaviors.
Signed-off-by: Mengchen Teng <[email protected]>
* [utest]: [signal]:Correct issues including grammatical errors, spelling mistakes, and ambiguities in function names.
Fixed the issue of grammatical errors in words; changed the variable 'recive_sig' to 'receive_sig'.
Originally, rt_signal_unmask_test was testing the masking function of rt_signal_mask, while
rt_signal_mask_test was verifying whether signals could be sent correctly during unmasking——the
function names were exactly opposite to their functions. Now the two function names have been swapped,
and the corresponding comments have also been updated accordingly.After modification, it has been
verified that the signal-related utests can be executed correctly.
Signed-off-by: Mengchen Teng <[email protected]>
---------
Signed-off-by: Mengchen Teng <[email protected]>
|
|
Update bsp/stm32/stm32f407-micu/rtconfig.py
Co-authored-by: Copilot <[email protected]>
Update bsp/stm32/stm32f407-micu/rtconfig.h
Co-authored-by: Copilot <[email protected]>
Update bsp/stm32/stm32f407-micu/project.uvproj
Co-authored-by: Copilot <[email protected]>
Update bsp/stm32/stm32f407-micu/project.uvproj
Co-authored-by: Copilot <[email protected]>
Update bsp/stm32/stm32f407-micu/board/board.h
Co-authored-by: Copilot <[email protected]>
add ci
Delete bsp/stm32/stm32f407-micu/project.uvgui.dlx
modified: MAINTAINERS
deleted: bsp/stm32/stm32f407-micu/figures/board.png.png
deleted: bsp/stm32/stm32f407-micu/project.uvopt
modified: bsp/stm32/stm32f407-micu/project.uvoptx
modified: bsp/stm32/stm32f407-micu/project.uvprojx
|
|
* 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]>
|
