# Fetch Conexio Firmware SDK and Board Definition Files

All the sample applications for the Stratus board can be found in the [<mark style="color:red;">conexio-firmware-sdk</mark>](https://github.com/Conexiotechnologies/conexio-firmware-sdk) repository on GitHub. With the introduction of the Hardware Model v2 HWMv2 from NCS v2.7.x, a redesign of the way the Stratus board definition files and sample applications are fetched has been made. The [<mark style="color:red;">conexio-firmware-sdk</mark>](https://github.com/Conexiotechnologies/conexio-firmware-sdk) repository now contains both the example applications as well as the HWMv2 board definition files for all the Stratus devices.

## 1: Fetching **Sample Applications for nRF Connect SDK**

Check out or clone the [main Git repo branch](https://github.com/Conexiotechnologies/conexio-firmware-sdk) for the sample applications supported by the nRF SDK v2.9.0 or [SDK branch v2.7.0](https://github.com/Conexiotechnologies/conexio-firmware-sdk/tree/v2.7.0) for NCS v2.7.0 support.

Download the files, extract them, and place the extracted folder into:

&#x20;`/nordic/ncs/v2.7.0 for ncs v2.7.0`

or

`/nordic/ncs/v2.9.0 for ncs v2.9.0`

Your nRF Connect SDK v2.7.0 or v2.9.0 folder structure should now look like this:

```
v2.7.0/
├─ bootloader/
├─ conexio-firmware-sdk/ <---------- downloaded SDK files directory
├─ mbedtls/
├─ modules/
├─ nrf/
├─ nrfxlib/
├─ test/
├─ toolchain/
├─ tools/
├─ zephyr/
```

## Conexio Stratus Board Definition Files

Inside the `/conexio-firmware-sdk`you will find the custom board root directory for Conexio devices. These are the new Hardware Model v2 (HWMv2) for Conexio Stratus Pro nRF9161, nRF9151, and Stratus nRF9160, a redesign of the way Zephyr models boards and SOCs.

```
v2.7.0/
├─ conexio-firmware-sdk/
    ├─ boards/
        ├─ conexio/
            ├─ stratus_pro <---- Stratus Pro nRF9151 & nRF9161 MultiSoC board files
            ├─ stratus     <---- Stratus nRF9160 board files
```

## 2: Patch MCUBoot file for Stratus Pro Devices

<figure><img src="https://3229153654-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXjGw-Z8_tCuNQB93OW%2Fuploads%2FOlCi7m34kY7p0vPJuLZI%2Ftop-view.png?alt=media&#x26;token=d8635e8f-04ce-4864-9972-9e8f7aa6eb0b" alt=""><figcaption><p>Conexio Stratus Pro nRF9161</p></figcaption></figure>

{% hint style="danger" %}
Stratus Pro nRF9151 and nRF9161 use MCUBOOT as the main bootloader to properly execute and bootup applications. So make sure not to miss or ignore this step.
{% endhint %}

Download the following two MCUBoot configuration files and place them in the following directory of the nRF Connect SDK (NCS):

> `ncs/v2.7.0/bootloader/mcuboot/boot/zephyr/boards` for ncs v2.7.0
>
> or
>
> `ncs/v2.9.0/bootloader/mcuboot/boot/zephyr/boards` for ncs v2.9.0

1. `conexio_stratus_pro_nrf9151.conf`&#x20;
2. `conexio_stratus_pro_nrf9161.conf`&#x20;

{% file src="<https://3229153654-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXjGw-Z8_tCuNQB93OW%2Fuploads%2FvQGwuwfSgEXtfD941vAM%2Fconexio_stratus_pro_nrf9151.conf?alt=media&token=10550561-1c47-4db0-be64-c0d218e21f1c>" %}
Stratus Pro nRF9151  MCUBoot configuration file
{% endfile %}

{% file src="<https://3229153654-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXjGw-Z8_tCuNQB93OW%2Fuploads%2FHztCg0cgAqM52mMIQDhx%2Fconexio_stratus_pro_nrf9161.conf?alt=media&token=f72572d9-dda3-4f7b-9bd4-8fc0e98e9c51>" %}
Stratus Pro nRF9161  MCUBoot configuration file
{% endfile %}

We have now met all the requirements for compiling applications for the Conexio Stratus boards.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.conexiotech.com/master/building-and-programming-an-application/fetch-conexio-firmware-sdk-and-board-definition-files.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.