| commit | 987c8df33f90da95aedc5249e3e7b18f76eeca4e | [log] [tgz] |
|---|---|---|
| author | Hansong Zhang <hsz@google.com> | Thu May 28 15:34:19 2020 -0700 |
| committer | Hansong Zhang <hsz@google.com> | Thu May 28 15:39:18 2020 -0700 |
| tree | 1e461cf2561873c4678a0b22731cb84771f6e398 | |
| parent | f3f1a8705eda6fec35a98a1af59e50a47d198369 [diff] |
L2cap: Fix ERTM test Send S-Frame [REJ] Under some circunstances, the stack might enter "local busy" state, and sending an "Receiver Not Ready" packet. Almost immediately the stack exits "local busy" state and sends "Receiver Ready" packet with P=1. We should allow this situation in cert test, and not explicitly require P=0. We still need to figure out why we enter and exit "local busy" state. Currently it solely depends on queue size on client queue end, and it detects local busy when there is more than 1 pending item. Maybe we can set the threshold to 2 if this occurs often and causes real problem. Test: cert/run --host Tag: #gd-refactor Bug: 157251860 Change-Id: I33cbd46d266865f396edb624550b8c7cb38f51a8
Just build AOSP - Fluoride is there by default.
Instructions for Ubuntu, tested on 14.04 with Clang 3.5.0 and 16.10 with Clang 3.8.0
mkdir ~/fluoride cd ~/fluoride git clone https://android.googlesource.com/platform/packages/modules/Bluetooth/system
Install dependencies (require sudo access):
cd ~/fluoride/bt build/install_deps.sh
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/aac git clone https://android.googlesource.com/platform/external/libchrome git clone https://android.googlesource.com/platform/external/libldac 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
NOTE: If packages/modules/Bluetooth/system is checked out under AOSP, then create symbolic links instead of downloading sources
cd packages/modules/Bluetooth/system mkdir third_party cd third_party ln -s ../../../external/aac aac ln -s ../../../external/libchrome libchrome ln -s ../../../external/libldac libldac ln -s ../../../external/modp_b64 modp_b64 ln -s ../../../external/tinyxml2 tinyxml2 ln -s ../../../external/googletest googletest
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
Follows the Chromium project Eclipse Setup Instructions until "Optional: Building inside Eclipse" section (don't do that section, we will set it up differently)
Generate Eclipse settings:
cd packages/modules/Bluetooth/system gn gen --ide=eclipse out/Default
In Eclipse, do File->Import->C/C++->C/C++ Project Settings, choose the XML location under packages/modules/Bluetooth/system/out/Default
Right click on the project. Go to Preferences->C/C++ Build->Builder Settings. Uncheck "Use default build command", but instead using "ninja -C out/Default"
Goto Behaviour tab, change clean command to "-t clean"