boards/arm/nrf9160_pca10090/doc/index.rst - third_party/github/zephyrproject-rtos/zephyr - Git at Google

 .. _nrf9160_pca10090:

 nRF9160-PCA10090
 ################

 Overview
 ********

 The nRF9160 PCA10090 is a single-board development kit for evaluation
 and development on the nRF9160 SiP for LTE-M and NB-IoT. The
 nrf9160_pca10090 board provides support for the Nordic Semiconductor
 nRF9160 ARM Cortex-M33F CPU with ARMv8-M Security Extension and the
 following devices:

 * :abbr:`ADC (Analog to Digital Converter)`
 * CLOCK
 * FLASH
 * :abbr:`GPIO (General Purpose Input Output)`
 * :abbr:`I2C (Inter-Integrated Circuit)`
 * :abbr:`MPU (Memory Protection Unit)`
 * :abbr:`NVIC (Nested Vectored Interrupt Controller)`
 * :abbr:`PWM (Pulse Width Modulation)`
 * :abbr:`RTC (nRF RTC System Clock)`
 * Segger RTT (RTT Console)
 * :abbr:`SPI (Serial Peripheral Interface)`
 * :abbr:`UARTE (Universal asynchronous receiver-transmitter with EasyDMA)`
 * :abbr:`WDT (Watchdog Timer)`
 * :abbr:`IDAU (Implementation Defined Attribution Unit)`

 .. figure:: img/nrf9160_pca10090.png
      :width: 711px
      :align: center
      :alt: nRF9160 PCA10090 DK

      nRF9160 PCA10090 DK (Credit: Nordic Semi)

 More information about the board can be found at the
 `nRF91 DK website`_. The `Nordic Semiconductor Documentation library`_
 contains the processor's information and the datasheet.

 Hardware
 ********

 nRF9160 DK has two external oscillators. The frequency of
 the slow clock is 32.768 kHz. The frequency of the main clock
 is 32 MHz.

 Supported Features
 ==================

 The nrf9160_pca10090 board configuration supports the following
 hardware features:

 +-----------+------------+----------------------+
 | Interface | Controller | Driver/Component     |
 +===========+============+======================+
 | ADC       | on-chip    | adc                  |
 +-----------+------------+----------------------+
 | CLOCK     | on-chip    | clock_control        |
 +-----------+------------+----------------------+
 | FLASH     | on-chip    | flash                |
 +-----------+------------+----------------------+
 | GPIO      | on-chip    | gpio                 |
 +-----------+------------+----------------------+
 | I2C(M)    | on-chip    | i2c                  |
 +-----------+------------+----------------------+
 | MPU       | on-chip    | arch/arm             |
 +-----------+------------+----------------------+
 | NVIC      | on-chip    | arch/arm             |
 +-----------+------------+----------------------+
 | PWM       | on-chip    | pwm                  |
 +-----------+------------+----------------------+
 | RTC       | on-chip    | system clock         |
 +-----------+------------+----------------------+
 | RTT       | Segger     | console              |
 +-----------+------------+----------------------+
 | SPI(M/S)  | on-chip    | spi                  |
 +-----------+------------+----------------------+
 | SPU       | on-chip    | system protection    |
 +-----------+------------+----------------------+
 | UARTE     | on-chip    | serial               |
 +-----------+------------+----------------------+
 | WDT       | on-chip    | watchdog             |
 +-----------+------------+----------------------+

 Other hardware features are not supported by the Zephyr kernel.
 See `nRF91 DK website`_ and `Nordic Semiconductor Documentation library`_
 for a complete list of nRF9160 Development Kit board hardware features.

 Connections and IOs
 ===================

 LED
 ---

 * LED1 (green) = P0.2
 * LED2 (green) = P0.3
 * LED3 (green) = P0.4
 * LED4 (green) = P0.5

 Push buttons and Switches
 -------------------------

 * BUTTON1 = P0.6
 * BUTTON2 = P0.7
 * SWITCH1 = P0.8
 * SWITCH2 = P0.9
 * BOOT = SW5 = boot/reset

 Security components
 ===================

 - Implementation Defined Attribution Unit (`IDAU`_).  The IDAU is implemented
   with the System Protection Unit and is used to define secure and non-secure
   memory maps.  By default, all of the memory space  (Flash, SRAM, and
   peripheral address space) is defined to be secure accessible only.
 - Secure boot.


 Programming and Debugging
 *************************

 nrf9160_pca10090 supports the Armv8m Security Extension, and by default boots
 in the Secure state.

 Building Secure/Non-Secure Zephyr applications
 ==============================================

 The process requires the following steps:

 1. Build the Secure Zephyr application using ``-DBOARD=nrf9160_pca10090`` and
    ``CONFIG_TRUSTED_EXECUTION_SECURE=y`` in the the application project configuration file.
 2. Build the Non-Secure Zephyr application using ``-DBOARD=nrf9160_pca10090ns``.
 3. Merge the two binaries together.

 When building a Secure/Non-Secure application, the Secure application will
 have to set the IDAU (SPU) configuration to allow Non-Secure access to all
 CPU resources utilized by the Non-Secure application firmware. SPU
 configuration shall take place before jumping to the Non-Secure application.

 Building a Secure only application
 ==================================

 Build the Zephyr app in the usual way (see :ref:`build_an_application`
 and :ref:`application_run`), using ``-DBOARD=nrf9160_pca10090``.


 Flashing
 ========

 Follow the instructions in the :ref:`nordic_segger` page to install
 and configure all the necessary software. Further information can be
 found in :ref:`nordic_segger_flashing`. Then build and flash
 applications as usual (see :ref:`build_an_application` and
 :ref:`application_run` for more details).

 Here is an example for the :ref:`hello_world` application.

 First, run your favorite terminal program to listen for output.

 .. code-block:: console

    $ minicom -D <tty_device> -b 115200

 Replace :code:`<tty_device>` with the port where the board nRF9160 DK
 can be found. For example, under Linux, :code:`/dev/ttyACM0`.

 Then build and flash the application in the usual way.

 .. zephyr-app-commands::
    :zephyr-app: samples/hello_world
    :board: nrf9160_pca10090
    :goals: build flash

 Debugging
 =========

 Refer to the :ref:`nordic_segger` page to learn about debugging Nordic boards with a
 Segger IC.


 Testing the LEDs and buttons in the nRF9160 DK
 **********************************************

 There are 2 samples that allow you to test that the buttons (switches) and LEDs on
 the board are working properly with Zephyr:

 * :ref:`blinky-sample`
 * :ref:`button-sample`

 You can build and flash the examples to make sure Zephyr is running correctly on
 your board. The button and LED definitions can be found in
 :zephyr_file:`boards/arm/nrf9160_pca10090/nrf9160_pca10090_common.dts`.

 References
 **********

 .. target-notes::

 .. _IDAU:
    https://developer.arm.com/products/architecture/cpu-architecture/m-profile/docs/100690/latest/attribution-units-sau-and-idau
 .. _nRF91 DK website: https://www.nordicsemi.com/Software-and-Tools/Development-Kits/nRF9160-DK
 .. _Nordic Semiconductor Documentation library: https://www.nordicsemi.com/DocLib
	.. _nrf9160_pca10090:

	nRF9160-PCA10090
	################

	Overview
	********

	The nRF9160 PCA10090 is a single-board development kit for evaluation
	and development on the nRF9160 SiP for LTE-M and NB-IoT. The
	nrf9160_pca10090 board provides support for the Nordic Semiconductor
	nRF9160 ARM Cortex-M33F CPU with ARMv8-M Security Extension and the
	following devices:

	* :abbr:`ADC (Analog to Digital Converter)`
	* CLOCK
	* FLASH
	* :abbr:`GPIO (General Purpose Input Output)`
	* :abbr:`I2C (Inter-Integrated Circuit)`
	* :abbr:`MPU (Memory Protection Unit)`
	* :abbr:`NVIC (Nested Vectored Interrupt Controller)`
	* :abbr:`PWM (Pulse Width Modulation)`
	* :abbr:`RTC (nRF RTC System Clock)`
	* Segger RTT (RTT Console)
	* :abbr:`SPI (Serial Peripheral Interface)`
	* :abbr:`UARTE (Universal asynchronous receiver-transmitter with EasyDMA)`
	* :abbr:`WDT (Watchdog Timer)`
	* :abbr:`IDAU (Implementation Defined Attribution Unit)`

	.. figure:: img/nrf9160_pca10090.png
	:width: 711px
	:align: center
	:alt: nRF9160 PCA10090 DK

	nRF9160 PCA10090 DK (Credit: Nordic Semi)

	More information about the board can be found at the
	`nRF91 DK website`_. The `Nordic Semiconductor Documentation library`_
	contains the processor's information and the datasheet.

	Hardware
	********

	nRF9160 DK has two external oscillators. The frequency of
	the slow clock is 32.768 kHz. The frequency of the main clock
	is 32 MHz.

	Supported Features
	==================

	The nrf9160_pca10090 board configuration supports the following
	hardware features:

	+-----------+------------+----------------------+
	\| Interface \| Controller \| Driver/Component \|
	+===========+============+======================+
	\| ADC \| on-chip \| adc \|
	+-----------+------------+----------------------+
	\| CLOCK \| on-chip \| clock_control \|
	+-----------+------------+----------------------+
	\| FLASH \| on-chip \| flash \|
	+-----------+------------+----------------------+
	\| GPIO \| on-chip \| gpio \|
	+-----------+------------+----------------------+
	\| I2C(M) \| on-chip \| i2c \|
	+-----------+------------+----------------------+
	\| MPU \| on-chip \| arch/arm \|
	+-----------+------------+----------------------+
	\| NVIC \| on-chip \| arch/arm \|
	+-----------+------------+----------------------+
	\| PWM \| on-chip \| pwm \|
	+-----------+------------+----------------------+
	\| RTC \| on-chip \| system clock \|
	+-----------+------------+----------------------+
	\| RTT \| Segger \| console \|
	+-----------+------------+----------------------+
	\| SPI(M/S) \| on-chip \| spi \|
	+-----------+------------+----------------------+
	\| SPU \| on-chip \| system protection \|
	+-----------+------------+----------------------+
	\| UARTE \| on-chip \| serial \|
	+-----------+------------+----------------------+
	\| WDT \| on-chip \| watchdog \|
	+-----------+------------+----------------------+

	Other hardware features are not supported by the Zephyr kernel.
	See `nRF91 DK website`_ and `Nordic Semiconductor Documentation library`_
	for a complete list of nRF9160 Development Kit board hardware features.

	Connections and IOs
	===================

	LED
	---

	* LED1 (green) = P0.2
	* LED2 (green) = P0.3
	* LED3 (green) = P0.4
	* LED4 (green) = P0.5

	Push buttons and Switches
	-------------------------

	* BUTTON1 = P0.6
	* BUTTON2 = P0.7
	* SWITCH1 = P0.8
	* SWITCH2 = P0.9
	* BOOT = SW5 = boot/reset

	Security components
	===================

	- Implementation Defined Attribution Unit (`IDAU`_). The IDAU is implemented
	with the System Protection Unit and is used to define secure and non-secure
	memory maps. By default, all of the memory space (Flash, SRAM, and
	peripheral address space) is defined to be secure accessible only.
	- Secure boot.


	Programming and Debugging
	*************************

	nrf9160_pca10090 supports the Armv8m Security Extension, and by default boots
	in the Secure state.

	Building Secure/Non-Secure Zephyr applications
	==============================================

	The process requires the following steps:

	1. Build the Secure Zephyr application using ``-DBOARD=nrf9160_pca10090`` and
	``CONFIG_TRUSTED_EXECUTION_SECURE=y`` in the the application project configuration file.
	2. Build the Non-Secure Zephyr application using ``-DBOARD=nrf9160_pca10090ns``.
	3. Merge the two binaries together.

	When building a Secure/Non-Secure application, the Secure application will
	have to set the IDAU (SPU) configuration to allow Non-Secure access to all
	CPU resources utilized by the Non-Secure application firmware. SPU
	configuration shall take place before jumping to the Non-Secure application.

	Building a Secure only application
	==================================

	Build the Zephyr app in the usual way (see :ref:`build_an_application`
	and :ref:`application_run`), using ``-DBOARD=nrf9160_pca10090``.


	Flashing
	========

	Follow the instructions in the :ref:`nordic_segger` page to install
	and configure all the necessary software. Further information can be
	found in :ref:`nordic_segger_flashing`. Then build and flash
	applications as usual (see :ref:`build_an_application` and
	:ref:`application_run` for more details).

	Here is an example for the :ref:`hello_world` application.

	First, run your favorite terminal program to listen for output.

	.. code-block:: console

	$ minicom -D <tty_device> -b 115200

	Replace :code:`<tty_device>` with the port where the board nRF9160 DK
	can be found. For example, under Linux, :code:`/dev/ttyACM0`.

	Then build and flash the application in the usual way.

	.. zephyr-app-commands::
	:zephyr-app: samples/hello_world
	:board: nrf9160_pca10090
	:goals: build flash

	Debugging
	=========

	Refer to the :ref:`nordic_segger` page to learn about debugging Nordic boards with a
	Segger IC.


	Testing the LEDs and buttons in the nRF9160 DK
	**********************************************

	There are 2 samples that allow you to test that the buttons (switches) and LEDs on
	the board are working properly with Zephyr:

	* :ref:`blinky-sample`
	* :ref:`button-sample`

	You can build and flash the examples to make sure Zephyr is running correctly on
	your board. The button and LED definitions can be found in
	:zephyr_file:`boards/arm/nrf9160_pca10090/nrf9160_pca10090_common.dts`.

	References
	**********

	.. target-notes::

	.. _IDAU:
	https://developer.arm.com/products/architecture/cpu-architecture/m-profile/docs/100690/latest/attribution-units-sau-and-idau
	.. _nRF91 DK website: https://www.nordicsemi.com/Software-and-Tools/Development-Kits/nRF9160-DK
	.. _Nordic Semiconductor Documentation library: https://www.nordicsemi.com/DocLib