-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
samples: matter: Add guide on how to flash factory data on nRF54H #18398
samples: matter: Add guide on how to flash factory data on nRF54H #18398
Conversation
The following west manifest projects have been modified in this Pull Request:
Note: This message is automatically posted and updated by the Manifest GitHub Action. |
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: e464a7bfa5b7225f7a4aeaaf5ed9861900d7c67b more detailssdk-nrf:
matter:
Github labels
List of changed files detected by CI (7)
Outputs:ToolchainVersion: Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publishing GitHub Action. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two comments, the rest looks good to me:
- Should we add the same peace of docs into bridge .rst?
- Should we create a known issue for this limitation?
samples/matter/lock/README.rst
Outdated
west flash --erase | ||
|
||
The ``west flash --erase`` command does not clear the factory data partition. | ||
If you want to clear it, use the following command, and fill the ``<address>`` argument as an address of the factory data partition, by default it is set to ``0xe174000``: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you want to clear it, use the following command, and fill the ``<address>`` argument as an address of the factory data partition, by default it is set to ``0xe174000``: | |
If you want to clear it, use the following command, and fill the ``<address>`` argument as an address of the factory data partition. | |
By default, the address is set to ``0xe174000``. |
Could also be that the argument defaults to the value, not sure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They can modify that value in the dts file, so maybe we should do it generically but point out the default value to ensure that it will work for the first attempt.
@FrancescoSer Since this is about nRF54H, do you want to take a look? |
67a8ac5
to
1c00a39
Compare
I believe factory data was not supported for v2.7.0 for nRF54H20, so no known issue is needed. |
Until we do not have a proper solution for merging the factory data hex file with the firmware hex file, we need to flash the factory data manually. This commit allows doing that on nRF54H20 DK and describes how to do it in Matter samples. Signed-off-by: Arkadiusz Balys <[email protected]>
1c00a39
to
e464a7b
Compare
Until we do not have a proper solution for merging the factory data hex file with the firmware hex file, we need to flash the factory data manually. This commit allows doing that on nRF54H20 DK and describes how to do it in Matter samples.