commit | 404ace923bf6f4d7067d365fe6addb98d47db25a | [log] [tgz] |
---|---|---|
author | Sarah Chan <spqchan@google.com> | Mon May 23 01:20:20 2022 +0000 |
committer | CQ Bot <fuchsia-internal-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon May 23 01:20:20 2022 +0000 |
tree | 2c6923749ec1c4f714ce0839592d719cb905ea0a | |
parent | 8f0fd5b483f94cee972ccb400b26ffb1f73636a0 [diff] |
[i2c_sample] Add test i2c controller Add a test controller that interacts with the i2c temperature driver via the i2c protocol. The test controller receives commands in the form of read/write transactions through the protocol. It returns a fake temperature for read transactions. Each time the controller receives a measure command, it increase the temperature by 5. Once it receives a reset command, it reset back to the starting temperature Bug: 98633 Change-Id: I518bef9977a0d9ca96bd3419a32b70f77abc082a Reviewed-on: https://fuchsia-review.googlesource.com/c/sdk-samples/drivers/+/679311 Reviewed-by: David Gilhooley <dgilhooley@google.com> Commit-Queue: Sarah Chan <spqchan@google.com> Reviewed-by: Renato Mangini Dias <mangini@google.com>
This repository contains instructions and source code to build, package and run Fuchsia samples using only the Fuchsia SDK. To update the dependencies of this repository, follow the instructions in update_dependencies.md.
Install Bazel version 5.1 or later by following the instructions at https://bazel.build/install. In some Linux distributions, sudo apt-get install bazel
should be enough.
Make sure this repository has the required submodules:
git submodule update --recursive --init
Ensure that there are Fuchsia SSH keys in your host machine. You will need them for running the Fuchsia emulator.
[[ -f "${HOME}/.ssh/fuchsia_ed25519" ]] || ssh-keygen -P "" -t ed25519 -f "${HOME}/.ssh/fuchsia_ed25519" -C "${USER}@$(hostname -f) Shared SSH Key for Fuchsia" [[ -f "${HOME}/.ssh/fuchsia_authorized_keys" ]] || ssh-keygen -y -f "${HOME}/.ssh/fuchsia_ed25519" > "${HOME}/.ssh/fuchsia_authorized_keys"
Now the repository is ready to build the samples.
Build the samples:
Note: in order to use an SDK produced by a local Fuchsia platform tree, you can set an environment variable named
LOCAL_FUCHSIA_PLATFORM_BUILD
as described in https://fuchsia.googlesource.com/sdk-integration/+/0503b02c059a6de76242280b467898358ba30ae3
bazel build --config=fuchsia_x64 src/...
This command will build and package all the samples.
If using an emmulator:
Fetch the system images
tools/ffx product-bundle get workstation.qemu-x64
Start the emulator
tools/ffx emu start workstation.qemu-x64 --headless \ --kernel-args "driver_manager.use_driver_framework_v2=true" \ --kernel-args "driver_manager.root-driver=fuchsia-boot:///#meta/platform-bus.cm" \ --kernel-args "devmgr.enable-ephemeral=true"
The product bundle comes with on-demand packages in a separate repository. Use the following command to register it with the emulator:
tools/ffx target repository register -r workstation.qemu-x64 --alias fuchsia.com
If using a physical device like a Pixelbook Go:
Fetch the system images
tools/ffx product-bundle get workstation.qemu-x64-dfv2
Prepare and connect the Pixelbook Go, by flashing and/or paving it (not covered here), and connect using Ethernet.
The product bundle comes with on-demand packages in a separate repository. Use the following command to register it with the device:
tools/ffx target repository register -r workstation.qemu-x64-dfv2 --alias fuchsia.com
Update (OTA) the device to the version of the SDK:
tools/ffx target update check-now --monitor
(optional) watch the device log in a separate window
tools/ffx log
Load the sample drivers
Now you are ready to register a driver. Starting with the example driver:
First, let's confirm that the driver is not loaded:
tools/ffx driver list | grep example_driver
The command above should not return any driver named “example_driver” because it has not been registered.
Now register the driver:
bazel run --config=fuchsia_x64 src/example_driver:pkg.component
The driver now should show in the list of loaded drivers:
tools/ffx driver list | grep example_driver fuchsia-pkg://bazel.pkg.component/example_driver#meta/example_driver.cm
You can also watch in the log to see if the driver is loaded correctly. The ffx log window should show a message similar to:
[88.961][bootstrap/driver_manager][driver_manager.cm][I] Loaded driver 'fuchsia-pkg://bazel.pkg.component/example_driver#meta/example_driver.cm'