Explain a few common questions first:
1。 Where does RT-Thread come from?
RT-Thread RTOS, the kernel was partially completed in the first half of 2006. Its founder originated from an old RTOS in China: Dulutos, and even some structures of BSP originated from Dulutos. But obviously different from DOOLOO RTOS, the kernel is completely rewritten, which is characterized by real-time, small and flexible, and introduces the object model of the kernel, abandoning the independence of the kernel object to the dynamic memory manager.
2.RT-Thread is used in commercial products &; Project, how to define copyright?
The kernel part of RT-Thread RTOS is completely written by us, and there are no other copyright issues. You can rest assured that it is safe in commercial products &; Used in engineering. For the use of RT-Thread in commercial products, we promise never to charge (users have the right to use it, so please bear the responsibility for using it). There are two more points to note:
The original copyright of RT-Thread RTOS code belongs to RT-Thread.
-In commercial products &; If RT-Thread RTOS is used in the project, please clearly indicate the use of RT-Thread in the product manual. If there is a serial output, please display the version information of RT-Thread when the system is started. If you use RT-Thread RTGUI, please keep RT-Thread LOGO.
3. Who developed 3.RT-ThreadRTOS and who maintained it?
At present, RT-Thread RTOS is developed and maintained by RT-Thread Studio in China.
4. Has 4.RT-ThreadRTOS been used in the product? Stability &; How's the BUG?
At present, several companies have used RT-Thread RTOS as the system platform for their product development, with good stability.
Just like there is no 100% perfect thing, there are bugs, and we will try our best to correct them as soon as possible after feedback.
5. Can I join the developer team of RT-Thread?
Sure！
We welcome anyone who is interested in RTOS, whether you are a student or a senior embedded system development engineer. RT-Thread developers usually rely on forums, emails and GTalk to communicate. Because there are many developers in Shanghai at present, developers' parties will be held in Shanghai from time to time.
6. What is the sustainable development of 6.RT-Thread and can it be profitable?
At present, the development of RT-Thread mainly depends on everyone's hobbies, and most of them are developed in their spare time. In the future, we will make profits through technical support, component customization, component development and auxiliary tools. From several open source softwares, commercial support is an indispensable part of software sustainable development, so we hope that more companies will choose RT-Thread RTOS as the system platform, which is a win-win situation for the company and the entire RT-Thread community. For the company, we can get a free RTOS suite, and at the same time, we can promote the development of this RTOS suite in a stable direction. For us, the development supported by the company will undoubtedly take the development of RT-Thread to the next level, which of course means that the support fees will be settled in the future.
=========
The question is over, and we begin to enter the theme of 0.3.x series. In terms of external release, I believe you have seen that RT-Thread has entered the intensive release cycle of 0.3.x, RT- Thread/STM32F 103VB has released three beta versions of 0.3 series, and RT-Thread/STM32F 103ZE has released two beta versions of 0.3 series, RT-Thread. Next, we will consider releasing the first beta version of RT-Thread/LM3S (Khan, the newly issued board has some hardware problems and has been fixed). ...
Most of these versions will include: kernel +finsh shell+ file system +lwip, etc.
0.3.0 series, RT-Thread also includes two major contents:
-Programming Guide documentation
-RTGUI graphical interface system
The programming guide has been revised all the time, but unfortunately the writing style is limited, so please don't be too picky about the documents. You are welcome to make any suggestions. As for the programming guide, it is also worth mentioning that this document is a programming guide, and all the places that need to be considered in programming on RT-Thread will be put forward. However, it is not a document for code analysis. Although some internal general structural frameworks may be mentioned, the code will not be analyzed line by line, so please pay more attention.
Another RTGUI component will be a key task in the future. The current plan is to realize an available handheld terminal device on the existing STM32F 103ZE development board, and of course, it will continue the habit of RT-Thread and release it in the form of open source. On s3c24 10/2440, this GUI is quite good, with object-oriented design and independent control object model, which gives users the greatest scalability.
In addition, Cao Xulong's x86 branch will be placed on the branch of 0.3.0 after completion. Through this branch, you can completely abandon the development board and experience RT-Thread on PC or VMWare/QEMU. At present, the branch of LPC series suffers from insufficient development board and slow progress. The last version of rt-thread/lpc2148 0.3.0beta1can only contain SD card and Ethernet port driver framework. Wyoujtg/ Fengcheng Shaozhu LPC2 106 will be transplanted in this series.
Now that the file system code has been released, it actually includes another branch: DFS-FAT. This branch, like DFS, is written by ourselves, and can also support bad block management on media such as NandFlash. Many test examples have been written and will be released after passing the stress test, instead of the current DFS-EFSL.