Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable building tracing in chip-tool by default #13702

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 4 additions & 9 deletions examples/chip-tool/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,21 +29,16 @@ scripts/examples/gn_build_example.sh examples/chip-tool SOME-PATH/

which puts the binary at `SOME-PATH/chip-tool`.

### Building with message tracing
### Using message tracing

Message tracing allows capture of the secure messages which can be used for test
automation.

```
gn gen out/with_trace/ --args='import("//with_pw_trace.gni")'
ninja -C out/with_trace chip-tool
```

This enables tracing and adds additional flags to chip-tool to control where the
traces should go:
There are additional flags to chip-tool to control where the traces should go:

- --trace_file <file> Outputs trace data to the specified file.
- --trace_log Outputs trace data to the chip log stream.
- --trace_log <0/1> Outputs trace data to the console with automation logs if
set to 1

For example:

Expand Down
1 change: 1 addition & 0 deletions examples/chip-tool/args.gni
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@
import("//build_overrides/chip.gni")

import("${chip_root}/config/standalone/args.gni")
import("${chip_root}/examples/chip-tool/with_pw_trace.gni")

chip_device_project_config_include = "<CHIPProjectAppConfig.h>"
chip_project_config_include = "<CHIPProjectAppConfig.h>"
Expand Down