[NXP][examples][k32w0] Update paths after nxp_matter_support switch

Signed-off-by: marius-alex-tache <marius.tache@nxp.com>
(cherry picked from commit 871ea893b3ad1f7d6d7b6943827a666b89f50b8f)

Author: marius-alex-tache

examples/contact-sensor-app/nxp/k32w0/BUILD.gn

@@ -41,7 +41,7 @@ if (chip_pw_tokenizer_logging) {
 
 assert(current_os == "freertos")
 
-k32w0_platform_dir = "${chip_root}/examples/platform/nxp/k32w0"
+k32w0_platform_dir = "${nxp_sdk_matter_support_root}/examples/platform/k32w0"
 
 k32w0_sdk("sdk") {
   sources = [

examples/contact-sensor-app/nxp/k32w0/README.md

@@ -49,7 +49,7 @@ network.
 
 ## Introduction
 
-![K32W061 DK6](../../../platform/nxp/k32w0/doc/images/k32w-dk6.jpg)
+![K32W061 DK6](../../../../third_party/nxp/nxp_matter_support/examples/platform/k32w0/doc/images/k32w-dk6.jpg)
 
 The K32W061 contact sensor example application provides a working demonstration
 of a connected contact sensor device, built using the Project CHIP codebase and
@@ -79,7 +79,7 @@ Deployment of this firmware configuration requires the K32W061 board setups
 using the K32W061 module board, SE051 Expansion board and Generic Expansion
 board as shown below:
 
-![SE051H  + K32W061 DK6](../../../platform/nxp/k32w0/doc/images/k32w-se.jpg)
+![SE051H  + K32W061 DK6](../../../../third_party/nxp/nxp_matter_support/examples/platform/k32w0/doc/images/k32w-se.jpg)
 
 The SE051H Secure Element extension may be used for best in class security and
 offloading some of the Project CHIP cryptographic operations. Depending on your
@@ -356,17 +356,17 @@ See
 [Guide for writing manufacturing data on NXP devices](../../../../docs/guides/nxp/nxp_manufacturing_flow.md).
 
 There are factory data generated binaries available in
-examples/platform/nxp/k32w0/scripts/demo_generated_factory_data folder.
+`third_party/nxp/nxp_matter_support/examples/platform/k32w0/scripts/demo_generated_factory_data` folder.
 These are based on the DAC, PAI and PAA certificates found in
 scripts/tools/nxp/demo_generated_certs folder. The demo_factory_data_dut1.bin
 uses the DAC certificate and private key found in
-examples/platform/nxp/k32w0/scripts/demo_generated_factory_data/dac/dut1
+`third_party/nxp/nxp_matter_support/examples/platform/k32w0/scripts/demo_generated_factory_data/dac/dut1`
 folder. The demo_factory_data_dut2.bin uses the DAC certificate and private key
 found in
-examples/platform/nxp/k32w0/scripts/demo_generated_factory_data/dac/dut2
+`third_party/nxp/nxp_matter_support/examples/platform/k32w0/scripts/demo_generated_factory_data/dac/dut2`
 folder. These two factory data binaries can be used for testing topologies with
 2 DUTS. They contain the corresponding DACs/PAIs generated using
-generate_nxp_chip_factory_bin.py script. The discriminator is 14014 and the
+`generate_nxp_chip_factory_bin.py` script. The discriminator is 14014 and the
 passcode is 1000. These demo certificates are working with the CDs installed in
 CHIPProjectConfig.h.
 
@@ -375,7 +375,7 @@ Regarding factory data provider, there are two options:
 -   use the default factory data provider: `FactoryDataProviderImpl` by setting
     `chip_with_factory_data=1` in the gn build command.
 -   use a custom factory data provider: please see
-    [Guide for implementing a custom factory data provider](../../../platform/nxp/k32w0/common/README.md).
+    [Guide for implementing a custom factory data provider](../../../../third_party/nxp/nxp_matter_support/examples/platform/k32w0/common/README.md).
     This can be enabled when `chip_with_factory_data=1` by setting
     `use_custom_factory_provider=1` in the gn build command.
 
@@ -509,7 +509,7 @@ needed for parsing the hashed scripts.
 
 The python3 script detokenizer.py is a script that decodes the tokenized logs
 either from a file or from a serial port. It is located in the following path
-`examples/platform/nxp/k32w0/scripts/detokenizer.py`.
+`third_party/nxp/nxp_matter_support/examples/platform/k32w0/scripts/detokenizer.py`.
 
 The script can be used in the following ways:
 
@@ -544,7 +544,7 @@ by the script is loaded by the environment. An example of running the
 detokenizer script to see logs of a contact-sensor app:
 
 ```
-python3 ../../../../examples/platform/nxp/k32w0/scripts/detokenizer.py serial -i /dev/ttyACM0 -d out/debug/chip-k32w0x-contact-example-database.bin -o device.txt
+python3 ../../../../third_party/nxp/nxp_matter_support/examples/platform/k32w0/scripts/detokenizer.py serial -i /dev/ttyACM0 -d out/debug/chip-k32w0x-contact-example-database.bin -o device.txt
 ```
 
 ### Known issues tokenizer
@@ -616,7 +616,7 @@ is done.
 The OTA topology used for OTA testing is illustrated in the figure below.
 Topology is similar with the one used for Matter Test Events.
 
-![OTA_TOPOLOGY](../../../platform/nxp/k32w0/doc/images/ota_topology.JPG)
+![OTA_TOPOLOGY](../../../../third_party/nxp/nxp_matter_support/examples/platform/k32w0/doc/images/ota_topology.JPG)
 
 The concept for OTA is the next one:
 
@@ -795,13 +795,13 @@ Power Measurement Tool can be used inside MCUXpresso for checking the power
 consumption pattern: Window -> Show View -> Other -> Power Measurement Tool. The
 configuration for this tool is the next one:
 
-![POWER_CONF](../../../platform/nxp/k32w0/doc/images/power_conf.JPG)
+![POWER_CONF](../../../../third_party/nxp/nxp_matter_support/examples/platform/k32w0/doc/images/power_conf.JPG)
 
 Also, please make sure that the J14 jumper is set to the _ENABLED_ position and
 no expansion board is attached to the DK6. A view from this tool is illustrated
 below:
 
-![POWER_VIEW](../../../platform/nxp/k32w0/doc/images/power_view.JPG)
+![POWER_VIEW](../../../../third_party/nxp/nxp_matter_support/examples/platform/k32w0/doc/images/power_view.JPG)
 
 Please note that that the Power Measurement Tool is not very accurate and
 professional tools must be used if exact power consumption needs to be known.

examples/lighting-app/nxp/k32w0/BUILD.gn

@@ -40,7 +40,7 @@ if (chip_pw_tokenizer_logging) {
 
 assert(current_os == "freertos")
 
-k32w0_platform_dir = "${chip_root}/examples/platform/nxp/k32w0"
+k32w0_platform_dir = "${nxp_sdk_matter_support_root}/examples/platform/k32w0"
 
 k32w0_sdk("sdk") {
   sources = [

examples/lighting-app/nxp/k32w0/README.md

@@ -47,7 +47,7 @@ network.
 
 ## Introduction
 
-![K32W061 DK6](../../../platform/nxp/k32w0/doc/images/k32w-dk6.jpg)
+![K32W061 DK6](../../../../third_party/nxp/nxp_matter_support/examples/platform//k32w0/doc/images/k32w-dk6.jpg)
 
 The K32W061 lighting example application provides a working demonstration of a
 light bulb device, built using the Project CHIP codebase and the NXP K32W061
@@ -77,7 +77,7 @@ Deployment of this firmware configuration requires the K32W061 board setups
 using the K32W061 module board, SE051 Expansion board and Generic Expansion
 board as shown below:
 
-![SE051H  + K32W061 DK6](../../../platform/nxp/k32w0/doc/images/k32w-se.jpg)
+![SE051H  + K32W061 DK6](../../../../third_party/nxp/nxp_matter_support/examples/platform//k32w0/doc/images/k32w-se.jpg)
 
 The SE051H Secure Element extension may be used for best in class security and
 offloading some of the Project CHIP cryptographic operations. Depending on your
@@ -332,17 +332,17 @@ See
 [Guide for writing manufacturing data on NXP devices](../../../../docs/guides/nxp/nxp_manufacturing_flow.md).
 
 There are factory data generated binaries available in
-examples/platform/nxp/k32w0/scripts/demo_generated_factory_data folder.
+`third_party/nxp/nxp_matter_support/examples/platform/k32w0/scripts/demo_generated_factory_data` folder.
 These are based on the DAC, PAI and PAA certificates found in
 scripts/tools/nxp/demo_generated_certs folder. The demo_factory_data_dut1.bin
 uses the DAC certificate and private key found in
-examples/platform/nxp/k32w0/scripts/demo_generated_factory_data/dac/dut1
+`third_party/nxp/nxp_matter_support/examples/platform/k32w0/scripts/demo_generated_factory_data/dac/dut1`
 folder. The demo_factory_data_dut2.bin uses the DAC certificate and private key
 found in
-examples/platform/nxp/k32w0/scripts/demo_generated_factory_data/dac/dut2
+`third_party/nxp/nxp_matter_support/examples/platform/k32w0/scripts/demo_generated_factory_data/dac/dut2`
 folder. These two factory data binaries can be used for testing topologies with
 2 DUTS. They contain the corresponding DACs/PAIs generated using
-generate_nxp_chip_factory_bin.py script. The discriminator is 14014 and the
+`generate_nxp_chip_factory_bin.py` script. The discriminator is 14014 and the
 passcode is 1000. These demo certificates are working with the CDs installed in
 CHIPProjectConfig.h.
 
@@ -351,7 +351,7 @@ Regarding factory data provider, there are two options:
 -   use the default factory data provider: `FactoryDataProviderImpl` by setting
     `chip_with_factory_data=1` in the gn build command.
 -   use a custom factory data provider: please see
-    [Guide for implementing a custom factory data provider](../../../platform/nxp/k32w0/common/README.md).
+    [Guide for implementing a custom factory data provider](../../../../third_party/nxp/nxp_matter_support/examples/platform//k32w0/common/README.md).
     This can be enabled when `chip_with_factory_data=1` by setting
     `use_custom_factory_provider=1` in the gn build command.
 
@@ -485,7 +485,7 @@ needed for parsing the hashed scripts.
 
 The python3 script detokenizer.py is a script that decodes the tokenized logs
 either from a file or from a serial port. It is located in the following path
-`examples/platform/nxp/k32w0/scripts/detokenizer.py`.
+`third_party/nxp/nxp_matter_support/examples/platform/k32w0/scripts/detokenizer.py`.
 
 The script can be used in the following ways:
 
@@ -520,7 +520,7 @@ by the script is loaded by the environment. An example of running the
 detokenizer script to see logs of a lighting app:
 
 ```
-python3 ../../../../examples/platform/nxp/k32w0/scripts/detokenizer.py serial -i /dev/ttyACM0 -d out/debug/chip-k32w0x-light-example-database.bin -o device.txt
+python3 ../../../../third_party/nxp/nxp_matter_support/examples/platform/k32w0/scripts/detokenizer.py serial -i /dev/ttyACM0 -d out/debug/chip-k32w0x-light-example-database.bin -o device.txt
 ```
 
 ### Known issues tokenizer
@@ -592,7 +592,7 @@ is done.
 The OTA topology used for OTA testing is illustrated in the figure below.
 Topology is similar with the one used for Matter Test Events.
 
-![OTA_TOPOLOGY](../../../platform/nxp/k32w0/doc/images/ota_topology.JPG)
+![OTA_TOPOLOGY](../../../../third_party/nxp/nxp_matter_support/examples/platform//k32w0/doc/images/ota_topology.JPG)
 
 The concept for OTA is the next one:
 

src/platform/nxp/k32w0/args.gni

@@ -24,7 +24,7 @@ nxp_use_mbedtls_port = false
 
 if (getenv("NXP_K32W0_SDK_ROOT") == "") {
   k32w0_sdk_root =
-      "${nxp_sdk_matter_support_root}/github_sdk/k32w0_sdk/repo"
+      "${nxp_sdk_matter_support_root}/github_sdk/k32w0/repo"
 } else {
   k32w0_sdk_root = getenv("NXP_K32W0_SDK_ROOT")
 }
@@ -72,6 +72,6 @@ openthread_external_mbedtls = mbedtls_target
 openthread_project_core_config_file = "OpenThreadConfig.h"
 openthread_core_config_platform_check_file =
     "openthread-core-k32w061-config-check.h"
-openthread_core_config_deps = [ "${chip_root}/examples/platform/nxp/k32w0:openthread_core_config_k32w0_chip_examples" ]
+openthread_core_config_deps = [ "${nxp_sdk_matter_support_root}/examples/platform/k32w0:openthread_core_config_k32w0_chip_examples" ]
 
 openthread_external_platform = "${chip_root}/third_party/openthread/platforms/nxp/k32w0:libopenthread-k32w0"

third_party/openthread/platforms/nxp/k32w0/BUILD.gn

@@ -30,7 +30,7 @@ config("openthread_k32w0_config") {
     "${openthread_nxp_root}/src/k32w0/platform",
     "${openthread_nxp_root}/src/common",
   ]
-  include_dirs += [ "${chip_root}/examples/platform/nxp/k32w0" ]
+  include_dirs += [ "${nxp_sdk_matter_support_root}/examples/platform/k32w0" ]
 
   if (is_clang) {
     cflags = [ "-Wno-format-nonliteral" ]
@@ -46,7 +46,7 @@ config("openthread_k32w0_config") {
 
 source_set("openthread_core_config_k32w0") {
   sources = [
-    "${chip_root}/examples/platform/nxp/k32w0/app/project_include/OpenThreadConfig.h",
+    "${nxp_sdk_matter_support_root}/examples/platform/k32w0/app/project_include/OpenThreadConfig.h",
     "${openthread_nxp_root}/src/k32w0/k32w061/openthread-core-k32w061-config-check.h",
   ]