BLE_API wrapper library for STMicroelectronics' BlueNRG Bluetooth Low Energy expansion board shield (Component)

Dependents:   Nucleo_Zumo_BLE_IDB04A1 contest_IOT5 contest_IOT6 contest_IOT_10 ... more

Fork of X_NUCLEO_IDB0XA1 by ST Expansion SW Team

Arduino Connector Compatibility Warning

X-NUCLEO-IDB04A1 and X-NUCLEO-IDB05A1 are Arduino compatible with an exception: instead of using pin D13 for the SPI clock, they use pin D3. The default configuration for this library is having the SPI clock on pin D3.

To be fully Arduino compatible, X-NUCLEO-IDB04A1 and X-NUCLEO-IDB05A1 need a small HW patch.

For X-NUCLEO-IDB04A1 this patch consists in removing zero resistor R10 and instead soldering zero resistor R11. For X-NUCLEO-IDB05A1 this patch consists in removing zero resistor R4 and instead soldering zero resistor R6.

In case you patch your board, then you also have to configure this library to use pin D13 to drive the SPI clock (see macro IDB0XA1_D13_PATCH in file x_nucleo_idb0xa1_targets.h).

If you use pin D13 for the SPI clock, please be aware that on STM32 Nucleo boards you may not drive the LED, otherwise you will get a conflict: the LED on STM32 Nucleo boards is connected to pin D13.

Referring to the current list of tested platforms (see X-NUCLEO-IDB04A1 and X-NUCLEO-IDB05A1 pages), the patch is required by ST-Nucleo-F103RB; ST-Nucleo-F302R8; ST-Nucleo-F411RE; and ST-Nucleo-F446RE.

Revision:
173:821942ac7d5a
Parent:
169:485bbcddf0c3
Child:
177:65d9b1b75fca
Child:
183:3bc6d59b9c81
--- a/source/BlueNRGDevice.cpp	Mon Nov 09 08:36:16 2015 +0100
+++ b/source/BlueNRGDevice.cpp	Tue Nov 10 06:25:29 2015 +0100
@@ -140,6 +140,14 @@
 	irq_.mode(PullDown); // betzw: set irq mode
 	irq_.rise(&HCI_Isr);
 
+	// betzw - WORKAROUND: exploit current mbed 'InterruptIn' implementation
+	//                     to handle spurious BlueNRG interrupts
+	irq_.fall(&HCI_Isr); // attach IRQ handler & enable IRQ 
+	irq_.fall(NULL);     // this doesn't clear the attachment but just disables the IRQ!
+                             // In this way spurious BlueNRG interrupts (e.g. IRQs happening
+	                     // even without being enabled) end up in a real IRQ handler 
+	                     // function rather than in a NULL pointer (i.e. in a hard fault).
+	
 	/* ToDo: Clear memory contents, reset the SD, etc. */
 	// By default, we set the device GAP role to PERIPHERAL
 	btle_init(BlueNRGGap::getInstance().getIsSetAddress(), GAP_PERIPHERAL_ROLE_IDB04A1);