From 71d79025a6fe79395c47482fb290ee882603782e Mon Sep 17 00:00:00 2001 From: Borja Outerelo Date: Wed, 17 Apr 2019 19:02:51 +0200 Subject: [PATCH 1/8] Fix broken link and improve consistency with rest of concepts pages. --- _docs/system_modes/index.md | 21 ++++++++++----------- 1 file changed, 10 insertions(+), 11 deletions(-) diff --git a/_docs/system_modes/index.md b/_docs/system_modes/index.md index 137b169d..573f1a67 100644 --- a/_docs/system_modes/index.md +++ b/_docs/system_modes/index.md @@ -5,17 +5,16 @@ redirect_from: /system_modes/ --- -Table of Contents -- [Lifecycle and System Modes](#lifecycle-and-system-modes) - - [Introduction and Goal](#introduction-and-goal) - - [Requirements](#requirements) - - [Background: ROS 2 Lifecycle](#background-ros-2-lifecycle) - - [Main Features](#main-features) - - [Extended Lifecycle](#extended-lifecycle) - - [System Hierarchy and Modes](#system-hierarchy-and-modes) - - [Mode manager](#mode-manager) - - [Roadmap](#roadmap) - - [Acknowledgments](#acknowledgments) +Table of contents +- [Introduction and Goal](#introduction-and-goal) +- [Requirements](#requirements) +- [Background: ROS 2 Lifecycle](#background-ros-2-lifecycle) +- [Main Features](#main-features) + - [Extended Lifecycle](#extended-lifecycle) + - [System Hierarchy and Modes](#system-hierarchy-and-modes) + - [Mode manager](#mode-manager) +- [Roadmap](#roadmap) +- [Acknowledgments](#acknowledgments) ## Introduction and Goal From de3d39b1a000b48851f534a8fd9af06789d7d1be Mon Sep 17 00:00:00 2001 From: Borja Outerelo Date: Wed, 17 Apr 2019 19:11:12 +0200 Subject: [PATCH 2/8] Fix 404 errors on tutorials. --- _docs/tutorials/debugging/vscode-start.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_docs/tutorials/debugging/vscode-start.md b/_docs/tutorials/debugging/vscode-start.md index 534d6399..5e161d85 100644 --- a/_docs/tutorials/debugging/vscode-start.md +++ b/_docs/tutorials/debugging/vscode-start.md @@ -4,7 +4,7 @@ permalink: /docs/tutorials/advanced/debugging-vscode/ author: Ingo Lütkebohle --- -This is a follow-up to [Debugging with gdb and openocd](/docs/tutorials/debugging-gdb-openocd/), because the set up done in that tutorial is a pre-requisite to debugging with Visual Studio Code. +This is a follow-up to [Debugging with gdb and openocd](/docs/tutorials/advanced/debugging-gdb-openocd/), because the set up done in that tutorial is a pre-requisite to debugging with Visual Studio Code. ## Motivation @@ -12,7 +12,7 @@ Visual Studio Code is a modern IDE that is very easy to extend and popular with ## Prerequisites - * All the prerequisites of [Debugging with gdb and openocd](/docs/tutorials/debugging-gdb-openocd/) + * All the prerequisites of [Debugging with gdb and openocd](/docs/tutorials/advanced/debugging-gdb-openocd/) * Cortex-M hardware (all of our standard boards are ARM based) * [Visual Studio Code](https://code.visualstudio.com/) From c6693350e2132817448ab4423d9d705edb10441f Mon Sep 17 00:00:00 2001 From: Borja Outerelo Date: Wed, 17 Apr 2019 23:24:21 +0200 Subject: [PATCH 3/8] Fix anchor points. --- .../advanced/nuttx_getting_started/index.md | 79 ++++++++++--------- 1 file changed, 40 insertions(+), 39 deletions(-) diff --git a/_docs/tutorials/advanced/nuttx_getting_started/index.md b/_docs/tutorials/advanced/nuttx_getting_started/index.md index f04d98b7..e194997d 100644 --- a/_docs/tutorials/advanced/nuttx_getting_started/index.md +++ b/_docs/tutorials/advanced/nuttx_getting_started/index.md @@ -8,33 +8,32 @@ the defconfig files for NuttX, OFERA project has created. # Example list - ## Olimex STM32-E407 -- [NSH over USB](#How-to-execute-NSH-over-USB-under-Olimex-STM32-E407) -- [NSH over UART](#How-to-use-NSH-over-UART) -- [Auxiliar UART port](#How-to-use-an-auxiliary-UART) -- [BMP180 through I2C](#How-to-execute-BMP180-example) -- [HIH6130 through I2C](#How-to-execute-HIH6130-example) -- [UDP echo server](#How-to-execute-UDPEcho-server-example) -- [TCP echo server](#How-to-execute-TCP-Echo-server-example) -- [MRF24J40-6LowPan through SPI](#How-to-use-MRF24j40-6LowPan) -- [ADC](#How-to-use-the-ADC-demo) -- [Telemetry](#How-to-execute-telemetry-app) -- [Power Manager](#How-to-execute-Power-Manager-example) -- [SD Card](#How-to-use-a-micro-SD-Card-in-the-Olimex-STM32-E407-board) -- [Micro XRCE-DDS through serial](#How-to-execute-Micro-XRCE-DDS) -- [micro-ROS demo](#How-to-use-micro-ROS-demo) +- [NSH over USB](#NSH-USB-Olimex) +- [NSH over UART](#NSH-UART-Olimex) +- [Auxiliar UART port](#Auxiliar-UART-Olimex) +- [BMP180 through I2C](#BMP180-Olimex) +- [HIH6130 through I2C](#HIH6130-Olimex) +- [UDP echo server](#UDPEcho-Olimex) +- [TCP echo server](#TCPEcho-Olimex) +- [MRF24J40-6LowPan through SPI](#MRF24j40-6LowPan-Olimex) +- [ADC](#ADC-Olimex) +- [Telemetry](#Telemetry-Olimex) +- [Power Manager](#Power-Manager-Olimex) +- [SD Card](#SD-Card-Olimex) +- [Micro XRCE-DDS through serial](#Micro-XRCE-DDS-Olimex) +- [micro-ROS demo](#micro-ROS-demo-Olimex) ## STM32L Discovery -- [NSH through UART](#How-to-execute-NSH-under-STM32L-Discovery) -- [BMP180 through I2C](#How-to-execute-BMP180-example) -- [HIH6130 through I2C](#How-to-execute-HIH6130-example) -- [Power Manager](#How-to-execute-Power-Manager-example) -- [Micro XRCE-DDS through serial](#How-to-execute-Micro-XRCE-DDS) +- [NSH through UART](#NSH-UART-Discovery) +- [BMP180 through I2C](#BMP180-Discovery) +- [HIH6130 through I2C](#HIH6130-Discovery) +- [Power Manager](#Power-Manager-Discovery) +- [Micro XRCE-DDS through serial](#Micro-XRCE-DDS-Discovery) @@ -63,7 +62,7 @@ The flash script will execute the proper command to upload the firmware to the b This section provides step-by-step tutorials so you can start executing the examples we have created. These tutorials starts using NuttX, using many different peripherals and tools, and ends up showing how to execute Micro XRCE-DDS client and micro-ROS client. -## How to execute NSH over USB under Olimex-STM32-E407 +## How to execute NSH over USB under Olimex-STM32-E40 {#NSH-USB-Olimex} NSH is a system console that can be use throught the next interfaces: USB,UART and Telnet. With this console you can execute apps, set system configuration and see the state of the system. @@ -119,7 +118,8 @@ If you don't know which interface is the micro USB, type `dmesg` command at a te ## How to execute NSH with the UART. -### Olimex-STM32-E407 +### Olimex-STM32-E407 {#NSH-UART-Olimex} + This board have the possibility to show the console through the UART or through USB. Go to the main folder of NuttX and execute the next command to configure the board: @@ -173,7 +173,8 @@ nsh> ``` -### STM32L1Discovery +### STM32L1Discovery {#NSH-UART-Discovery} + **This board only can show the NSH console throught the UART** Go to the main folder of NuttX and execute the next command to configure the board: @@ -225,7 +226,7 @@ nsh> ``` If you don't know which interface is the micro USB, type `dmesg` command at a terminal, this command should let you know which is the last USB device that has been connected to your computer and at what interface is attached. -## How to use an auxiliary UART: +## How to use an auxiliary UART {#Auxiliar-UART-Olimex} In this demo we will show how to use an auxiliary UART to send and receive messages. When we run this demos, we will send the first argument to the auxiliary terminal and we will wait for an input from the auxiliary terminal. @@ -265,7 +266,7 @@ BMP180 is a I2C barometric pressure sensor. With this sensor you can obtain the [BMP180 breakout link](https://www.adafruit.com/product/1603) -### Olimex STM32-E407 +### Olimex STM32-E407 {#BMP180-Olimex} Go to the main folder of NuttX and type the command to configure the board: `./scripts/configure.sh olimex-stm32-e407 bmp180` @@ -276,7 +277,7 @@ Compile: Upload: `./scripts/flash.sh olimex-stm32-e407` -### STM32L Discovery +### STM32L Discovery {#BMP180-Discovery} Go to the main folder of NuttX and type the command to configure the board: `./scripts/configure.sh stm32l1 bmp180` @@ -360,7 +361,7 @@ Pressure: 95985 Pressure: 95988 ``` -## How to execute HIH6130 example +## How to execute HIH6130 example {#HIH6130-Olimex} The HIH6130 is humidity/temperature that works through I2C interface. @@ -377,7 +378,7 @@ Compile: Upload: `./scripts/flash.sh olimex-stm32-e407` -### STM32L Discovery +### STM32L Discovery {#HIH6130-Discovery} Go to the main folder of NuttX and type the command to configure the board: `./scripts/configure.sh stm32l1 hih6130` @@ -468,7 +469,7 @@ Temperature: 31 �ºC Humidity: 44 Temperature: 31 �ºC Humidity: 44 ``` -## How to execute UDP Echo server example +## How to execute UDP Echo server example {#UDPEcho-Olimex} Go to the main folder of NuttX and type the next command to configure the board: `./scripts/configure.sh olimex-stm32-e407 udpecho` @@ -534,7 +535,7 @@ Now if you type something in the computer, the board should echo the same and sh ![image](imgs/udp_5.jpg) -## How to execute TCP Echo server example +## How to execute TCP Echo server example {#TCPEcho-Olimex} Go to the main folder of NuttX and type the next command to configure the board: @@ -631,7 +632,7 @@ The variables are shown in two hexadecimal numbers per each field. In case of th `0x85` = 133 -## How to use MRF24j40-6LowPan +## How to use MRF24j40-6LowPan {#MRF24j40-6LowPan-Olimex} With this demo, we'll be able to create a point to point connection with the MRF24J40 module using the protocol 6LowPan. This network, allows you to have hundreds of nodes with very little power consumption. One of the nodes is a TCP or UDP server, and the other nodes are TCP or UDP clients that they connect to the server. @@ -736,7 +737,7 @@ Now the UDP Client, will send a `HelloWorld` to the UDP Server. -## How to use the ADC demo +## How to use the ADC demo {#ADC-Olimex} In this demo we will take the analog value pin A1, that is attached to channel 4 of the ADC number 3. This demo only works in the Olimex board. @@ -759,7 +760,7 @@ If you execute the application typing `adc_simple`, you will see a measurement o ![image](imgs/adc_measure.png) -# How to execute CPU performance telemetry app +# How to execute CPU performance telemetry app {#Telemetry-Olimex} Go to the main folder of NuttX and type the next command to configure the board: `./scripts/configure.sh olimex-stm32-e407 telemetry` @@ -895,7 +896,7 @@ SigMask: 00000000 This example is simple. After some seconds, the board enter into a sleep mode that could be re-waken up, writing into the serial season. As the MCU is in low power mode, some data is lost, until the complete wake up is done. -### Olimex STM32-E407 +### Olimex STM32-E407 {#Power-Manager-Olimex} Go to the main folder of NuttX and type the command to configure the board: `./scripts/configure.sh olimex-stm32-e407 pm` @@ -906,7 +907,7 @@ Compile: Upload: `./scripts/flash.sh olimex-stm32-e407` -### STM32L Discovery +### STM32L Discovery {#Power-Manager-Discovery} Go to the main folder of NuttX and type the command to configure the board: `./scripts/configure.sh stm32l1 pm` @@ -939,7 +940,7 @@ Info : Listening on port 4444 for telnet connections Now open a serial session for connecting to the board. Once the prompt pops-up, do not type for some seconds and you will see that, in a point, if you type something, it will not appear at the command line. After some seconds, the command line will again work properly. -## How to use a micro SD-Card in the Olimex-STM32-E407 board +## How to use a micro SD-Card in the Olimex-STM32-E407 board {#SD-Card-Olimex} This demo it's only for the Olimex board. This demo shows how to write and read files from a SD card. @@ -974,7 +975,7 @@ In this example, we will execute Micro XRCE-DDS client in NuttX. This example ru For this demo we need two boards (It doesn't matter if it's the Olimex Board or the STM32L1), one will be the publisher which will send a topic with a shape, the color of the shape and the coordinate of the shape. The other board will subscribe to the topic. At this moment it's only possible to work through serial, but it could be possible to use with UDP and TCP in a future. -### Olimex STM32-E407 +### Olimex STM32-E407 {#Micro-XRCE-DDS-Olimex} Go to the main folder of NuttX and type the command to configure the board: `./scripts/configure.sh olimex-stm32-e407 microxrcedds` @@ -985,7 +986,7 @@ Compile: Upload: `./scripts/flash.sh olimex-stm32-e407` -### STM32L Discovery +### STM32L Discovery {#Micro-XRCE-DDS-Discovery} Go to the main folder of NuttX and type the command to configure the board: `./scripts/configure.sh stm32l1 microxrcedds` @@ -1089,7 +1090,7 @@ We have the STM32L1 as publisher, so we need to check the serial port number of Then, we have the Olimex as subscriber, so we need to follow the same steps as with the STM32L1 board. -## How to use micro-ROS demo: +## How to use micro-ROS demo {#micro-ROS-demo-Olimex} In this demo, we will use the alpha version of microROS for NuttX running under the Olimex-STM32-E407 board. With board running this demo we could create a ROS2 publisher or a ROS2 subscriber. From e315fc57b9da5f2840da339a851fe1097d74d8fb Mon Sep 17 00:00:00 2001 From: Borja Outerelo Date: Wed, 17 Apr 2019 23:31:48 +0200 Subject: [PATCH 4/8] Use correct product names, micro-ROS and Micro XRCE-DDS. --- .../advanced/nuttx_getting_started/index.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/_docs/tutorials/advanced/nuttx_getting_started/index.md b/_docs/tutorials/advanced/nuttx_getting_started/index.md index e194997d..c9312a09 100644 --- a/_docs/tutorials/advanced/nuttx_getting_started/index.md +++ b/_docs/tutorials/advanced/nuttx_getting_started/index.md @@ -41,8 +41,8 @@ the defconfig files for NuttX, OFERA project has created. For the examples listed below, please make use of the branch called `master` for this two repositories: -- [NuttX](https://github.com/microROS/Nuttx) fork, where NuttX RTOS is stored. -- [Apps](https://github.com/microROS/apps) fork, whee NuttX applications and examples are placed. +- [NuttX](https://github.com/micro-ROS/Nuttx) fork, where NuttX RTOS is stored. +- [Apps](https://github.com/micro-ROS/apps) fork, whee NuttX applications and examples are placed. ---------------------- @@ -1034,7 +1034,7 @@ And it should look like this: For this board we need two TTL232 cables. The first one is used to show the console. Connect the serial cable `RX` to pin `PA9` and `TX` to pin `PA10` and the GND wire to a `GND` pin. -Then, you need to connect to the second UART to use micro-XRCE-DDS: +Then, you need to connect to the second UART to use Micro XRCE-DDS: Connect the serial cable `RX` to pin `PA2` and `TX` to pin `PA3` and the GND wire to a `GND` pin. And it should look like this: @@ -1043,7 +1043,7 @@ And it should look like this: In this example, we use an Olimex board and a STM32L1 Board, but you can use any combination between STM32L1, Olimex Board and PC. Now we're going to execute the Agent in the PC. First, we need to check the port number of the serial cable that we want to use as Micro XRCE-DDS interface. -Note: You must installed micro-XRCE-DDS agent previously, follow this guide -> https://micro-xrce-dds.readthedocs.io/en/latest/installation.html +Note: You must installed Micro XRCE-DDS agent previously, follow this guide -> https://micro-xrce-dds.readthedocs.io/en/latest/installation.html Open a console and type the next command: `MicroXRCE-DDSAgent serial ` @@ -1092,14 +1092,14 @@ Then, we have the Olimex as subscriber, so we need to follow the same steps as w ## How to use micro-ROS demo {#micro-ROS-demo-Olimex} -In this demo, we will use the alpha version of microROS for NuttX running under the Olimex-STM32-E407 board. +In this demo, we will use the alpha version of micro-ROS for NuttX running under the Olimex-STM32-E407 board. With board running this demo we could create a ROS2 publisher or a ROS2 subscriber. The publisher creates and publishes as a topic a progressive count of integers (From 0 to 1000). The subscriber subscribes to that topic and shows the value of the number published. This demo is a little bit different as the other demos because we need to follow another path to configure it. We need to download the docker files of micro-ROS, executing the next command: -`git clone -b features/micro-ros https://github.com/microROS/docker` +`git clone -b features/micro-ros https://github.com/micro-ROS/docker` (Note: This repository might change of location) Now it's necessary to build the docker file, so type the next command: @@ -1124,11 +1124,11 @@ Now the board it's ready. Connect the serial cable (TTL232) to the computer and check which is the number of the serial port. Note: We need to install previously the micro-ROS agent. So you can follow the next guide to install it: -https://github.com/microROS/micro-ROS-doc/blob/master/docs/install_and_run.md +https://github.com/micro-ROS/micro-ROS-doc/blob/master/docs/install_and_run.md ## Run a publisher: -First you need to execute the **microROS Agent** in your computer using the next command: +First you need to execute the **micro-ROS Agent** in your computer using the next command: ``` cd ~/agent_ws/install/uros_agent/lib/uros_agent/ ./uros_agent serial From dceb532d536a5888f92dddd4198b0fe7a6396143 Mon Sep 17 00:00:00 2001 From: Borja Outerelo Date: Wed, 17 Apr 2019 23:54:31 +0200 Subject: [PATCH 5/8] Fix broken links. --- _docs/tutorials/getting_started/index.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/_docs/tutorials/getting_started/index.md b/_docs/tutorials/getting_started/index.md index 81918092..a1df19b2 100644 --- a/_docs/tutorials/getting_started/index.md +++ b/_docs/tutorials/getting_started/index.md @@ -5,16 +5,16 @@ permalink: /docs/tutorials/getting_started/ Table of contents -* [Running Micro XRCE-DDS example using prebuilt Docker](#running-Micro-XRCE-DDS-example-using-prebuilt-docker) -* [Running micro-ROS example using prebuilt Docker](#running-micro-ROS-example-using-prebuilt-docker) -* [Running rclc and rclcpp examples in your ROS2 workspace](#running-rclc-and-rclcpp-examples-in-your-ros2-workspace) +* [Running Micro XRCE-DDS example using prebuilt Docker](#Micro-XRCE-DDS-prebuilt-Docker) +* [Running micro-ROS example using prebuilt Docker](#micro-ROS-prebuilt-Docker) +* [Running rclc and rclcpp examples in your ROS2 workspace](#rclc-rclcpp-ROS2-ws) ## Introduction The aim of this section is to be able of running micro-ROS architecture examples using Docker files at your computer, without the need of any embedded board. -## Running micro-ROS example at Docker using prebuilt Docker +## Running micro-ROS example at Docker using prebuilt Docker {#micro-ROS-prebuilt-Docker} _Explain how to set up and run, @BorjaOuterelo need your help here_ @@ -24,7 +24,7 @@ At docker repo, we have one folder for each. ---------------- -## Running Micro XRCE-DDS example using prebuilt Docker +## Running Micro XRCE-DDS example using prebuilt Docker {#Micro-XRCE-DDS-prebuilt-Docker} _Explain how to set up and run, @BorjaOuterelo need your help here_ @@ -35,7 +35,7 @@ At docker repo, we have one folder for each. ---------------- -## Running rclc and rclcpp examples in your ROS2 workspace +## Running rclc and rclcpp examples in your ROS2 workspace {#rclc-rclcpp-ROS2-ws} There are also available examples that you could run building the code at your Linux or Windows computer. @@ -422,7 +422,7 @@ rad0_control_cpp.exe #### Callback-group-level Executor -Demo of the Callback-group-level Executor concept. See [Cpp/cbg-executor_ping-pong/README.md](Cpp/cbg-executor_ping-pong/README.md) for details. +Demo of the Callback-group-level Executor concept. See [cbg-executor_ping-pong/README.md](https://github.com/micro-ROS/micro-ROS_experiments/blob/experiment/cbg-executor-0.6.1/cbg-executor_ping-pong/README.md) for details. Run the micro-ROS Agent. From 93d3591af4a135bc172cae17484e9d64593e78e7 Mon Sep 17 00:00:00 2001 From: Borja Outerelo Date: Wed, 17 Apr 2019 23:55:40 +0200 Subject: [PATCH 6/8] Improve html errors checks. --- scripts/cibuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/cibuild b/scripts/cibuild index 4d5702d7..789f699a 100755 --- a/scripts/cibuild +++ b/scripts/cibuild @@ -2,4 +2,4 @@ set -e # halt script on error bundle exec jekyll build -bundle exec htmlproofer ./_site \ No newline at end of file +bundle exec htmlproofer --check_html --check-favicon --assume-extension ./_site From b6f11a6e64ee8746398c151df535006d5e143fae Mon Sep 17 00:00:00 2001 From: Borja Outerelo Date: Fri, 19 Apr 2019 19:08:58 +0200 Subject: [PATCH 7/8] Fix internal links. --- _docs/tutorials.md | 28 +++++++++---------- .../getting_started_embedded/index.md | 4 +-- .../getting_started_simulator/index.md | 4 +-- 3 files changed, 18 insertions(+), 18 deletions(-) diff --git a/_docs/tutorials.md b/_docs/tutorials.md index 0027e899..cae654f5 100644 --- a/_docs/tutorials.md +++ b/_docs/tutorials.md @@ -1,14 +1,14 @@ ---- -title: Tutorials -permalink: /docs/tutorials/ ---- - -content to be added by all - - -## Basic Tutorials - -## Intermediate Tutorials - - * [Debugging NuttX with gdb and OpenOCD](/docs/tutorials/debugging-gdb-openocd) - * [Debugging using Visual Studio Code](/docs/tutorials/debugging-vscode) \ No newline at end of file +--- +title: Tutorials +permalink: /docs/tutorials/ +--- + +content to be added by all + + +## Basic Tutorials + +## Intermediate Tutorials + +* [Debugging NuttX with gdb and OpenOCD](/docs/tutorials/advanced/debugging-gdb-openocd) +* [Debugging using Visual Studio Code](/docs/tutorials/advanced/debugging-vscode) diff --git a/_docs/tutorials/getting_started_embedded/index.md b/_docs/tutorials/getting_started_embedded/index.md index bf81de4e..7a829d2d 100644 --- a/_docs/tutorials/getting_started_embedded/index.md +++ b/_docs/tutorials/getting_started_embedded/index.md @@ -5,8 +5,8 @@ permalink: /docs/tutorials/getting_started_embedded/ Table of contents -* [Running micro-ROS example at an embedded board](#running-micro-ROS-example) -* [Running Micro XRCE-DDS example at an embedded board](#running-Micro-XRCE-DDS-example) +* [Running micro-ROS example at an embedded board](#running-micro-ros-example) +* [Running Micro XRCE-DDS example at an embedded board](#running-micro-xrce-dds-example) ## Introduction diff --git a/_docs/tutorials/getting_started_simulator/index.md b/_docs/tutorials/getting_started_simulator/index.md index e7f601b1..04184e57 100644 --- a/_docs/tutorials/getting_started_simulator/index.md +++ b/_docs/tutorials/getting_started_simulator/index.md @@ -6,8 +6,8 @@ author: Iñigo Muguruza Goenaga, Juan Muñoz Flores Table of contents -* [Running micro-ROS example in the simulator](#running-micro-ROS-example) -* [Running Micro XRCE-DDS example in the simulator](#running-Micro-XRCE-DDS-example) +* [Running micro-ROS example in the simulator](#running-micro-ros-example) +* [Running Micro XRCE-DDS example in the simulator](#running-micro-xrce-dds-example) ## Introduction From d2db650859dfe7db4b1b1259ba7df8489288579c Mon Sep 17 00:00:00 2001 From: Borja Outerelo Date: Mon, 22 Apr 2019 07:22:15 +0200 Subject: [PATCH 8/8] Ignore alt attribute for images. Fails only on 4xx HTTP errors. --- scripts/cibuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/cibuild b/scripts/cibuild index 789f699a..a0d6d7a0 100755 --- a/scripts/cibuild +++ b/scripts/cibuild @@ -2,4 +2,4 @@ set -e # halt script on error bundle exec jekyll build -bundle exec htmlproofer --check_html --check-favicon --assume-extension ./_site +bundle exec htmlproofer --check_html --check-favicon --assume-extension --empty-alt-ignore --only-4xx ./_site