Skip to content

[Tooling] BLE Cancel Connection #27632

Closed
Closed
@jjm202

Description

Reproduction steps / Feature

Build chip-tool using a linux/arm64 based Docker container. After installing the necessary build tools and sysroot:

  • export SYSROOT_AARCH64=/opt/ubuntu-22.04.1-aarch64-sysroot
  • checkout source code
  • ./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?

[1688578543.970738][6727:6729] CHIP:BLE: CancelBleIncompleteConnection() failed, err = src/platform/Linux/BLEManagerImpl.cpp:732: CHIP Error 0x0000002D: Not Implemented
.
.
.
 CHIP:BLE: CancelBleIncompleteConnection() failed, err = src/ble/BleLayer.cpp:372: CHIP Error 0x00000003: Incorrect state

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

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions