You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
./scripts/checkout_submodules.py --shallow --platform linux
source ./scripts/bootstrap.sh
./scripts/gn_build_example.sh examples/chip-tool out
chip-tool builds then is copied to the R Pi and used normally. The question is why does the chip-tool that is packed with the test harness image not produce the following errors (these appear to be benign, but still inconsistent). Are these being suppressed somehow?
Reproduction steps / Feature
Build chip-tool using a linux/arm64 based Docker container. After installing the necessary build tools and sysroot:
chip-tool builds then is copied to the R Pi and used normally. The question is why does the chip-tool that is packed with the test harness image not produce the following errors (these appear to be benign, but still inconsistent). Are these being suppressed somehow?
Platform
raspi
Platform Version(s)
No response
Type
Manually tested with SDK
(Optional) If manually tested please explain why this is only manually tested
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: