Nordic nRF5340 User manual

nRF5340 PDK
User Guide
v1.0
4406_489 v1.0 / 2019-11-13

Contents
Revision history.................................. iv
1Introduction................................... 5
2Minimum requirements............................ 6
3Kit content.................................... 7
3.1 Hardware content ................................ 7
3.2 Downloadable content .............................. 7
3.3 Related documentation .............................. 7
4Interface MCU.................................. 9
4.1 IF Boot/Reset button ............................... 9
4.2 Virtual COM port ................................ 9
4.2.1 Dynamic HWFC handling ........................... 10
4.3 MSD ..................................... 10
5Hardware description............................. 12
5.1 Hardware drawings ............................... 12
5.2 Block diagram ................................. 12
5.3 Power supply ..................................13
5.3.1 5 V power sources ..............................14
5.3.2 VDD power sources ............................. 14
5.3.3 Interface MCU power ............................ 16
5.3.4 nRF5340 power source ............................ 17
5.3.5 nRF5340 direct supply ............................ 18
5.4 Operating modes ................................ 19
5.4.1 USB detect ................................. 19
5.4.2 nRF only mode ............................... 19
5.4.3 Signal switches ............................... 20
5.5 External memory ................................ 21
5.6 Connector interface ............................... 22
5.6.1 Mapping of analog pins ........................... 24
5.7 Buttons and LEDs ................................ 24
5.8 32.768 kHz crystal ................................25
5.9 Debug input and trace .............................. 26
5.10 Debug output ................................. 27
5.11 NFC antenna interface ............................. 28
5.12 Extra op-amp ................................. 29
5.13 Solder bridge configuration ........................... 29
6Measuring current............................... 32
6.1 Preparing the PDK board ............................. 32
6.2 Using an oscilloscope for current profile measurement ................ 33
6.3 Using an ampere-meter for current measurement .................. 34
7RF measurements............................... 36
4406_489 v1.0 ii

Glossary ..................................... 37
Acronyms and abbreviations............................39
FCC regulatory notice............................... 40
Legal notices................................... 41
4406_489 v1.0 iii

Revision history
Date Version Description
November 2019 1.0 First release
4406_489 v1.0 iv

1Introduction
The nRF5340 Preview Development Kit (PDK) includes hardware, firmware source code, documentation,
hardware schematics, and layout files.
The key features of the development kit are:
• Support for nRF5340 System on Chip (SoC) development
• Support for the following wireless protocols:
•Bluetooth® Low Energy
• NFC
• 802.15.4
• Thread
• Zigbee
• ANT™
• 2.4 GHz proprietary
• Arduino Rev3 compatibility
• 2.4 GHz and NFC antennas
• SWF RF connector for direct RF measurements
• User-programmable LEDs(4) and buttons(4)
• SEGGER J-Link OB programmer/debugger
• Pins for measuring power consumption
• 1.7-5.0 V power supply from USB, external Li-Po battery, or CR2032 coin cell battery
For access to firmware source code, hardware schematics, and layout files, see www.nordicsemi.com.
4406_489 v1.0 5

2Minimum requirements
Before you start, check that you have the required hardware and software.
Hardware requirements
• Personal computer (PC) or Mac
• Micro-USB 2.0 cable
Software requirements
• Operating system: Windows 7, Windows 8, Windows 10, MacOS, or Linux
• SEGGER J-Link Software
4406_489 v1.0 6

3Kit content
The nRF5340 PDK consists of hardware, access to software components, reference design files, and
documentation.
3.1 Hardware content
The nRF5340 PDK contains the development kit board PCA10095 and a Near Field Communication (NFC)
antenna.
Figure 1: nRF5340 PDK board (PCA10095) and NFC antenna
3.2 Downloadable content
The nRF5340 PDK downloadable content includes the hardware files.
Hardware files
Schematics, layout, bill of materials, and Gerber files for the nRF5340 PDK are included in a zip file.
•nRF5340 PDK Downloads
3.3 Related documentation
In addition to the information in this document, you may need to consult other documents.
Nordic documentation
•nRF5340 Objective Product Specification
•nRF5340 Compatibility Matrix
•nRF5340 Errata
4406_489 v1.0 7

Kit content
•nRF Connect SDK
4406_489 v1.0 8

4Interface MCU
The interface MCU on the nRF5340 PDK board runs SEGGER J-Link OB interface firmware and is used to
program and debug the firmware of the nRF5340 SoC.
Figure 2: Interface MCU
4.1 IF Boot/Reset button
The nRF5340 PDK board is equipped with an IF Boot/Reset button (SW5).
This button is connected to the interface MCU on the board and has two functions:
• Resetting the nRF5340 SoC.
• Entering bootloader mode of the interface MCU.
The button is also used to enter the bootloader mode of the interface MCU. To enter the bootloader
mode, keep the reset button pressed while powering up the board until LED5 starts to blink. You can
power up the board either by disconnecting and reconnecting the USB cable or by toggling the power
switch (SW8).
4.2 Virtual COM port
The onboard interface MCU features a UART interface through a virtual COM port.
The virtual COM port has the following features:
•Flexible baud rate setting up to 1 Mbps.1
• Dynamic Hardware Flow Control (HWFC) handling.
• Tri-stated UART lines when no terminal is connected.
The table below shows an overview of the UART connections on nRF5340 and the interface MCU.
1Baud rate 921 600 is not supported through the virtual COM port.
4406_489 v1.0 9

Interface MCU
GPIO nRF5340 nRF5340 UART
P0.19 RTS
P0.20 TXD
P0.21 CTS
P0.22 RXD
Table 1: Relationship of UART connections on nRF5340 and interface MCU
The UART signals are routed directly to the interface MCU. The UART pins connected to the interface MCU
are tri-stated when no terminal is connected to the virtual COM port on the computer.
Note: The terminal software used must send a Data Terminal Ready (DTR) signal to configure the
UART interface MCU pins.
The P0.19 (Request to Send (RTS)) and P0.21 (Clear to Send (CTS)) can be used freely when HWFC is
disabled on the SoC.
4.2.1 Dynamic HWFC handling
When the interface MCU receives a DTR signal from a terminal, it performs automatic HWFC detection.
Automatic HWFC detection is done by driving P0.21 (CTS) from the interface MCU and evaluating the state
of P0.19 (RTS) when the first data is sent or received. If the state of P0.19 (RTS) is high, HWFC is assumed
not to be used. If HWFC is not detected, both CTS and RTS can be used freely by the nRF application.
After a power-on reset of the interface MCU, all UART lines are tri-stated when no terminal is connected
to the virtual COM port. Due to the dynamic HWFC handling, if HWFC has been used and detected, P0.21
(CTS) will be driven by the interface MCU until a power-on reset has been performed or until a new DTR
signal is received and the detection is redone.
To ensure that the UART lines are not affected by the interface MCU, the solder bridges for these signals
can be cut and later resoldered if needed. This might be necessary if UART without HWFC is needed while
P0.19 (RTS) and P0.21 (CTS) are used for other purposes.
4.3 MSD
The interface MCU features an Mass Storage Device (MSD). This makes the development kit appear as an
external drive on your computer.
This drive can be used for drag-and-drop programming. However, files cannot be stored on this drive. By
copying a HEX file to the drive, the interface MCU will program the file to the device.
Note:
• Windows might try to defragment the MSD part of the interface MCU. If this happens, the
interface MCU will disconnect and be unresponsive. To return to normal operation, the
development kit must be power cycled.
• Your antivirus software might try to scan the MSD part of the interface MCU. Some antivirus
programs trigger a false positive alert in one of the files and quarantine the unit. If this happens,
the interface MCU will become unresponsive.
• If the computer is set up to boot from USB, it can try to boot from the development kit if the
development kit is connected during boot. This can be avoided by unplugging the development
kit before a computer restart, or changing the boot sequence of the computer.
4406_489 v1.0 10