Multitasking on Arduino

Arduino Due

Arduino IDE

Arduino MKR ZERO (I2S bus & SD for sound, music & digital audio data)

RT-Thread IoT OS

<h3 >Background</h3>As most of the Arduino players, I started from Arduino Uno. And soon I collected a lot of shields. To drive those shields I used various libraries, which ate up all the memory space.So I moved to Arduino Mega and had a lot of fun, until I started working on a little bit more complex projects, like playing with display and sound.Recently, I upgrade my weapon again to Arduino Due which has completely different architecture (ARM Cortex-M) with my previous boards (AVR). A 32-bit core with &#34;huge&#34; memory space and much higher clock speed, without doubt, is a powerful weapon. However, to fully utilize the power, using a simple &#34;loop&#34; function may not be enough. That's the issue Arduino RT-Thread library project want to address.<h3 >RT-Thread</h3><a href="https://github.com/RT-Thread/rt-thread">RT-Thread</a> is a free and open source (Apache License 2.0) RTOS. Some unique features, like tiny shell (named FinSH), dynamic loading module and lots of device drivers, make it very interesting. Even though the most important feature is it has a very active community.<h3 >Let's Start</h3>The library is hosted on <a href="https://github.com/onelife/Arduino_RT-Thread">Github</a> and can be installed through &#34;Library Manager&#34;.Currently, there are two examples available which are also listing in &#34;CODE&#34; section. (More examples will be available later.)The first example &#34;Blink&#34; shows how to create and start a thread named &#34;Blink&#34;. The task of &#34;Blink&#34; thread is to blink the builtin LED with 1 second interval.The second example &#34;FinSH&#34; shows how to add user defined variable and command to the tiny shell. There are two user variables <code >led_id</code>, <code >led_state</code> and one user command <code >led()</code> implemented.<h3 >FinSH</h3>FinSH, the tiny shell accepts C-style input (e.g. <code >hello()</code>), supports auto-completion (e.g. type <code >lis[Tab]</code>) and history (after issued several commands try type <code >↑</code> and <code >↓</code>).It provides the following predefined commands.<ul ><li ><code >hello()</code>: print &#34;Hello RT-Thread!&#34;</li></ul><ul ><li ><code >version()</code>: print version information</li></ul><ul ><li ><code >list()</code>: print available command list</li></ul><ul ><li ><code >list_mem()</code>: print memory information</li></ul><ul ><li ><code >list_thread()</code>: print thread information</li></ul><ul ><li ><code >list_sem()</code>: print semaphore information</li></ul><ul ><li ><code >list_mutex()</code>: print mutex information</li></ul><ul ><li ><code >list_event()</code>: print event information</li></ul><ul ><li ><code >list_mb()</code>: print mailbox information</li></ul><ul ><li ><code >list_mq()</code>: print message queue information</li></ul><ul ><li ><code >list_memp()</code>: print memory pool information</li></ul><ul ><li ><code >list_timer()</code>: print timer information</li></ul>You may add your own command by two steps.<ul ><li >Firstly, define a function of cause. The return value can be &#34;<code >void</code>&#34; or any type. The recommendation is to return a value with &#34;<code >char</code>&#34;, &#34;<code >byte</code>&#34;, &#34;<code >short</code>&#34;, &#34;<code >unsigned short</code>&#34;, &#34;<code >int</code>&#34; or &#34;<code >unsigned int</code>&#34; type, because of these types can be interpreted well by FinSH. There is no limitation on parameters. (However, there do have limit of FinSH command length, which is 80 characters by default.) So any number and any type are fine.</li></ul><ul ><li >Secondly insert a line with <code >ADD_SHELL_CMD(</code><code >command_name, command description, function_name, return_type, parameter list</code><code >)</code> macro into &#34;<code >shell_cmd.h</code>&#34;. </li></ul>Following is a example of adding user command.<ul ><li >Define the function <code >led()</code>.</li></ul><pre ><code >unsigned int led(unsigned int id, byte state) { // use &#34;rt_kprintf()&#34; to print a message rt_kprintf(&#34;led%d=%d\ &#34;, id, state); if (id != 0) { return 1; } if (state) { digitalWrite(LED_BUILTIN, HIGH); } else { digitalWrite(LED_BUILTIN, LOW); } return 0; } </code></pre><ul ><li >Add a line to &#34;<code >shell_cmd.h</code>&#34;. </li></ul><pre ><code >ADD_SHELL_CMD(led, Turn on/off builtin LED, led, unsigned int, unsigned int id, rt_int32_t val) </code></pre>In the example above the command name and the function name are the same. However, they can be different. Then the command name becomes the alias of the function name. When issue command to FinSH, the command name should be used.You may also add your own variable by the similar steps.<ul ><li >Firstly, define a variable. The available types are &#34;<code >char</code>&#34;, &#34;<code >byte</code>&#34;, &#34;<code >char*</code>&#34;, &#34;<code >short</code>&#34;, &#34;<code >unsigned short</code>&#34;, &#34;<code >short*</code>&#34;, &#34;<code >int</code>&#34;, &#34;<code >unsigned int</code>&#34;, &#34;<code >int*</code>&#34; and &#34;<code >void*</code>&#34;.</li></ul><ul ><li >Secondly, add a line with <code >ADD_SHELL_VAR(variable_alias, variable description, variable_name, variable_type)</code> macro into &#34;<code >shell_var.h</code>&#34;. The corresponding variable types here are &#34;<code >finsh_type_char</code>&#34;, &#34;<code >finsh_type_uchar</code>&#34;, &#34;<code >finsh_type_charp</code>&#34;, &#34;<code >finsh_type_short</code>&#34;, &#34;<code >finsh_type_ushort</code>&#34;, &#34;<code >finsh_type_shortp</code>&#34;, &#34;<code >finsh_type_int</code>&#34;, &#34;<code >finsh_type_uint</code>&#34;, &#34;<code >finsh_type_intp</code>&#34; and &#34;<code >finsh_type_voidp</code>&#34;.</li></ul>Following is a example of adding user variables.<ul ><li >Define the variables.</li></ul><pre ><code > unsigned int led_id = 0; byte led_state = 1; </code></pre><ul ><li >Add two lines to &#34;<code >shell_var.h</code>&#34;. </li></ul><pre ><code >ADD_SHELL_VAR(id, LED ID, led_id, finsh_type_uint) ADD_SHELL_VAR(state, LED state, led_state, finsh_type_uchar) </code></pre>After uploaded the example sketch &#34;FinSH&#34;, open the &#34;Serial Monitor&#34; and you will see the tiny shell.<pre ><code >\\ | / - RT - Thread Operating System / | \\ 4.0.1 build Mar 8 2019 2006 - 2019 Copyright by rt-thread team finsh &gt; </code></pre>Try some predefined commands.<pre ><code >finsh &gt;hello() Hello RT-Thread! 0, 0x00000000 finsh &gt;list() --Function List: hello -- say hello world version -- show RT-Thread version information list -- list available commands list_mem -- list memory usage information list_thread -- list thread list_sem -- list semaphore in system list_mutex -- list mutex in system list_event -- list event in system list_mb -- list mail box in system list_mq -- list message queue in system list_memp -- list memory pool in system list_timer -- list timer in system led -- Turn on/off builtin LED --Variable List: dummy -- dummy variable for finsh id -- LED ID state -- LED state 0, 0x00000000 </code></pre>You may notice that after executed each command, the tiny shell prints a line with two values, &#34;<code >0, 0x00000000</code>&#34;. These two values are actually the return value of the underlying function, in decimal and hexadecimal formats. &#34;<code >hello()</code>&#34; and &#34;<code >list()</code>&#34; return &#34;<code >void</code>&#34;. Trying to issue &#34;<code >led(1, 0)</code>&#34;, you will get a different value (which is an error code). Now try the user defined command and variables. Having fun!<pre ><code >finsh &gt;id 0, 0x00000000 finsh &gt;state 1, 0x00000001 finsh &gt;led(id, state) led0=1 0, 0x00000000 finsh &gt;state=0 536870912, 0x20000000 finsh &gt;led(id, state) led0=0 0, 0x00000000 finsh &gt;led(1, 1) led1=1 1, 0x00000001 finsh &gt;led(0, 1) led0=1 0, 0x00000000 </code></pre><h3 >Next Steps</h3>I have not done the examples of showing how to use kernel utilities like semaphore, mutex, mailbox, memory pool and etc., although all these features are currently ready in the library. I will update the library and this article later. In the meantime, you may check <a href="https://github.com/RT-Thread/rt-thread/tree/master/examples/kernel">the examples from the original RT-Thread project</a>.I also plan to bring back some optional components (which I removed when porting) and develop some complex examples to show the potential of RT-Thread. Thanks for reading!<ul ><li ><a href="https://create.arduino.cc/projecthub/onelife/a-better-sd-library-with-rt-thread-242130">A better SD library with RT-Thread</a></li></ul><ul ><li >RT-Thread Primer (coming soon)</li></ul><h3 >Update</h3><ul ><li >Mar 15, 2019: The library is already available in &#34;Library Manager&#34;.</li></ul><ul ><li >Apr 17, 2019: <a href="https://create.arduino.cc/projecthub/onelife/a-better-sd-library-with-rt-thread-242130">FAT file system and SD card driver</a> are available with v0.4.4.</li></ul><ul ><li >May 6, 2019: From v0.5.1 onward, please use ADD_FINSH_CMD instead of ADD_SHELL_CMD.</li></ul>

Multitasking on Arduino

RT-Thread, a powerful multitasking tool optimized for Arduino. You are able to issue shell (FinSH) commands to control your hardware now!