You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Micro-ROS aims to **bring ROS 2 to a wide set of microcontrollers** to allow having first-class ROS 2 entities in the embedded world.
32
34
33
-
The main targets of micro-ROS are mid-range 32-bits microcontroller families. Usually, the minimum requirements for running micro-ROS in an embedded platform are memory constraints. Since memory usage in micro-ROS is a complex matter we provide a [complete article](/docs/concepts/benchmarking/benchmarking/) describing it and a tutorial on [how to tune the memory consuption](../../tutorials/advanced/microxrcedds_rmw_configuration/) in the micro-ROS middleware.
35
+
The main targets of micro-ROS are mid-range 32-bits microcontroller families. Usually, the minimum requirements for running micro-ROS in an embedded platform are memory constraints. Since memory usage in micro-ROS is a complex matter we provide a [complete article](/docs/concepts/benchmarking/benchmarking/) describing it and a tutorial on [how to tune the memory consuption](../../tutorials/advanced/microxrcedds_rmw_configuration/) in the micro-ROS middleware.
34
36
35
37
In general micro-ROS will need MCUs that have tens of kilobytes of RAM memory and communication peripherals that enable the micro-ROS [Client to Agent communication](../features/).
36
38
37
-
The micro-ROS hardware support is divided into two categories:
39
+
The micro-ROS hardware support is divided into two categories:
38
40
- Officially supported boards
39
41
- Community supported boards
40
42
@@ -44,6 +46,37 @@ The micro-ROS hardware support is divided into two categories:
44
46
45
47
The officially supported boards are those which have been carried out or tested officially, and to which LTS is guaranteed.
46
48
49
+
<divclass="hardwarecontainer">
50
+
<divclass="hardwareitem_description">
51
+
<h3><b>Renesas EK RA6M5</b> and <b>e2studio</b></h3>
Copy file name to clipboardExpand all lines: _docs/overview/rtos/index.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ permalink: /docs/overview/rtos/
20
20
}
21
21
22
22
.rtositem_description {
23
-
width: 50%;
23
+
width: 50%;
24
24
}
25
25
26
26
.rtositem_imageimg {
@@ -34,7 +34,7 @@ The standard approach to micro-ROS assumes a Real-Time Operating System undernea
34
34
35
35
Even though recent developments aim at loosening this requirement, with the integration into Arduino IDE as an important step towards true micro-ROS bare-metal support, the RTOS-based support remains the main entrypoint to micro-ROS.
36
36
37
-
To date, micro-ROS is supported by the RTOSes FreeRTOS, Zephyr, NuttX, in addition to Linux and Windows.
37
+
To date, micro-ROS is supported by the RTOSes FreeRTOS, Zephyr, NuttX, in addition to Linux and Windows.
38
38
All three RTOSes are downloaded natively with the [micro-ROS build system](https://github.com/micro-ROS/micro_ros_setup), and can be chosen when creating
39
39
a new firmware workspace.
40
40
Dedicated tutorials for running your first micro-ROS application on each of these Operating Systems can be found [here](https://micro-ros.github.io/docs/tutorials/core/first_application_rtos/).
@@ -62,7 +62,7 @@ FreeRTOS is distributed under the MIT license. It is known particularly for its
62
62
<li>Memory management tools</li>
63
63
<li>Standard and idle tasks available with assignable priorities</li>
0 commit comments