1.. zephyr:board:: we_proteus2ev
2
3Overview
4********
5
6The Proteus-II-EV hardware provides
7support for the Proteus-II radio module that uses the Nordic Semiconductor nRF52832 ARM Cortex-M4F CPU and
8the following devices:
9
10* :abbr:`ADC (Analog to Digital Converter)`
11* CLOCK
12* FLASH
13* :abbr:`GPIO (General Purpose Input Output)`
14* :abbr:`I2C (Inter-Integrated Circuit)`
15* :abbr:`MPU (Memory Protection Unit)`
16* :abbr:`NVIC (Nested Vectored Interrupt Controller)`
17* :abbr:`PWM (Pulse Width Modulation)`
18* RADIO (Bluetooth Low Energy)
19* :abbr:`RTC (nRF RTC System Clock)`
20* Segger RTT (RTT Console)
21* :abbr:`SPI (Serial Peripheral Interface)`
22* :abbr:`UART (Universal asynchronous receiver-transmitter)`
23* :abbr:`WDT (Watchdog Timer)`
24
25More information about the radio module can be found the Würth Elektronik web page https://www.we-online.com/katalog/de/PROTEUS-II .
26
27
28Hardware
29********
30
31Proteus-II radio module provides only the internal oscillators. The frequency of the slow clock
32is 32.768 kHz. The frequency of the main clock is 32 MHz.
33
34Supported Features
35==================
36
37The we_proteus2ev/nrf52832 board configuration supports the following
38hardware features:
39
40+-----------+------------+----------------------+
41| Interface | Controller | Driver/Component     |
42+===========+============+======================+
43| ADC       | on-chip    | adc                  |
44+-----------+------------+----------------------+
45| CLOCK     | on-chip    | clock_control        |
46+-----------+------------+----------------------+
47| FLASH     | on-chip    | flash                |
48+-----------+------------+----------------------+
49| GPIO      | on-chip    | gpio                 |
50+-----------+------------+----------------------+
51| I2C(M)    | on-chip    | i2c                  |
52+-----------+------------+----------------------+
53| MPU       | on-chip    | arch/arm             |
54+-----------+------------+----------------------+
55| NVIC      | on-chip    | arch/arm             |
56+-----------+------------+----------------------+
57| PWM       | on-chip    | pwm                  |
58+-----------+------------+----------------------+
59| RADIO     | on-chip    | Bluetooth            |
60+-----------+------------+----------------------+
61| RTC       | on-chip    | system clock         |
62+-----------+------------+----------------------+
63| RTT       | Segger     | console              |
64+-----------+------------+----------------------+
65| SPI(M/S)  | on-chip    | spi                  |
66+-----------+------------+----------------------+
67| UART      | on-chip    | serial               |
68+-----------+------------+----------------------+
69| WDT       | on-chip    | watchdog             |
70+-----------+------------+----------------------+
71
72Other hardware features are not supported by the Zephyr kernel.
73
74Connections and IOs
75===================
76
77LED
78---
79
80* LED1 = P0.00
81* LED2 = P0.01
82
83Push buttons
84------------
85
86* BUTTON1 = SW1 = P0.29
87
88
89Programming and Debugging
90*************************
91
92Applications for the ``we_proteus2ev/nrf52832`` board configuration can be
93built, flashed, and debugged in the usual way. See
94:ref:`build_an_application` and :ref:`application_run` for more details on
95building and running.
96
97Flashing
98========
99
100Follow the instructions in the :ref:`nordic_segger` page to install
101and configure all the necessary software. Further information can be
102found in :ref:`nordic_segger_flashing`. Then build and flash
103applications as usual (see :ref:`build_an_application` and
104:ref:`application_run` for more details).
105
106Here is an example for the :zephyr:code-sample:`hello_world` application.
107
108First, run your favorite terminal program to listen for output.
109
110.. code-block:: console
111
112   $ minicom -D <tty_device> -b 115200
113
114Replace :code:`<tty_device>` with the port where the board Proteus-II-EV
115can be found. For example, under Linux, :code:`/dev/ttyACM0`.
116
117Then build and flash the application in the usual way.
118
119.. zephyr-app-commands::
120   :zephyr-app: samples/hello_world
121   :board: we_proteus2ev/nrf52832
122   :goals: build flash
123
124Debugging
125=========
126
127Refer to the :ref:`nordic_segger` page to learn about debugging Nordic boards with a
128Segger IC.
129
130
131Testing the LEDs and buttons in the Proteus-II-EV
132*************************************************
133
134There are 2 samples that allow you to test that the buttons (switches) and LEDs on
135the board are working properly with Zephyr:
136
137.. code-block:: console
138
139   samples/basic/blinky
140   samples/basic/button
141
142You can build and flash the examples to make sure Zephyr is running correctly on
143your board. The button and LED definitions can be found in
144:zephyr_file:`boards/we/proteus2ev/we_proteus2ev_nrf52832.dts`.
145
146References
147**********
148
149.. target-notes::
150
151.. _Proteus-II radio module website: https://www.we-online.com/katalog/de/PROTEUS-II
152.. _nRF52 DK website: https://www.nordicsemi.com/Software-and-Tools/Development-Kits/nRF52-DK
153.. _Nordic Semiconductor Infocenter: https://infocenter.nordicsemi.com
154