Prototype RF driver for STM Sub-1 GHz RF expansion board based on the SPSGRF-868 module for STM32 Nucleo.
Prototype RF Driver for STM Sub-1 GHz RF Expansion Boards based on the SPSGRF-868 and SPSGRF-915 Modules for STM32 Nucleo
Currently supported boards:
Note, in order to use expansion board X-NUCLEO-IDS01A4
in mbed you need to perform the following HW modifications on the board:
- Unmount resistor
R4
- Mount resistor
R7
Furthermore, on some Nucleo development boards (e.g. the 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!
This driver can be used together with the 6LoWPAN stack (a.k.a. Nanostack).
Diff: source/libs/Contiki_STM32_Library/spirit1-config.h
- Revision:
- 44:aedd63cb0ce3
- Parent:
- 43:a512f909514a
- Child:
- 45:2d01cc9bc761
--- a/source/libs/Contiki_STM32_Library/spirit1-config.h Fri Dec 16 12:06:21 2016 +0100 +++ b/source/libs/Contiki_STM32_Library/spirit1-config.h Fri Dec 16 13:46:02 2016 +0100 @@ -42,14 +42,23 @@ #define SPIRIT_MAX_FIFO_LEN (96) // betzw - WAS: 600 /*---------------------------------------------------------------------------*/ -/* Define beyond macro when your network includes a platform - like the K64F from - * Freescale - which suffers from a not yet analyzed (HW) bug in delivering/receiving - * further interrupts by/from Spirit after having reached the RX FIFO threshold and - * elaborated the corresponding 'IRQ_RX_FIFO_ALMOST_FULL' interrupt. - * Furthermore, enable this macro if you want to use CSMA/CA. - * NOTE: this enables just a workaround!!! +/* Sometimes Spirit1 seems to NOT deliver (correctly) the 'IRQ_RX_DATA_READY' + * event. + * This can be avoided by reducing the maximum packet length to a value which + * is lower than the RX FIFO size. + * The mbed driver currently implements another workaround to this which allows + * stable packet delivery of packets with maximum length up to 128 bytes + * (which is the recommended 6LoWPAN payload length). + * Enable beyond macro if you want to use the version of the driver which avoids + * FIFO overflows by reducing packet length. + * + * NOTE: the non delivery of event 'IRQ_RX_DATA_READY' MUST still be + * investigated further deeply (both on HW & SW level)! + * Furthermore, the current limit of 128 bytes should also be overcome, + * which again requires a further analysis of the RX process, which + * currently seems to run into RX FIFO (most likely) overflow situations. */ -// #define RX_FIFO_THR_AO_CSMA_WA +// #define RX_FIFO_THR_WA /** * The MAX_PACKET_LEN is an arbitrary value used to define the two array @@ -57,10 +66,10 @@ * The SPIRIT1 supports with its packet handler a length of 65,535 bytes, * and in direct mode (without packet handler) there is no limit of data. */ -#ifdef RX_FIFO_THR_AO_CSMA_WA +#ifdef RX_FIFO_THR_WA #define MAX_PACKET_LEN (SPIRIT_MAX_FIFO_LEN-1) #else -#define MAX_PACKET_LEN (255) // betzw - WAS: SPIRIT_MAX_FIFO_LEN, but LEN_WIDTH is set to 7 so the variable payload length is theoretically from 0 to 255 bytes +#define MAX_PACKET_LEN (128) // betzw - WAS: SPIRIT_MAX_FIFO_LEN, but LEN_WIDTH is set to 7 so the variable payload length is theoretically from 0 to 255 bytes #endif /*---------------------------------------------------------------------------*/