1.. zephyr:board:: raytac_mdbt53_db_40 2 3Overview 4******** 5 6Raytac MDBT53-DB-40 demo board is a development board based on the Raytac MDBT53-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 MDBT53-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_mdbt53_db_40/nrf5340/cpuapp`` build target provides support for the application 21core on the nRF5340 SoC. The ``raytac_mdbt53_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* :abbr:`QSPI (Quad Serial Peripheral Interface)` 36* RADIO (Bluetooth Low Energy and 802.15.4) 37* :abbr:`RTC (nRF RTC System Clock)` 38* Segger RTT (RTT Console) 39* :abbr:`SPI (Serial Peripheral Interface)` 40* :abbr:`UARTE (Universal asynchronous receiver-transmitter)` 41* :abbr:`WDT (Watchdog Timer)` 42 43More information about the board can be found at the `MDBT53-DB-40 website`_. 44The `MDBT53-DB-40 Specification`_ contains the demo board's datasheet. 45The `MDBT53-DB-40 Schematic`_ contains the demo board's schematic. 46 47Hardware 48******** 49- Module Demo Board build by MDBT53-1M 50- Nordic nRF5340 SoC Solution 51- A recommnded 3rd-party module by Nordic Semiconductor. 52- Dual-core Arm® Cortex® M33 53- 1MB/256KB Flash Memory; 512kB/ 64kB RAM 54- Supports BT5 Long Range Features 55- Bluetooth specification v5.2 56- Supports Bluetooth Direction Finding & Mesh 57- Supports Bluetooth low energy audio 58- Certifications: FCC, IC, CE, Telec (MIC), KC, SRRC, NCC, RCM, WPC 59- RoHs & Reach Compiant. 60- 48 GPIO 61- Chip Antenna 62- Interfaces: SPI, UART, I2C, I2S, PWM, ADC, NFC, and USB 63- Highly flexible multiprotocol SoC ideally suited for Bluetooth® Low Energy, ANT+, Zigbee, Thread (802.15.4) ultra low-power wireless applications. 64- 4 User LEDs 65- 4 User buttons 66- 1 Mini USB connector for power supply 67- SWD connector for FW programing 68- J-Link interface for FW programing 69- UART interface for UART communication 70 71Supported Features 72================== 73 74The ``raytac_mdbt53_db_40_nrf5340/cpuapp`` board configuration supports the following 75hardware features: 76 77+-----------+------------+----------------------+ 78| Interface | Controller | Driver/Component | 79+===========+============+======================+ 80| ADC | on-chip | adc | 81+-----------+------------+----------------------+ 82| CLOCK | on-chip | clock_control | 83+-----------+------------+----------------------+ 84| FLASH | on-chip | flash | 85+-----------+------------+----------------------+ 86| GPIO | on-chip | gpio | 87+-----------+------------+----------------------+ 88| I2C(M) | on-chip | i2c | 89+-----------+------------+----------------------+ 90| MPU | on-chip | arch/arm | 91+-----------+------------+----------------------+ 92| NVIC | on-chip | arch/arm | 93+-----------+------------+----------------------+ 94| QSPI(M) | on-chip | nor | 95+-----------+------------+----------------------+ 96| PWM | on-chip | pwm | 97+-----------+------------+----------------------+ 98| RTC | on-chip | system clock | 99+-----------+------------+----------------------+ 100| SPI(M/S) | on-chip | spi | 101+-----------+------------+----------------------+ 102| SPU | on-chip | system protection | 103+-----------+------------+----------------------+ 104| UARTE | on-chip | serial | 105+-----------+------------+----------------------+ 106| WDT | on-chip | watchdog | 107+-----------+------------+----------------------+ 108 109The ``raytac_mdbt53_db_40_nrf5340/cpunet`` board configuration supports the following 110hardware features: 111 112+-----------+------------+----------------------+ 113| Interface | Controller | Driver/Component | 114+===========+============+======================+ 115| CLOCK | on-chip | clock_control | 116+-----------+------------+----------------------+ 117| FLASH | on-chip | flash | 118+-----------+------------+----------------------+ 119| GPIO | on-chip | gpio | 120+-----------+------------+----------------------+ 121| I2C(M) | on-chip | i2c | 122+-----------+------------+----------------------+ 123| MPU | on-chip | arch/arm | 124+-----------+------------+----------------------+ 125| NVIC | on-chip | arch/arm | 126+-----------+------------+----------------------+ 127| RADIO | on-chip | Bluetooth, | 128| | | ieee802154 | 129+-----------+------------+----------------------+ 130| RTC | on-chip | system clock | 131+-----------+------------+----------------------+ 132| SPI(M/S) | on-chip | spi | 133+-----------+------------+----------------------+ 134| UARTE | on-chip | serial | 135+-----------+------------+----------------------+ 136| WDT | on-chip | watchdog | 137+-----------+------------+----------------------+ 138 139Other hardware features have not been enabled yet for this board. 140See `MDBT53-DB-40 website`_ and `MDBT53-DB-40 Specification`_ 141for a complete list of Raytac MDBT53-DB-40 board hardware features. 142 143Connections and IOs 144=================== 145 146LED 147--- 148 149* LED1 (green) = P0.28 150* LED2 (red) = P0.30 151* LED3 = P0.31 152* LED4 = P0.29 153 154Push buttons 155------------ 156 157* BUTTON1 = SW1 = P0.24 158* BUTTON2 = SW2 = P0.08 159* BUTTON3 = SW3 = P0.23 160* BUTTON4 = SW4 = P0.09 161 162UART 163---- 164* RX = P0.22 165* TX = P0.20 166* RTS = P0.19 167* CTS = P0.21 168 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_mdbt53_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_mdbt53_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_mdbt53_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 211.. warning:: 212 213 The nRF5340 has a flash read-back protection feature. When flash read-back 214 protection is active, you will need to recover the chip before reflashing. 215 If you are flashing with :ref:`west <west-build-flash-debug>`, run 216 this command for more details on the related ``--recover`` option: 217 218Here is an example for the :zephyr:code-sample:`hello_world` application. 219 220Use a USB to TTL converter to connect the computer and raytac_mdbt53_db_40_nrf5340 221J10 connector. Then run your favorite terminal program to listen for output. 222 223.. code-block:: console 224 225 $ minicom -D <tty_device> -b 115200 226 227Replace :code:`<tty_device>` with the port where the USB to TTL converter 228can be found. For example, under Linux, :code:`/dev/ttyUSB0`. 229 230Then build and flash the application in the usual way. 231 232.. zephyr-app-commands:: 233 :zephyr-app: samples/hello_world 234 :board: raytac_mdbt53_db_40_nrf5340 235 :goals: build flash 236 237Debugging 238========= 239 240The ``raytac_mdbt53_db_40_nrf5340`` board does not have an on-board-J-Link debug IC, 241however, instructions from the :ref:`nordic_segger` page also apply to this board. 242Use the Debug out connector of nRF52x DK to connect to the J1 connector, and use SEGGER 243J-Link OB IF to debug. 244 245Refer to the :ref:`nordic_segger` page to learn about debugging Nordic 246boards with a Segger IC. 247 248 249References 250********** 251 252.. target-notes:: 253 254.. _IDAU: 255 https://developer.arm.com/docs/100690/latest/attribution-units-sau-and-idau 256.. _MDBT53-DB-40 website: 257 https://www.raytac.com/product/ins.php?index_id=139 258.. _MDBT53-DB-40 Specification: 259 https://www.raytac.com/download/index.php?index_id=60 260.. _MDBT53-DB-40 Schematic: 261 https://www.raytac.com/upload/catalog_b/8b5e364600a9cc8c53a869733e97f07e.jpg 262.. _J-Link Software and documentation pack: 263 https://www.segger.com/jlink-software.html 264