doc: Updates to Asset tracker template docs

Updates to Asset tracker template docs.

Signed-off-by: divya pillai <[email protected]>

Author: divipillai

README.md

@@ -14,156 +14,10 @@
 
 ## Overview
 
-The Asset Tracker Template is a modular framework for developing IoT applications on nRF91-based devices. Built on [nRF Connect SDK](https://www.nordicsemi.com/Products/Development-software/nRF-Connect-SDK) and [Zephyr RTOS](https://docs.zephyrproject.org/latest/), it provides an event-driven architecture for battery-powered IoT use cases with cloud connectivity, location tracking, and sensor data collection.
+The Asset Tracker Template is a modular framework for developing IoT applications on nRF91-based devices. It is built on the [nRF Connect SDK](https://www.nordicsemi.com/Products/Development-software/nRF-Connect-SDK) and [Zephyr RTOS](https://docs.zephyrproject.org/latest/), and provides a modular, event-driven architecture suitable for battery-powered IoT use cases. The framework supports features such as cloud connectivity, location tracking, and sensor data collection.
 
-The system uses modules that communicate through [zbus](https://docs.nordicsemi.com/bundle/ncs-latest/page/zephyr/services/zbus/index.html) channels for loose coupling and maintainability. It's suitable for asset tracking, environmental monitoring, and other IoT applications requiring modularity and power efficiency.
+The system is organized into modules, each responsible for a specific functionality, such as managing network connectivity, handling cloud communication, or collecting environmental data. Modules communicate through [zbus](https://docs.nordicsemi.com/bundle/ncs-latest/page/zephyr/services/zbus/index.html) channels, ensuring loose coupling and maintainability.
 
-**Supported hardware**: [Thingy:91 X](https://www.nordicsemi.com/Products/Development-hardware/Nordic-Thingy-91-X), [nRF9151 DK](https://www.nordicsemi.com/Products/Development-hardware/nRF9151-DK)
+## Getting started
 
-> **Note**: If you're new to nRF91 series and cellular IoT, consider taking the [Nordic Developer Academy Cellular Fundamentals Course](https://academy.nordicsemi.com/courses/cellular-iot-fundamentals).
-
-## Quick Start
-
-For detailed setup instructions using the [nRF Connect for VS Code extension](https://docs.nordicsemi.com/bundle/nrf-connect-vscode/page/index.html) and advanced configuration options, see the [Getting Started Guide](docs/common/getting_started.md).
-
-For pre-built binaries, refer to the latest tag and release artifacts documentaion; [release artifacts](docs/common/release.md).
-
-### Prerequisites
-
-* nRF Connect SDK development environment ([setup guide](https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/installation.html))
-
-### Build and Run
-
-<details>
-<summary>1. <strong>Initialize workspace:</strong></summary>
-
-```shell
-# Install nRF Util
-pip install nrfutil
-
-# or follow install [documentation](https://docs.nordicsemi.com/bundle/nrfutil/page/guides/installing.html)
-
-# Install toolchain
-nrfutil toolchain-manager install --ncs-version v3.1.0
-
-# Launch toolchain
-nrfutil toolchain-manager launch --ncs-version v3.1.0 --shell
-
-# Initialize workspace
-west init -m https://github.com/nrfconnect/Asset-Tracker-Template.git --mr main asset-tracker-template
-cd asset-tracker-template/project/app
-west update
-```
-</details>
-
-<details>
-<summary>2. <strong>Build and flash:</strong></summary>
-
-**For Thingy:91 X:**
-```shell
-west build --pristine --board thingy91x/nrf9151/ns
-west thingy91x-dfu  # For Thingy:91 X serial bootloader
-# Or with external debugger:
-west flash --erase
-```
-
-**For nRF9151 DK:**
-```shell
-west build --pristine --board nrf9151dk/nrf9151/ns
-west flash --erase
-```
-</details>
-
-<details>
-<summary>3. <strong>Provision device:</strong></summary>
-
-1. Get the device attestation token over terminal shell:
-
-   ```bash
-   at at%attesttoken
-   ```
-
-   *Note: Token is printed automatically on first boot of unprovisioned devices.*
-
-2. In nRF Cloud: **Security Services** → **Claimed Devices** → **Claim Device**
-3. Paste token, set rule to "nRF Cloud Onboarding", click **Claim Device**
-
-    <details>
-    <summary><strong>If "nRF Cloud Onboarding" rule is not showing:</strong></summary>
-
-    Create a new rule using the following configuration:
-
-    <img src="docs/images/claim.png" alt="Claim Device" width="300" />
-    </details>
-
-4. Wait for the device to provision credentials and connect to nRF Cloud over CoAP.
-
-See [Provisioning](docs/common/provisioning.md) for more details.
-</details>
-
-## System Architecture
-
-Core modules include:
-
-* **[Main](docs/modules/main.md)**: Central coordinator implementing business logic
-* **[Storage](docs/modules/storage.md)**: Data collection and buffering management
-* **[Network](docs/modules/network.md)**: LTE connectivity management
-* **[Cloud](docs/modules/cloud.md)**: nRF Cloud CoAP communication
-* **[Location](docs/modules/location.md)**: GNSS, Wi-Fi, and cellular positioning
-* **[LED](docs/modules/led.md)**: RGB LED control for Thingy:91 X
-* **[Button](docs/modules/button.md)**: User input handling
-* **[FOTA](docs/modules/fota.md)**: Firmware over-the-air updates
-* **[Environmental](docs/modules/environmental.md)**: Sensor data collection
-* **[Power](docs/modules/power.md)**: Battery monitoring and power management
-
-![System overview](docs/images/system_overview.svg)
-
-### Key Features
-
-* **State Machine Framework (SMF)**: Predictable behavior with run-to-completion model
-* **Message-Based Communication**: Loose coupling via [zbus](https://docs.nordicsemi.com/bundle/ncs-latest/page/zephyr/services/zbus/index.html) channels
-* **Modular Architecture**: Separation of concerns with dedicated threads for blocking operations
-* **Power Optimization**: LTE PSM enabled by default with configurable power-saving features
-
-The architecture is detailed in the [Architecture documentation](docs/common/architecture.md).
-
-## Table of Content
-
-* [Getting Started](docs/common/getting_started.md)
-* [Architecture](docs/common/architecture.md)
-  * [System Overview](docs/common/architecture.md#system-overview)
-  * [Zbus](docs/common/architecture.md#zbus)
-  * [State Machine Framework](docs/common/architecture.md#state-machine-framework)
-* [Configurability](docs/common/configuration.md)
-  * [Set sampling interval and logic from cloud](docs/common/configuration.md#set-sampling-interval-and-logic-from-cloud)
-  * [Set location method priorities](docs/common/configuration.md#set-location-method-priorities)
-  * [Network configuration](docs/common/configuration.md#network-configuration)
-  * [LED Status Indicators](docs/common/configuration.md#led-status-indicators)
-* [Customization](docs/common/customization.md)
-  * [Add a new zbus event](docs/common/customization.md#add-a-new-zbus-event)
-  * [Add environmental sensor](docs/common/customization.md#add-environmental-sensor)
-  * [Add your own module](docs/common/customization.md#add-your-own-module)
-  * [Enable support for MQTT](docs/common/customization.md#enable-support-for-mqtt)
-* [Location Services](docs/common/location_services.md)
-* [Test and CI Setup](docs/common/test_and_ci_setup.md)
-* [nRF Cloud FOTA](docs/common/nrfcloud_fota.md)
-* [Tooling and Troubleshooting](docs/common/tooling_troubleshooting.md)
-  * [Shell Commands](docs/common/tooling_troubleshooting.md#shell-commands)
-  * [Debugging Tools](docs/common/tooling_troubleshooting.md#debugging-tools)
-  * [Memfault Remote Debugging](docs/common/tooling_troubleshooting.md#memfault-remote-debugging)
-  * [Modem Tracing](docs/common/tooling_troubleshooting.md#modem-tracing)
-  * [Common Issues and Solutions](docs/common/tooling_troubleshooting.md#common-issues-and-solutions)
-* [Release artifacts](docs/common/release.md)
-
-### Module Documentation
-
-* [Button](docs/modules/button.md)
-* [Cloud](docs/modules/cloud.md)
-* [Storage](docs/modules/storage.md)
-* [Environmental](docs/modules/environmental.md)
-* [FOTA](docs/modules/fota.md)
-* [LED](docs/modules/led.md)
-* [Location](docs/modules/location.md)
-* [Main](docs/modules/main.md)
-* [Network](docs/modules/network.md)
-* [Power](docs/modules/power.md)
+To get started with Asset tracker template for the nRF9151 and Thingy:91 X, follow [documentation](https://docs.nordicsemi.com/bundle/asset-tracker-template-latest/page/index.html).

docs/common/architecture.md

@@ -13,6 +13,7 @@ This document provides an overview of the architecture and explains how the diff
 The Asset Tracker Template is built around a modular architecture where each module is responsible for a specific functionality. The template consists of the following modules:
 
 - **[Main module](../modules/main.md)**: The central coordinator that implements the business logic and controls the overall application flow.
+- **[Storage module](../modules/storage.md)**: Forwards or stores data from enabled modules.
 - **[Network module](../modules/network.md)**: Manages LTE connectivity and tracks network status.
 - **[Cloud module](../modules/cloud.md)**: Handles communication with nRF Cloud using CoAP.
 - **[Location module](../modules/location.md)**: Provides location services using GNSS, Wi-Fi, and cellular positioning.

docs/common/getting_started.md

@@ -20,6 +20,8 @@ Once you have created the project, you can access various development actions th
 
 For more details on how to use the VS Code extension, refer to the [nRF Connect for VS Code documentation](https://docs.nordicsemi.com/bundle/nrf-connect-vscode/page/index.html).
 
+For pre-built binaries, refer to the latest tag and the [release artifacts](release.md) documentation.
+
 ## Prerequisites
 
 * **The nRF Util command line tool and the SDK manager command**
@@ -29,7 +31,7 @@ For more details on how to use the VS Code extension, refer to the [nRF Connect
 
 * **nRF Connect SDK toolchain v3.0.0 or later**
 
-    - Follow the instructions in the [sdk-manager command](https://docs.nordicsemi.com/bundle/nrfutil/page/nrfutil-sdk-manager/nrfutil-sdk-manager.html) documentation to install v3.0.0 of the nRF Connect SDK toolchain.
+    - Follow the instructions in the [sdk-manager command](https://docs.nordicsemi.com/bundle/nrfutil/page/nrfutil-sdk-manager/nrfutil-sdk-manager.html) documentation to install {{version}} of the nRF Connect SDK toolchain.
 
 ## Supported boards
 
@@ -48,13 +50,13 @@ The Asset Tracker Template is continuously verified in CI on the following board
 Before initializing, start the toolchain environment:
 
 ```shell
-nrfutil sdk-manager toolchain launch --ncs-version v3.0.0 --shell
+nrfutil sdk-manager toolchain launch --ncs-version {{version}} --shell
 ```
 
-Alternatively, you can run the command with a specific nRF Connect SDK version. For example, if you are using version 3.0.1, run:
+Alternatively, you can run the command with a specific nRF Connect SDK version. For example, if you are using {{version}}, run:
 
 ```shell
-nrfutil sdk-manager toolchain launch --ncs-version v3.0.0 -- <your command>
+nrfutil sdk-manager toolchain launch --ncs-version {{version}} -- <your command>
 ```
 
 To run for instance the `west` command with the specified version of toolchain. You can create an alias or shell function for this command to avoid typing it in full every time.
@@ -152,7 +154,7 @@ To test that everything is working as expected, you can do the following:
 
     ```shell
 
-    *** Booting nRF Connect SDK v3.0.0-3bfc46578e42 ***
+    *** Booting nRF Connect SDK {{version}}-3bfc46578e42 ***
     *** Using Zephyr OS v4.0.99-a0e545cb437a ***
     Attempting to boot slot 0.
     Attempting to boot from address 0x8200.
@@ -171,7 +173,7 @@ To test that everything is working as expected, you can do the following:
     [00:00:00.257,324] <inf> spi_nor: GD25LE255E@0: 32 MiBy flash
     [00:00:00.311,828] <inf> wifi_nrf_bus: SPIM spi@b000: freq = 8 MHz
     [00:00:00.311,889] <inf> wifi_nrf_bus: SPIM spi@b000: latency = 0
-    ]mJ*** Using nRF Connect SDK v3.0.0-3bfc46578e42 ***
+    ]mJ*** Using nRF Connect SDK {{version}}-3bfc46578e42 ***
     *** Using Zephyr OS v4.0.99-a0e545cb437a ***
     [00:00:00.520,202] <dbg> main: main: Main has started
     [00:00:00.520,263] <dbg> main: running_entry: running_entry

docs/common/image.png

@@ -10,10 +10,20 @@ Device provisioning establishes credentials for secure communication with nRF Cl
    at at%attesttoken
    ```
 
-   *Note: Token is printed automatically on first boot of unprovisioned devices.*
+   !!! note "Note"
 
-2. In nRF Cloud: **Security Services** → **Claimed Devices** → **Claim Device**
-3. Paste token, set rule to "nRF Cloud Onboarding", click **Claim Device**
+      Token is printed automatically on first boot of unprovisioned devices.
+
+1. Log in to the In [nRF Cloud](https://nrfcloud.com/#/) portal.
+1. Select **Security Services** in the left sidebar.
+
+   A panel opens to the right.
+1. Select **Claimed Devices**.
+1. Click **Claim Device**
+
+   A pop-up opens.
+1. Copy and paste the attestation token into the **Claim token** text box.
+1. Set rule to nRF Cloud Onboarding and click **Claim Device**
 
     <details>
     <summary><strong>If "nRF Cloud Onboarding" rule is not showing:</strong></summary>
@@ -25,6 +35,8 @@ Device provisioning establishes credentials for secure communication with nRF Cl
 
 ### REST API Alternative
 
+You can also use the REST API as an alternative for provisioning by running the following command:
+
 ```bash
 curl 'https://api.provisioning.nrfcloud.com/v1/claimed-devices' \
 -H 'Content-Type: application/json' \
@@ -36,25 +48,32 @@ curl 'https://api.provisioning.nrfcloud.com/v1/claimed-devices' \
 
 To update device credentials:
 
-> In an end-product it's recommended to reprovision the device at a reasonable interval depending on the application use case, for security reasons.
+> In an end product it is recommended to reprovision the device at a reasonable interval depending on the application use case for security reasons.
 
 ### Manual
 
-1. In nRF Cloud: **Security Services** → **Claimed Devices** → find device → **Add Command**
-2. Select **Cloud Access Key Generation** → **Create Command**
-3. Trigger on device:
+1. Log in to the In [nRF Cloud](https://nrfcloud.com/#/) portal.
+1. Select **Security Services** in the left sidebar.
+
+   A panel opens to the right.
+1. Select **Claimed Devices**.
+1. Find the device and click **Add Command**.
+1. Select **Cloud Access Key Generation** and click **Create Command**.
+1. Trigger on device:
    - **Shell**: `att_cloud_provision now`
    - **Cloud**: Update device shadow with `{"desired": {"command": [1, 1]}}`.
 
-*For detailed information on sending commands to devices via REST API, including command structure and available command types, see [Sending commands through REST API](configuration.md#sending-commands-through-rest-api) in the configuration documentation.*
+For detailed information on sending commands to devices through REST API, including command structure and available command types, see [Sending commands through REST API](configuration.md#sending-commands-through-rest-api) in the configuration documentation.
 
 ### REST API Alternative
 
+You can also use the REST API as an alternative for reprovisioning by running the following command:
+
 ```bash
 curl 'https://api.provisioning.nrfcloud.com/v1/claimed-devices/YOUR_DEVICE_ID/provisioning' \
 -H 'Content-Type: application/json' \
 -H 'Authorization: Bearer YOUR_API_TOKEN' \
 -d '{"request": {"cloudAccessKeyGeneration": {"secTag": 16842753}}}'
 ```
 
-*For detailed API documentation, see [nRF Cloud REST API](https://api.nrfcloud.com/docs).*
+For detailed API documentation, see [nRF Cloud REST API](https://api.nrfcloud.com/docs).

docs/common/provisioning.md

@@ -1,6 +1,7 @@
 # Release Artifacts
 
-This document provides a comprehensive overview of all firmware deliverables and artifacts generated by the Asset Tracker Template. Each firmware variant is optimized for specific use cases and hardware platforms.
+This document provides a comprehensive overview of all firmware deliverables and artifacts generated by the Asset Tracker Template.
+Each firmware variant is optimized for specific use cases and hardware platforms.
 
 ## Firmware Deliverables
 
@@ -29,9 +30,9 @@ The Asset Tracker Template generates multiple firmware artifacts for different h
 
 | **Artifact Name** | **Hardware Platform** | **Description** | **Use Case** |
 |-------------------|----------------------|----------------|--------------|
-| `att-thingy91x-{VERSION}-mtrace.hex` | Thingy:91 X (nRF9151) | Firmware with modem trace output enabled via UART 1 | Cellular connectivity debugging and analysis |
-| `att-nrf9151dk-{VERSION}-mtrace.hex` | nRF9151 DK | Firmware with modem trace output enabled via UART 1  | Cellular connectivity debugging and analysis |
-| `att-nrf9161dk-{VERSION}-mtrace.hex` | nRF9161 DK | Firmware with modem trace output enabled via UART 1  | Cellular connectivity debugging and analysis |
+| `att-thingy91x-{VERSION}-mtrace.hex` | Thingy:91 X (nRF9151) | Firmware with modem trace output enabled through UART 1 | Cellular connectivity debugging and analysis |
+| `att-nrf9151dk-{VERSION}-mtrace.hex` | nRF9151 DK | Firmware with modem trace output enabled through UART 1  | Cellular connectivity debugging and analysis |
+| `att-nrf9161dk-{VERSION}-mtrace.hex` | nRF9161 DK | Firmware with modem trace output enabled through UART 1  | Cellular connectivity debugging and analysis |
 | `att-nrf9151dk-{VERSION}-ext-gnss.hex` | nRF9151 DK | Firmware configured for external GNSS antenna | Testing with external GNSS antenna setup |
 
 ### Configuration Overlays
@@ -57,6 +58,6 @@ The firmware variants are built using different configuration overlays that modi
 #### Development Kits
 
 - **nRF9151 DK**: Primary development platform for nRF9151-based projects
-- **nRF9160 DK**: Legacy development support for nRF9160-based projects  
+- **nRF9160 DK**: Legacy development support for nRF9160-based projects
 - **nRF9161 DK**: Latest development platform with enhanced features
 - **Thingy:91**: Legacy compact development platform