Matter 4.3.1.8. Device Type (DT) TXT key

[H-ogawa]

Hi,

This function is optional, but what if I want to turn it on on the DUT side?

Best regards,

Hiroki

[AHaug]

Hi Hiroki,

As far as I know, you can enable them during testing using the CHIP tool: https://docs.nordicsemi.com/bundle/ncs-latest/page/matter/chip_tool_guide.html#using_chip_tool_for_matter_device_testing. 

In case you've not seen this documentation page, have you found anything seen the creating a Matter end product page documentation https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/matter/end_product/index.html 

Kind regards,
Andreas

[H-ogawa]

Hi, Andreas

Thank you for reply.

AHaug said:

As far as I know, you can enable them during testing using the CHIP tool: https://docs.nordicsemi.com/bundle/ncs-latest/page/matter/chip_tool_guide.html#using_chip_tool_for_matter_device_testing. 

I checked the URL and it is a document on how to use the chip-tool. I would like you to tell me in detail which part is actually related to Matter 4.3.1.8. Device Type (DT) TXT key.

AHaug said:

In case you've not seen this documentation page, have you found anything seen the creating a Matter end product page documentation https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/matter/end_product/index.html 

This is also the same. Could you please tell me in detail where in the documentation the Matter 4.3.1.8. Device Type (DT) TXT key is?

Best regards,

Hiroki

[H-ogawa]

Hi,Andreas

I'm not sure I answered the question correctly either, so I'll ask it again.

I am conducting the TC-DD-2.1 test cases in the Matter certification exam.

I cannot determine whether the test in step 13b of that test case can be tested as a device or not.
In fact, when I test with the v2.9.0 lock sample code, the Device Type value is not visible as TH.
I would like to confirm whether I need to change the settings in the lock sample code to make this visible.

In the Lock sample code, the vendor ID and product ID in step 13a of the test case were confirmed in TH.

Best regards,

Hiroki

 

[AHaug]

Hi Hiroki,

Just a status update to let you know I'm waiting for some input from the Matter team.

Thank you for your patience

Kind regards,
Andreas

[AHaug]

Hi again Hiroki

I got some input from R&D. Since the Device Type TXT Key is not something that the sample supports out of the box, you will have to add support for this in the application before testing it in the TH. You only need to change MCORE.DD.TXT_KEY_DT to true in the Base.xml PICS file used to certification.

Let me know if this works and I'll get back to you

Kind regards,
Andreas

[H-ogawa]

Hi,Andreas

Thank you for reply.

AHaug said:

I got some input from R&D. Since the Device Type TXT Key is not something that the sample supports out of the box, you will have to add support for this in the application before testing it in the TH.

I would like to know how to add this or set it in my application.

AHaug said:

ou only need to change MCORE.DD.TXT_KEY_DT to true in the Base.xml PICS file used to certification

I believe this PICS setting is at the discretion of the certification body to decide whether or not to perform certification testing. I do not believe that simply enabling this setting will change the settings of the device being tested.

Best regards,

Hiroki

[AHaug]

Hello Hiroki,

Apologies for the long response time. I had to clarify the details with the Matter team because I did misunderstand something.

Here's what they said:

If you want to enable testing the DT TXT KEy in certfication you should state that in the PICS. However setting PICS does not affect the DUT implementation (PICS are information for CSA/Certification about supported features to know what to test and what to expect).

If the client want to enable the DT TXT key in commissionable service in the DUT implementation, the prj.conf need to be update to enable following configs:

CONFIG_CHIP_COMMISSIONABLE_DEVICE_TYPE=y

CONFIG_CHIP_DEVICE_TYPE=<int value of device type e.g. 257> 

It should enable the additional txt key in the commissionable service.

https://github.com/nrfconnect/sdk-connectedhomeip/blob/master/config/zephyr/Kconfig#L264

https://github.com/nrfconnect/sdk-connectedhomeip/blob/master/config/zephyr/Kconfig#L162

Let me know if this makes more sense

Kind regards,
Andreas