Skip to content

Latest commit

 

History

History
124 lines (86 loc) · 3.49 KB

README.md

File metadata and controls

124 lines (86 loc) · 3.49 KB

#CHIP EFR32 Test Driver

This builds and runs the PW Unit Tests on the efr32 device

Introduction

This builds a test binary which contains the pw_unit_test and can be flashed onto a device. The device is controlled using the included RPCs, through the python test runner.

Building

  • Download the Simplicity Commander command line tool, and ensure that commander is your shell search path. (For Mac OS X, commander is located inside Commander.app/Contents/MacOS/.)

  • Download and install a suitable ARM gcc tool chain (For most Host, the bootstrap already installs the toolchain): GNU Arm Embedded Toolchain 12.2 Rel1

  • Install some additional tools(likely already present for CHIP developers):

#Linux sudo apt-get install git libwebkitgtk-1.0-0 ninja-build

#Mac OS X brew install ninja

  • Supported hardware:

    MG12 boards:

    • BRD4161A / SLWSTK6000B / Wireless Starter Kit / 2.4GHz@19dBm
    • BRD4162A / SLWSTK6000B / Wireless Starter Kit / 2.4GHz@10dBm
    • BRD4163A / SLWSTK6000B / Wireless Starter Kit / 2.4GHz@10dBm, 868MHz@19dBm
    • BRD4164A / SLWSTK6000B / Wireless Starter Kit / 2.4GHz@19dBm
    • BRD4166A / SLTB004A / Thunderboard Sense 2 / 2.4GHz@10dBm
    • BRD4170A / SLWSTK6000B / Multiband Wireless Starter Kit / 2.4GHz@19dBm, 915MHz@19dBm
    • BRD4304A / SLWSTK6000B / MGM12P Module / 2.4GHz@19dBm

    MG21 boards: Currently not supported due to RAM limitation.

    • BRD4180A / SLWSTK6006A / Wireless Starter Kit / 2.4GHz@20dBm

    MG24 boards :

    • BRD2601B / SLWSTK6000B / Wireless Starter Kit / 2.4GHz@10dBm
    • BRD2703A / SLWSTK6000B / Wireless Starter Kit / 2.4GHz@10dBm
    • BRD4186A / SLWSTK6006A / Wireless Starter Kit / 2.4GHz@10dBm
    • BRD4186C / SLWSTK6006A / Wireless Starter Kit / 2.4GHz@10dBm
    • BRD4187A / SLWSTK6006A / Wireless Starter Kit / 2.4GHz@20dBm
    • BRD4187C / SLWSTK6006A / Wireless Starter Kit / 2.4GHz@20dBm

OR use GN/Ninja directly

      ```
      cd ~/connectedhomeip/src/test_driver/efr32/
      git submodule update --init
      source third_party/connectedhomeip/scripts/activate.sh
      export SILABS_BOARD=BRD4161A
      gn gen out/debug
      ninja -C out/debug
      ```

  • To delete generated executable, libraries and object files use:

      ```
  cd ~/connectedhomeip/src/test_driver/efr32/
  rm -rf out/
  ```

Running The Tests

Build the runner using gn:

```
cd <connectedhomeip>/src/test_driver/efr32
gn gen out/debug
ninja -C out/debug runner
```

Or build using build script from the root

```
cd <connectedhomeip>
./scripts/build/build_examples.py --target linux-x64-pw-test-runner build
```

The runner will be installed into the venv and python wheels will be packaged in the output folder for deploying.

Then the python wheels need to installed using pip3.

```
pip3 install out/debug/chip_pw_test_runner_wheels/*.whl
```

Other python libraries may need to be installed such as

```
pip3 install pyserial
```

To run all tests:

```
python -m pw_test_runner.pw_test_runner -d /dev/ttyACM1 -f out/debug -o out.log
```