As this example runs on multiple different mbed OS development boards there might be combinations of board and RF shields that may, or may not, work together due to pin collision or other reasons.
This page aims to collect information regarding different hardware combinations.
Following RF shield have been used with mbed OS mesh examples.
- FIREFLY 6LOWPAN ARDUINO SHIELD
- Freedom Development Board for MCR20A
- X-NUCLEO-IDS01A4
- DVK-NCS36510-MBED-GEVB Development board, contains internal RF chip.
Following table shows which development boards have been tested. It does not present our current testing infrastructure, so we cannot guarantee all combinations but we do our best to ensure it is up to date.
| board / RF shield | Atmel | MCR20A | X-NUCLEO-IDS01A4 |
|---|---|---|---|
| K64F | Yes | Yes | |
| NUCLEO_F429ZI (1) | Yes | Yes | Modified, (3) |
| NUCLEO_F401RE | Yes | ||
| UBLOX_EVK_ODIN_W2 | Yes | No. (2) | |
| Onsemi NCS36510 (internal RF) | |||
| NXP KW24D (internal RF) | Yes (4) | ||
| NXP KW41Z (internal RF) | |||
| NUCLEO_L476RG (6) | Yes |
Notes:
- If ethernet driver is enabled, requires HW modifications if RF shield uses SPI1. See Driver notes and nanostack-borderrouter-private Issue #17
- Pin collision, see mesh-minimal Issue 55
- X-NUCLEO-IDS01A4 expansion board required modifications to be used in mbed OS. See Driver readme
- KW24D have MCR20A chip integrated. Use the same driver.
- KW24D has limited amount of memory (two banks of 32 RAM). For example, for the Thread end device use ARM or GCC_ARM. And for GCC_ARM use this heap configuration.
- NUCLEO_L476RF have LEDs on same pins that are used by Atmel RF shield so those should not be used in Light control demo. (LED1 & SPI_SCK == PA_5)