RIOT-OS/RIOT
RIOT-OS/RIOT
1
0
Fork 0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00
Code Releases Activity

boards: fix references in documentation

Browse Source
This commit is contained in:
Gunar Schorcht 2023-09-27 09:10:15 +02:00
parent 7a4c2a526f
commit c80591779f
33 changed files with 74 additions and 116 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
boards/adafruit-grand-central-m4-express/doc.txt
View File

@ -5,8 +5,7 @@
### General information ### General information
![Adafruit Grand Central M4 Expressboard] ![Adafruit Grand Central M4 Expressboard](https://cdn-learn.adafruit.com/assets/assets/000/068/748/medium800/adafruit_products_grand_central_top_angle.jpg?1546734839)
(https://cdn-learn.adafruit.com/assets/assets/000/068/748/medium800/adafruit_products_grand_central_top_angle.jpg?1546734839)
The main features of the board are: The main features of the board are:
- ATSAMD51 Cortex M4 running at 120 MHz - ATSAMD51 Cortex M4 running at 120 MHz

9
boards/airfy-beacon/doc.txt
View File

@ -11,13 +11,11 @@ usual micro-controller peripherals with a 2.4GHz radio that supports both
Nordics proprietary ShockBurst as well as Bluetooth Low Energy (BLE). Nordics proprietary ShockBurst as well as Bluetooth Low Energy (BLE).
The board was available via The board was available via
[Indiegogo] [Indiegogo](https://www.indiegogo.com/projects/airfy-beacon-make-your-smart-home-even-smarter).
(https://www.indiegogo.com/projects/airfy-beacon-make-your-smart-home-even-smarter).
## Hardware ## Hardware
![airfy-beacon] ![airfy-beacon](https://raw.githubusercontent.com/wiki/RIOT-OS/RIOT/images/airfy-beacon.jpg)
(https://raw.githubusercontent.com/wiki/RIOT-OS/RIOT/images/airfy-beacon.jpg)
| MCU | NRF51822QFAA | | MCU | NRF51822QFAA |
|:--------------------- |:--------------------------------- | |:--------------------- |:--------------------------------- |
@ -114,8 +112,7 @@ SWD data I/O: SWDIO <-----------> SWDIO (CN3, pin4)
The following image shows the wiring for an SWD flasher board: The following image shows the wiring for an SWD flasher board:
![airfy-beacon-flash-connect] ![airfy-beacon-flash-connect](https://raw.githubusercontent.com/wiki/RIOT-OS/RIOT/images/airfy-beacon-flash-connect.jpg)
(https://raw.githubusercontent.com/wiki/RIOT-OS/RIOT/images/airfy-beacon-flash-connect.jpg)
### Software ### Software
Debugging and programming this module works well with Debugging and programming this module works well with

3
boards/arduino-mega2560/doc.txt
View File

@ -72,8 +72,7 @@ to overwrite the bootloader on the MCU. Because of that it is a necessity to use
an ISP (in system programmer) to do the debugging. This isn't an issue because an ISP (in system programmer) to do the debugging. This isn't an issue because
all of the afore mentioned devices have ISP capabilities, but it requires some all of the afore mentioned devices have ISP capabilities, but it requires some
additional steps to get back normal operation after debugging: additional steps to get back normal operation after debugging:
* flash a new arduino bootloader on the device, e.g. [this one] * flash a new arduino bootloader on the device, e.g. [this one](https://raw.githubusercontent.com/arduino/Arduino-stk500v2-bootloader/master/goodHexFiles/stk500boot_v2_mega2560.hex)
(https://raw.githubusercontent.com/arduino/Arduino-stk500v2-bootloader/master/goodHexFiles/stk500boot_v2_mega2560.hex)
* restore the fuses to the default state. * restore the fuses to the default state.

10
boards/cc2538dk/doc.txt
View File

@ -42,8 +42,7 @@ internal bootloader, then run:
Activating this bootloader is NOT enabled if the flash content is in factory Activating this bootloader is NOT enabled if the flash content is in factory
default state (e.g. after unboxing). To set the bits in the CCA accordingly you default state (e.g. after unboxing). To set the bits in the CCA accordingly you
have to follow the guidelines found [here] have to follow the guidelines found [here](https://web.archive.org/web/20170610111337/http://processors.wiki.ti.com/index.php/CC2538_Bootloader_Backdoor).
(https://web.archive.org/web/20170610111337/http://processors.wiki.ti.com/index.php/CC2538_Bootloader_Backdoor).
To manage this first time access you have to download the To manage this first time access you have to download the
["Uniflash"](http://processors.wiki.ti.com/index.php/Category:CCS_UniFlash) tool ["Uniflash"](http://processors.wiki.ti.com/index.php/Category:CCS_UniFlash) tool
at TI's website. at TI's website.
@ -58,8 +57,7 @@ FTDI driver manually:
If the path `/sys/bus/usb-serial/drivers/ftdi_sio/` doesn't exist, you also If the path `/sys/bus/usb-serial/drivers/ftdi_sio/` doesn't exist, you also
have to load the module `ftdi_sio` by hand. Alternatively, you can install a have to load the module `ftdi_sio` by hand. Alternatively, you can install a
`udev` rule that configures this on device connection, see [this post on TI's `udev` rule that configures this on device connection, see [this post on TI's
E2E site] E2E site](https://e2e.ti.com/support/microcontrollers/c2000/f/171/p/359074/1843485#1843485)
(https://e2e.ti.com/support/microcontrollers/c2000/f/171/p/359074/1843485#1843485)
for details. for details.
RIOT will use /dev/ttyUSB1 by default, but if the UART is given a different RIOT will use /dev/ttyUSB1 by default, but if the UART is given a different
@ -114,8 +112,8 @@ $ csrutil status
System Integrity Protection status: disabled. System Integrity Protection status: disabled.
``` ```
Afterwards you'll be able to install this [driver] Afterwards you'll be able to install this
(https://cdn.sparkfun.com/assets/learn_tutorials/7/4/FTDIUSBSerialDriver_v2_3.dmg). [driver](https://cdn.sparkfun.com/assets/learn_tutorials/7/4/FTDIUSBSerialDriver_v2_3.dmg).
If everything goes OK reboot your Mac and then edit If everything goes OK reboot your Mac and then edit
`/System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/Info.plist` with a `/System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/Info.plist` with a

3
boards/cc2650stk/doc.txt
View File

@ -54,8 +54,7 @@ The arm-none-eabi toolchain works fine. You can get it
## Programming and Debugging ## Programming and Debugging
You'll need [debugging hardware] You'll need [debugging hardware](https://processors.wiki.ti.com/index.php?title=CC13xx_CC26xx_Tools_Overview#Debuggers).
(https://processors.wiki.ti.com/index.php?title=CC13xx_CC26xx_Tools_Overview#Debuggers).
So far, the [XDS110 debug probe](https://www.ti.com/tool/CC-DEVPACK-DEBUG) has So far, the [XDS110 debug probe](https://www.ti.com/tool/CC-DEVPACK-DEBUG) has
been tested. That bugger requires you to load a firmware onto it each time it been tested. That bugger requires you to load a firmware onto it each time it
powers up. The tool is contained in the Uniflash utility or the `CodeComposer powers up. The tool is contained in the Uniflash utility or the `CodeComposer

4
boards/common/slwstk6000b/doc.txt
View File

@ -90,8 +90,8 @@ symbols (`-gdwarf-2` for GCC).
### Clock selection ### Clock selection
There are several clock sources that are available for the different There are several clock sources that are available for the different
peripherals. You are advised to read [AN0004.1] peripherals. You are advised to read
(https://www.silabs.com/documents/public/application-notes/an0004.1-efm32-cmu.pdf) [AN0004.1](https://www.silabs.com/documents/public/application-notes/an0004.1-efm32-cmu.pdf)
to get familiar with the different clocks. to get familiar with the different clocks.
| Source | Internal | Speed | Comments | | Source | Internal | Speed | Comments |

27
boards/derfmega128/doc.txt
View File

@ -9,32 +9,23 @@ deRFmega128 modules are based on [ATmega128rfa1](http://ww1.microchip.com/downlo
MCUs. It include 16MHz main and 32K RTC crystalls and (depending on module type) integrated or not integrated 2.4GHz antenna. MCUs. It include 16MHz main and 32K RTC crystalls and (depending on module type) integrated or not integrated 2.4GHz antenna.
These modules are available in different variants: These modules are available in different variants:
- [deRFmega128-22M00] - [deRFmega128-22M00](https://www.dresden-elektronik.de/produkt/24-ghz-avr-derfmega128-22m00.html)
(https://www.dresden-elektronik.de/produkt/24-ghz-avr-derfmega128-22m00.html)
with integrated antenna, with integrated antenna,
- [deRFmega128-22M10] - [deRFmega128-22M10](https://www.dresden-elektronik.de/produkt/24-ghz-avr-derfmega128-22m10.html)
(https://www.dresden-elektronik.de/produkt/24-ghz-avr-derfmega128-22m10.html)
without integrated antenna. without integrated antenna.
- [deRFmega128-22A00] - [deRFmega128-22A00](https://www.dresden-elektronik.de/produkt/24-ghz-avr-derfmega128-22a00.html)
(https://www.dresden-elektronik.de/produkt/24-ghz-avr-derfmega128-22a00.html)
with connectors and integrated antenna, with connectors and integrated antenna,
- [deRFmega128-22A02] - [deRFmega128-22A02](https://www.dresden-elektronik.de/produkt/24-ghz-avr-derfmega128-22a02.html)
(https://www.dresden-elektronik.de/produkt/24-ghz-avr-derfmega128-22a02.html)
with connectors, but without integrated antenna. with connectors, but without integrated antenna.
- [deRFmega128-22C00] - [deRFmega128-22C00](https://www.dresden-elektronik.de/produkt/24-ghz-avr-derfmega128-22c00.html)
(https://www.dresden-elektronik.de/produkt/24-ghz-avr-derfmega128-22c00.html)
solderable with integrated antenna, solderable with integrated antenna,
- [deRFmega128-22C02] - [deRFmega128-22C02](https://www.dresden-elektronik.de/produkt/24-ghz-avr-derfmega128-22c02.html)
(https://www.dresden-elektronik.de/produkt/24-ghz-avr-derfmega128-22c02.html)
solderable without integrated antenna. solderable without integrated antenna.
# Hardware # Hardware
For details see the according data sheets: For details see the according data sheets:
- [deRFmega128-22M00 and deRFmega128-22M10] - [deRFmega128-22M00 and deRFmega128-22M10](https://www.dresden-elektronik.de/files/dresden-elektronik/content/downloads/datenblaetter/_outdated/deRFmega128-22M00-22M10-DBT-de.pdf)
(https://www.dresden-elektronik.de/files/dresden-elektronik/content/downloads/datenblaetter/_outdated/deRFmega128-22M00-22M10-DBT-de.pdf) - [deRFmega128-22A00 and deRFmega128-22C00](https://www.dresden-elektronik.de/files/dresden-elektronik/content/downloads/datenblaetter/_outdated/deRFmega128-22A00-C00-DBT-de.pdf)
- [deRFmega128-22A00 and deRFmega128-22C00] - [deRFmega128-22A02 and deRFmega128-22C02](https://www.dresden-elektronik.de/files/dresden-elektronik/content/downloads/datenblaetter/_outdated/deRFmega128-22A02-C02-DBT-de.pdf)
(https://www.dresden-elektronik.de/files/dresden-elektronik/content/downloads/datenblaetter/_outdated/deRFmega128-22A00-C00-DBT-de.pdf)
- [deRFmega128-22A02 and deRFmega128-22C02]
(https://www.dresden-elektronik.de/files/dresden-elektronik/content/downloads/datenblaetter/_outdated/deRFmega128-22A02-C02-DBT-de.pdf)
*/ */

9
boards/esp32-heltec-lora32-v2/doc.txt
View File

@ -22,8 +22,7 @@
2. [Board Configuration](#esp32_heltec_lora32_v2_board_configuration) 2. [Board Configuration](#esp32_heltec_lora32_v2_board_configuration)
3. [Board Pinout](#esp32_heltec_lora32_v2_pinout) 3. [Board Pinout](#esp32_heltec_lora32_v2_pinout)
4. [Using the OLED Display](#esp32_heltec_lora32_v2_oled_display) 4. [Using the OLED Display](#esp32_heltec_lora32_v2_oled_display)
5. [Optional Hardware Configurations] 5. [Optional Hardware Configurations](#esp32_heltec_lora32_v2_optional_hardware)
(#esp32_heltec_lora32_v2_optional_hardware)
3. [Flashing the Device](#esp32_heltec_lora32_v2_flashing) 3. [Flashing the Device](#esp32_heltec_lora32_v2_flashing)
## Overview {#esp32_heltec_lora32_v2_overview} ## Overview {#esp32_heltec_lora32_v2_overview}
@ -217,10 +216,8 @@ purpose. However, if optional off-board hardware modules are used,
these GPIOs may also be occupied, these GPIOs may also be occupied,
see section \ref esp32_heltec_lora32_v2_board_configuration for more information. see section \ref esp32_heltec_lora32_v2_board_configuration for more information.
The corresponding board schematics can be found [here for SX1276 version] The corresponding board schematics can be found [here for SX1276 version](https://github.com/Heltec-Aaron-Lee/WiFi_Kit_series/blob/master/SchematicDiagram/WiFi_LoRa_32(V2)/WIFI_LoRa_32_V2(868-915).PDF)
(https://github.com/Heltec-Aaron-Lee/WiFi_Kit_series/blob/master/SchematicDiagram/WiFi_LoRa_32(V2)/WIFI_LoRa_32_V2(868-915).PDF) and [here for SX1278 version](https://github.com/Heltec-Aaron-Lee/WiFi_Kit_series/blob/master/SchematicDiagram/WiFi_LoRa_32(V2)/WiFi_LoRa_32_V2(433%2C470-510).PDF).
and [here for SX1278 version]
(https://github.com/Heltec-Aaron-Lee/WiFi_Kit_series/blob/master/SchematicDiagram/WiFi_LoRa_32(V2)/WiFi_LoRa_32_V2(433%2C470-510).PDF).
\anchor esp32_heltec_lora_32_v2_pinout_img \anchor esp32_heltec_lora_32_v2_pinout_img
@image html "https://gitlab.com/gschorcht/RIOT.wiki-Images/raw/master/esp32/Heltec_WiFi_LoRa_32_V2_pinout.png" "WiFi LoRa 32 V2 Pintout Diagram" @image html "https://gitlab.com/gschorcht/RIOT.wiki-Images/raw/master/esp32/Heltec_WiFi_LoRa_32_V2_pinout.png" "WiFi LoRa 32 V2 Pintout Diagram"

8
boards/esp32-mh-et-live-minikit/doc.txt
View File

@ -21,17 +21,15 @@
1. [MCU](#esp32_mh_et_live_minikit_mcu) 1. [MCU](#esp32_mh_et_live_minikit_mcu)
2. [Board Configuration](#esp32_mh_et_live_minikit_board_configuration) 2. [Board Configuration](#esp32_mh_et_live_minikit_board_configuration)
3. [Board Pinout](#esp32_mh_et_live_minikit_pinout) 3. [Board Pinout](#esp32_mh_et_live_minikit_pinout)
4. [Optional Hardware Configurations] 4. [Optional Hardware Configurations](#esp32_mh_et_live_minikit_optional_hardware)
(#esp32_mh_et_live_minikit_optional_hardware)
3. [Flashing the Device](#esp32_mh_et_live_minikit_flashing) 3. [Flashing the Device](#esp32_mh_et_live_minikit_flashing)
## Overview {#esp32_mh_et_live_minikit_overview} ## Overview {#esp32_mh_et_live_minikit_overview}
The MH-ET LIVE MiniKit for ESP32 uses the ESP32-WROOM-32 module. It is a very The MH-ET LIVE MiniKit for ESP32 uses the ESP32-WROOM-32 module. It is a very
interesting development kit as it uses in the stackable Wemos D1 Mini format. interesting development kit as it uses in the stackable Wemos D1 Mini format.
Thus, all [shields for Wemos D1 mini] Thus, all [shields for Wemos D1 mini](https://docs.wemos.cc/en/latest/d1_mini_shield/index.html)
(https://docs.wemos.cc/en/latest/d1_mini_shield/index.html) for ESP8266 for ESP8266 can also be used with ESP32. Examples for such shields are:
can also be used with ESP32. Examples for such shields are:
- Micro SD-Card Shield - Micro SD-Card Shield
- MRF24J40 IEEE 802.15.4 radio Shield - MRF24J40 IEEE 802.15.4 radio Shield

7
boards/esp32-wemos-lolin-d32-pro/doc.txt
View File

@ -21,8 +21,7 @@
1. [MCU](#esp32_wemos_lolin_d32_pro_mcu) 1. [MCU](#esp32_wemos_lolin_d32_pro_mcu)
2. [Board Configuration](#esp32_wemos_lolin_d32_pro_board_configuration) 2. [Board Configuration](#esp32_wemos_lolin_d32_pro_board_configuration)
3. [Board Pinout](#esp32_wemos_lolin_d32_pro_pinout) 3. [Board Pinout](#esp32_wemos_lolin_d32_pro_pinout)
4. [Optional Hardware Configurations] 4. [Optional Hardware Configurations](#esp32_wemos_lolin_d32_pro_optional_hardware)
(#esp32_wemos_lolin_d32_pro_optional_hardware)
3. [Flashing the Device](#esp32_wemos_lolin_d32_pro_flashing) 3. [Flashing the Device](#esp32_wemos_lolin_d32_pro_flashing)
## Overview {#esp32_wemos_lolin_d32_pro_overview} ## Overview {#esp32_wemos_lolin_d32_pro_overview}
@ -164,8 +163,8 @@ any purpose. However, if optional off-board hardware modules are used,
these GPIOs may also be occupied, see section these GPIOs may also be occupied, see section
\ref esp32_wemos_lolin_d32_pro_board_configuration for more information. \ref esp32_wemos_lolin_d32_pro_board_configuration for more information.
The corresponding board schematic can be found [here] The corresponding board schematic can be found
(https://docs.wemos.cc/en/latest/_static/files/sch_d32_pro_v2.0.0.pdf). [here](https://docs.wemos.cc/en/latest/_static/files/sch_d32_pro_v2.0.0.pdf).
\anchor esp32_wemos_lolin_d32_pro_pinout_img \anchor esp32_wemos_lolin_d32_pro_pinout_img
@image html "https://gitlab.com/gschorcht/RIOT.wiki-Images/raw/master/esp32/Wemos_LOLIN_D32_PRO_pinout.png" "Wemos LOLIN D32 PRO pinout" @image html "https://gitlab.com/gschorcht/RIOT.wiki-Images/raw/master/esp32/Wemos_LOLIN_D32_PRO_pinout.png" "Wemos LOLIN D32 PRO pinout"

4
boards/esp32-wroom-32/doc.txt
View File

@ -170,8 +170,8 @@ and can be used for any purpose. However, if optional off-board hardware
modules are used, these GPIOs may also be occupied, see modules are used, these GPIOs may also be occupied, see
section \ref esp32_wroom_32_board_configuration for more information. section \ref esp32_wroom_32_board_configuration for more information.
The corresponding board schematics can be found her [here] The corresponding board schematics can be found
(https://dl.espressif.com/dl/schematics/esp32_devkitc_v4-sch-20180607a.pdf) [here](https://dl.espressif.com/dl/schematics/esp32_devkitc_v4-sch-20180607a.pdf)
@image html "https://gitlab.com/gschorcht/RIOT.wiki-Images/raw/master/esp32/ESP32-WROOM-32_pinouts.png" "EPS32-DevKitC V4 Pinout" @image html "https://gitlab.com/gschorcht/RIOT.wiki-Images/raw/master/esp32/ESP32-WROOM-32_pinouts.png" "EPS32-DevKitC V4 Pinout"

10
boards/esp32-wrover-kit/doc.txt
View File

@ -286,8 +286,7 @@ for ESP32 boards, see \ref esp32_riot.
Since the USB bridge based on FDI FT2232HL provides a JTAG interface for Since the USB bridge based on FDI FT2232HL provides a JTAG interface for
debugging through an USB interface, using ESP-WROVER-Kit V3 is the easiest debugging through an USB interface, using ESP-WROVER-Kit V3 is the easiest
and most convenient way for On-Chip debugging. Please refer the and most convenient way for On-Chip debugging. Please refer the
[ESP-IDF Programming Guide] [ESP-IDF Programming Guide](https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/jtag-debugging/index.html)
(https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/jtag-debugging/index.html)
for details on how to setup and how to use ESP-WROVER-Kit V3 and OpenOCD. for details on how to setup and how to use ESP-WROVER-Kit V3 and OpenOCD.
To use the JTAG interface, the `esp_jtag` module has to be enabled for To use the JTAG interface, the `esp_jtag` module has to be enabled for
@ -298,8 +297,8 @@ USEMODULE=esp_jtag make flash BOARD=esp32-wrover-kit ...
To flash and debug using OpenOCD, the precompiled version of OpenOCD for To flash and debug using OpenOCD, the precompiled version of OpenOCD for
ESP32 has to be installed using the install script while being in RIOT's ESP32 has to be installed using the install script while being in RIOT's
root directory, see also section [Using Local Toolchain Installation] root directory, see also section
(#esp32_local_toolchain_installation). [Using Local Toolchain Installation](#esp32_local_toolchain_installation).
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
dist/tools/esptool/install.sh openocd dist/tools/esptool/install.sh openocd
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@ -333,7 +332,6 @@ method for flashing with `esptool.py` can still be used. In that case, the
## Other Documentation Resources {#esp32_wrover_kit_other-resources} ## Other Documentation Resources {#esp32_wrover_kit_other-resources}
There is a comprehensive There is a comprehensive
[Getting Started Guide] [Getting Started Guide](https://docs.espressif.com/projects/esp-idf/en/latest/esp32/hw-reference/esp32/get-started-wrover-kit-v3.html)
(https://docs.espressif.com/projects/esp-idf/en/latest/esp32/hw-reference/esp32/get-started-wrover-kit-v3.html)
for the ESP-WROVER-KIT with a lot information about hardware configuration. for the ESP-WROVER-KIT with a lot information about hardware configuration.
*/ */

8
boards/esp32c3-wemos-mini/doc.txt
View File

@ -26,9 +26,9 @@
## Overview {#esp32c3_wemos_mini_overview} ## Overview {#esp32c3_wemos_mini_overview}
The Wemos ESP32-C3 mini board is an interesting development kit as it uses The Wemos ESP32-C3 mini board is an interesting development kit as it uses
in the stackable Wemos LOLIN D1 Mini format. Thus, all [shields for Wemos D1 mini] in the stackable Wemos LOLIN D1 Mini format. Thus, all
(https://docs.wemos.cc/en/latest/d1_mini_shield/index.html) for ESP8266 [shields for Wemos D1 mini](https://docs.wemos.cc/en/latest/d1_mini_shield/index.html)
can also be used with ESP32-C3. Examples for such shields are: for ESP8266 can also be used with ESP32-C3. Examples for such shields are:
- Micro SD-Card Shield - Micro SD-Card Shield
- MRF24J40 IEEE 802.15.4 radio Shield - MRF24J40 IEEE 802.15.4 radio Shield
@ -45,7 +45,7 @@ the need for a soldering iron or a breadboard.
This stackable platform was tested in an RIOT application with: This stackable platform was tested in an RIOT application with:
- MRF24J40 IEEE 802.15.4 radio Shield (contact gunar@schorcht.net for more information) - MRF24J40 IEEE 802.15.4 radio Shield (contact gunar@schorcht.net for more information)
- [BMP180 Pressure Sensor Shield] - [BMP180 Pressure Sensor Shield](http://www.esp8266learning.com/wemos-mini-bmp180-shield.php)
This application is a good example how easy it is with this board to create This application is a good example how easy it is with this board to create
different hardware applications. different hardware applications.

3
boards/esp32s2-lilygo-ttgo-t8/doc.txt
View File

@ -125,8 +125,7 @@ definition.
@image html https://ae01.alicdn.com/kf/H4a77f8684c144384a165d7a89476c602q.jpg "LILYGO TTGO T8 ESP32-S2 Pinout" width=900px @image html https://ae01.alicdn.com/kf/H4a77f8684c144384a165d7a89476c602q.jpg "LILYGO TTGO T8 ESP32-S2 Pinout" width=900px
The corresponding board schematics can be found [here] The corresponding board schematics can be found [here](https://github.com/Xinyuan-LilyGO/LilyGo-T-Display-S2/raw/master/schematic/ESP32_S2-Display.pdf)
(https://github.com/Xinyuan-LilyGO/LilyGo-T-Display-S2/raw/master/schematic/ESP32_S2-Display.pdf)
[Back to table of contents](#esp32s2_lilygo_ttgo_t8_toc) [Back to table of contents](#esp32s2_lilygo_ttgo_t8_toc)

4
boards/esp32s3-pros3/doc.txt
View File

@ -128,8 +128,8 @@ The following figure shows the pinout as configured by board definition.
@image html https://esp32s3.com/images/pins_pros3.jpg "ESP32 ProS3C-1 Pinout" width=900px @image html https://esp32s3.com/images/pins_pros3.jpg "ESP32 ProS3C-1 Pinout" width=900px
The corresponding board schematic can be found [here] The corresponding board schematic can be found
(https://github.com/UnexpectedMaker/esp32s3/raw/main/schematics/schematic-pros3.pdf) [here](https://github.com/UnexpectedMaker/esp32s3/raw/main/schematics/schematic-pros3.pdf)
[Back to table of contents](#esp32s3_pros3_toc) [Back to table of contents](#esp32s3_pros3_toc)

4
boards/esp32s3-wt32-sc01-plus/doc.txt
View File

@ -31,8 +31,8 @@ is a smart panel development platform with the ESP32-S3 SoC.
\image html https://raw.githubusercontent.com/sukesh-ak/ESP32-TUX/master/datasheet/WT32-SC01-Plus.png "ESP32-S3 WT32-SC01 Plus" width=400px \image html https://raw.githubusercontent.com/sukesh-ak/ESP32-TUX/master/datasheet/WT32-SC01-Plus.png "ESP32-S3 WT32-SC01 Plus" width=400px
It also available on the market as [Smart Panlee SC01 Plus] It also available on the market as
(http://en.smartpanle.com/product-item-15.html). [Smart Panlee SC01 Plus](http://en.smartpanle.com/product-item-15.html).
The ESP32-S3 WT32-SC01 Plus has following main features: The ESP32-S3 WT32-SC01 Plus has following main features:
<center> <center>

10
boards/esp8266-esp-12x/doc.txt
View File

@ -63,13 +63,12 @@ RIOT for ESP8266 boards, see \ref esp8266_riot.
## WEMOS LOLIN D1 mini {#esp8266_wemos_lolin_d1_mini} ## WEMOS LOLIN D1 mini {#esp8266_wemos_lolin_d1_mini}
[WEMOS LOLIN D1 mini] [WEMOS LOLIN D1 mini](https://www.wemos.cc/en/latest/d1/d1_mini.html)
(https://www.wemos.cc/en/latest/d1/d1_mini.html)
is a very interesting board series as it offers a stackable ESP8266 platform. is a very interesting board series as it offers a stackable ESP8266 platform.
This board can be easily extended with a large number of compatible peripheral This board can be easily extended with a large number of compatible peripheral
shields, e.g. a micro SD card shield, an IR controller shield, a battery shields, e.g. a micro SD card shield, an IR controller shield, a battery
shield, and various sensor and actuator shields, see [D1 mini shields] shield, and various sensor and actuator shields, see
(https://docs.wemos.cc/en/latest/d1_mini_shield/index.html) for more [D1 mini shields](https://docs.wemos.cc/en/latest/d1_mini_shield/index.html) for more
information. This makes it possible to create different hardware configurations information. This makes it possible to create different hardware configurations
without the need for a soldering iron or a breadboard. without the need for a soldering iron or a breadboard.
@ -88,8 +87,7 @@ microUSB port with flash / boot / reset logic that makes flashing much
easier. Their peripherals are equal and work with the default ESP8266 ESP-12x easier. Their peripherals are equal and work with the default ESP8266 ESP-12x
board definition. board definition.
For more information, see [D1 Boards] For more information, see [D1 Boards](https://docs.wemos.cc/en/latest/d1/d1_mini.html).
(https://docs.wemos.cc/en/latest/d1/d1_mini.html).
<center> <center>
Board | MCU | Flash | Antenna | Remark Board | MCU | Flash | Antenna | Remark

4
boards/esp8266-sparkfun-thing/doc.txt
View File

@ -93,8 +93,8 @@ Since the SparkFun Thing Dev board has an USB to Serial adapter on board,
this can done directly using the Micro USB. SparkFun Thin board has to be this can done directly using the Micro USB. SparkFun Thin board has to be
connected to the host computer using the FTDI interface and a FTDI USB to connected to the host computer using the FTDI interface and a FTDI USB to
Serial adapter/cable. For more information on how to program the Serial adapter/cable. For more information on how to program the
SparkFun Thing board, please refer the [ESP8266 Thing Hookup Guide] SparkFun Thing board, please refer the
(https://learn.sparkfun.com/tutorials/esp8266-thing-hookup-guide/programming-the-thing). [ESP8266 Thing Hookup Guide](https://learn.sparkfun.com/tutorials/esp8266-thing-hookup-guide/programming-the-thing).
@note Please make sure the FTDI USB to Serial adapter/cable uses 3.3 V. @note Please make sure the FTDI USB to Serial adapter/cable uses 3.3 V.

4
boards/ikea-tradfri/doc.txt
View File

@ -103,8 +103,8 @@ with `EFM32_USE_LEUART=1`.
### Clock selection ### Clock selection
There are several clock sources that are available for the different There are several clock sources that are available for the different
peripherals. You are advised to read [AN0004.1] peripherals. You are advised to read
(https://www.silabs.com/documents/public/application-notes/an0004.1-efm32-cmu.pdf) [AN0004.1](https://www.silabs.com/documents/public/application-notes/an0004.1-efm32-cmu.pdf)
to get familiar with the different clocks. to get familiar with the different clocks.
| Source | Internal | Speed | Comments | | Source | Internal | Speed | Comments |

6
boards/iotlab-m3/doc.txt
View File

@ -18,13 +18,11 @@
## Board HW overview ## Board HW overview
![IoT-LAB M3 Layout] ![IoT-LAB M3 Layout](https://www.iot-lab.info/wp-content/uploads/2013/10/m3opennode.png)
(https://www.iot-lab.info/wp-content/uploads/2013/10/m3opennode.png)
### Board Architecture ### Board Architecture
![IoT-LAB M3 Architecture] ![IoT-LAB M3 Architecture](https://github.com/iot-lab/iot-lab/wiki/Images/archiopenm3.png)
(https://github.com/iot-lab/iot-lab/wiki/Images/archiopenm3.png)
### [Board schematics](http://github.com/iot-lab/iot-lab/wiki/Docs/openm3-schematics.pdf) ### [Board schematics](http://github.com/iot-lab/iot-lab/wiki/Docs/openm3-schematics.pdf)
, wiring, pinouts, etc... , wiring, pinouts, etc...

3
boards/mulle/doc.txt
View File

@ -3,8 +3,7 @@
@ingroup boards @ingroup boards
@brief Support for Eistec Mulle IoT boards @brief Support for Eistec Mulle IoT boards
![Mulle] ![Mulle](https://web.archive.org/web/20161213064400im_/http://eistec.github.io/images/mulle-small.jpg)
(https://web.archive.org/web/20161213064400im_/http://eistec.github.io/images/mulle-small.jpg)
The Mulle is a miniature wireless Embedded Internet System suitable for The Mulle is a miniature wireless Embedded Internet System suitable for
wireless sensors connected to the Internet of Things, and designed for rapid wireless sensors connected to the Internet of Things, and designed for rapid

3
boards/native/doc.txt
View File

@ -6,8 +6,7 @@
[Family: native](https://github.com/RIOT-OS/RIOT/wiki/Family:-native) [Family: native](https://github.com/RIOT-OS/RIOT/wiki/Family:-native)
# Overview # Overview
![Terminal running RIOT native] ![Terminal running RIOT native](https://raw.githubusercontent.com/wiki/RIOT-OS/RIOT/images/Native.jpg)
(https://raw.githubusercontent.com/wiki/RIOT-OS/RIOT/images/Native.jpg)
# Hardware # Hardware
- CPU: Host CPU - CPU: Host CPU

3
boards/nrf51dongle/doc.txt
View File

@ -18,8 +18,7 @@ While the pca10000 contains an on-board J-Link debugger, the pca10005 boards
have to be flashed/debugged using the (included) external J-Link device. have to be flashed/debugged using the (included) external J-Link device.
## Hardware: ## Hardware:
![Nordic Semiconductor nrF51822 Development Kit] ![Nordic Semiconductor nrF51822 Development Kit](https://www.nordicsemi.com/-/media/Images/Products/DevKits/nRF51-Series/nRF51-Dongle-promo.png)
(https://www.nordicsemi.com/-/media/Images/Products/DevKits/nRF51-Series/nRF51-Dongle-promo.png)
| MCU | NRF51822QFAA | | MCU | NRF51822QFAA |
|:----------------- |:----------------------------------------------------------------------------- | |:----------------- |:----------------------------------------------------------------------------- |

3
boards/nucleo-f030r8/doc.txt
View File

@ -10,8 +10,7 @@ STM32F030R8 microcontroller with 8KiB of RAM and 64KiB of Flash.
## Hardware ## Hardware
![Nucleo64 F030R8] ![Nucleo64 F030R8](http://www.open-electronics.org/wp-content/uploads/2015/08/Figura2-500x467.png)
(http://www.open-electronics.org/wp-content/uploads/2015/08/Figura2-500x467.png)
## Pinout ## Pinout

3
boards/nucleo-f070rb/doc.txt
View File

@ -10,8 +10,7 @@ STM32F070RB microcontroller with 16KiB of RAM and 128KiB of Flash.
## Hardware ## Hardware
![Nucleo64 F070RB] ![Nucleo64 F070RB](http://www.open-electronics.org/wp-content/uploads/2015/08/Figura2-500x467.png)
(http://www.open-electronics.org/wp-content/uploads/2015/08/Figura2-500x467.png)
## Pinout ## Pinout

3
boards/nucleo-f446re/doc.txt
View File

@ -10,8 +10,7 @@ STM32F446RE microcontroller with 128KiB of RAM and 512KiB of Flash.
## Hardware ## Hardware
![Nucleo64 F446RE] ![Nucleo64 F446RE](http://www.open-electronics.org/wp-content/uploads/2015/08/Figura2-500x467.png)
(http://www.open-electronics.org/wp-content/uploads/2015/08/Figura2-500x467.png)
## Pinout ## Pinout

3
boards/openmote-cc2538/doc.txt
View File

@ -10,8 +10,7 @@ SoC combining an ARM Cortex-M3 microcontroller with an IEEE802.15.4 radio.
## Hardware ## Hardware
![openmote] ![openmote](https://raw.githubusercontent.com/wiki/RIOT-OS/RIOT/images/openmote.jpg)
(https://raw.githubusercontent.com/wiki/RIOT-OS/RIOT/images/openmote.jpg)
| MCU | CC2538SF53 | | MCU | CC2538SF53 |
|:------------- |:--------------------- | |:------------- |:--------------------- |

4
boards/slstk3701a/doc.txt
View File

@ -159,8 +159,8 @@ symbols (`-gdwarf-2` for GCC).
### Clock selection ### Clock selection
There are several clock sources that are available for the different There are several clock sources that are available for the different
peripherals. You are advised to read [AN0004.0] peripherals. You are advised to read
(https://www.silabs.com/documents/public/application-notes/an0004.0-efm32-cmu.pdf) [AN0004.0](https://www.silabs.com/documents/public/application-notes/an0004.0-efm32-cmu.pdf)
to get familiar with the different clocks. to get familiar with the different clocks.
| Source | Internal | Speed | Comments | | Source | Internal | Speed | Comments |

8
boards/sltb009a/doc.txt
View File

@ -130,8 +130,8 @@ expects data from the MCU with the same settings.
### Clock selection ### Clock selection
There are several clock sources that are available for the different There are several clock sources that are available for the different
peripherals. You are advised to read [AN0004.0] peripherals. You are advised to read
(https://www.silabs.com/documents/public/application-notes/an0004.0-efm32-cmu.pdf) [AN0004.0](https://www.silabs.com/documents/public/application-notes/an0004.0-efm32-cmu.pdf)
to get familiar with the different clocks. to get familiar with the different clocks.
| Source | Internal | Speed | Comments | | Source | Internal | Speed | Comments |
@ -249,8 +249,8 @@ make emulate
## Supported Toolchains ## Supported Toolchains
For using the Silicon Labs SLTB009A starter kit we strongly recommend For using the Silicon Labs SLTB009A starter kit we strongly recommend
the usage of the [GNU Tools for ARM Embedded Processors] the usage of the
(https://developer.arm.com/open-source/gnu-toolchain/gnu-rm) [GNU Tools for ARM Embedded Processors](https://developer.arm.com/open-source/gnu-toolchain/gnu-rm)
toolchain. toolchain.
## License information ## License information

3
boards/spark-core/doc.txt
View File

@ -12,8 +12,7 @@ when you're ready to integrate the Core into your product, you can.
## Hardware ## Hardware
![Spark-Core image] ![Spark-Core image](https://raw.githubusercontent.com/wiki/RIOT-OS/RIOT/images/spark-core.jpg)
(https://raw.githubusercontent.com/wiki/RIOT-OS/RIOT/images/spark-core.jpg)
Link to [product website](http://docs.spark.io/hardware/). Link to [product website](http://docs.spark.io/hardware/).

3
boards/stm32f3discovery/doc.txt
View File

@ -15,8 +15,7 @@ and 3-axis magnetometer).
The board does however not provide any radio capabilities, radio devices have The board does however not provide any radio capabilities, radio devices have
to be connected externally via I2C, SPI, UART or similar. to be connected externally via I2C, SPI, UART or similar.
See [this page] See [this page](https://github.com/RIOT-OS/RIOT/wiki/Getting-started-with-STM32F%5B0%7C3%7C4%5Ddiscovery-boards)
(https://github.com/RIOT-OS/RIOT/wiki/Getting-started-with-STM32F%5B0%7C3%7C4%5Ddiscovery-boards)
for a quick getting started guide. for a quick getting started guide.
## Hardware ## Hardware

3
boards/stm32mp157c-dk2/doc.txt
View File

@ -11,8 +11,7 @@ and no ROM Flash.
## Hardware ## Hardware
![STM32MP157C-DK2] ![STM32MP157C-DK2](https://www.st.com/bin/ecommerce/api/image.PF267415.en.feature-description-include-personalized-no-cpn-medium.jpg)
(https://www.st.com/bin/ecommerce/api/image.PF267415.en.feature-description-include-personalized-no-cpn-medium.jpg)
### MCU ### MCU

8
boards/waveshare-nrf52840-eval-kit/doc.txt
View File

@ -6,9 +6,8 @@
## Overview ## Overview
The [Waveshare nRF52840 Eval Kit] The [Waveshare nRF52840 Eval Kit](https://www.waveshare.com/NRF52840-Eval-Kit.htm)
(https://www.waveshare.com/NRF52840-Eval-Kit.htm) is an evaluation board is an evaluation board for the nRF52840 SoC with the following on-board components:
for the nRF52840 SoC with the following on-board components:
1. Arduino headers for connecting Arduino shields 1. Arduino headers for connecting Arduino shields
2. Raspberry Pi GPIO header for connecting Raspberry Pi HATs 2. Raspberry Pi GPIO header for connecting Raspberry Pi HATs
@ -29,8 +28,7 @@ for the nRF52840 SoC with the following on-board components:
16. TF card slot 16. TF card slot
17. CR2032 battery holder 17. CR2032 battery holder
![Waveshare nRF52840 Eval Kit] ![Waveshare nRF52840 Eval Kit](https://www.waveshare.com/img/devkit/accBoard/NRF52840-Eval-Kit/NRF52840-Eval-Kit-intro.jpg)
(https://www.waveshare.com/img/devkit/accBoard/NRF52840-Eval-Kit/NRF52840-Eval-Kit-intro.jpg)
Using the onboard Arduino and Raspberry Pi compatible headers, both Arduino Using the onboard Arduino and Raspberry Pi compatible headers, both Arduino
shields and Raspberry Pi HATs can be used at the same time. shields and Raspberry Pi HATs can be used at the same time.