Rt thread

Last Updated on: February 18th, 2023 This article is a continuation of the Series on RT-Thread STM32 Tutorials and carries the discussion on RT-Thread RTOS and implementation with STM32. The aim of this series is to provide easy and practical examples that anyone can understand. In this Getting Started STM32 with RT-Thread RTOS post, we will see how to install the IDE and create the first program.You can find a video explanation of this tutorial here.Table of ContentsGetting Started STM32 with RT-Thread RTOSTools and Components RequiredRT-Thread StudioRT-Thread Studio FeaturesRT-Thread Studio InstallationProject CreationBuild ErrorSource CodeConnectionsFlashing and DemoVideo ExplanationWhat’s NextIn our last post, we have seen RT-Thread RTOS Introduction. In this post, we will start coding directly. Tools and Components RequiredSTM32F411 Dev Board (You can use any STM32F4 controller)RT-Thread StudioRT-Thread StudioWe need to use the IDE to write code. RT-Thread supports many IDEs including IAR, Keil, etc. But they have launched its Innovative and Powerful Embedded Integrated Development Environment called RT-Thread Studio. RT-Thread Studio is built on Eclipse but has innovative interface interaction designs and it is deep customization of Eclipse, easy and simple to use, even new developers can easily get started.RT-Thread Studio has the features of project creation and management, code editing, SDK management, RT-Thread configuration, build configuration, debugging configuration, program download, and debugging. Also, it combined the graphical configuration system with packages and component resources, reducing the duplication of work and improving development efficiency.RT-Thread Studio FeaturesRT-Thread studio is a one-stop development tool, it has an easy-to-use graphical configuration system and a wealth of software packages and components resources, which makes IoT development simple and efficient.The community version is free forever. Supports mainstream C/C++ language development. Powerful code editing and refactoring functionality. SDK Manager supports online downloads and updates the latest source package of RT-Thread. Easy-to-use project creation wizard can quickly validate prototypes. Brand new graphical configuration system, which supports both schema diagram and tree diagram configuration. The software package market offers a variety of package resources. Rich debugging facilities to quickly view and track code issues.Okay, Let’s stop the theory here. We will start creating the project.RT-Thread Studio InstallationPlease download the RT-Thread Studio from their official website.Install the RT-Thread Studio. Click Next.Accept the Agreement and click Next.Install the RT-Thread Studio in the proper location.Click Next and Install.Wait until it installs the RT-Thread Studio. Then launch RT-Thread Studio.That’s it. It will open the RT-Thread Studio.Project CreationFollow the below video to create a project.Build ErrorIf you use the latest RT-Thread Studio version 4.0.3 and the latest CSL (Chip Support Library) version 0.2.3, then you will get the below build error.../drivers/drv_usart.c:338:16: error: ‘struct serial_configure’ has no member named ‘flowcontrol’../drivers/drv_usart.c:340:10: error: ‘RT_SERIAL_FLOWCONTROL_NONE’ undeclared../drivers/drv_usart.c:343:10: error: ‘RT_SERIAL_FLOWCONTROL_CTSRTS’ undeclaredWe can solve this error by three methods.Downgrade

The RT-Thread OS version to 4.0.2, and use the latest CSL (0.2.3)Downgrade the CSL version to 0.0.2, and use the latest RT-Thread OS version (4.0.3)Use the RT-Thread OS version over 4.1.0, then you won’t see the error.We have explained the second method in the video. Please check that, if you don’t know how to do that. But we suggest you to use the third method. You can install that through the SDK manager.You can also change the Chip Support Library by below easy method.Right-click the Project name in the Project ExplorerClick Modify ProjectClick Chip support package versionThen select your desired CSL version.By this method, you can change the OS version also.Source CodeWe are not going to modify the source code. We will just use the default program now. The application main.c will be present under the HelloWorld/applications/main.c directory. You can also get the complete source code from GitHub./* * Copyright (c) 2006-2023, RT-Thread Development Team * * SPDX-License-Identifier: Apache-2.0 * * Change Logs: * Date Author Notes * 2023-02-10 RT-Thread first version */#include #define DBG_TAG "main"#define DBG_LVL DBG_LOG#include int main(void){ int count = 1; while (count++) { LOG_D("Hello RT-Thread!"); rt_thread_mdelay(1000); } return RT_EOK;}Build the source code. It should build without any errors.ConnectionsIn this project, we are using the STM32F411 and its UART1 (PA9 and PA10) for Debug prints.Connection diagramFlashing and DemoFlash the Code using RT-Thread Studio. Please refer to the below image.FlashingOnce you flash the code, then open any serial terminal application. Here, I am going to use the RT-Thread Studio’s inbuilt terminal. Set the baud rate (115200). You should see the print “Hello RT-Thread!“. Refer to the below images.Open TerminalConfigureOutputVideo ExplanationWhat’s NextIn our next post, we will discuss about the RT-Thread RTOS thread management and STM32 GPIOs.You can also read the below tutorials.Linux Device Driver TutorialsC Programming TutorialsFreeRTOS TutorialsNuttX RTOS TutorialsRTX RTOS TutorialsInterrupts BasicsI2C Protocol – Part 1 (Basics)I2C Protocol – Part 2 (Advanced Topics)STM32 TutorialsLPC2148 (ARM7) TutorialsPIC16F877A Tutorials8051 TutorialsUnit Testing in C TutorialsESP32-IDF TutorialsRaspberry Pi TutorialsEmbedded Interview TopicsReset Sequence in ARM Cortex-M4BLE BasicsVIC and NVIC in ARMSPI – Serial Peripheral Interface ProtocolSTM32F7 Bootloader TutorialsRaspberry PI Pico TutorialsSTM32F103 Bootloader TutorialsRT-Thread RTOS TutorialsZephyr RTOS Tutorials – STM32Zephyr RTOS Tutorials – ESP32AUTOSAR TutorialsUDS Protocol TutorialsProduct ReviewsSTM32 MikroC Bootloader TutorialVHDL TutorialsEmbedded Software | Firmware | Linux Devic Driver | RTOSHi, I am a tech blogger and an Embedded Engineer. I am always eager to learn and explore tech-related concepts. And also, I wanted to share my knowledge with everyone in a more straightforward way with easy practical examples. I strongly believe that learning by doing is more powerful than just learning by reading. I love to do experiments. If you want to help or support me on my journey, consider sharing my

Riscv-rtthread Release VersionEnglish | 中文OverviewThis release version is based on the RISC-V architecture, integrating the RT-Thread kernel while retaining the RT-Thread build system. We have also restructured the RT-Thread repository to make the structure clearer and focus developers on their own product development. The components and device drivers integrated in this release version have been tested on actual hardware and projects, and bugs are fixed regularly. Out-of-the-box usage is supported.WhyWhy create such a release version?The official RT-Thread repository supports multiple RISC-V architecture chips, but the official repository focuses on the kernel and lacks targeted upper-layer applications.HowCancel online package management and adopt an integrated components and device_driver approach. The components and device drivers integrated in this release version have been tested and will be regularly fixed.If the required components or device drivers are not integrated, they can still be integrated using the package approach. You can add source "$PKGS_DIR/Kconfig" to the Kconfig file of the required project to integrate it, and use the default RT-Thread package download method.Optimize the RT-Thread build system to allow developers to focus more on application development. The application (examples/applications) is the entry point, and the BSP is canceled, replaced by boards. Developers can select the target board and components to compile in the application, completing the application configuration.Reduce the barrier to entry for users, allowing first-time users to quickly get started.Simplifying the environment setup is the first step in hand. We have optimized the process of setting up the development environment, minimizing the number of software packages installed.Optimized the RT-Thread toolchain configuration method, automatically downloading the toolchain, eliminating the need for manual download and configuration.Optimized the chip packaging script, allowing this project to be cross-platform compiled, currently supporting Windows x86_64, Linux x86_64/arm64/riscv64, macOS x86_64/riscv64 series operating systems.Directory.├── applications # Applications├── examples # Examples│ └── get-started #

Normally.macOSPlease install the following software packages using the brew tool:$ brew install scons u-boot-tools dtcConfiguration and CompilationApplications in this release version are located in the examples and applications directories. Using the examples/get-started/blink directory as an example:$ cd examples/get-started/blinkProject ConfigurationYou can select the default configuration based on the current running target development board. The config file is located in the boards/configs directory.$ scons --defconfig=milkv_duo256m_sd_c906_configMenu-based configurationSelect the current target board to compile, then configure the RT-Thread kernel and software. Save the configuration after completion.Compilation$ cd examples/get-started/blink$ scons -j8After compilation, firmware for the corresponding development board will be generated in the output directory of examples/get-started/blink.How to UseThe method of burning/run for each different development board may vary slightly. Please refer to the documentation for the corresponding development board (e.g., board/sopogo) for details.Burn the firmware to the development board, and refer to the documentation for the corresponding development board for the burning method.After burning, reset the development board, and you will see the RT-Thread startup information.FAQLinux/macOS prompt "u-boot-tools not installed"$ mkimage not found, please check ...Solution: Install u-boot-tools$ sudo apt-get install -y u-boot-tools device-tree-compileror$ brew install u-boot-tools dtcOtherWe still follow the code style and License of the official RT-Thread repository. Please refer to RT-Thread Coding Style for code style.More information can be found in the RT-Thread Official Documentation Center.Welcome to join us and help improve this release version. Welcome to submit issues or PRs.Welcome to contact me: flyingcys@163.com