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

[pre-sve] [TC-GC-1.1]General commissioning cluster---Value mismatch for FeatureMap attribute #19218

Closed
AlvinHsiao opened this issue Jun 6, 2022 · 1 comment · Fixed by #20003
Assignees
Labels
spec Mismatch between spec and implementation

Comments

@AlvinHsiao
Copy link
Contributor

Problem

As per test plan [TC-GC-1.1] FeatureMap attribute showing value mismatch error when executed, DUT should
responds with feature map value 0 but currently DUT responding feature map value has 6.

expected behavior:-FeatureMap attribute value should be bit 0.
actual behavior:- DUT responds has bit 6
steps to reproduce:-./chip-tool generalcommissioning read feature-map 2 0

system configuration

  • Chip-Tool: RPI
  • DUT used : Infineon CYW30739
  • app use: lighting-app
  • chip-tool and DUT commit id : 425f1fb (pre-sve SHA)

logs

@bzbarsky-apple bzbarsky-apple added the spec Mismatch between spec and implementation label Jun 7, 2022
@bzbarsky-apple
Copy link
Contributor

Looks similar to #18028 but for lighting-app.

bzbarsky-apple added a commit to bzbarsky-apple/connectedhomeip that referenced this issue Jun 27, 2022
The spec changed and this cluster no longer has a FeatureMap defined,
so the default value needs to be 0.

Fixes project-chip#19218
@bzbarsky-apple bzbarsky-apple self-assigned this Jun 27, 2022
andy31415 pushed a commit that referenced this issue Jun 28, 2022
The spec changed and this cluster no longer has a FeatureMap defined,
so the default value needs to be 0.

Fixes #19218
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec Mismatch between spec and implementation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants