Figure 2: Secure SSH setup with DUT 1 on port 2200, DUT 2 on port 2201, and the bt peer on port 3141.
There is a helpful
[script](https://source.corp.google.com/chromeos_public/src/platform/chameleon/utils/raspberrypi_setup?q=src%2Fplatform%2Fchameleon%2Futils%2Fraspberrypi_setup)
to configure the SSH keys on your laptop and Raspberry Pi so that you can SSH
into the Pi without a password (which is necessary for running Tast tests).
However, this script is not possible for Cloudtop users since it only accepts IP
addresses of the form `192.168.0.1`, not port-forwarded address like
`localhost:3141`.
**For non-Cloudtop users**, you can run the following command:
```
sh ~/chromiumos/src/platform/chameleon/utils/raspberrypi_setup $RASPBERRY_PI_IP raspberry
```
**For Cloudtop users**, we have to be a little bit more roundabout. Copy the
[setup script](https://source.corp.google.com/chromeos_public/src/platform/chameleon/utils/raspberrypi_setup?q=src%2Fplatform%2Fchameleon%2Futils%2Fraspberrypi_setup)
to your local machine into a new file like `/tmp/setup_pi` (don't worry, it's
just bash commands).
From the laptop:
```
sh /tmp/setup_host $RASPBERRY_PI_IP raspberry
```
Copy the setup script into the Raspberry Pi and run
[this line](https://source.chromium.org/chromium/chromiumos/platform/chameleon/+/HEAD:utils/raspberrypi_setup;l=104;drc=3c9fd0cb9dff2c7ec5a795b9717765cbb6fa5e58)
in the script manually:
```
scp /tmp/setup_pi pi@$RASPERRY_PI_IP:/tmp/
ssh pi@$RASPBERRY_PI_IP
sudo sh /tmp/setup_pi $RASPBERRY_PI_IP raspberry yes
```
At this point, you should be able to ssh into the permission user `root` with no
password from your laptop!
```
ssh root@$RASPBERRY_PI_IP
```
We still need to add the SSH keys to the Cloudtop. The easiest way to do this is
through the script, however the script will fail early since it can't ping the
Raspberry Pi's IP address (due to the port forwarding issue with the script).
Open up the
[setup script](https://source.chromium.org/chromium/chromiumos/platform/chameleon/+/HEAD:utils/raspberrypi_setup)
file in your local checkout of `chromiumos`, which at the time of writing is at
`chromiumos/src/platform/chameleon/utils/raspberrypi_setup`. You'll want to
modify it to ignore the ping commands (which will fail). Here's an example of my
[modified](https://paste.googleplex.com/6023581201858560) version.
```
cd ~/chromiumos/src
sh platform/chameleon/utils/raspberrypi_setup localhost raspberry
```
You'll know you've completed this step if you see the file `testing_rsa` inside
of `ls ~/.ssh`.
### Installing Chameleon daemon on the Raspberry Pi
Finally, we'll setup the Chameleon package on the Raspberry Pi. Note that `repo
sync` can take a long time. If you encounter errors during this step, it's
likely that you didn't setup the SSH keys correctly on the Pi and on the
Cloudtop.
```
(outside) $ cd ~/chromiumos/src
(outside) $ repo sync
(outside) $ cros_sdk
(inside) $ setup_board --board arm-generic
(inside) $ cd ~/trunk/src/platform/chameleon
(inside) $ make PY_VERSION=python3
(inside) $ make remote-install CHAMELEON_HOST=localhost CHAMELEON_SSH_PORT=3141 CHAMELEON_USER=root
```
Tip: Remember to set CHAMELEON_SSH_PORT to the Raspberry Pi's port-forwarded SSH
port, which we set to 3141 in SecureSSH.
This is also how you'll develop and make changes on Python services running on
the Raspberry Pi, such as the
[Fast Pair GATT service](https://source.corp.google.com/h/chromium/chromiumos/codesearch/+/main:src/platform/chameleon/chameleond/utils/bluez_le_fast_pair_service.py).
```
# Make changes to code in ~/chromiumos/src/platform/chameleon
# You have to commit code changes before you can run "make"
(outside) $ git add .
(outside) $ git commit
(inside) $ make PY_VERSION=python3
(inside) $ make remote-install CHAMELEON_HOST=localhost CHAMELEON_SSH_PORT=3141 CHAMELEON_USER=root
# Test your changes by running Tast tests and observe the logs
# on your Raspberry Pi at /var/log/chameleon.
```
You can verify that Chameleon is installed correctly by SSHing into the
Raspberry Pi and running:
```
sudo /etc/init.d/chameleond status
```
If you see the message `chameleond is running`, you're done!!! Check out the
[AVL guide](https://chromeos.google.com/partner/dlm/docs/component-qual/wf_bt_device_prep.html##raspberry-pi)
for troubleshooting tips.
## Running Bluetooth Tast tests locally
At this point, you should finally be ready to run Bluetooth Tast tests locally.
This usually looks like the following:
```
(outside) $ cd ~/chromiumos/src
(outside) $ cros_sdk
(inside) $ cd ~/chromiumos/src/platform/tast-tests
(inside) $ tast run --var=bluetooth.BTPeers=localhost:3141 localhost:2200 bluetooth.FastPairInitialPair
```
Tip: localhost:3141 and localhost:2200 match the port forwarded arguments I set
in SecureShell for the bt peer and DUT, respectively.
## Links
- [CrOS Bluetooth new team member guide](http://doc/1i9eXdf1toC7YFK889xwyoEZA0TUUCz4I74-zuL-I7zw#heading=h.p06ptmcspa8e)
- [Chameleon WFH Quick Start](https://docs.google.com/document/d/16K6depBwoxSRs6iI6UZkoJVllY1gAMR_F7hL9aDXwpQ/edit#heading=h.9lf16cckkrd)
- [How to run tests on Chameleon v2](https://docs.google.com/document/d/1ykCAvyQXN94tCpujaPGR4vTxw8Z_HQz5epg7efJGWNw/edit#heading=h.jc2s1arhb57e)
- [Setup ssh to access lab DUTs](https://g3doc.corp.google.com/company/teams/chrome/ops/fleet/systems/access_lab_duts.md)
- [go/cros-conn-bluetooth-engprod-tast](http://go/cros-conn-bluetooth-engprod-tast)
- [Connectivity EngProd docs](http://g3doc/company/teams/chrome/ops/chromeos/engprod/connectivity/bluetooth/automated_tests_and_lab)
- Code references
- [Fast Pair gatt service running on bt peer](https://source.chromium.org/chromiumos/chromiumos/codesearch/+/main:src/platform/chameleon/chameleond/utils/bluez_le_fast_pair_service.py?q=chameleond%2Futils%2Fbluez_le_fast_pair_service.py)
Figure 1:
A local Bluetooth testbed setup with 2 Chromebooks and 1 Bluetooth peer