blenrf51-dk - user guide v1_0_W

1、nRF51 Development KitDeveloping with the MDK-ARM Microcontroller Development KitUser Guide v1.0Copyright 2014 Nordic Semiconductor ASA. All rights reserved.Reproduction in whole or in part is prohibited without the prior written permission of the copyright holder.nRF51 Development Kit User Guide v1.

2、01 IntroductionThe nRF51 Development Kit combined with the nRF51 SDK forms a complete solution for product development based on nRF51 serieschips.The nRF51 Development Kit is fitted with the nRF51422 chip, which is a powerful, highly flexible multi- protocol System on Chip (SoC) ideally suited for A

3、NT/ANT+, Bluetooth low energy (BLE), and 2.4 GHz proprietary ultra-low power wireless applications.And, if you are not using the ANT protocol, you can use the nRF51822 chip in your end product - without any changes needed to yourcode.1.1 Key featuresThe nRF51 DK board has the following key features:

4、 nRF51422 flash based ANT/ANT+, Bluetooth low energy SoC solution 2.4 GHz compatible with nRF24L devices Buttons and LEDs for user interaction I/O interface for Arduino form factor plug-in modules SEGGER J-Link OB Debugger with debug out functionality Virtual COM Port interface via UART Drag and dro

5、p Mass Storage Device (MSD) programming mbed enabledPage 211.2 Required toolsBelow is a list of hardware and software tools that is required if you plan to explore all the features on this development kit. All the tools may not be required for all use cases.Nordic ToolsDescriptionnRFgo StudionRFgo S

6、tudio is our tool to program and configure devices. It supports the programming of nRF51 SoftDevices, applications, and bootloaders. The different programming modes are available on individual tabs in the nRF51 programming module. Studio is used for the following: Bluetooth Direct Test Mode (DTM) te

7、sting Erasing flash memory Programming a SoftDevice Programming an application Programming the bootloadernRFgo Studio supports programming of SEGGER J-Link based nRF51 devices. For more information, see the help in nRFgo Studio.nRF51 ToolsnRF51 Tools is a package that contains JLinkARM, JLink CDC, n

8、RFjprog, and mergehex.The nRFjprog is a command line tool for programming nRF51 series chips. It is also useful in a production setup.nRF51 Tools will be installed together with nRFgo Studio.nRF51 SDKThe nRF51 Software Development Kit (SDK) provides source code of examples and libraries forming the

9、base of your application development. The nRF51 SDK includes: Example code ANT profile examples Bluetooth profile examples Drivers LibrariesFor more information, see the documentation packaged with the nRF51 SDK.Master Control PanelThe Master Control Panel is the software tool that is used with the

10、nRF51 Dongle (PCA10031) to act as a Bluetooth low energy peer device. You can test your applications wireless connection with this tool.The Master Control Panel supports programming of SEGGER J-Link based nRF51 devices. For more information, see the help files in the Master Control Panel.nRF Master

11、ControlnRF Master Control Panel for Android 4.3 is a powerful generic tool that allows you to scan and Panel forAndroid 4.3explore your Bluetooth Smart devices and communicate with them on an Android phone.MCP supports a number of Bluetooth SIG adopted profiles including the Device Firmware Update (

12、DFU) profile from Nordic Semiconductor.S110 SoftDeviceBluetooth low energy Peripheral/Broadcaster protocol stack. For more information, see the S110 nRF51822 SoftDevice Specification and the nRF51 SDK documentation.S120 SoftDeviceBluetooth low energy Central protocol stack solution supporting up to

13、eight simultaneous Central role connections. For more information, see the S120 nRF51822 SoftDevice Specification and the nRF51 SDK documentation.S130 SoftDeviceBluetooth Smart concurrent multi-link protocol stack solution supporting simultaneous Central/ Peripheral/Broadcaster/Observer role connect

14、ions. For more information, see the S130 nRF51822 SoftDevice Specification and the nRF51 SDK documentation.S210 SoftDeviceANT protocol stack. For more information, see the S210 nRF51422 SoftDevice Specification and the nRF51 SDK documentation.S310 SoftDeviceANT and Bluetooth low energy Peripheral co

15、ntroller and host multiprotocol stack. For more information, see the S310 nRF51422 SoftDevice Specification and the nRF51 SDK documentation.Third party toolsDescriptionKeil MDK-ARMDevelopment KitKeil MDK-ARM Development Kit is a development environment specifically designed for microcontroller appli

16、cations that lets you develop using the nRF51 SDK application and example files.SEGGER J-LinkSoftwareThe J-Link software is required to debug using the J-Link hardware that is packaged with this development kit.ANTware IIANTWare is an application used for the control of ANT wireless devices. It is a

17、n excellent tool for first time ANT developers to explore the capabilities of ANT as a low power wireless solution, and for experienced users to easily setup and monitor advanced ANT networks. ANTWare II improves upon past versions with a slick new interface, streamlined functions, and a variety of

18、new features.1.3 DocumentationBelow is a list of the core documentation for the nRF51 Series and the nRF51x22 chip.Note: See our website for additional documentation such as Application Notes and White Papers.DocumentDescriptionnRF51 Series Reference ManualThe nRF51 Series Reference Manual is a func

19、tional description of all the modules and peripherals supported by the nRF51 series.nRF51x22 Product SpecificationThe nRF51x22 Product Specification contains all specifications specific to the chip.S110 nRF51822 SoftDevice SpecificationThe S110 nRF51822 SoftDevice Specification contains information

20、about the SoftDevice features and performance.S120 nRF51822 SoftDevice SpecificationThe S120 nRF51822 SoftDevice Specification contains information about the SoftDevice features and performance.S130 nRF51822 SoftDevice SpecificationThe S130 nRF51822 SoftDevice Specification contains information abou

21、t the SoftDevice features and performance.S210 nRF51422 SoftDevice SpecificationThe S210 nRF51422 SoftDevice Specification contains information about the SoftDevice features and performance.S310 nRF51422 SoftDevice SpecificationThe S310 nRF51422 SoftDevice Specification contains information about th

22、e SoftDevice features and performance.nRF51 SDK DocumentationThe nRF51 SDKdocumentationincludes user guides, descriptions, and referencematerialto help you understand the protocols, examples, and other components of the SDK.nRF51x22 Product Anomaly NotificationThe nRF51x22 Product Anomaly Notificati

23、on - list of anomalies relevant for the chip.ANT Message Protocol and UsageThe ANT Message Protocol and Usage document describes the ANT protocol in detail and contains the fundamental knowledge you need in order to develop successfully with ANT.nRF51 Development Kit Hardware FilesThe nRF51 Developm

24、ent Kit includes firmware source code, documentation, hardware schematics, and layout files. Included are the following files: Altium Designer files Schematics PCB layout files Production files Assembly drawings Drill files Gerber files Pick and Place files Bill of Materials1.4 Development Kit relea

25、se notesDateKit versionDescriptionOctober 20141.0 First release.2 Kit contentIn addition to hardware, the nRF51 Development Kit consists of firmware source code, documentation, hardware schematics, and layout files which are available from .1 x 3V CR2032Lithiumbattery5 x nRF51422 s

26、amples1 x nRF51 Development Kit board (PCA10028)Figure 1 nRF51 Development Kit content3 Getting startedThis section shows you how to get access to the tools, libraries, and documentation.Connect your nRF51 Development Kit to a computer.1. Connect your nRF51 DK board to a computer with a USB cable.2.

27、 The status light (LD5) will come on, indicating it has power.3. After a few seconds, the computer will recognize the nRF51 DK board as a standard USB drive.Figure 2 Windows exampleGet started with the toolchain and examples.1. Download and install nRFgo Studio (which includes the nRF Tools package;

28、 JLinkARM, JLink CDC, nRFjprog, and mergehex) .2. Download and install the latest Keil MDK-ARM /arm.3. Download and install the latest nRF51 SDK found on .4. Read the information in the Readme.txt file that is installed together wit

29、h the SDK. After the installation, the SDK documentation is found here:Online: /nRF51_SDK/doc/index.html.Offline: /ARM/Pack/NordicSemiconductor/nRF_Examples/documentation4 Interface MCUInterface MCU LD5Power switchIF BOOT/RESET buttonFigure 3 Interface MCU4.1 IF Boot/Re

30、set buttonThe nRF51 DK board is equipped with a boot/reset button (SW5). This button is connected to the interface MCU on the board and have two functions: Reset button for the nRF device. Enter boot loader mode of the interface MCU.During normal operation the button will function as a reset button

31、for the nRF device. To enter boot loader mode of the Interface MCU, the button must be pressed while the board is powered until the LED LD5 starts to blink. This is done by pressing the reset button and power cycle the board, either by disconnecting and reconnecting the USB cable or toggle the power

32、 switch (SW6).4.2 Virtual COM portThe on-board Interface MCU features a Virtual COM port via UART. Flexible baudrate setting up to 1 Mbps Dynamic Hardware Flow Control (HWFC) handling Tri-stated UART lines while no terminal isconnectedTable 1 shows an overview of the UART connections on nRF51422 and

33、 the interface MCU.nRF51422Default GPIOUARTInterface MCUUARTP0.08P0.09RTSTXDCTSRXDP0.11RXDTXDP0.10CTSRTSTable 1 Relationship of UART connections on nRF51422 and Interface MCUThe UART signals are routed directly to the Interface MCU. The UART pins connected to the Interface MCU is tri-stated when no

34、terminal is connected to the Virtual COM port on the computer.Note: The terminal used must send a DTR signal in order to configure the UART Interface MCU pins.The P0.08 (RTS) and P0.10 (CTS) can be used freely when HWFC is disabled on the nRF51422.4.3 Interface MCU FirmwareThe on board Interface MCU

35、 is factory programmed with an mbed compliant bootloader, this feature enables the ability to swap interface FW between the factory preloaded SEGGER J-Link OB and the nRF51 mbed interface FW, see section 4.1 “IF Boot/Reset button” on page 8 on how to enter the bootloader.To swap Interface MCU FW, si

36、mply drag the Interface image (.bin) into the mounted bootloader drive on the connected computer and power cycle the board.Both the nRF51 mbed interface FW and the J-Link OB image can be downloaded from .Note: If you have swapped to the mbed image and want to revert back to the J-L

37、ink image, download the latest SEGGER J-Link software from and open a debug session to update to the latest J-Link OB firmware version.Note: The J-Link serial number is linked to the Interface MCU and will not change even when swapping the Interface MCU FW, so it can be useful to writ

38、e the serial number on a sticker on the board.5 Hardware descriptionThis chapter describes the nRF51 Development Kit board (PCA10028).The nRF51 Development Kit can be used as a development platform for the nRF51 device. It features an on- board programming and debugging solution. In addition to radi

39、o communication, the nRF51 device can communicate with a computer through a virtual COM port provided by the interface MCU.5.1 Hardware drawingsFigure 4 nRF51 DK board topFigure 5 nRF51 DK board bottom5.2 Block diagram9&BQ5)$QWHQQD3RZHU VZLWFK 6:86% VHQVH9%86,QWHUIDFH 0&8 DWD86%8$57,) %2275(6(72VF2V

40、FN+0+HEXJ LQQ5)9ROWDJH UHJXODWRU&XUUHQW PHDVXUHPHQW3RZHU VZLWFKHEXJ RXW(WHUQDO VXSSO0DWFKLQJ QHWZRUN%XWWRQV/(V*3,2%DWWHUFigure 6 nRF51 DK board block diagram5.3 Power supplyThe nRF51 DK board has several power options:USBExternal power supplyCoin cell batteryFigure 7 Power supply optionsThe 5 V from

41、 the USB is regulated down to 3.3 V through an on-board voltage regulator. The battery and external power supply are not regulated. The power sources are routed through a set of diodes (D1A, D1B, and D1C) for reverse voltage protection, where the circuit is supplied from the source with the highest

42、voltage.Note: When not USB powered, the Interface MCU is in dormant state and will draw an additional current of 20 A in order to maintain the reset button functionality. This will affect board current consumption, but will not affect the nRF51 current measurements as described in Section 5.7 “Measu

43、ring current” on page 18.USB power voltage regulatorReverse voltageprotectionPower switchnRF current measurementV5VUSB_DETECT U3Vin VoutSB10D1AVBUSSW6V5VVIOR6 N.C.VDD_nRFC16GNDC17C18 SD103ATW-7-F SB91.0FAP7333-33SAG-71.0F 100nF SB11SwitchBat1 + Bat Holder CR2032D1BSD103ATW-7-F SB1221P22Pin List 1x2,

44、 AngledP21 21Pin List 1x2, AngledD1CSD103ATW-7-F TP11Figure 8 Power supply circuitryThe reverse voltage protection diodes will add a voltage drop to the supply voltage of the circuit. To avoid this voltage drop the diodes can be bypassed by shorting one or more solder bridges.Power sourceProtection

45、bypassVoltage levelUSBSB103.3 VCoin-cell batterySB11BatteryExternal supplySB121.8 V - 3.6 V Table 2 Protection diode bypass solder bridgesSB10 SB11 SB12Figure 9 Protection diode bypass solder bridgesNote: By shorting the solder bridges, the reverse voltage protection is removed, and you must make su

46、re to connect only one power source at the time.5.4 Connector interfaceAccess to the nRF51422 GPIOs is available at connectors P2, P3, P4, P5, and P6 on the nRF51 DK board. In addition there is access to ground and power on the P1 connector.Figure 10 nRF51 DK board connectorsThe signals are also ava

47、ilable on bottom side connectors P7, P8, P9, P10, P11, and P12. By mounting pin lists on the connector footprints, the nRF51 DK board can be used as a shield for Arduino motherboards or other boards that follows the Arduino standard.For easy access to GPIO, power, and ground, the signals can also be

48、 found on the through-hole connectorsP13-P17.Note: Some pins have default settings. P0.08, P0.09, P0.10, and P0.11 are by default used by the UART connected to the Interface MCU. See Section 4.2 “Virtual COM port” on page 9 for moreinformation. P0.17 - P0.24 are by default connected to the buttons a

49、ndLED.See Section 5.5 “Buttons and LEDs” on page 16 for more information. P0.26 and P0.27 are by default used for the 32 kHz crystal and are not available on the connectors. See Section 5.6 “32.768 kHz crystal” on page 17 for more information.When the nRF51 DK board is used as a shield together with

50、 an Arduino standard motherboard, the Arduino signals is routed like shown in Figure 11.Figure 11 Arduino signals routing on the nRF51 DK board5.5 Buttons and LEDsThe four buttons and four LEDs on nRF51 DK board are connected to dedicated I/Os on the nRF51422 chip. The connections are shown in Table

51、 3.PartGPIOShortButton 1P0.17-Button 2P0.18-Button 3P0.19-Button 4P0.20-LED 1P0.21SB5LED 2P0.22SB6LED 3P0.23SB7LED 4P0.24SB8Table 3 Button and LED connectionIf GPIO P0.21 - P0.24 are needed elsewhere, the LEDs can be disconnected by cutting the short on SB5-SB8, see Figure 12.SB5 SB6 SB7 SB8Figure 1

52、2 Disconnecting the LEDsThe buttons are active low meaning the input will be connected to ground when the button is activated. The buttons have no external pull-up resistor, so to use the buttons the P0.17 - P0.20 pins must be configured as an input with internal pull-up resistor.The LEDs are active

53、 low, meaning that writing a logical zero (0) to the output pin will illuminate the LED.LED 1R1P0.21220RL0805GLED 2SB5R2P0.22220RL0805G LED 3SB6R3220RP0.23L0805G LED 4SB7R4P0.24P0.17P0.18P0.19P0.20VIOBUTTON1 SW1 PB SWBUTTON2 SW2 PB SWBUTTON3 SW3 PB SWBUTTON4 SW4 PB SW220RL0805GSB8Figure 13 Button an

54、d LED configuration5.6 32.768 kHz crystalnRF51422 can use an optional 32.768 kHz crystal (X2) for higher accuracy and lower average power consumption. On the DK board, P0.26 and P0.27 are by default used for the 32.768 kHz crystal and are not available as a GPIO on the connectors.Note: When using AN

55、T/ANT+, the 32.768 kHz crystal (X2) is required for correct operation.If P0.26 and P0.27 are needed as normal I/Os the 32.768 kHz crystal can be disconnected and the GPIO routed to the connectors. Cut the shorting track on SB1 and SB2, and solder SB3 and SB4. See Figure 14 for reference.SB1 (Cut) SB2 (Cut)SB3 (Solder) SB4 (Solder)Figure 14 Disconnecting 32.768 kHz crystal and connecting P0.26 and P0.27 to the connectorsSB4SB2C14 12pFX2 32.768kHzSB3SB1C1312pFXL1P0.27XL2P0.26Figure 15 32.768 kHz crystal and SB1 to SB4 schematic5.7 Mea