Gitiles
Code Review Sign In
review.blissroms.org / platform_system_bt / fcff2797964e5aa65152845e3b277078d3d9e705
commitfcff2797964e5aa65152845e3b277078d3d9e705[log] [tgz]
authorSrinu Jella <sjella@codeaurora.org>Mon Sep 21 19:29:50 2015 +0530
committerLinux Build Service Account <lnxbuild@localhost>Wed Aug 24 08:09:22 2016 -0600
tree6419edfc76ae209aa43fe8bf571f6e30a9c7b0e1
parent33673ead7849a834d592e9427a8bec5b0802e958 [diff]
Bluetooth: Add support to send h/w error event

- Bluedroid stack needs to be reset whenever H/w
  chip restarts like Subsytem restart.

- Emulates the hardware error event on detecting
  SSR event from PR controller.

CRs-Fixed: 914079
Change-Id: I9248a4e6ad689fc590fd4fd0f7a067cd33bf314f

Bluetooth: Reset bluetooth status to download NVM tags

- Reset bluetooth status to download the NVM tags once
  the SSR is detected.

- NVM tags downloaded only once for the first BT on and
  downloaded again in case of SSR or command timeout.

- Without this change, there would be diffrence in
  BD addr which would lead to pair/connection issues.

CRs-Fixed: 932195
Change-Id: I75a44e7ae7d301ff1c9be8349c1b51d4c80cbf36

BT: Adding check for packet size before allocating buffer

During controller reset, corrupted packet might reach
to host. This packet might indicate length value more
than maximum allowed packet length. This causes crash
during buffer allocation.
Added the correct length check before allocating the
memory.

CRs-Fixed: 978009
Change-Id: I462b9b18e4c9db67d4860509376b0cb38830e56d

BT: Rectify the method to reset host after controller crash

Use case: When controller is forcefully crashed for testing,
the host process should reset itself.

Steps: Testing envolving forceful crashing of controller
to observe recovery and behavior of host in such events.

Failure: Once controller crash was enforced, the host
process was not resetting itself.

Root cause: The packet created to send hw reset event to
stack was getting truncated.

Fix: Changed the logic to first create an empty packet and
later set its type and data to make hw reset event.

CRs-Fixed: 1000446

Change-Id: Ied4e62db0be5bb8e16fac05787b9a071fd86b1e7
5 files changed
tree: 6419edfc76ae209aa43fe8bf571f6e30a9c7b0e1
  1. audio_a2dp_hw/
  2. bta/
  3. btcore/
  4. btif/
  5. build/
  6. conf/
  7. device/
  8. doc/
  9. embdrv/
  10. hci/
  11. include/
  12. main/
  13. osi/
  14. profile/
  15. service/
  16. stack/
  17. test/
  18. tools/
  19. udrv/
  20. utils/
  21. vendor_libs/
  22. vnd/
  23. .gitignore
  24. .gn
  25. Android.mk
  26. BUILD.gn
  27. CleanSpec.mk
  28. MODULE_LICENSE_APACHE2
  29. NOTICE
  30. README.md
README.md

Fluoride Bluetooth stack

Building and running on AOSP

Just build AOSP - Fluoride is there by default.

Building and running on Linux

Instructions for Ubuntu, tested on 15.10 with GCC 5.2.1.

Install required libraries

sudo apt-get install libevent-dev

Install build tools

  • Install ninja build system
sudo apt-get install ninja-build

or download binary from https://github.com/ninja-build/ninja/releases

  • Install gn - meta-build system that generates NinjaBuild files.

Get sha1 of current version from here and then download corresponding executable:

wget -O gn http://storage.googleapis.com/chromium-gn/<gn.sha1>

i.e. if sha1 is "3491f6687bd9f19946035700eb84ce3eed18c5fa" (value from 24 Feb 2016) do

wget -O gn http://storage.googleapis.com/chromium-gn/3491f6687bd9f19946035700eb84ce3eed18c5fa

Then make binary executable and put it on your PATH, i.e.:

chmod a+x ./gn
sudo mv ./gn /usr/bin

Download source

mkdir ~/fluoride
cd ~/fluoride
git clone https://android.googlesource.com/platform/system/bt

Then fetch third party dependencies:

cd ~/fluoride/bt
mkdir third_party
git clone https://github.com/google/googletest.git
git clone https://android.googlesource.com/platform/external/libchrome
git clone https://android.googlesource.com/platform/external/modp_b64
git clone https://android.googlesource.com/platform/external/tinyxml2

And third party dependencies of third party dependencies:

cd fluoride/bt/third_party/libchrome/base/third_party
mkdir valgrind
cd valgrind
curl https://chromium.googlesource.com/chromium/src/base/+/master/third_party/valgrind/valgrind.h?format=TEXT | base64 -d > valgrind.h
curl https://chromium.googlesource.com/chromium/src/base/+/master/third_party/valgrind/memcheck.h?format=TEXT | base64 -d > memcheck.h

Fluoride currently has dependency on some internal Android projects, which also need to be downloaded. This will be removed in future:

cd ~/fluoride
git clone https://android.googlesource.com/platform/system/core
git clone https://android.googlesource.com/platform/hardware/libhardware
git clone https://android.googlesource.com/platform/system/media

Configure your build

We need to configure some paths to make the build successful. Run:

cd ~/fluoride/bt
gn args out/Default

This will prompt you to fill the contents of your "out/Default/args.gn" file. Make it look like below. Replace "/home/job" with path to your home directory, and don't use "~" in build arguments:

# Build arguments go here. Examples:
#   is_component_build = true
#   is_debug = false
# See "gn args <out_dir> --list" for available build arguments.

libhw_include_path = "/home/job/fluoride/libhardware/include"
core_include_path = "/home/job/fluoride/core/include"
audio_include_path = "/home/job/fluoride/media/audio/include"

Then generate your build files by calling

cd ~/fluoride/bt
gn gen out/Default

Build

cd ~/fluoride/bt
ninja -C out/Default all

This will build all targets (the shared library, executables, tests, etc) and put them in out/Default. To build an individual target, replace "all" with the target of your choice, e.g. ninja -C out/Default net_test_osi.

Run

cd ~/fluoride/bt/out/Default
LD_LIBRARY_PATH=./ ./bluetoothtbd -create-ipc-socket=fluoride