Skip to content
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/soc_flash_nrf: Fix soc_flash_nrf doc and printfs #68565

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions samples/drivers/soc_flash_nrf/README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -8,9 +8,9 @@ Overview
********

This sample demonstrates using the :ref:`Flash API <flash_api>` on an SoC internal storage.
The sample uses :ref:`Flash map API <flash_map_api>` to obtain a device that has
partition defined with label `storage_partition`, then uses :ref:`Flash API <flash_api>`
to directly access and modify contents of a device, within area defined for said
The sample uses :ref:`Flash map API <flash_map_api>` to obtain a device that has one
partition defined with the label ``storage_partition``, then uses :ref:`Flash API <flash_api>`
to directly access and modify the contents of a device within the area defined for said
partition.

Within the sample, user may observe how read/write/erase operations
Expand All @@ -20,9 +20,9 @@ ready for operation.
Building and Running
********************

The application will build for any SoC with internal storage
access enabled, as it is default for SoC devices with defined
fixed-partition, over that internal storage, labeled `storage_partition`.
The sample will be built for any SoC with internal storage, as long as
there is a fixed-partition named ``storage_partition`` defined
on that internal storage.

.. zephyr-app-commands::
:zephyr-app: samples/drivers/soc_flash_nrf
Expand Down
Loading