merge master branch into bluetooth5#364
Merged
rymanluk merged 96 commits intoapache:bluetooth5from Jun 30, 2017
Merged
Conversation
We would persist the authenticated flag if either peer supported authentication. We should only persist it if both support it.
If a device is already bonded, ;he host should not allow the same device
to pair again. Currently, the host blindly proceeds with the pairing
operation. This should not be allowed because the second peer could be
an imposter masquerading as the original.
New behavior in such a scenario:
1. Host notifies application of the duplicate pairing attempt via the
gap event callback. The callback specifies a new event code
(BLE_GAP_EVENT_REPEAT_PAIRING) that specifically indicates a duplicate
pairing attempt.
2. The gap event callback returns an error code indicating which
of the following behaviors to perform:
a. Retry: Return BLE_GAP_REPEAT_PAIRING_RETRY after deleting the
conflicting bond. The stack will verify the bond has been deleted
and continue the pairing procedure. If the bond is still present,
this event will be reported again.
b. Ignore: Return BLE_GAP_REPEAT_PAIRING_IGNORE. The stack will
silently ignore the pairing request.
- Use util/parse package for parsing instead of using sensor_shell_stol() or parsing functions in individual drivers
bootloader would still boot image in slot0 with invalid signature.
- Removing os_time_delay() from driver and moving it to shell for using it with shell. - Sensor framework polling timer should be used for reading instead of os_time_delay().
MYNEWT-752 Allow confirm of tentative slot.
MYNEWT-777 SensorAPI: Use util/parse pkg instead of using sensor_shell_stol()
MYNEWT-779 tcs34725 driver: remove os_time_delay()
MYNEWT-780 Sensor driver shells: expose ADDR syscf
MYNEWT-699; re-add sample linker scripts to Olimex BSP.
- The apps/sensors_test had an issue where it would not build standalone without specifying an offboard sensor and an interface in the targets syscfg.yml file. This change would make that possible.
Function generated using Cube MX, with the STM32F7-DISCOVERY board definition.
16-bit, or 128-bit service uuid for oic.
Close the failed transport only.
- Fix onbaord sensor config by adding it to sysinit - removing DEVICE_READY check from config functions as it is not needed as the check already happens in os_dev_open() - Fixing comments
Fix onboard sensor config & misc
Allow more even access to TX and RX in 'interrupt handler'.
VBLUno51 board from VNG (Nordic nRF51822 SoC based) + Abstract nRF51822 Bluetooth Low Energy DAPLink interface UNO pinout 4 power + Wiki: https://vngiotlab.github.io/vbluno/ + The following samples were tested: blinky bleprph Signed-off-by: iotvietmember <robotden@gmail.com>
Add support for VBLUno51 board
BLE Host - Policy for SM key overflow
add NRF52 thingy BSP
This file provides descriptions for custom events that the SystemView app can trace. It should be put inside the /description/ directory of SystemView, e.g. "/opt/SEGGER/SystemView/Description/".
BLE Host - Allow get / set of channel map.
BLE Host - Persist bonding material to sys/config
Add back in the crypto code that was commented out (for now). At some point in the future we will look to see if we should use mynewt crypto libraries. Also brought in some code that was recently updated in the lora repo (well, more recently than when the original code was committed).
[RFC] MYNEWT-430: Segger's SystemView working with Mynewt
Conflicts: apps/bletiny/src/main.c net/nimble/host/include/host/ble_gap.h net/nimble/host/src/ble_hs_hci_cmd.c
Contributor
|
Looks good to me |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.