rt-thread icon indicating copy to clipboard operation
rt-thread copied to clipboard

RT-Thread is an open source IoT real-time operating system (RTOS).

Results 626 rt-thread issues
Sort by recently updated
recently updated
newest added

### RT-Thread Version master ### Hardware Type/Architectures 与BSP无关 ### Develop Toolchain Other ### Describe the bug RTT文档中心对于Ringbuffer的说明如下 > 下面介绍第二类接口,读数据但不取出数据: rt_size_t rt_ringbuffer_peek(struct rt_ringbuffer *rb, rt_uint8_t**ptr); 该接口用于获取 rb 指向的 ringbuffer 内部缓冲区第一个可读数据的地址,并保存到 *ptr,该接口返回...

- [x] Understand the current elm-fatfs implementation in RT-Thread - [x] Download official elm-fatfs R0.15 and R0.16 sources - [x] Identify RT-Thread specific modifications - [x] Update dfs_v2/elmfat to clean...

Component

## 拉取/合并请求描述:(PR description) There is no proper windows toolchain for risvc for gcc 10.0 upgrade 12.x we have same tool with linux. rv64gc is equivalent to rv64imafdc_zicsr_zifencei in gcc 12.x...

BSP
action
tools
Arch: RISC-V

### Describe problem solved by the proposed feature riscv32 rt-thread支持跑在s-mode ### Describe your preferred solution riscv32 rt-thread支持跑在s-mode ### Describe possible alternatives riscv32 rt-thread支持跑在s-mode

Arch: RISC-V

### RT-Thread Version master ### Hardware Type/Architectures RISC-V with CLIC Interrupt ### Develop Toolchain GCC ### Describe the bug The interrupt handling logic for risc-v, see as below https://github.com/RT-Thread/rt-thread/blob/fcd0b1e6797cbdca987f24d7c24a032709e5e53b/libcpu/risc-v/common/interrupt_gcc.S#L101-L109 In...

Arch: RISC-V

### RT-Thread Version 8a71f41 ### Hardware Type/Architectures riscv64 ### Develop Toolchain GCC ### Describe the bug 1.问题复现 下面程序在linux上运行,线程终止且不会打印任何数据,但是在qemu-riscv64上运行 rt-smart,线程会一直循环打印“should not reach here“ ``` #include #include #include #include #include #include int...

Arch: RISC-V

### RT-Thread Version ece19e9 ### Hardware Type/Architectures riscv64 qemu ### Develop Toolchain GCC ### Describe the bug components/lwp/arch/risc-v/rv64/lwp_gcc.S 中的arch_signal_quit中将内核栈中的地址保存到用户栈中,之后又从用户栈中的保存值恢复sp,在多核环境下,如果另外一个核心运行的其他线程(属于同一进程)通过修改当前线程用户栈里保存的内核栈地址,可能导致内核崩溃,需要考虑该函数更安全的实现方案。 ``` arch_signal_quit: LOAD a0, FRAME_OFF_SP(sp) addi a1, sp, CTX_REG_NR * REGBYTES...

Arch: RISC-V

### Describe problem solved by the proposed feature 能不能搞个把每次CI运行完的结果发到comment里面?合并者合并之前,或者PR的人能明显看到。 ### Describe your preferred solution _No response_ ### Describe possible alternatives _No response_

## 拉取/合并请求描述:(PR description) [ #### 为什么提交这份PR (why to submit this PR) > https://github.com/RT-Thread/rt-thread/issues/10847 #### 你的解决方案是什么 (what is your solution) - 修改后,内存大小未发生改变,再多次cat进行open/close操作后 ```sh msh /flash/log>memtrace memory heap address: name : heap...

Component

### Describe problem solved by the proposed feature > https://elm-chan.org/fsw/ff/updates.html - 目前rtt的版本为R0.15 ### Describe your preferred solution _No response_ ### Describe possible alternatives _No response_