diff --git a/_docs/concepts/rtos/index.md b/_docs/concepts/rtos/index.md index bfd86ef0..50c45742 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/ext_tools/index.md b/_docs/overview/ext_tools/index.md index 26da8ada..907b1676 100644 --- a/_docs/overview/ext_tools/index.md +++ b/_docs/overview/ext_tools/index.md @@ -20,7 +20,7 @@ permalink: /docs/overview/ext_tools/ } .extplatitem_description { - width: 65%; + width: 65%; } .extplatitem_image img { @@ -51,7 +51,7 @@ The modules that exist up to date for integrating into external build systems ar
  • micro-ROS component for ESP-IDF on GitHub
  • ESP-IDF on GitHub
  • ESP-IDF docs
    • - + @@ -73,12 +73,12 @@ The modules that exist up to date for integrating into external build systems ar
  • micro-ROS module for Zephyr build system on GitHub
  • Primary GitHub repository for the Zephyr Project
  • Zephyr Project official webpage
    • - +
    - +
    diff --git a/_docs/overview/hardware/imgs/renesas.png b/_docs/overview/hardware/imgs/renesas.png new file mode 100644 index 00000000..2c8602ea Binary files /dev/null and b/_docs/overview/hardware/imgs/renesas.png differ diff --git a/_docs/overview/hardware/index.md b/_docs/overview/hardware/index.md index 6f0236bb..9d57c00f 100644 --- a/_docs/overview/hardware/index.md +++ b/_docs/overview/hardware/index.md @@ -20,21 +20,23 @@ permalink: /docs/overview/hardware/ } .hardwareitem_description { - width: 60%; + width: 60%; } .hardwareitem_image img { max-width: 100%; + max-height: 80%; + } 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. -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. +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. 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/). -The micro-ROS hardware support is divided into two categories: +The micro-ROS hardware support is divided into two categories: - Officially supported boards - Community supported boards @@ -44,6 +46,37 @@ The micro-ROS hardware support is divided into two categories: The officially supported boards are those which have been carried out or tested officially, and to which LTS is guaranteed. +
    +
    +

    Renesas EK RA6M5 and e2studio

    +
    + ✔ Key features: +
      +
    • MCU: ARM Cortex M-33 core @ 200 MHz
      • +
    • RAM: 512 kB
      • +
    • Flash: up to 2 MB
      • +
    • Peripherals: Ethernet, SCI, SPI, I2C, I2S, UART, USB, SDIO, CAN, GPIO, ADC/DAC, PWM
      • +
    + 🌎 Resources: + + ⚙ Supported platforms: + + 🔌 Supported transports: + UDP, UART, USB-CDC +
    +
    + +
    + +
    +
    +

    Espressif ESP32

    @@ -54,7 +87,7 @@ The officially supported boards are those which have been carried out or tested
  • RAM: 520 kB
  • Flash: 4 MB
  • Peripherals: Ethernet MAC, Wi-Fi 802.11 b/g/n, Bluetooth v4.2 BR/EDR, BLE, SPI, I2C, I2S, UART, SDIO, CAN, GPIO, ADC/DAC, PWM
    • - + 🌎 Resources: + 🌎 Resources: 🔌 Supported transports: - USB, WiFi UDP + USB, WiFi UDP
    @@ -117,7 +150,7 @@ The officially supported boards are those which have been carried out or tested
  • RAM: 264 kB
  • Flash: up to 16 MB
  • Peripherals: I2C, SPI, PIO...
    • - + 🌎 Resources: 🔌 Supported transports: - USB, UART + USB, UART @@ -149,7 +182,7 @@ The officially supported boards are those which have been carried out or tested
  • RAM: 320 kB
  • Flash: 1024 kB
  • Peripherals: 3-axis IMU, Dynamixel ports, SPI, I2C...
    • - + 🌎 Resources: 🔌 Supported transports: - USB, UART + USB, UART @@ -180,7 +213,7 @@ The officially supported boards are those which have been carried out or tested
  • RAM: 64 kB
  • Flash: 256 kB
  • Peripherals: USB, SPI, I2C, CAN, I2S...
    • - + 🌎 Resources: 🔌 Supported transports: - USB, UART + USB, UART @@ -211,7 +244,7 @@ The officially supported boards are those which have been carried out or tested
  • RAM: 1024 kB
  • Flash: 2048 kB
  • Peripherals: USB, PWM, SPI, I2C, CAN, I2S, SDIO,...
    • - + 🌎 Resources: 🔌 Supported transports: - USB, UART + USB, UART @@ -242,7 +275,7 @@ The officially supported boards are those which have been carried out or tested
  • RAM: 192 kB
  • Flash: 1 MB
  • Peripherals: 3 axis IMU, pressure sensor, SPI, I2C, UART, nRF51822 radio...
    • - + 🌎 Resources: 🔌 Supported transports: - Custom Radio Link + Custom Radio Link @@ -273,7 +306,7 @@ The officially supported boards are those which have been carried out or tested
  • RAM: 128 kB
  • Flash: 1 MB
  • Peripherals: Bluetooth, low-power RF module, 802.11 b/g/n, NFC, 2 digital microphone, temperature/humidity sensor, 3 axis IMU, ToF sensor...
    • - + 🌎 Resources: 🔌 Supported transports: - USB, UART, Ethernet UDP + USB, UART, Ethernet UDP @@ -304,7 +337,7 @@ The officially supported boards are those which have been carried out or tested
  • RAM: 196 kB
  • Flash: 1 MB
  • Peripherals: USB OTG, Ethernet, SD Card slot, SPI, CAN, I2C...
    • - + 🌎 Resources: 🔌 Supported transports: USB (Z, N), UART (Z, F, N), Ethernet UDP (F, N) -
    Note: Only RTOS initials used for convenience. +
    Note: Only RTOS initials used for convenience. @@ -340,7 +373,7 @@ The micro-ROS community supported boards are contributions of micro-ROS' users a
  • MCU: ARM Cortex-M3 AT91SAM3X8E
  • RAM: 96 kB
  • Flash: 512 kB
    • - + 🌎 Resources: 🔌 Supported transports: - USB, UART + USB, UART @@ -369,7 +402,7 @@ The micro-ROS community supported boards are contributions of micro-ROS' users a
  • MCU: ARM Cortex-M0+ ATSAMD21G18
  • RAM: 32 kB
  • Flash: 256 kB
    • - + 🌎 Resources: 🔌 Supported transports: - USB, UART + USB, UART @@ -403,7 +436,7 @@ The micro-ROS community supported boards are contributions of micro-ROS' users a
  • External tools: STM32CubeMX
    • 🔌 Supported transports: - UART + UART @@ -426,7 +459,7 @@ The micro-ROS community supported boards are contributions of micro-ROS' users a
  • External tools: STM32CubeMX
    • 🔌 Supported transports: - UART + UART @@ -449,7 +482,7 @@ The micro-ROS community supported boards are contributions of micro-ROS' users a
  • External tools: STM32CubeMX
    • 🔌 Supported transports: - UART + UART diff --git a/_docs/overview/rtos/index.md b/_docs/overview/rtos/index.md index 2b46275e..108ee3ea 100644 --- a/_docs/overview/rtos/index.md +++ b/_docs/overview/rtos/index.md @@ -20,7 +20,7 @@ permalink: /docs/overview/rtos/ } .rtositem_description { - width: 50%; + width: 50%; } .rtositem_image img { @@ -34,7 +34,7 @@ The standard approach to micro-ROS assumes a Real-Time Operating System undernea 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. -To date, micro-ROS is supported by the RTOSes FreeRTOS, Zephyr, NuttX, in addition to Linux and Windows. +To date, micro-ROS is supported by the RTOSes FreeRTOS, Zephyr, NuttX, in addition to Linux and Windows. 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 a new firmware workspace. 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
  • Memory management tools
  • Standard and idle tasks available with assignable priorities
  • Transport resources: TCP/IP and lwIP
    • - + FreeRTOS resources: @@ -98,7 +98,7 @@ Zephyr is a fairly new open-source RTOS, developed in a Linux Foundation Project
  • Multiple Scheduling Algorithms
  • Highly configurable/Modular for flexibility
  • Native Linux, macOS, and Windows Development
    • - + Zephyr resources: + NuttX resources: diff --git a/_posts/2020-10-01-zephyr_partnership.md b/_posts/2020-10-01-zephyr_partnership.md index d8f39bce..314f7348 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/scripts/cibuild b/scripts/cibuild index 06085ee9..cf238dc5 100755 --- a/scripts/cibuild +++ b/scripts/cibuild @@ -18,6 +18,7 @@ IGNORE_HREFS=${IGNORE_HREFS:+$IGNORE_HREFS,}$(ruby -e "puts %w{ vimeo.com omg.org twitter.com + renesas.com ieeexplore.ieee.org build.ros2.org ${ADDITIONS}