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 recommended 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 programming
68- J-Link interface for FW programming
69
70Supported Features
71==================
72
73.. zephyr:board-supported-hw::
74
75See `MDBT53V-DB-40 website`_ and `MDBT53V-DB-40 Specification`_
76for a complete list of Raytac MDBT53V-DB-40 board hardware features.
77
78Connections and IOs
79===================
80
81LED
82---
83
84* LED1 (green) = P0.31
85
86Push buttons
87------------
88
89* BUTTON1 = SW1 = P1.13
90* BUTTON2 = SW2 = P0.25
91* BUTTON3 = SW3 = P0.26
92
93HSPI
94----
95* MOSI = P0.9
96* MISO = P0.10
97* SCK = P0.8
98* CSN = P0.11
99* DCX = P0.12
100
101QSPI
102----
103* SCK = P0.17
104* CSN = P0.18
105* DATA0 = P0.13
106* DATA1 = P0.14
107* DATA2 = P0.15
108* DATA3 = P0.16
109
110Security components
111===================
112
113- Implementation Defined Attribution Unit (`IDAU`_) on the application core.
114  The IDAU is implemented with the System Protection Unit and is used to
115  define secure and non-secure memory maps.  By default, all of the memory
116  space  (Flash, SRAM, and peripheral address space) is defined to be secure
117  accessible only.
118- Secure boot.
119
120Programming and Debugging
121*************************
122
123nRF5340 application core supports the Armv8-M Security Extension.
124Applications built for the raytac_mdbt53v_db_40_nrf5340_cpuapp board by
125default boot in the Secure state.
126
127nRF5340 network core does not support the Armv8-M Security Extension.
128nRF5340 IDAU may configure bus accesses by the nRF5340 network core
129to have Secure attribute set; the latter allows to build and run
130Secure only applications on the nRF5340 SoC.
131
132Applications for the ``raytac_mdbt53v_db_40_nrf5340`` board configuration can be
133built, flashed, and debugged in the usual way. See :ref:`build_an_application` and
134:ref:`application_run` for more details on building and running.
135
136.. note::
137   Flashing and Debugging Zephyr onto the raytac_mdbt53v_db_40_nrf5340 board
138   requires an	external J-Link programmer. The programmer is attached to the J1
139   or J9 SWD connector.
140
141
142Flashing
143========
144
145Follow the instructions in the :ref:`nordic_segger` page to install
146and configure all the necessary software. Further information can be
147found in :ref:`nordic_segger_flashing`. Then build and flash
148applications as usual (see :ref:`build_an_application` and
149:ref:`application_run` for more details).
150
151Here is an example for the :zephyr:code-sample:`hello_world` application.
152
153Use a USB to TTL converter to connect the computer and raytac_mdbt53v_db_40_nrf5340
154J13 connector pin 8(RX), 9(TX) and GND. Then run your favorite terminal program to listen for output.
155
156.. code-block:: console
157
158   $ minicom -D <tty_device> -b 115200
159
160Replace :code:`<tty_device>` with the port where the USB to TTL converter
161can be found. For example, under Linux, :code:`/dev/ttyUSB0`.
162
163Then build and flash the application in the usual way.
164
165.. zephyr-app-commands::
166   :zephyr-app: samples/hello_world
167   :board: raytac_mdbt53v_db_40_nrf5340
168   :goals: build flash
169
170Debugging
171=========
172
173The ``raytac_mdbt53v_db_40_nrf5340`` board does not have an on-board-J-Link debug IC,
174however, instructions from the :ref:`nordic_segger` page also apply to this board.
175Use the Debug out connector of nRF52x DK to connect to the J1 connector, and use SEGGER
176J-Link OB IF to debug.
177
178
179References
180**********
181
182.. target-notes::
183
184.. _IDAU:
185   https://developer.arm.com/docs/100690/latest/attribution-units-sau-and-idau
186.. _MDBT53V-DB-40 website:
187	https://www.raytac.com/product/ins.php?index_id=140
188.. _MDBT53V-DB-40 Specification:
189	https://www.raytac.com/download/index.php?index_id=62
190.. _MDBT53V-DB-40 Schematic:
191	https://www.raytac.com/upload/catalog_b/f2c33d52dca8cd6546c95938bc0cb295.jpg
192.. _J-Link Software and documentation pack:
193	https://www.segger.com/jlink-software.html
194