Fork of my original MQTTGateway

Dependencies:   mbed-http

Committer:
vpcola
Date:
Sat Apr 08 14:43:14 2017 +0000
Revision:
0:a1734fe1ec4b
Initial commit

Who changed what in which revision?

UserRevisionLine numberNew contents of line
vpcola 0:a1734fe1ec4b 1 # Prototype RF Driver for STM Sub-1 GHz RF Expansion Boards based on the SPSGRF-868 Module for STM32 Nucleo #
vpcola 0:a1734fe1ec4b 2
vpcola 0:a1734fe1ec4b 3 Currently supported boards:
vpcola 0:a1734fe1ec4b 4 * [X-NUCLEO-IDS01A4](http://www.st.com/content/st_com/en/products/ecosystems/stm32-open-development-environment/stm32-nucleo-expansion-boards/stm32-ode-connect-hw/x-nucleo-ids01a4.html)
vpcola 0:a1734fe1ec4b 5
vpcola 0:a1734fe1ec4b 6 **Note**, in order to use expansion board `X-NUCLEO-IDS01A4` in mbed you need to perform the following HW modifications on the board:
vpcola 0:a1734fe1ec4b 7 * **Un**mount resistor `R4`
vpcola 0:a1734fe1ec4b 8 * **Mount** resistor `R7`
vpcola 0:a1734fe1ec4b 9
vpcola 0:a1734fe1ec4b 10 Furthermore, on some Nucleo development boards (e.g. the [NUCLEO_F429ZI](https://developer.mbed.org/platforms/ST-Nucleo-F429ZI/)), in order to be able to use Ethernet together with these Sub-1 GHz RF expansion boards, you need to compile this driver with macro `SPIRIT1_SPI_MOSI=PB_5` defined, while the development board typically requires some HW modification as e.g. described [here](https://github.com/ARMmbed/sal-nanostack-driver-stm32-eth)!
vpcola 0:a1734fe1ec4b 11
vpcola 0:a1734fe1ec4b 12 This driver is used with 6LoWPAN stack.