|author||Nitin Arora <firstname.lastname@example.org>||Tue Mar 15 15:00:36 2016 -0700|
|committer||Andre Eisenbach <email@example.com>||Mon Jun 06 19:50:41 2016 +0000|
Remote device changes for SMP certification Use Case: Certification test cases for SMP require various scenarios where the remote device needs to show a specific behavior where it fails the pairing in a certain way, and the DUT is required to abort the pairing properly. In abcense of a proper PTS suite to execute these test cases, we can use another device running the same host by configuring certain run time property. Test Cases: TP/SCJW/BI-02-C TP/SCJW/BV-02-C TP/SCPK/BI-03-C TP/SCPK/BI-04-C TP/SCPK/BV-02-C TP/SCPK/BV-03-C TP/SCJW/BI-01-C TP/SCCT/BV-01-C TP/SCCT/BV-02-C TP/SCPK/BI-01-C TP/SCPK/BI-02-C TP/SCPK/BV-04-C TP/SCPK/BV-01-C Fix: Added a property in the bt_stack.conf file. The property name is "SmpFailureCase". The values 2 to 6(inclusive), are forcausing SMP failures with various failure reasons. Failure case 1 and 9 are for producing error "Confirm value failure". Cases 7 and 8 are for generating specific errors at pair cancel. Note: The default use of this feature is controlled using a compile time flag BTM_BLE_SMP_CERTIFICATION. The BTM_BLE_SMP_CERTIFICATION = TRUE is needed only while we wait for the PTS support for the LE Secure connections. Bug: 27852645 Change-Id: I1f7a8ff2659d85b5978b75870c57162a34d394d0
Just build AOSP - Fluoride is there by default.
Instructions for Ubuntu, tested on 15.10 with GCC 5.2.1.
sudo apt-get install libevent-dev
sudo apt-get install ninja-build
or download binary from https://github.com/ninja-build/ninja/releases
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
mkdir ~/fluoride cd ~/fluoride git clone https://android.googlesource.com/platform/system/bt
Then fetch third party dependencies:
cd ~/fluoride/bt mkdir third_party cd 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
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
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.
cd ~/fluoride/bt/out/Default LD_LIBRARY_PATH=./ ./bluetoothtbd -create-ipc-socket=fluoride