Google Git
Sign in
chromium / chromiumos / platform / btpeerd
Clone this repo:

Branches

More...
  1. 42fd3d4 btpeerd: Add scripts/update_btpeers.sh by Jared Bennett · 2 months ago firmware-R126-15885.B firmware-R127-15916.B firmware-android-15949.B firmware-hps-15892.B main release-R126-15886.B release-R127-15917.B stabilize-15886.46.B stabilize-15888.B stabilize-15905.B stabilize-15926.B stabilize-hps-15890.B stabilize-quickfix-15886.43.B
  2. 2dbaec5 btpeerd: Clean DeviceInfo data by Jared Bennett · 2 months ago
  3. 43f8994 btpeerd: Add model to DeviceInfo by Jared Bennett · 2 months ago
  4. 1c90c89 btpeerd: Implement DeviceInfo and related tooling by Jared Bennett · 3 months ago
  5. 7ebba4e btpeerd: Add gRPC service scaffold by Jared Bennett · 3 months ago

btpeerd

A system service for controlling Raspberry Pi btpeers for ChromeOS bluetooth testing.

Design: go/btpeerd

Building btpeerd

System must have golang installed (any version) in order to download and configure the local golang version used by the btpeerd build process.

Build btpeerd on the same system environment the executable is meant to be run on (e.g. in the pi-gen chroot) to ensure system compatibility. The unit tests should not be system dependent, so running the build script on gLinux should be sufficient to say those test pass.

Run scripts/build.sh to build btpeerd. This will do the following:

  • Download the specific version of golang needed for btpeerd to ./go/bin
  • Downloads go package dependencies.
  • Run all unit tests
  • Build btpeerd binary to ./go/bin/btpeerd

Running btpeerd

No files in this repository are used during btpeerd runtime, the ./go/bin/btpeerd executable should be runnable directly to launch btpeerd.

Note: Golang is only used during the compilation of the btpeerd executable.

The btpeerd accepts the following optional command line options:

  • --ListenPort=<port> (default 8100) Sets the port the gRPC server will listen on.
  • --LogLevel=<DEBUG|INFO|WARN|ERROR> (default INFO) Sets the log level of btpeerd.

The btpeerd process will run continuously until a SIGINT signal (Ctrl+C) is received, upon which it will gracefully shut down the gRPC server and then close.