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 5.2.0 commit 2f559906d6202c27142237ab4b1d893034a5b7c3 ### Hardware Type/Architectures VEXPRESS_A9 ### Develop Toolchain GCC ### Describe the bug Mutex initialization failure due to invalid lock state or resource exhaustion ###...

### RT-Thread Version 5.2.0 commit 2f559906d6202c27142237ab4b1d893034a5b7c3 ### Hardware Type/Architectures VEXPRESS_A9 ### Develop Toolchain GCC ### Describe the bug Log output fails due to serial device busy or buffer overflow. ###...

### RT-Thread Version 5.2.0 commit 2f559906d6202c27142237ab4b1d893034a5b7c3 ### Hardware Type/Architectures VEXPRESS_A9 ### Develop Toolchain GCC ### Steps to reproduce 1.Build RT-Thread 2.Use the following command to start the kernel with QEMU:...

### RT-Thread Version 5.2.0 commit 2f559906d6202c27142237ab4b1d893034a5b7c3 ### Hardware Type/Architectures VEXPRESS_A9 ### Develop Toolchain GCC ### Describe the bug I encountered another error in rt_vsnprintf function. ### Steps to reproduce 1.Build...

### RT-Thread Version 5.2.0 commit 2f559906d6202c27142237ab4b1d893034a5b7c3 ### Hardware Type/Architectures VEXPRESS_A9 ### Develop Toolchain GCC Hi, I'm encountering an unexpected rt_kprintf error. ### Steps to reproduce 1.Build RT-Thread 2.Use the following...

### Describe problem solved by the proposed feature 不是太理解为什么要将这个__RT_KERNEL_SOURCE__宏放置到每个单独文件的选项设置框里。 有个内核文件不小心从工程中移除了,再手动添加该文件就开始报错,找了好久最后使用env重刷工程才恢复正常,经过对比才发现有这个宏存在。手动添加文件后,还要在文件单独选项设置框里添加__RT_KERNEL_SOURCE__ ![image](https://github.com/user-attachments/assets/a8cb9efe-ba2a-4ade-a8d1-01b3e58a17f3) ### Describe your preferred solution _No response_ ### Describe possible alternatives _No response_

### RT-Thread Version 5.2.0 commit 2f559906d6202c27142237ab4b1d893034a5b7c3 ### Hardware Type/Architectures VEXPRESS_A9 ### Develop Toolchain GCC ### Describe the bug ### Steps to reproduce: 1.Build RT-Thread 2.Use the following command to start...

### RT-Thread Version master ### Hardware Type/Architectures all ### Develop Toolchain Other ### Describe the bug 1. 线程退出时若持有递归获取的锁不能完全释放 pr: https://github.com/RT-Thread/rt-thread/pull/9337 释放前把mutex获取计数设为1 用例:https://github.com/RT-Thread/rt-thread/pull/9365 2.线程take mutex等待时被意外resume唤醒触发assert pr:https://github.com/RT-Thread/rt-thread/pull/9357 用例:https://github.com/RT-Thread/rt-thread/pull/9353 ### Other additional context...

### Describe problem solved by the proposed feature ## 描述 #9194 在 QEMU 平台引入了 ILP32D 支持,同时也引入了内核对该 ABI 的支持需求。但内核、组件众多代码仍然隐式依赖、混用 intptr_t 与 RT-Thread 的架构关联类型 rt_base_t。 https://github.com/RT-Thread/rt-thread/blob/8249e71bcccffc8d4e96b32178f1e40863656ccf/include/rttypes.h#L36 如注释中清晰表达 —— `Nbit CPU related data...

Arch: RISC-V

## 拉取/合并请求描述:(PR description) [ #### 为什么提交这份PR (why to submit this PR) 之前提交过一份相关pr,不过由于64kb太小导致程序容易超过限制close了。前天有管理员回复,可以在readme里增加提醒。 此外,顺便整理了attachconfig为yml。 https://github.com/RT-Thread/rt-thread/pull/10258#issuecomment-2972145610 ![image](https://github.com/user-attachments/assets/5c072cd0-5524-4832-9957-cb7371674544) #### 你的解决方案是什么 (what is your solution) #### 请提供验证的bsp和config (provide the config and bsp) - BSP:...

BSP: STM32
BSP