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-BINFO-2.2] #2a and#4 cannot be exectued. #6 is optional and was not executed. the output of chip-tool command and RTT log for DUT do not match the expected outcome for #2b. #20283

Closed
morahman2022 opened this issue Jul 4, 2022 · 8 comments

Comments

@morahman2022
Copy link

morahman2022 commented Jul 4, 2022

Test Case ID: TC-BINFO-2.2

Git Hash: 6efefe3

Describe Issue:

EFR32 end devices with BRD-4187A and BRD-4161A are considered for testing TC-BINFO-2.2. lighting app was used.

#2a cannot be executed as graceful shutdown is not supported in the end devices.
#2b outputs from chip-tool command and J-Link RTT Viewer log for DUT do not match the expected outcome mentioned in test plan ( https://docs.google.com/spreadsheets/d/1h4d4J90KAxFqUL_cXZHyM3pHjHCEXzFITkQhN2KMqDY/edit#gid=66916293 ).
#4 outputs in the test plan could not be reproduced with factory resetting the end device.
#6 cannot be executed as there is no way to change the Reachable attribute. Moreover, #6 is optional.

TC-BINFO-2.2_2b.txt
TC-BINFO-2.2_2b_DUT_RTT_LOG.txt

@bzbarsky-apple
Copy link
Contributor

@cjandhyala can you please take a look?

@andy31415
Copy link
Contributor

@morahman2022 - please provide the commands that are included in TC-BINFO-2.2 in this bug report. I opened the spreadsheet and still have a hard time finding the information.

@andy31415
Copy link
Contributor

Cert blocker review: clean shutdown is indeed not generally supported for devices. We may need to do one of:

  • figure out a trigger of such shutdown (e.g. test trigger)
  • can we even ask for graceful shutdown

for 2b, human log review is generally subjective. Could we automate this or can the test case be reviewed for correctness? We need for details in this issue to make an assesment.

DUT logs are generally not acceptable for test cases - firmware on embedded devices may not provide logs and it should still be able to pass cert. Some small devices disable logging due to flash size constraints.

@cjandhyala DUT logs cannot be used for certification, what can we do here?

@andy31415
Copy link
Contributor

--trace_decode 1 appended to chip-tool may help in verification steps by providing more data on chip-tool side (instead of DUT side)

@cjandhyala
Copy link
Contributor

@morahman2022 , as per the verification steps document, this test case is not ready for execution. Pls do not execute until the test case is ready. closing the issue for now.

@lisaaaas
Copy link

lisaaaas commented Apr 6, 2023

Hello, I want to know TC-BINFO-2.2 step 2 what shut down the DUT means. I have the same result as you, but I have not solved this problem at present

@stefano055415
Copy link

@lisaaaas @cjandhyala @bzbarsky-apple

I too have the same problem, I don't understand how to execute the shutdown command

is there a way via chip-tool?

@bzbarsky-apple
Copy link
Contributor

is there a way via chip-tool?

Not for a real device. Has to be done manually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants