Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 42b28c5

Browse files
raul-marquez-csaraul-marquez-csa
committedFeb 23, 2024·
Updates Test_TC_DLOG_2_1.yaml
1 parent 3880094 commit 42b28c5

File tree

1 file changed

+242
-80
lines changed

1 file changed

+242
-80
lines changed
 

‎src/app/tests/suites/certification/Test_TC_DLOG_2_1.yaml

+242-80
Original file line numberDiff line numberDiff line change
@@ -29,138 +29,300 @@ tests:
2929
- label: "Precondition"
3030
verification: |
3131
DUT supports BDX
32+
Length of TransferFileDesignator is zero
33+
Length of TransferFileDesignator is within 32 characters
34+
Length of TransferFileDesignator is equal to 32 characters
35+
Length of TransferFileDesignator is greater than 32 characters
36+
To send a message that mismatches the current transfer mode
3237
disabled: true
3338

34-
- label: "Step 1: Reboot DUT"
39+
- label: "Step 1: Commission DUT to TH"
3540
verification: |
3641
3742
disabled: true
3843

39-
- label: "Step 2: Commission DUT to TH"
44+
- label:
45+
"Step 2: TH sends RetrieveLogsRequest Command to DUT with
46+
RequestedProtocol argument as BDX : RetrieveLogsRequest (Intent =
47+
EndUserSupport, RequestedProtocol= BDX, TransferFileDesignator =
48+
TH_LOG_OK_FULL_LENGTH)"
49+
PICS: MCORE.BDX.Initiator
4050
verification: |
51+
"Repeating steps from 2 to 4 by setting Intent field to CrashLogs
52+
53+
diagnosticlogs retrieve-logs-request 2 1 1 0 --TransferFileDesignator Length_123456789123456789123.txt
4154
55+
Note: crash_log < 1024 Bytes and DUT does not inittiate the BDX transfer
56+
SendInitMsgfromDUT = false"
4257
disabled: true
4358

4459
- label:
45-
"Step 3: TH sends RetrieveLogsRequest Command (Intent =
46-
EndUserSupport,TransferFileDesignator = 'test.txt', RequestedProtocol=
47-
BDX) to DUT"
60+
"Step 3: if (SendInitMsgfromDUT = true) TH Sends BDX SendAccept
61+
message to DUT"
62+
PICS: MCORE.BDX.Initiator
4863
verification: |
49-
sudo ./chip-tool diagnosticlogs retrieve-logs-request 0 1 "test.txt" 1 0
50-
51-
52-
[1651207333.385887][2441:2446] CHIP:DMG: StatusIB =
53-
[1651207333.385937][2441:2446] CHIP:DMG: {
54-
[1651207333.385985][2441:2446] CHIP:DMG: status = 0x00 (SUCCESS),
55-
[1651207333.386037][2441:2446] CHIP:DMG: },
64+
"SendInitMsgfromDUT = false this step is not applicable"
5665
disabled: true
5766

5867
- label:
59-
"Step 4: Verify that the DUT initiates a BDX Transfer, sending a BDX
60-
SendInit message with the File Designator field of the message set to
61-
the value of the TransferFileDesignator field of the
62-
RetrieveLogsRequest"
68+
"Step 4: if (SendInitMsgfromDUT = false) TH does not send BDX
69+
SendAccept message to DUT"
70+
PICS: MCORE.BDX.Initiator
6371
verification: |
64-
Not Verifiable
72+
"On TH(chip-tool), verify that the DUT responds by sending RetrieveLogsResponse Command with Exhausted(1) status code to TH and LogContent field of RetrieveLogsResponse contains at most 1024 bytes
73+
74+
1707894938.009997][34371:34374] CHIP:TOO: RetrieveLogsResponse: {
75+
[1707894938.010025][34371:34374] CHIP:TOO: status: 1
76+
[1707894938.010057][34371:34374] CHIP:TOO: logContent: RetrieveLogsResponse: {
77+
[1707967525.484222][10866:10869] CHIP:TOO: status: 1
78+
[1707967525.484229][10866:10869] CHIP:TOO: logContent: 353535350A
79+
[1707967525.484233][10866:10869] CHIP:TOO: }"
6580
disabled: true
6681

67-
- label: "Step 5: TH Sends BDX SendAccept message"
68-
PICS: DLOG.S.C01.Tx
82+
- label:
83+
"Step 5: Repeat Steps from 2 to 4 by setting Intent field to
84+
NetworkDiag and CrashLogs"
6985
verification: |
70-
Not Verifiable
86+
7187
disabled: true
7288

7389
- label:
74-
"Step 6: Verify that DUT sends RetrieveLogsResponse Command,Verify
75-
that the Status field is set to Success,If LogContent size < 1024
76-
octets,Verify that the BDX transfer is not initiated from DUT Verify
77-
that DUT sends RetrieveLogsResponse command with a Status field set to
78-
Exhausted Note: In this case steps 5 and 6 does not hold good. else
79-
Verify that the BDX transfer is initiated from DUT Verify that the
80-
LogContent field of RetrieveLogsResponse is empty Verify that DUT
81-
sends RetrieveLogsResponse command with a Status field set to Success
82-
Verify that UTCTimeStamp is included in the RetrieveLogsResponse
83-
command Verify that TimeSinceBoot is included in the
84-
RetrieveLogsResponse command Note: In this case steps 5 and 6 holds
85-
good."
86-
PICS: DLOG.S.C01.Tx
90+
"Step 6: TH sends RetrieveLogsRequest Command to DUT with
91+
RequestedProtocol argument as BDX : RetrieveLogsRequest(Intent =
92+
EndUserSupport, RequestedProtocol= BDX, TransferFileDesignator =
93+
TH_LOG_OK_NORMAL)"
94+
PICS: MCORE.BDX.Initiator
8795
verification: |
88-
sudo ./chip-tool diagnosticlogs retrieve-logs-request 0 1 "test.txt" 1 0
96+
"diagnosticlogs retrieve-logs-request 0 1 1 0 --TransferFileDesignator Length_1234567.txt
97+
98+
On TH(chip-tool), Verify that the DUT sends SendInit message with TransferFileDesignator field set to Length_1234567891234567891
99+
[1707967645.770994][10882:10885] CHIP:ATM: SendInit
100+
[1707967645.770997][10882:10885] CHIP:ATM: Proposed Transfer Control: 0x10
101+
[1707967645.771001][10882:10885] CHIP:ATM: Range Control: 0x0
102+
[1707967645.771004][10882:10885] CHIP:ATM: Proposed Max Block Size: 1024
103+
[1707967645.771009][10882:10885] CHIP:ATM: Start Offset: 0x0000000000000000
104+
[1707967645.771011][10882:10885] CHIP:ATM: Proposed Max Length: 0x0000000000000000
105+
[1707967645.771014][10882:10885] CHIP:ATM: File Designator Length: 18
106+
[1707967645.771018][10882:10885] CHIP:ATM: File Designator: Length_1234567.txt
89107
90-
[1651207369.743117][2450:2455] CHIP:DMG: StatusIB =
91-
[1651207369.743155][2450:2455] CHIP:DMG: {
92-
[1651207369.743192][2450:2455] CHIP:DMG: status = 0x00 (SUCCESS),
93-
[1651207369.743228][2450:2455] CHIP:DMG: },
108+
Note: end_user_support_log > 1024 bytes so that BDX inititation happens from DUT
109+
SendInitMsgfromDUT = true"
94110
disabled: true
95111

96112
- label:
97-
"Step 7: TH sends RetrieveLogsRequest Command (Intent =
98-
EndUserSupport,TransferFileDesignator = 'test.txt', RequestedProtocol=
99-
BDX) to DUT"
113+
"Step 7: if (SendInitMsgfromDUT = true) TH Sends
114+
StatusReport(GeneralCode: FAILURE, ProtocolId: BDX, ProtocolCode:
115+
TH_LOG_ERROR_TRANSFER_METHOD_NOT_SUPPORTED) to DUT"
116+
PICS: MCORE.BDX.Initiator
100117
verification: |
101-
sudo ./chip-tool diagnosticlogs retrieve-logs-request 0 1 "test.txt" 1 0
102-
103-
[1651207386.883337][2457:2462] CHIP:DMG:
104-
[1651207386.883383][2457:2462] CHIP:DMG: StatusIB =
105-
[1651207386.883443][2457:2462] CHIP:DMG: {
106-
[1651207386.883498][2457:2462] CHIP:DMG: status = 0x00 (SUCCESS),
107-
[1651207386.883563][2457:2462] CHIP:DMG: },
118+
Not Verifiable. This step requires additional API for error injection.(Not available in the Chip-tool)
108119
disabled: true
109120

110121
- label:
111-
"Step 8: Verify that the DUT initiates a BDX Transfer, sending a BDX
112-
SendInit message with the File Designator field of the message set to
113-
the value of the TransferFileDesignator field of the
114-
RetrieveLogsRequest"
115-
PICS: DLOG.S.C01.Tx
122+
"Step 8: TH sends RetrieveLogsRequest Command RequestedProtocol as
123+
ResponsePayload : RetrieveLogsRequest(Intent =
124+
EndUserSupport,RequestedProtocol = ResponsePayload) Repeat this step
125+
by setting Intent field to . NetworkDiag . CrashLogs"
126+
PICS: MCORE.BDX.Initiator
116127
verification: |
117-
Not Verifiable
128+
"diagnosticlogs retrieve-logs-request 0 0 1 0
129+
130+
On TH(chip-tool), Verify that the DUT responds with Success(0) status code for the RetrieveLogsResponse command Verify that LogContent field contains at most 1024 bytes
131+
132+
RetrieveLogsResponse: {
133+
[1707901602.742523][36080:36083] CHIP:TOO: status: 0
134+
[1707901602.742542][36080:36083] CHIP:TOO: logContent: 31353238303033363031313533353030333730303234303030303234303133653234303230313138333530313331303034373032313533313031316230323330383230323137303630393261383634383836663730643031303730326130383230323038333038323032303430323031303333313064333030623036303936303836343830313635303330343032303133303832303137303036303932613836343838366637306430313037303161303832303136313034383230313564313532343030303132353031663166663336303230353030383030353031383030353032383030353033383030353034383030353035383030353036383030353037383030353038383030353039383030353061383030353062383030353063383030353064383030353065383030353066383030353130383030353131383030353132383030353133383030353134383030353135383030353136383030353137383030353138383030353139383030353161383030353162383030353163383030353164383030353165383030353166383030353230383030353231383030353232383030353233383030353234383030353235383030353236383030353237383030353238383030353239383030353261383030353262383030353263383030353264383030353265383030353266383030353330383030353331383030353332383030353333383030353334383030353335383030353336383030353337383030353338383030353339383030353361383030353362383030353363383030353364383030353365383030353366383030353430383030353431383030353432383030353433383030353434383030353435383030353436383030353437383030353438383030353439383030353461383030353462383030353463383030353464383030353465383030353466383030353530383030353531383030353532383030353533383030353534383030353535383030353536383030353537383030353538383030353539383030353561383030353562383030353563383030353564383030353565383030353566383030353630383030353631383030353632383030353633383031383234303331363263303431333433353334313330333033303330333035333537343333303330333033303330326433303330323430353030323430363030323430373031323430383030313833313763333037613032303130333830313466653334336639353939343737363362363165653435333931333133333834393466653637643865333030623036303936303836343830633733653461363039363038363438303630393630383634383036303936303836343830363039363038363438303630393630383634383036303936303836
135+
136+
Repeat this setp by setting Intent filed to NetworkDiag
137+
diagnosticlogs retrieve-logs-request 1 0 1 0
138+
139+
On TH(chip-tool), verify that the DUT responds with NoLogs(2) status code to TH for the RetrieveLogsResponse command and LogContent field is empty
140+
141+
[1707967219.637228][10723:10726] CHIP:TOO: RetrieveLogsResponse: {
142+
[1707967219.637242][10723:10726] CHIP:TOO: status: 2
143+
[1707967219.637248][10723:10726] CHIP:TOO: logContent:
144+
[1707967219.637253][10723:10726] CHIP:TOO: }
145+
146+
Repeat this setp by setting Intent filed to Crash_log
147+
diagnosticlogs retrieve-logs-request 2 0 1 0
148+
149+
On TH(chip-tool), verify that the DUT responds with success(0) status code to TH for the RetrieveLogsResponse command and LogContent field of RetrieveLogsResponse contains at most 1024 bytes
150+
151+
[1707982645.639415][11765:11767] CHIP:TOO: RetrieveLogsResponse: {
152+
[1707982645.639457][11765:11767] CHIP:TOO: status: 0
153+
[1707982645.639489][11765:11767] CHIP:TOO: logContent: logContent: 353535350A
154+
}"
118155
disabled: true
119156

120157
- label:
121-
"Step 9: TH Sends StatusReport(GeneralCode: FAILURE, ProtocolId: BDX,
122-
ProtocolCode: TRANSFER_METHOD_NOT_SUPPORTED)"
158+
"Step 9: TH sends RetrieveLogsRequest Command to DUT without
159+
TransferFileDesignator argument : RetrieveLogsRequest(Intent =
160+
EndUserSupport, RequestedProtocol= BDX)"
161+
PICS: MCORE.BDX.Initiator
123162
verification: |
124-
Not Verifiable
163+
"diagnosticlogs retrieve-logs-request 0 1 1 0
164+
165+
On TH(chip-tool), Verify that the DUT responds with INVALID_COMMAND for the RetrieveLogsRequest that was sent without TransferFileDesignator
166+
167+
[1707924172.241489][42120:42123] CHIP:DMG: InvokeResponseIB =
168+
[1707924172.241494][42120:42123] CHIP:DMG: {
169+
[1707924172.241497][42120:42123] CHIP:DMG: CommandStatusIB =
170+
[1707924172.241500][42120:42123] CHIP:DMG: {
171+
[1707924172.241503][42120:42123] CHIP:DMG: CommandPathIB =
172+
[1707924172.241507][42120:42123] CHIP:DMG: {
173+
[1707924172.241511][42120:42123] CHIP:DMG: EndpointId = 0x0,
174+
[1707924172.241514][42120:42123] CHIP:DMG: ClusterId = 0x32,
175+
[1707924172.241519][42120:42123] CHIP:DMG: CommandId = 0x0,
176+
[1707924172.241527][42120:42123] CHIP:DMG: },
177+
[1707924172.241536][42120:42123] CHIP:DMG:
178+
[1707924172.241539][42120:42123] CHIP:DMG: StatusIB =
179+
[1707924172.241543][42120:42123] CHIP:DMG: {
180+
[1707924172.241546][42120:42123] CHIP:DMG: status = 0x85 (INVALID_COMMAND),
181+
[1707924172.241549][42120:42123] CHIP:DMG: },
182+
[1707924172.241553][42120:42123] CHIP:DMG:
183+
[1707924172.241555][42120:42123] CHIP:DMG: },
184+
[1707924172.241560][42120:42123] CHIP:DMG:
185+
[1707924172.241562][42120:42123] CHIP:DMG: },
186+
[1707924172.241567][42120:42123] CHIP:DMG:
187+
[1707924172.241573][42120:42123] CHIP:DMG: ],
188+
[1707924172.241577][42120:42123] CHIP:DMG:
189+
[1707924172.241579][42120:42123] CHIP:DMG: InteractionModelRevision = 11
190+
[1707924172.241582][42120:42123] CHIP:DMG: },"
125191
disabled: true
126192

127193
- label:
128-
"Step 10: Verify that DUT sends RetrieveLogsResponse command with a
129-
Status field set to Denied"
194+
"Step 10: TH sends RetrieveLogsRequest Command to DUT that does not
195+
support BDX : RetrieveLogsRequest(Intent = EndUserSupport,
196+
RequestedProtocol= BDX, TransferFileDesignator = TH_LOG_OK_NORMAL)"
197+
PICS: "!MCORE.BDX.Initiator"
130198
verification: |
131-
Not Verifiable
199+
"diagnosticlogs retrieve-logs-request 0 1 1 0 --TransferFileDesignator Length_1234567.txt
200+
201+
On TH(chip-tool), Verify that the DUT responds with Exhausted(1) status code for the RetrieveLogsResponse command with the LogContent field containing at most 1024 bytes
202+
203+
[1707979121.749537][7593:7596] CHIP:TOO: RetrieveLogsResponse: {
204+
[1707979121.749565][7593:7596] CHIP:TOO: status: 1
205+
[1707979121.749593][7593:7596] CHIP:TOO: logContent: 31353238303033363031313533353030333730303234303030303234303133653234303230313138333530313331303034373032313533313031316230323330383230323137303630393261383634383836663730643031303730326130383230323038333038323032303430323031303333313064333030623036303936303836343830313635303330343032303133303832303137303036303932613836343838366637306430313037303161303832303136313034383230313564313532343030303132353031663166663336303230353030383030353031383030353032383030353033383030353034383030353035383030353036383030353037383030353038383030353039383030353061383030353062383030353063383030353064383030353065383030353066383030353130383030353131383030353132383030353133383030353134383030353135383030353136383030353137383030353138383030353139383030353161383030353162383030353163383030353164383030353165383030353166383030353230383030353231383030353232383030353233383030353234383030353235383030353236383030353237383030353238383030353239383030353261383030353262383030353263383030353264383030353265383030353266383030353330383030353331383030353332383030353333383030353334383030353335383030353336383030353337383030353338383030353339383030353361383030353362383030353363383030353364383030353365383030353366383030353430383030353431383030353432383030353433383030353434383030353435383030353436383030353437383030353438383030353439383030353461383030353462383030353463383030353464383030353465383030353466383030353530383030353531383030353532383030353533383030353534383030353535383030353536383030353537383030353538383030353539383030353561383030353562383030353563383030353564383030353565383030353566383030353630383030353631383030353632383030353633383031383234303331363263303431333433353334313330333033303330333035333537343333303330333033303330326433303330323430353030323430363030323430373031323430383030313833313763333037613032303130333830313466653334336639353939343737363362363165653435333931333133333834393466653637643865333030623036303936303836343830633733653461363039363038363438303630393630383634383036303936303836343830363039363038363438303630393630383634383036303936303836}"
132206
disabled: true
133207

134208
- label:
135-
"Step 11: TH sends RetrieveLogsRequest Command (Intent =
136-
EndUserSupport, RequestedProtocol = ResponsePayload) to DUT"
209+
"Step 12: TH sends RetrieveLogsRequest Command to DUT with Invalid
210+
RequestedProtocol : RetrieveLogsRequest(Intent =
211+
EndUserSupport,RequestedProtocol= 2, TransferFileDesignator =
212+
TH_LOG_OK_NORMAL)"
213+
PICS: MCORE.BDX.Initiator
137214
verification: |
138-
sudo ./chip-tool diagnosticlogs retrieve-logs-request 0 0 "test.txt" 1 0
215+
"diagnosticlogs retrieve-logs-request 0 2 1 0 --TransferFileDesignator Length_1234567.txt
139216
140-
[1651207416.783607][2465:2470] CHIP:DMG: StatusIB =
141-
[1651207416.783676][2465:2470] CHIP:DMG: {
142-
[1651207416.783722][2465:2470] CHIP:DMG: status = 0x00 (SUCCESS),
143-
[1651207416.783766][2465:2470] CHIP:DMG: },
217+
On TH(chip-tool), Verify that the DUT responds with INVALID_COMMAND for the RetrieveLogsRequest that was sent Invalid RequestedProtocol(2)
218+
219+
707901794.468418][36124:36127] CHIP:DMG: InvokeResponseMessage =
220+
[1707901794.468425][36124:36127] CHIP:DMG: {
221+
[1707901794.468433][36124:36127] CHIP:DMG: suppressResponse = false,
222+
[1707901794.468440][36124:36127] CHIP:DMG: InvokeResponseIBs =
223+
[1707901794.468452][36124:36127] CHIP:DMG: [
224+
[1707901794.468459][36124:36127] CHIP:DMG: InvokeResponseIB =
225+
[1707901794.468471][36124:36127] CHIP:DMG: {
226+
[1707901794.468477][36124:36127] CHIP:DMG: CommandStatusIB =
227+
[1707901794.468485][36124:36127] CHIP:DMG: {
228+
[1707901794.468492][36124:36127] CHIP:DMG: CommandPathIB =
229+
[1707901794.468501][36124:36127] CHIP:DMG: {
230+
[1707901794.468510][36124:36127] CHIP:DMG: EndpointId = 0x0,
231+
[1707901794.468518][36124:36127] CHIP:DMG: ClusterId = 0x32,
232+
[1707901794.468526][36124:36127] CHIP:DMG: CommandId = 0x0,
233+
[1707901794.468533][36124:36127] CHIP:DMG: },
234+
[1707901794.468545][36124:36127] CHIP:DMG:
235+
[1707901794.468552][36124:36127] CHIP:DMG: StatusIB =
236+
[1707901794.468560][36124:36127] CHIP:DMG: {
237+
[1707901794.468569][36124:36127] CHIP:DMG: status = 0x85 (INVALID_COMMAND),
238+
[1707901794.468576][36124:36127] CHIP:DMG: },
239+
[1707901794.468584][36124:36127] CHIP:DMG:
240+
[1707901794.468591][36124:36127] CHIP:DMG: },
241+
[1707901794.468602][36124:36127] CHIP:DMG:
242+
[1707901794.468608][36124:36127] CHIP:DMG: },
243+
[1707901794.468619][36124:36127] CHIP:DMG:
244+
[1707901794.468624][36124:36127] CHIP:DMG: ],
245+
[1707901794.468635][36124:36127] CHIP:DMG:"
144246
disabled: true
145247

146248
- label:
147-
"Step 12: Verify that the BDX transfer is not initiated from DUT,
148-
Verify that the LogContent field of RetrieveLogsResponse has the size
149-
< = 1024 octets"
249+
"Step 13: TH sends RetrieveLogsRequest Command with Invalid
250+
TransferFileDesignator length : RetrieveLogsRequest(Intent =
251+
EndUserSupport,RequestedProtocol= BDX, TransferFileDesignator =
252+
TH_LOG_ERROR_EMPTY)"
150253
verification: |
151-
Not Verifiable
254+
"diagnosticlogs retrieve-logs-request 0 1 1 0 --TransferFileDesignator ''
255+
256+
[1707904517.151453][36678:36681] CHIP:DMG: ICR moving to [ResponseRe]
257+
[1707904517.151489][36678:36681] CHIP:DMG: InvokeResponseMessage =
258+
[1707904517.151501][36678:36681] CHIP:DMG: {
259+
[1707904517.151511][36678:36681] CHIP:DMG: suppressResponse = false,
260+
[1707904517.151522][36678:36681] CHIP:DMG: InvokeResponseIBs =
261+
[1707904517.151541][36678:36681] CHIP:DMG: [
262+
[1707904517.151548][36678:36681] CHIP:DMG: InvokeResponseIB =
263+
[1707904517.151565][36678:36681] CHIP:DMG: {
264+
[1707904517.151573][36678:36681] CHIP:DMG: CommandStatusIB =
265+
[1707904517.151582][36678:36681] CHIP:DMG: {
266+
[1707904517.151590][36678:36681] CHIP:DMG: CommandPathIB =
267+
[1707904517.151599][36678:36681] CHIP:DMG: {
268+
[1707904517.151613][36678:36681] CHIP:DMG: EndpointId = 0x0,
269+
[1707904517.151627][36678:36681] CHIP:DMG: ClusterId = 0x32,
270+
[1707904517.151640][36678:36681] CHIP:DMG: CommandId = 0x0,
271+
[1707904517.151652][36678:36681] CHIP:DMG: },
272+
[1707904517.151670][36678:36681] CHIP:DMG:
273+
[1707904517.151681][36678:36681] CHIP:DMG: StatusIB =
274+
[1707904517.151696][36678:36681] CHIP:DMG: {
275+
[1707904517.151708][36678:36681] CHIP:DMG: status = 0x87 (CONSTRAINT_ERROR),
276+
[1707904517.151720][36678:36681] CHIP:DMG: },
277+
[1707904517.151734][36678:36681] CHIP:DMG:
278+
[1707904517.151745][36678:36681] CHIP:DMG: },
279+
[1707904517.151763][36678:36681] CHIP:DMG:
280+
[1707904517.151772][36678:36681] CHIP:DMG: },
281+
[1707904517.151790][36678:36681] CHIP:DMG:
282+
[1707904517.151798][36678:36681] CHIP:DMG: ],
283+
[1707904517.151816][36678:36681] CHIP:DMG:
284+
[1707904517.151824][36678:36681] CHIP:DMG: InteractionModelRevision = 11
285+
[1707904517.151830][36678:36681] CHIP:DMG: },"
152286
disabled: true
153287

154288
- label:
155-
"Step 13: Verify that DUT sends RetrieveLogsResponse command with a
156-
Status field set to Success, Verify that UTCTimeStamp is included in
157-
the RetrieveLogsResponse command,Verify that TimeSinceBoot is included
158-
in the RetrieveLogsResponse command"
289+
"Step 14: TH sends RetrieveLogsRequest Command to DUT with Invalid
290+
TransferFileDesignator length : RetrieveLogsRequest(Intent =
291+
EndUserSupport,RequestedProtocol= BDX, TransferFileDesignator =
292+
TH_LOG_BAD_LENGTH)"
159293
verification: |
160-
sudo ./chip-tool diagnosticlogs retrieve-logs-request 0 1 "test.txt" 1 0
294+
"diagnosticlogs retrieve-logs-request 0 1 1 0 --TransferFileDesignator Length_1234567891234567891234567891212345.txt
295+
296+
On TH(chip-tool), Verify that the DUT responds with CONSTRAINT_ERRORfor the RetrieveLogsRequest that was sent Invalid Invalid TransferFileDesignator length(> 32)
161297
162-
[1651207438.423557][2475:2480] CHIP:DMG: StatusIB =
163-
[1651207438.423594][2475:2480] CHIP:DMG: {
164-
[1651207438.423648][2475:2480] CHIP:DMG: status = 0x00 (SUCCESS),
165-
[1651207438.423708][2475:2480] CHIP:DMG: },
298+
[1707904517.151453][36678:36681] CHIP:DMG: ICR moving to [ResponseRe]
299+
[1707904517.151489][36678:36681] CHIP:DMG: InvokeResponseMessage =
300+
[1707904517.151501][36678:36681] CHIP:DMG: {
301+
[1707904517.151511][36678:36681] CHIP:DMG: suppressResponse = false,
302+
[1707904517.151522][36678:36681] CHIP:DMG: InvokeResponseIBs =
303+
[1707904517.151541][36678:36681] CHIP:DMG: [
304+
[1707904517.151548][36678:36681] CHIP:DMG: InvokeResponseIB =
305+
[1707904517.151565][36678:36681] CHIP:DMG: {
306+
[1707904517.151573][36678:36681] CHIP:DMG: CommandStatusIB =
307+
[1707904517.151582][36678:36681] CHIP:DMG: {
308+
[1707904517.151590][36678:36681] CHIP:DMG: CommandPathIB =
309+
[1707904517.151599][36678:36681] CHIP:DMG: {
310+
[1707904517.151613][36678:36681] CHIP:DMG: EndpointId = 0x0,
311+
[1707904517.151627][36678:36681] CHIP:DMG: ClusterId = 0x32,
312+
[1707904517.151640][36678:36681] CHIP:DMG: CommandId = 0x0,
313+
[1707904517.151652][36678:36681] CHIP:DMG: },
314+
[1707904517.151670][36678:36681] CHIP:DMG:
315+
[1707904517.151681][36678:36681] CHIP:DMG: StatusIB =
316+
[1707904517.151696][36678:36681] CHIP:DMG: {
317+
[1707904517.151708][36678:36681] CHIP:DMG: status = 0x87 (CONSTRAINT_ERROR),
318+
[1707904517.151720][36678:36681] CHIP:DMG: },
319+
[1707904517.151734][36678:36681] CHIP:DMG:
320+
[1707904517.151745][36678:36681] CHIP:DMG: },
321+
[1707904517.151763][36678:36681] CHIP:DMG:
322+
[1707904517.151772][36678:36681] CHIP:DMG: },
323+
[1707904517.151790][36678:36681] CHIP:DMG:
324+
[1707904517.151798][36678:36681] CHIP:DMG: ],
325+
[1707904517.151816][36678:36681] CHIP:DMG:
326+
[1707904517.151824][36678:36681] CHIP:DMG: InteractionModelRevision = 11
327+
[1707904517.151830][36678:36681] CHIP:DMG: },"
166328
disabled: true

0 commit comments

Comments
 (0)
Please sign in to comment.