diff --git a/_docs/concepts/rtos/index.md b/_docs/concepts/rtos/index.md index 3ba8275e8..625e17e7e 100644 --- a/_docs/concepts/rtos/index.md +++ b/_docs/concepts/rtos/index.md @@ -21,7 +21,7 @@ By clicking on the logos below, you'll be redirected to the Overview section, wh - +

FreeRTOS
Zephyr
Zephyr
NuttX
diff --git a/_docs/overview/docker_ci_status/index.md b/_docs/overview/docker_ci_status/index.md index ba903d491..45f67c64f 100644 --- a/_docs/overview/docker_ci_status/index.md +++ b/_docs/overview/docker_ci_status/index.md @@ -49,7 +49,7 @@ Most repositories can be found in GitHub's micro-ROS organization at [github.com | [micro-ROS-demos](https://github.com/micro-ROS/micro-ROS-demos) [![](https://img.shields.io/badge/ROS-galactic-brightgreen)](https://github.com/micro-ROS/micro-ROS-demos/tree/galactic) [![](https://img.shields.io/badge/ROS-foxy-brightgreen)](https://github.com/micro-ROS/micro-ROS-demos/tree/foxy) | Collection of generic demos, using publishers, subscribers, custom messages, services and graph introspection | [![Build status](https://img.shields.io/github/workflow/status/micro-ROS/micro-ROS-demos/CI)](https://github.com/micro-ROS/micro-ROS-demos/actions?query=workflow%3ACI) | [![](https://img.shields.io/github/issues/micro-ROS/micro-ROS-demos.svg)](https://github.com/micro-ROS/micro-ROS-demos/issues) [![](https://img.shields.io/github/issues-pr/micro-ROS/micro-ROS-demos.svg)](https://github.com/micro-ROS/micro-ROS-demos/pulls) | [![](https://img.shields.io/badge/read-the%20docs-blue)](https://github.com/micro-ROS/micro-ROS-demos/blob/foxy/README.md) | | [freertos_apps](https://github.com/micro-ROS/freertos_apps) [![](https://img.shields.io/badge/ROS-foxy-brightgreen)](https://github.com/micro-ROS/freertos_apps/tree/foxy) | Demo applications for FreeRTOS | [![](https://img.shields.io/badge/-unavailable-lightgrey)]() | [![](https://img.shields.io/github/issues/micro-ROS/freertos_apps.svg)](https://github.com/micro-ROS/freertos_apps/issues) [![](https://img.shields.io/github/issues-pr/micro-ROS/freertos_apps.svg)](https://github.com/micro-ROS/freertos_apps/pulls) | [![](https://img.shields.io/badge/read-the%20docs-blue)](https://github.com/micro-ROS/freertos_apps/blob/foxy/README.md) | | [zephyr_apps](https://github.com/micro-ROS/zephyr_apps) [![](https://img.shields.io/badge/ROS-foxy-brightgreen)](https://github.com/micro-ROS/zephyr_apps/tree/foxy) | Demo applications for Zephyr | [![](https://img.shields.io/badge/-unavailable-lightgrey)]() | [![](https://img.shields.io/github/issues/micro-ROS/zephyr_apps.svg)](https://github.com/micro-ROS/zephyr_apps/issues) [![](https://img.shields.io/github/issues-pr/micro-ROS/zephyr_apps.svg)](https://github.com/micro-ROS/zephyr_apps/pulls) | [![](https://img.shields.io/badge/read-the%20docs-blue)](https://github.com/micro-ROS/zephyr_apps/blob/foxy/README.md) | -| [raspbian_apps](https://github.com/micro-ROS/raspian_apps) [![](https://img.shields.io/badge/ROS-foxy-brightgreen)](https://github.com/micro-ROS/raspbian_apps/tree/foxy) | Demo applications for Raspbian | [![](https://img.shields.io/badge/-unavailable-lightgrey)]() | [![](https://img.shields.io/github/issues/micro-ROS/raspbian_apps.svg)](https://github.com/micro-ROS/raspbian_apps/issues) [![](https://img.shields.io/github/issues-pr/micro-ROS/raspbian_apps.svg)](https://github.com/micro-ROS/raspbian_apps/pulls) | [![](https://img.shields.io/badge/read-the%20docs-blue)](https://github.com/micro-ROS/raspbian_apps/blob/foxy/README.md) | +| [raspbian_apps](https://github.com/micro-ROS/raspbian_apps) [![](https://img.shields.io/badge/ROS-foxy-brightgreen)](https://github.com/micro-ROS/raspbian_apps/tree/foxy) | Demo applications for Raspbian | [![](https://img.shields.io/badge/-unavailable-lightgrey)]() | [![](https://img.shields.io/github/issues/micro-ROS/raspbian_apps.svg)](https://github.com/micro-ROS/raspbian_apps/issues) [![](https://img.shields.io/github/issues-pr/micro-ROS/raspbian_apps.svg)](https://github.com/micro-ROS/raspbian_apps/pulls) | [![](https://img.shields.io/badge/read-the%20docs-blue)](https://github.com/micro-ROS/raspbian_apps/blob/foxy/README.md) | | [nuttx_apps](https://github.com/micro-ROS/nuttx_apps) [![](https://img.shields.io/badge/ROS-dashing-brightgreen)](https://github.com/micro-ROS/nuttx_apps/tree/dashing) [![](https://img.shields.io/badge/ROS-foxy-brightgreen)](https://github.com/micro-ROS/nuttx_apps/tree/foxy) | Demo applications for NuttX (**discontinued**) | [![](https://img.shields.io/badge/-unavailable-lightgrey)]() | [![](https://img.shields.io/github/issues/micro-ROS/nuttx_apps.svg)](https://github.com/micro-ROS/nuttx_apps/issues) [![](https://img.shields.io/github/issues-pr/micro-ROS/nuttx_apps.svg)](https://github.com/micro-ROS/nuttx_apps/pulls) | [![](https://img.shields.io/badge/read-the%20docs-blue)](https://github.com/micro-ROS/nuttx_apps/blob/foxy/README.md) | | [Kobuki demo](https://github.com/micro-ROS/micro-ROS_kobuki_demo) | Kobuki (Turtlebot 2) controller demo application using micro-ROS in an Olimex board over NuttX | [![](https://img.shields.io/badge/-unavailable-lightgrey)]() | [![](https://img.shields.io/github/issues/micro-ROS/micro-ROS_kobuki_demo.svg)](https://github.com/micro-ROS/micro-ROS_kobuki_demo/issues) [![](https://img.shields.io/github/issues-pr/micro-ROS/micro-ROS_kobuki_demo.svg)](https://github.com/micro-ROS/micro-ROS_kobuki_demo/pulls) | [![](https://img.shields.io/badge/read-the%20docs-blue)](https://github.com/micro-ROS/micro-ROS_kobuki_demo/blob/master/README.md) | | [Crazyflie demo](https://github.com/micro-ROS/micro-ROS_crazyflie_demo) [![](https://img.shields.io/badge/ROS-foxy-brightgreen)](https://github.com/micro-ROS/micro-ROS_crazyflie_demo/tree/foxy) | Crazyflie drone demo application using micro-ROS over FreeRTOS | [![](https://img.shields.io/badge/-unavailable-lightgrey)]() | [![](https://img.shields.io/github/issues/micro-ROS/micro-ROS_crazyflie_demo.svg)](https://github.com/micro-ROS/micro-ROS_crazyflie_demo/issues) [![](https://img.shields.io/github/issues-pr/micro-ROS/micro-ROS_crazyflie_demo.svg)](https://github.com/micro-ROS/micro-ROS_crazyflie_demo/pulls) | [![](https://img.shields.io/badge/read-the%20docs-blue)](https://github.com/micro-ROS/micro-ROS_crazyflie_demo/blob/foxy/README.md) | diff --git a/_docs/overview/ext_tools/index.md b/_docs/overview/ext_tools/index.md index b853885bb..030575152 100644 --- a/_docs/overview/ext_tools/index.md +++ b/_docs/overview/ext_tools/index.md @@ -88,7 +88,7 @@ The modules that exist up to date for integrating into external build systems ar
- +
diff --git a/_docs/overview/hardware/index.md b/_docs/overview/hardware/index.md index 02bb32a07..a51221e3e 100644 --- a/_docs/overview/hardware/index.md +++ b/_docs/overview/hardware/index.md @@ -109,7 +109,7 @@ The officially supported boards are those which have been carried out or tested
- +
diff --git a/_docs/overview/rtos/index.md b/_docs/overview/rtos/index.md index 108ee3eaa..f148f681f 100644 --- a/_docs/overview/rtos/index.md +++ b/_docs/overview/rtos/index.md @@ -116,7 +116,7 @@ Zephyr is a fairly new open-source RTOS, developed in a Linux Foundation Project
- +
diff --git a/_docs/tutorials/advanced/microxrcedds_rmw_configuration/index.md b/_docs/tutorials/advanced/microxrcedds_rmw_configuration/index.md index 6782fad72..4a524d1c2 100644 --- a/_docs/tutorials/advanced/microxrcedds_rmw_configuration/index.md +++ b/_docs/tutorials/advanced/microxrcedds_rmw_configuration/index.md @@ -90,7 +90,7 @@ For example, in the [ping-pong application](https://micro-ros.github.io//docs/tu There are some build time parameters related to Client-to-Agent connection (such as **CONFIG_RMW_DEFAULT_UDP_PORT**, **CONFIG_RMW_DEFAULT_UDP_IP** and **CONFIG_RMW_DEFAULT_SERIAL_DEVICE**) that can be configured either at build time or at run-time. This means that you can set them in the [configuration file](https://github.com/micro-ROS/micro_ros_setup/blob/foxy/config/host/generic/client-host-colcon.meta) mentioned above and that micro-ROS provides a user configuration API for setting some RMW and middleware parameters at run-time. -The following example code shows the [API](https://github.com/micro-ROS/rmw-microxrcedds/blob/foxy/rmw_microxrcedds_c/include/rmw_uros/init_options.h) calls needed to set the agent's IP address, port or serial device: +The following example code shows the [API](https://github.com/micro-ROS/rmw_microxrcedds/blob/humble/rmw_microxrcedds_c/include/rmw_microros/init_options.h) calls needed to set the agent's IP address, port or serial device: ```c #include diff --git a/_docs/tutorials/core/first_application_rtos/index.md b/_docs/tutorials/core/first_application_rtos/index.md index ad03517c5..e3ce3049a 100644 --- a/_docs/tutorials/core/first_application_rtos/index.md +++ b/_docs/tutorials/core/first_application_rtos/index.md @@ -11,7 +11,7 @@ Micro-ROS currently supports three different RTOS, namely NuttX, FreeRTOS, and Z
NuttX
FreeRTOS -
Zephyr +
Zephyr diff --git a/_docs/tutorials/core/zephyr_emulator/imgs/4.jpg b/_docs/tutorials/core/zephyr_emulator/imgs/4.jpg deleted file mode 100644 index 6f3ad6433..000000000 Binary files a/_docs/tutorials/core/zephyr_emulator/imgs/4.jpg and /dev/null differ diff --git a/_docs/tutorials/core/zephyr_emulator/index.md b/_docs/tutorials/core/zephyr_emulator/index.md index d97f870d2..9cd7dd4d9 100644 --- a/_docs/tutorials/core/zephyr_emulator/index.md +++ b/_docs/tutorials/core/zephyr_emulator/index.md @@ -10,7 +10,7 @@ emulator (also known as [Native POSIX](https://docs.zephyrproject.org/latest/boa by testing a Ping Pong application.
- +
{% include first_application_common/build_system.md %} diff --git a/_docs/tutorials/programming_rcl_rclc/executor/executor.md b/_docs/tutorials/programming_rcl_rclc/executor/executor.md index e1db6489d..9bab34fae 100644 --- a/_docs/tutorials/programming_rcl_rclc/executor/executor.md +++ b/_docs/tutorials/programming_rcl_rclc/executor/executor.md @@ -300,7 +300,7 @@ return 0; } // main ``` -This completes the example. The source code can be found in the package rclc-examples [rclc-examples/example_executor_convenience.c](https://github.com/ros2/rclc/blob/master/rclc_examples/src/example_executor_convenience.c). +This completes the example. The source code can be found in the package rclc-examples [rclc-examples/example_executor_only_rcl.c](https://github.com/ros2/rclc/blob/master/rclc_examples/src/example_executor_only_rcl.c). ### Example 2: Triggered execution @@ -821,6 +821,6 @@ The following code will setup the executor accordingly: The custom structs `pub_trigger_object_t` are used to save the pointer of the handles. The timers `my_string_timer` and `my_int_timer` for the publishing executor; and, likewise, the subscriptions `my_string_sub` and `my_int_sub` for the subscribing executor. The configuration is done also with the `rclc_executor_set_trigger` by passing the trigger function and the trigger object, e.g. `pub_trigger` and `comm_obj_pub` for the `executor_pub`, respectivly. -The complete source code of this example can be found in the file [rclc-examples/example_executor_trigger.c](https://github.com/ros2/rclc/rclc_examples/example_executor_trigger.c). +The complete source code of this example can be found in the file [rclc-examples/example_executor_trigger.c](https://github.com/ros2/rclc/blob/humble/rclc_examples/src/example_executor_trigger.c). diff --git a/_posts/2019-03-20-micro-ROS_at_ERF2019.md b/_posts/2019-03-20-micro-ROS_at_ERF2019.md index 9d11ea592..618ce532b 100644 --- a/_posts/2019-03-20-micro-ROS_at_ERF2019.md +++ b/_posts/2019-03-20-micro-ROS_at_ERF2019.md @@ -3,7 +3,7 @@ title: micro-ROS at European Robotics Forum 2019 author: borjaouterelo --- -The [European Robotics Forum](https://www.eu-robotics.net/robotics_forum/), the most influential meeting of the robotics community in Europe, was held in Bucharest, Romania, in March 2019. Over 900 European robotics top experts attended the 10th edition of the conference. +The [European Robotics Forum](https://eu-robotics.net/eurobotics/activities/european-robotics-forum/), the most influential meeting of the robotics community in Europe, was held in Bucharest, Romania, in March 2019. Over 900 European robotics top experts attended the 10th edition of the conference. OFERA consortium, taking advantage of the opportunity, arranged one of their face-to-face meetings the days before the ERF as some of the members will also be attending to the forum. diff --git a/_posts/2020-03-03-micro-ROS-at-ERF2020.md b/_posts/2020-03-03-micro-ROS-at-ERF2020.md index e52079405..f5a46bb82 100644 --- a/_posts/2020-03-03-micro-ROS-at-ERF2020.md +++ b/_posts/2020-03-03-micro-ROS-at-ERF2020.md @@ -3,7 +3,7 @@ title: micro-ROS at European Robotics Forum 2020 author: ralph-lange --- -The 11th edition of the [**European Robotics Forum (ERF)**](https://www.eu-robotics.net/robotics_forum/) was held in Malaga, Spain from 3rd to 5th March 2020. The ERF is one of the most important events in the European robotics community and especially the place where almost all EU-funded robotics projects present their works. +The 11th edition of the [**European Robotics Forum (ERF)**](https://eu-robotics.net/eurobotics/activities/european-robotics-forum/) was held in Malaga, Spain from 3rd to 5th March 2020. The ERF is one of the most important events in the European robotics community and especially the place where almost all EU-funded robotics projects present their works. All partners of the EU project behind micro-ROS together organized a booth to display our latest developments. Most important, we showed a demo with a Kobuki platform, a Crazyflie quadcopter, and an IoT sensor running three different RTOS (NuttX, FreeRTOS, and Zephyr) supported by micro-ROS. In the front right of the following photo, you can also see our demo box to illustrate the different boot times and power consumptions of microprocessors versus microcontrollers running ROS 2 and micro-ROS, respectively. diff --git a/_posts/2020-10-01-zephyr_partnership.md b/_posts/2020-10-01-zephyr_partnership.md index 314f73486..603a8e33b 100644 --- a/_posts/2020-10-01-zephyr_partnership.md +++ b/_posts/2020-10-01-zephyr_partnership.md @@ -5,7 +5,7 @@ author: francesca-finocchiaro micro-ROS is now an Associate Partner of the [Zephyr Project](https://www.zephyrproject.org/)! -Zephyr +Zephyr Zephyr is a scalable open source Real-Time Operating System (RTOS) designed to fit resource constrained and embedded systems, with safety and security in mind. It forms part of [the Linux Foundation](https://www.linuxfoundation.org/), which supports a wide range of open source projects. Zephyr targets the same range of systems and applications with deterministic and time-critical constraints as micro-ROS, such as connected sensors and actuators, microcontrollers and small IoT devices of all kinds. micro-ROS and Zephyr complement each other by allowing to easily create heterogeneous distributed robotic systems and also integrate these devices seamlessly into the ROS 2 ecosystem. diff --git a/_posts/2021-04-13-ERF2021.md b/_posts/2021-04-13-ERF2021.md index 0fee024b0..16ecb02e0 100644 --- a/_posts/2021-04-13-ERF2021.md +++ b/_posts/2021-04-13-ERF2021.md @@ -3,7 +3,7 @@ title: micro-ROS at European Robotics Forum 2021 author: JanStaschulat --- -On April 13th 2021, we presented micro-ROS at the [European Robotics Forum 2021](https://www.eu-robotics.net/robotics_forum/) in a dedicated workshop organized by several partners of this project. First, Francesca Finoccharo (eProsima) presented in detail the micro-ROS architecture, the supported platforms, several demonstrations and reported on new features: A versatile API for custom transports, continuous fragment mode, static memory pools in the RMW and time synchronization between client and agent: +On April 13th 2021, we presented micro-ROS at the [European Robotics Forum 2021](https://eu-robotics.net/eurobotics/activities/european-robotics-forum/) in a dedicated workshop organized by several partners of this project. First, Francesca Finoccharo (eProsima) presented in detail the micro-ROS architecture, the supported platforms, several demonstrations and reported on new features: A versatile API for custom transports, continuous fragment mode, static memory pools in the RMW and time synchronization between client and agent: diff --git a/img/posts/logo-zephyr.jpg b/img/posts/logo-zephyr.jpg new file mode 100644 index 000000000..7e620b20b Binary files /dev/null and b/img/posts/logo-zephyr.jpg differ