Get started with Mbed OS on Arduino (Part 2)

The Blinky program could be considered the Hello World of Arduino Programming. In this section, we will rewrite the Blinky example for the Arduino using Mbed OS functions and classes. For reference, the regular Blinky is shown below.

Start by creating a new sketch, selecting the "Arduino Nano 33 BLE" under "Tools" > "Boards", and including the mbed.h header file in the program. Additionally, bring all members of the mbed, rtos andstd::chrono_literals namespaces into the current namespace through theusing directive. This is required to be able to use all the Mbed OS functions and classes without having to repeatedly prefix them withmbed::, rtos:: and std::chrono_literals::. The code should look as follows -

Unlike in Arduino which uses functions to control the mode and state of the pins, Mbed OS encapsulates this behavior in classes. The following code can be used to create a global object of the DigitalOut class that controls the state of the pin LED1. I have named the object led, but any valid identifier name can be used. LED1, in this case, refers to pin 13 on the Arduino (which contains the built-in LED). A list of all pin numbers and their corresponding Mbed pin names is given at the end of this blog for your reference. The code should now look as follows -

The above code implicitly sets the mode of pin 13, so the setup function can be left empty. Enter the following code in the loop, which switches on the pin, sleeps for a second, switches it off and waits for a second again. To set the state of the pin, the write method of the DigitalOut class has been used. To add delays within the program, the sleep_for function has been used from the ThisThread namespace. The function puts the current thread to sleep for the specified duration, during which other threads (or the OS) can execute.

Unlike the delay function used in regular Arduino programs, the function accepts the time as a chrono literal rather than an integer. The literal consists of a number with a suffix describing the units. For example, to create a delay of 500 milliseconds, the value 500ms should be used. For the current program, we use the value 1s to cause a delay of 1 second. A list of allowed suffixes for chrono literals are given at the end of this guide for your reference.

The complete code should look as follows -

This concludes the Blinky program. You may verify and upload the program as with a regular Arduino program to see the LED blink.

Now that we have finished blinking an LED, let's see how to spawn two threads to perform multiple tasks concurrently, therefore giving the effect of multi-tasking.

Once again, start by including the mbed.h header file and bringing members of the mbed and rtos namespaces into the current namespace. Also include all members from the std::chrono namespaces. This will be explained in a bit. Additionally, create two threads called t1 and t2 (you may use any valid identifier name, just make sure to substitute it in the remaining code) as shown below -

The threads will need functions to execute. Create two functions called func1 and func2. These functions should not return any value or accept any arguments. These functions will print the characters "A" and "B" to the Serial Monitor every 2 and 3 seconds respectively. The functions are also required to never return, so the code within them has been placed within infinite for(;;) loop blocks.

Finally, place the following code in the setup function to being Serial communication and start executing the threads using the provided functions. The loop function can be left empty.

The complete code should look as follows -

This concludes the multi-tasking example. You may verify and upload the program as with a regular Arduino Program and upload the Serial Monitor to see the output.

I hope you found this two-part series interesting and learnt something new. If you have any thoughts or queries, drop them in the comments below. I'd love to know them! Good Luck!

Allowed suffixes/units for chrono literals -

Note that while all of the above literals are syntactically valid, the sleep_for function only accepts integral hours, minutes, seconds and milliseconds. Providing floating-point versions of these literals, or literals with smaller units causes an error during compilation.

Pin mappings from Arduino to Mbed -