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
{{ message }}
Repository navigation
Commit db569c7
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: _docs/tutorials/core/first_application_rtos/index.md
+11-35Lines changed: 11 additions & 35 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,17 @@ redirect_from:
14
14
15
15
This tutorial is an entry point for using micro-ROS in one of the supported RTOS: Nuttx, FreeRTOS, or Zephyr. The target hardware for this tutorial is the **[Olimex STM32-E407](https://www.olimex.com/Products/ARM/ST/STM32-E407/open-source-hardware)** evaluation board.
16
16
17
+
First of all, make sure that you have a **ROS 2** environment and the **micro-ROS build system** installed in the computer. If not, please check [**First micro-ROS application on Linux**](../first_application_linux/) tutorial in order to learn how to start with micro-ROS.
18
+
19
+
The build system's workflow in the case of embedded systems is a four-step procedure:
20
+
21
+
***Create step:** downloads all required code repositories and cross-compilation toolchains for the specific hardware platform. Among these repositories, it will also download a collection of ready to use micro-ROS apps.
22
+
***Configure step:** user can select in this step which app is going to be crosscompiled by the toolchain. Some other options, such as transport, agent address or port will be also selected in this step.
23
+
***Build step:** here is where cross-compilation takes place and platform-specific binaries are generated.
24
+
***Flash step:** generated binaries are flashed onto hardware platform memory so micro-ROS app can be executed.
25
+
26
+
Further information about micro-ROS build system can be found [here](https://github.com/micro-ROS/micro-ros-build/tree/dashing/micro_ros_setup)
27
+
17
28
## Required hardware
18
29
19
30
The following hardware will be used:
@@ -24,41 +35,6 @@ The following hardware will be used:
First of all, make sure that you have a **ROS 2** installation in the computer. On the **ROS 2** installation open a command line and follow these steps:
30
-
31
-
```bash
32
-
# Source the ROS 2 installation
33
-
source /opt/ros/$ROS_DISTRO/setup.bash
34
-
35
-
# Create a workspace and download the micro-ROS tools
***TIP:** if you are familiar with Docker containers, this image may be useful: [ros:dashing](https://hub.docker.com/layers/ros/library/ros/dashing/images/sha256-b796c14ea663537129897769aa6c715a851ca08dffd4875ef2ecaa31a4dbd431?context=explore)*
50
-
51
-
These instructions will setup a workspace with a ready to use micro-ROS build system. This build system is in charge of downloading the required cross-compilation tools and building the apps for the required platforms.
52
-
53
-
The build system's workflow is a four-step procedure:
54
-
55
-
***Create step:** downloads all required code repositories and cross-compilation toolchains for the specific hardware platform. Among these repositories, it will also download a collection of ready to use micro-ROS apps.
56
-
***Configure step:** user can select in this step which app is going to be crosscompiled by the toolchain. Some other options, such as transport, agent address or port will be also selected in this step.
57
-
***Build step:** here is where cross-compilation takes place and platform-specific binaries are generated.
58
-
***Flash step:** generated binaries are flashed onto hardware platform memory so micro-ROS app can be executed.
59
-
60
-
Further information about micro-ROS build system can be found [here](https://github.com/micro-ROS/micro-ros-build/tree/dashing/micro_ros_setup)
61
-
62
38
## Step 1: Creating a new firmware workspace
63
39
64
40
In order to accomplish the first step, a new firmware workspace can be created using the following command. The created workspace is platform and RTOS specific.
0 commit comments