Merge pull request #249 from adafruit/develop

Multiple peripheral connection support

Author: hathach

README.md

@@ -51,18 +51,6 @@ There are two methods that you can use to install this BSP. We highly recommend
 
 - [SiLabs CP2104 driver](http://www.silabs.com/products/mcu/pages/usbtouartbridgevcpdrivers.aspx) is required for USB to Serial when using with Feather nRF52832
 
-## Arduino BLE Application Support
-
-This Arduino core contains basic BLE peripheral mode helper classes and an initial peripheral mode
-API. These helper classes and APIs aim to make it easier to work with the Nordic SoftDevice that
-contains Nordic's official Bluetooth Low Energy stack. You are also free to use the Nordic SDK to
-generate your own example code, since all of the SoftDevice header files are included in your
-projects by default.
-
-To see a list of example sketches that make use of these helper classes, select the appropriate
-board from the `Tools > Board` menu item, and then in the `Examples` menu look for the list of
-examples sketched for the selected board.
-
 ## Bootloader Support
 
 ### Upgrade existing Bootloader
@@ -74,7 +62,7 @@ Bluefruit's Bootloader is self-upgradable, you could upgrade to the latest Bootl
 - Select `Tools > Burn Bootloader`
 - **WAIT** until the process complete ~30 seconds
 
-Note: close the Serial Monitor before you click "Burn Bootloader". Afterwards, you shouldn't close the Arduino IDE, unplug the Feather, launch Serial Monitor etc ... to abort the process. There is a high chance it will brick your device! Do this with care and caution.
+**Note: close the Serial Monitor before you click "Burn Bootloader". Afterwards, you shouldn't close the Arduino IDE, unplug the Feather, launch Serial Monitor etc ... to abort the process. There is a high chance it will brick your device! Do this with care and caution.**
 
 ### Burning new Bootloader
 
@@ -111,36 +99,6 @@ $ nrfjprog --program feather_nrf52832_bootloader.hex -f nrf52
 $ nrfjprog --reset -f nrf52
 ```
 
-## Misc Notes
-
-#### nRF52DK Jlink Issue on macOS
-
-If developing with the nRF52DK on macOS, there is a bug where only 64 bytes can be sent
-over the USB CDC interface, which will prevent you from using the serial bootloader from
-the Arduino IDE with an error like this:
-
-```
-Upgrading target on /dev/cu.usbmodem1421 with DFU package /private/var/folders/86/hb2vp14n5_5_yvdz_z8w9x_c0000gn/T/arduino_build_267869/nRF51Blinky.ino.zip. Flow control is disabled.
-
-
-Timed out waiting for acknowledgement from device.
-
-Failed to upgrade target. Error is: No data received on serial port. Not able to proceed.
-
-Possible causes:
-- bootloader, SoftDevice or application on target does not match the requirements in the DFU package.
-- baud rate or flow control is not the same as in the target bootloader.
-- target is not in DFU mode. If using the SDK examples, press Button 4 and RESET and release both to enter DFU mode.
-```
-
-To resolve this and enable 512 byte packets over USB serial, you must disable the
-Mass Storage Device interface on the JLink-OB, which will free up two of the 512 byte
-USB end points. (For details see [this article](https://wiki.segger.com/index.php?title=J-Link-OB_SAM3U).)
-
-You can do so by running `JLinkExe` from the command line, and then entering the
-`MSDDisable` command, and power cycling your nRF52DK. To re-enable MSD support, do the same
-but enter the `MSDEnable` command.
-
 ## Credits
 
 This core is based on [Arduino-nRF5](https://github.com/sandeepmistry/arduino-nRF5) by Sandeep Mistry,
@@ -154,4 +112,3 @@ The following libraries are used:
 - [nrfx](https://github.com/NordicSemiconductor/nrfx) for peripherals driver
 - [littlefs](https://github.com/ARMmbed/littlefs) for internal file system
 - [fatfs by elm-chan](http://elm-chan.org/fsw/ff/00index_e.html) for external file system
-- Segger Sysview for debugging.

boards.txt

@@ -43,7 +43,7 @@ feather52832.build.extra_flags=-DNRF52832_XXAA -DNRF52 -DARDUINO_NRF52_FEATHER
 # SofDevice Menu
 # Ram & ROM size varies depending on SoftDevice (check linker script)
 
-feather52832.menu.softdevice.s132v6=0.2.7 (s132 6.1.1)
+feather52832.menu.softdevice.s132v6=0.2.9 (s132 6.1.1)
 feather52832.menu.softdevice.s132v6.build.sd_flags=-DS132
 feather52832.menu.softdevice.s132v6.build.sd_name=s132
 feather52832.menu.softdevice.s132v6.build.sd_version=6.1.1
@@ -103,7 +103,7 @@ feather52840.build.extra_flags=-DNRF52840_XXAA -DARDUINO_NRF52_FEATHER
 # SofDevice Menu
 # Ram & ROM size varies depending on SoftDevice (check linker script)
 
-feather52840.menu.softdevice.s140v6=0.2.7 (s140 6.1.1)
+feather52840.menu.softdevice.s140v6=0.2.9 (s140 6.1.1)
 feather52840.menu.softdevice.s140v6.build.sd_flags=-DS140
 feather52840.menu.softdevice.s140v6.build.sd_name=s140
 feather52840.menu.softdevice.s140v6.build.sd_version=6.1.1
@@ -125,44 +125,44 @@ feather52840.menu.debug.l3.build.debug_flags=-DCFG_DEBUG=3 -Os
 #**********************************************
 # Bluefruit Metro nRF52840 Express Board
 #**********************************************
-metro52840.name=Adafruit Bluefruit nRF52840 Metro Express
-metro52840.bootloader.tool=bootburn
+#metro52840.name=Adafruit Bluefruit nRF52840 Metro Express
+#metro52840.bootloader.tool=bootburn
 
 # Upload
-metro52840.upload.tool=nrfutil
-metro52840.upload.protocol=nrfutil
-metro52840.upload.use_1200bps_touch=true
-metro52840.upload.wait_for_upload_port=true
+#metro52840.upload.tool=nrfutil
+#metro52840.upload.protocol=nrfutil
+#metro52840.upload.use_1200bps_touch=true
+#metro52840.upload.wait_for_upload_port=true
 
 # Build
-metro52840.build.mcu=cortex-m4
-metro52840.build.f_cpu=64000000
-metro52840.build.board=NRF52840_METRO
-metro52840.build.core=nRF5
-metro52840.build.variant=metro_nrf52840_express
-metro52840.build.extra_flags=-DNRF52840_XXAA
+#metro52840.build.mcu=cortex-m4
+#metro52840.build.f_cpu=64000000
+#metro52840.build.board=NRF52840_METRO
+#metro52840.build.core=nRF5
+#metro52840.build.variant=metro_nrf52840_express
+#metro52840.build.extra_flags=-DNRF52840_XXAA
 
 # SofDevice Menu
 # Ram & ROM size varies depending on SoftDevice (check linker script)
 
-metro52840.menu.softdevice.s140v6=0.2.7 (s140 6.1.1)
-metro52840.menu.softdevice.s140v6.build.sd_flags=-DS140
-metro52840.menu.softdevice.s140v6.build.sd_name=s140
-metro52840.menu.softdevice.s140v6.build.sd_version=6.1.1
-metro52840.menu.softdevice.s140v6.build.sd_fwid=0x00B6
-metro52840.menu.softdevice.s140v6.build.ldscript=nrf52840_s140_v6.ld
-metro52840.menu.softdevice.s140v6.upload.maximum_size=815104
-metro52840.menu.softdevice.s140v6.upload.maximum_data_size=248832
+#metro52840.menu.softdevice.s140v6=0.2.9 (s140 6.1.1)
+#metro52840.menu.softdevice.s140v6.build.sd_flags=-DS140
+#metro52840.menu.softdevice.s140v6.build.sd_name=s140
+#metro52840.menu.softdevice.s140v6.build.sd_version=6.1.1
+#metro52840.menu.softdevice.s140v6.build.sd_fwid=0x00B6
+#metro52840.menu.softdevice.s140v6.build.ldscript=nrf52840_s140_v6.ld
+#metro52840.menu.softdevice.s140v6.upload.maximum_size=815104
+#metro52840.menu.softdevice.s140v6.upload.maximum_data_size=248832
 
 # Debug Menu
-metro52840.menu.debug.l0=Level 0 (Release)
-metro52840.menu.debug.l0.build.debug_flags=-DCFG_DEBUG=0 -Os
-metro52840.menu.debug.l1=Level 1 (Error Message)
-metro52840.menu.debug.l1.build.debug_flags=-DCFG_DEBUG=1 -Os
-metro52840.menu.debug.l2=Level 2 (Full Debug)
-metro52840.menu.debug.l2.build.debug_flags=-DCFG_DEBUG=2 -Os
-metro52840.menu.debug.l3=Level 3 (Segger SystemView)
-metro52840.menu.debug.l3.build.debug_flags=-DCFG_DEBUG=3 -Os
+#metro52840.menu.debug.l0=Level 0 (Release)
+#metro52840.menu.debug.l0.build.debug_flags=-DCFG_DEBUG=0 -Os
+#metro52840.menu.debug.l1=Level 1 (Error Message)
+#metro52840.menu.debug.l1.build.debug_flags=-DCFG_DEBUG=1 -Os
+#metro52840.menu.debug.l2=Level 2 (Full Debug)
+#metro52840.menu.debug.l2.build.debug_flags=-DCFG_DEBUG=2 -Os
+#metro52840.menu.debug.l3=Level 3 (Segger SystemView)
+#metro52840.menu.debug.l3.build.debug_flags=-DCFG_DEBUG=3 -Os
 
 #**********************************************
 # Nordic nRF52840DK (PCA10056)
@@ -187,7 +187,7 @@ pca10056.build.extra_flags=-DNRF52840_XXAA
 # SofDevice Menu
 # Ram & ROM size varies depending on SoftDevice (check linker script)
 
-pca10056.menu.softdevice.s140v6=0.2.7 (s140 6.1.1)
+pca10056.menu.softdevice.s140v6=0.2.9 (s140 6.1.1)
 pca10056.menu.softdevice.s140v6.build.sd_flags=-DS140
 pca10056.menu.softdevice.s140v6.build.sd_name=s140
 pca10056.menu.softdevice.s140v6.build.sd_version=6.1.1