forked from RIOT-OS/RIOT
-
Notifications
You must be signed in to change notification settings - Fork 1
Thirdparty hardware support
OlegHahm edited this page Oct 22, 2014
·
1 revision
If the hardware dependent code for your platform can for license or other reasons can or should not become part of the official RIOT repository, you can still include external folders into the build process. Therefore, you have to define the two variables RIOTCPU
and RIOTBOARD
in your application pointing to the respective directories. For example:
RIOTCPU ?= ../../thirdparty_cpu
RIOTBOARD ?= ../../thirdparty_boards
These directories should have a similar structure like cpu
and boards
in the main RIOT repository, i.e. contain a sub-directory for each supported MCU/platform.
RIOT - The friendly Operating System for the Internet of Things
Homepage | [GitHub] (https://github.com/RIOT-OS/) | Developers Mailing List | Users Mailing List | Twitter @RIOT_OS
- Family: ARM
- Board: Airfy Beacon
- Board: Arduino Due
- Board: CC2538DK
- Board: CC2650STK
- Board: HikoB Fox
- Board: IoT LAB M3
- Board: LimiFrog-v1
- Board: mbed_lpc1768
- Board: MSB-IoT
- Board: MSBA2
- Board: Nucleo-L1
- Board: Nucleo-F334
- Board: Nucleo-F303
- Board: Nucleo-F091
- Board: Mulle
- Board: OpenMote
- Board: PCA1000x (nRF51822 Development Kit)
- Board: Phytec phyWAVE-KW22
- Board: RFduino
- Board: SAMR21-xpro
- Board: SAML21-xpro
- Board: Spark Core
- Board: STM32F0discovery
- Board: STM32F3discovery
- Board: STM32F4discovery
- Board: UDOO
- Board: yunjia-nrf51822
- Board: Zolertia remote
- Family: ATmega
- Board: Arduino Mega2560
- Family: MSP430
- Board: MSB-430H
- Board: TelosB
- Board: WSN430
- Board: Zolertia Z1
- Board: eZ430-Chronos
- Family: native
- Board: native
- Family: x86
- Board: Intel Galileo