1.. zephyr:board:: raytac_mdbt53v_db_40
2
3Overview
4********
5
6Raytac MDBT53V-DB-40 demo board is a development board based on the Raytac MDBT53V-1M module,
7using Nordic Semiconductor nRF5340 ARM Cortex-M33 SoC. Its design concept is to connect all
8of the module's pins to 2.54mm pin headers. It is convenient for developers to verify whether
9the modules are connected to other peripheral devices or sensors as a tool for software development.
10
11The nRF5340 inside the MDBT53V-1M module is a
12dual-core SoC based on the Arm® Cortex®-M33 architecture, with:
13
14* a full-featured Arm Cortex-M33F core with DSP instructions, FPU, and
15  Armv8-M Security Extension, running at up to 128 MHz, referred to as
16  the **application core**
17* a secondary Arm Cortex-M33 core, with a reduced feature set, running
18  at a fixed 64 MHz, referred to as the **network core**.
19
20The raytac_mdbt53v_db_40_nrf5340_cpuapp build target provides support for the application
21core on the nRF5340 SoC. The raytac_mdbt53v_db_40_nrf5340_cpuapp build target provides
22support for the network core on the nRF5340 SoC.
23
24nRF5340 SoC provides support for the following devices:
25
26* :abbr:`ADC (Analog to Digital Converter)`
27* CLOCK
28* FLASH
29* :abbr:`GPIO (General Purpose Input Output)`
30* :abbr:`IDAU (Implementation Defined Attribution Unit)`
31* :abbr:`I2C (Inter-Integrated Circuit)`
32* :abbr:`MPU (Memory Protection Unit)`
33* :abbr:`NVIC (Nested Vectored Interrupt Controller)`
34* :abbr:`PWM (Pulse Width Modulation)`
35* RADIO (Bluetooth Low Energy and 802.15.4)
36* :abbr:`RTC (nRF RTC System Clock)`
37* Segger RTT (RTT Console)
38* :abbr:`SPI (Serial Peripheral Interface)`
39* :abbr:`UARTE (Universal asynchronous receiver-transmitter)`
40* :abbr:`WDT (Watchdog Timer)`
41
42More information about the board can be found at the `MDBT53V-DB-40 website`_.
43The `MDBT53V-DB-40 Specification`_ contains the demo board's datasheet.
44The `MDBT53V-DB-40 Schematic`_ contains the demo board's schematic.
45
46Hardware
47********
48- Module Demo Board build by MDBT53V-1M
49- Nordic nRF5340 SoC Solution
50- A recommnded 3rd-party module by Nordic Semiconductor.
51- Dual-core Arm® Cortex® M33
52- 1MB/256KB Flash Memory; 512kB/ 64kB RAM
53- Supports BT5 Long Range Features
54- Bluetooth specification v5.2
55- Supports BT5 Long Range Features
56- Supports Bluetooth Direction Finding & Mesh
57- Supports Bluetooth low energy audio
58- Cerifications: FCC, IC, CE, Telec(MIC), KC, SRRC, NCC, RCM, WPC
59- RoHs & Reach Compiant.
60- 25 GPIO
61- Chip Antenna
62- Interfaces: SPI, UART, I2C, I2S, PWM, ADC, and NFC
63- Highly flexible multiprotocol SoC ideally suited for Bluetooth® Low Energy, ANT+, Zigbee, Thread (802.15.4) ultra low-power wireless applications.
64- 1 User LEDs
65- 3 User buttons
66- 1 Mini USB connector for power supply
67- SWD connector for FW programing
68- J-Link interface for FW programing
69
70Supported Features
71==================
72
73The raytac_mdbt53v_db_40_nrf5340_cpuapp board configuration supports the following
74hardware features:
75
76+-----------+------------+----------------------+
77| Interface | Controller | Driver/Component     |
78+===========+============+======================+
79| ADC       | on-chip    | adc                  |
80+-----------+------------+----------------------+
81| CLOCK     | on-chip    | clock_control        |
82+-----------+------------+----------------------+
83| FLASH     | on-chip    | flash                |
84+-----------+------------+----------------------+
85| GPIO      | on-chip    | gpio                 |
86+-----------+------------+----------------------+
87| I2C(M)    | on-chip    | i2c                  |
88+-----------+------------+----------------------+
89| MPU       | on-chip    | arch/arm             |
90+-----------+------------+----------------------+
91| NVIC      | on-chip    | arch/arm             |
92+-----------+------------+----------------------+
93| PWM       | on-chip    | pwm                  |
94+-----------+------------+----------------------+
95| RTC       | on-chip    | system clock         |
96+-----------+------------+----------------------+
97| SPI(M/S)  | on-chip    | spi                  |
98+-----------+------------+----------------------+
99| UARTE     | on-chip    | serial               |
100+-----------+------------+----------------------+
101| WDT       | on-chip    | watchdog             |
102+-----------+------------+----------------------+
103
104The raytac_mdbt53v_db_40_nrf5340_cpunet board configuration supports the following
105hardware features:
106
107+-----------+------------+----------------------+
108| Interface | Controller | Driver/Component     |
109+===========+============+======================+
110| CLOCK     | on-chip    | clock_control        |
111+-----------+------------+----------------------+
112| FLASH     | on-chip    | flash                |
113+-----------+------------+----------------------+
114| GPIO      | on-chip    | gpio                 |
115+-----------+------------+----------------------+
116| I2C(M)    | on-chip    | i2c                  |
117+-----------+------------+----------------------+
118| MPU       | on-chip    | arch/arm             |
119+-----------+------------+----------------------+
120| NVIC      | on-chip    | arch/arm             |
121+-----------+------------+----------------------+
122| RADIO     | on-chip    | Bluetooth,           |
123|           |            | ieee802154           |
124+-----------+------------+----------------------+
125| RTC       | on-chip    | system clock         |
126+-----------+------------+----------------------+
127| SPI(M/S)  | on-chip    | spi                  |
128+-----------+------------+----------------------+
129| UARTE     | on-chip    | serial               |
130+-----------+------------+----------------------+
131| WDT       | on-chip    | watchdog             |
132+-----------+------------+----------------------+
133
134Other hardware features have not been enabled yet for this board.
135See `MDBT53V-DB-40 website`_ and `MDBT53V-DB-40 Specification`_
136for a complete list of Raytac MDBT53V-DB-40 board hardware features.
137
138Connections and IOs
139===================
140
141LED
142---
143
144* LED1 (green) = P0.31
145
146Push buttons
147------------
148
149* BUTTON1 = SW1 = P1.13
150* BUTTON2 = SW2 = P0.25
151* BUTTON3 = SW3 = P0.26
152
153HSPI
154----
155* MOSI = P0.9
156* MISO = P0.10
157* SCK = P0.8
158* CSN = P0.11
159* DCX = P0.12
160
161QSPI
162----
163* SCK = P0.17
164* CSN = P0.18
165* DATA0 = P0.13
166* DATA1 = P0.14
167* DATA2 = P0.15
168* DATA3 = P0.16
169
170Security components
171===================
172
173- Implementation Defined Attribution Unit (`IDAU`_) on the application core.
174  The IDAU is implemented with the System Protection Unit and is used to
175  define secure and non-secure memory maps.  By default, all of the memory
176  space  (Flash, SRAM, and peripheral address space) is defined to be secure
177  accessible only.
178- Secure boot.
179
180Programming and Debugging
181*************************
182
183nRF5340 application core supports the Armv8-M Security Extension.
184Applications built for the raytac_mdbt53v_db_40_nrf5340_cpuapp board by
185default boot in the Secure state.
186
187nRF5340 network core does not support the Armv8-M Security Extension.
188nRF5340 IDAU may configure bus accesses by the nRF5340 network core
189to have Secure attribute set; the latter allows to build and run
190Secure only applications on the nRF5340 SoC.
191
192Applications for the ``raytac_mdbt53v_db_40_nrf5340`` board configuration can be
193built, flashed, and debugged in the usual way. See :ref:`build_an_application` and
194:ref:`application_run` for more details on building and running.
195
196.. note::
197   Flashing and Debugging Zephyr onto the raytac_mdbt53v_db_40_nrf5340 board
198   requires an	external J-Link programmer. The programmer is attached to the J1
199   or J9 SWD connector.
200
201
202Flashing
203========
204
205Follow the instructions in the :ref:`nordic_segger` page to install
206and configure all the necessary software. Further information can be
207found in :ref:`nordic_segger_flashing`. Then build and flash
208applications as usual (see :ref:`build_an_application` and
209:ref:`application_run` for more details).
210
211Here is an example for the :zephyr:code-sample:`hello_world` application.
212
213Use a USB to TTL converter to connect the computer and raytac_mdbt53v_db_40_nrf5340
214J13 connector pin 8(RX), 9(TX) and GND. Then run your favorite terminal program to listen for output.
215
216.. code-block:: console
217
218   $ minicom -D <tty_device> -b 115200
219
220Replace :code:`<tty_device>` with the port where the USB to TTL converter
221can be found. For example, under Linux, :code:`/dev/ttyUSB0`.
222
223Then build and flash the application in the usual way.
224
225.. zephyr-app-commands::
226   :zephyr-app: samples/hello_world
227   :board: raytac_mdbt53v_db_40_nrf5340
228   :goals: build flash
229
230Debugging
231=========
232
233The ``raytac_mdbt53v_db_40_nrf5340`` board does not have an on-board-J-Link debug IC,
234however, instructions from the :ref:`nordic_segger` page also apply to this board.
235Use the Debug out connector of nRF52x DK to connect to the J1 connector, and use SEGGER
236J-Link OB IF to debug.
237
238
239References
240**********
241
242.. target-notes::
243
244.. _IDAU:
245   https://developer.arm.com/docs/100690/latest/attribution-units-sau-and-idau
246.. _MDBT53V-DB-40 website:
247	https://www.raytac.com/product/ins.php?index_id=140
248.. _MDBT53V-DB-40 Specification:
249	https://www.raytac.com/download/index.php?index_id=62
250.. _MDBT53V-DB-40 Schematic:
251	https://www.raytac.com/upload/catalog_b/f2c33d52dca8cd6546c95938bc0cb295.jpg
252.. _J-Link Software and documentation pack:
253	https://www.segger.com/jlink-software.html
254