From dfb01fba67d12715c393c49a83839b53544febc3 Mon Sep 17 00:00:00 2001 From: Marius Tache <102153746+marius-alex-tache@users.noreply.github.com> Date: Wed, 25 Sep 2024 23:34:46 +0300 Subject: [PATCH] [NXP][docs] Small updates to manufacturing flow format (#35720) * [nxp][docs][common] Small updates to manufacturing flow format Signed-off-by: marius-alex-tache * Restyled by prettier-markdown * [nxp][docs][common] Fix rw61x symbol * Restyled by prettier-markdown --------- Signed-off-by: marius-alex-tache Co-authored-by: Restyled.io --- docs/guides/nxp/nxp_manufacturing_flow.md | 41 ++++++----------------- 1 file changed, 11 insertions(+), 30 deletions(-) diff --git a/docs/guides/nxp/nxp_manufacturing_flow.md b/docs/guides/nxp/nxp_manufacturing_flow.md index 0551d43966f08e..08e09c866388ff 100644 --- a/docs/guides/nxp/nxp_manufacturing_flow.md +++ b/docs/guides/nxp/nxp_manufacturing_flow.md @@ -137,34 +137,14 @@ Here is the interpretation of the **optional** parameters: ## 3. Write provisioning data -For the **K32W0x1** variants, the binary needs to be written in the internal -flash at location **0x9D600** using `DK6Programmer.exe`: - -```shell -DK6Programmer.exe -Y -V2 -s -P 1000000 -Y -p FLASH@0x9D600="factory_data.bin" -``` - -For **K32W1** platform, the binary needs to be written in the internal flash at -location given by **0xFE080**, using `JLink`: - -``` -loadfile factory_data.bin 0xFE080 -``` - -For **RW61X** platform, the binary needs to be written in the internal flash at -location given by `__MATTER_FACTORY_DATA_START`, using `JLink`: - -``` -loadfile factory_data.bin 0xBFFF000 -``` - -where `0xBFFF000` is the value of `__FACTORY_DATA_START` in the corresponding -.map file (can be different if using a custom linker script). - -For the **RT1060** and **RT1170** platform, the binary needs to be written using -`MCUXpresso Flash Tool GUI` at the address value corresponding to -`__FACTORY_DATA_START` (the map file of the application should be checked to get -the exact value). +| platform | tool | command | details | +| --------- | -------------------------------- | ------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------- | +| `k32w0x1` | `DK6Programmer.exe` or `dk6prog` | `DK6Programmer.exe -Y -V2 -s -P 1000000 -Y -p FLASH@0x9D600="factory_data.bin"` | NA | +| `k32w1` | `JLink` | `loadfile factory_data.bin 0xFE080` | NA | +| `mcxw71` | `JLink` | `loadfile factory_data.bin 0xFE080` | NA | +| `rw61x` | `JLink` | `loadfile factory_data.bin 0xBFFF000` | Here, `0xBFFF000` is the value of symbol `__FACTORY_DATA_START` from the corresponding `.map` file | +| `rt1060` | `MCUXpresso Flash Tool GUI` | NA | The address is given by the `__FACTORY_DATA_START` symbol in the `.map` file | +| `rt1170` | `MCUXpresso Flash Tool GUI` | NA | The address is given by the `__FACTORY_DATA_START` symbol in the `.map` file | ## 4. Build app and usage @@ -202,11 +182,12 @@ Also, demo **DAC**, **PAI** and **PAA** certificates needed in case ## 6. Increased security for DAC private key -### 6.1 K32W1 +### 6.1 SSS-based platforms Supported platforms: -- K32W1 - `src/plaftorm/nxp/k32w1/FactoryDataProviderImpl.h` +- `k32w1` +- `mcxw71` For platforms that have a secure subsystem (`SSS`), the DAC private key can be converted to an encrypted blob. This blob will overwrite the DAC private key in