all | frequencies |
|
|
|
|
exhibits | applications |
---|---|---|---|---|---|---|---|
manual | photos | label |
app s | submitted / available | |||||||
---|---|---|---|---|---|---|---|---|
1 2 |
|
02. Operationa Description and User Manual v3 | Users Manual | 5.80 MiB | January 28 2020 / April 27 2020 | delayed release | ||
1 2 |
|
08. Internal photos | Internal Photos | 1.21 MiB | January 28 2020 / April 27 2020 | delayed release | ||
1 2 |
|
07. External photos | External Photos | 897.37 KiB | January 28 2020 / April 27 2020 | delayed release | ||
1 2 |
|
06. Label Design and location | ID Label/Location Info | 311.10 KiB | January 28 2020 | |||
1 2 |
|
01. Agent letter thingy91 | Cover Letter(s) | 26.56 KiB | January 28 2020 | |||
1 2 | 02. Operationa Description and User Manual v3 | Operational Description | January 28 2020 | confidential | ||||
1 2 | 03. Schematic v2 | Schematics | January 28 2020 | confidential | ||||
1 2 | 04. Antenna information | Block Diagram | January 28 2020 | confidential | ||||
1 2 | 05. block diagram v2 | Block Diagram | January 28 2020 | confidential | ||||
1 2 |
|
09. EMC Reports 60433REM.002s v2 | Test Report | 2.89 MiB | January 28 2020 | |||
1 2 |
|
10. EMC Test Set UP 60433REM.002 v2 | Test Setup Photos | 440.57 KiB | January 28 2020 / April 27 2020 | delayed release | ||
1 2 |
|
11. RF Test Report 60433RRF003s | Test Report | 5.46 MiB | January 28 2020 | |||
1 2 |
|
12. RF Test Set UP 60433RRF003 | Test Setup Photos | 1015.62 KiB | January 28 2020 / April 27 2020 | delayed release | ||
1 2 |
|
13. RF Test Report Colocation 60433RRF004s | Test Report | 3.50 MiB | January 28 2020 | |||
1 2 |
|
14. RF Test Set UP Colocation 60433RRF004 | Test Setup Photos | 592.41 KiB | January 28 2020 / April 27 2020 | delayed release | ||
1 2 |
|
15. RF Exposure 60433RAN.002s | RF Exposure Info | 601.79 KiB | January 28 2020 | |||
1 2 |
|
01. Confidentiality request Thingy91 | Cover Letter(s) | 29.95 KiB | January 27 2020 / January 28 2020 | |||
1 2 | 04. Antenna information | Operational Description | January 27 2020 | confidential | ||||
1 2 | Schematics | Schematics | January 27 2020 | confidential |
1 2 | 02. Operationa Description and User Manual v3 | Users Manual | 5.80 MiB | January 28 2020 / April 27 2020 | delayed release |
Nordic Thingy:91 User Guide v1.2 4418_1336 v1.2 / 2020-01-21 Contents Revision history. 1 2 Introduction. Kit content. 2.1 Downloadable content . 2.2 Related documentation . 3 Getting started. 3.1 Connecting LTE Link Monitor . 4 Firmware. 4.1 Getting the firmware . 4.1.1 Download pre-compiled firmware images . 4.1.2 Compile the source code . 4.2 Operating modes . 4.3 GPS . 4.4 LTE Band Lock . 4.5 LTE-M / NB-IoT switching . 5 Firmware update. 5.1 Updating modem firmware . 5.2 Updating application firmware . 5.2.1 Updating application firmware on nRF9160 . 5.2.2 Updating application firmware on nRF52840 . 6 Hardware description. 6.1 Block diagram . 6.2 Hardware figures . 6.3 nRF9160 . 6.3.1 Antenna tuning . 6.3.2 RF measurements . 6.3.3 GPS . 6.3.4 SIM card . 6.4 nRF52840 . 6.4.1 NFC passive tag . 6.4.2 USB . 6.5 Pin maps . 6.6 Motion sensors . 6.7 Environment sensors . 6.8 Buzzer . 6.9 LEDs and buttons . 6.9.1 RGB LED . 6.9.2 Buttons . 6.10 Power supply . 6.10.1 PMIC . 6.10.2 Current measurement . 6.11 Programming and debugging interface . iv
. 5
. 7 7 8
. 9 11
. 12 12
. 12 12 13
. 14 14
. 14
. 15
. 15 16 16 20
. 22 22
. 22
. 23 24
. 25
. 25
. 26
. 27
. 27
. 28 28
. 31 33 33
. 34
. 34 34 34
. 35
. 35
. 36
. 4418_1336 v1.2 ii 6.12 Interface . 6.12.1 N-MOS transistors . 6.12.2 Connectors . 6.12.3 Test points . 7 Regulatory notices. 7.1 FCC regulatory notices . 37 37 38 39
. 42
. 42 Glossary . 43 Acronyms and abbreviations. 45 Legal notices. 46 4418_1336 v1.2 iii Revision history Date Version Description January 2020 December 2019 1.2 1.1 Updated Introduction on page 5 Updated Kit content diagram and added a short description Getting started on page 9 Connecting LTE Link Monitor on page 11 Buttons on page 34 Figures with callouts indicating functionality of components Added the different ways to obtain firmware images for updating firmware, and operating modes:
Firmware on page 12 Updated different firmware update methods and added new update technique using USB (MCUBoot) Firmware update on page 15 August 2019 1.0 First release 4418_1336 v1.2 iv 1 Introduction The Nordic Thingy:91 is a battery-operated prototyping platform for cellular IoT, certified for global operation. It is ideal for rapid development of prototypes for cellular IoT systems and is especially suited for asset tracking applications and environmental monitoring. Nordic Thingy:91 includes sensors that gather data about its own movements and the surrounding environment. Temperature, humidity, air quality, air pressure, color, and light data can easily be extracted for local or remote analysis. For input, the Nordic Thingy:91 offers a user-programmable button. Visual output is achieved with RGB indicator LEDs, while a buzzer can provide audible output. The standard application firmware on Nordic Thingy:91 extracts the data from the different sensors and relays it securely to the nRF Connect for Cloud, where it is displayed in a user-friendly interface. The firmware supports concurrent operation with LTE Link Monitor, a tool providing an AT command interface, enabling link and network testing. LTE Link Monitor is an application, which is implemented as part of the nRF Connect for Desktop application. The firmware has been developed using the nRF Connect Software Development Kit (SDK). It is open source and can be leveraged and modified to suit your specific needs. The firmware can be updated and debugged by using an external programmer/debug probe, for example nRF9160 DK (Development Kit) or J-Link device supporting Arm Cortex-M33. Nordic Thingy:91 integrates the nRF9160 System in Package (SiP)1, supporting LTE-M, NB-IoT and Global Positioning System (GPS), and the nRF52840 System on Chip (SoC), supporting Bluetooth Low Energy and Near Field Communication (NFC) passive tag. Note: LTE-M or LTE NB-IoT can operate simultaneously with Bluetooth LE. Source code for firmware, hardware layout, and schematics are all available on our web site www.nordicsemi.com. Nordic Thingy:91 has an antenna supporting GPS, LTE-M, and NB-IoT that enables it to support a global range of LTE bands. It has two antennas connected to the nRF52840: a 2.4 GHz antenna for Bluetooth LE and an NFC passive tag antenna. To connect to cellular network out of the box, Nordic Thingy:91 has a nano/4FF SIM card slot and is bundled with a SIM card from iBasis that comes preloaded with 10 MB. NFC in Nordic Thingy:91 operates as a passive tag (e.g. it does not feature a reader function). Nordic Thingy:91 may use this tag function for the Out of Band pairing feature as described in the Bluetooth Core Specification. A 1400 mAh rechargeable Li-Po battery is also part of this prototyping platform giving a smooth transition into prototype field-testing. Key features of Nordic Thingy:91 700-960 MHz + 1710-2200 MHz LTE band support2. The following bands, based on geographic regions, are used:
USA 2, 4, 12, and 13 EU 3, 8, 20, and 28 Certifications: CE, FCC LTE-M/NB-IoT/GPS, Bluetooth LE and NFC passive tag antennas 1 The nRF9160 SiP is certified for USA bands 2, 4, 5, 12, 13, 14, 17, 25, 26, and 66. However, Nordic Thingy:91 operates and is only certified for USA bands 2, 4, 12, and 13. The Nordic Thingy:91 firmware is written and documented to only use this subset of USA bands. 2 The application currently enables the following frequency bands: 2, 3, 4, 8, 12, 13, 20, and 28. 4418_1336 v1.2 5 Introduction Nano/4FF Subscriber Identity Module (SIM) card slot User-programmable button and RGB LEDs Environmental sensor for temperature, humidity, air quality, and air pressure Color and light sensor Low-power and high-G accelerometer Buzzer 4 x N-MOS transistor for external DC motors or LEDs Rechargeable Li-Po battery with 1400 mAh capacity Charging through Universal Serial Bus (USB) PC connection through USB Normal operating temperature range: 5oC ~ 35oC nRF9160 Multimode LTE-M/NB-IoT modem GCF certified for global operation 23 dBm output power GPS Power saving features: DRX, eDRX, PSM Coverage enhancement modes Single pin 50 antenna interface Universal Integrated Circuit Card (UICC) interface Application processor 64 MHz Arm Cortex-M33 CPU Arm TrustZone for trusted execution Arm CryptoCell 310 for application layer security 1 MB flash and 256 kB RAM 4 x SPI/UART/TWI, PDM, I2S, PWM, ADC nRF52840 WLCSP Bluetooth LE and NFC passive tag support 64 MHz Arm Cortex-M4F CPU 1 MB flash and 256 kB RAM USB The battery in this product cannot be easily replaced by users themselves. Batteries should be removed only by qualified professionals due to safety concerns. 4418_1336 v1.2 6 2 Kit content The Nordic Thingy:91 kit consists of hardware and access to software components, hardware design files, applications, and documentation. Figure 1: Nordic Thingy:91 hardware content The Nordic Thingy:91 kit contains the following:
Nordic Thingy:91 device with a rubber enclosure serving as a protective cover An eSIM (SIM card) from iBASIS supported by the nano/4FF SIM card slot of Nordic Thingy:91 An information leaflet WARNING - Power adapter is not included in the kit.3 2.1 Downloadable content The Nordic Thingy:91 prototyping platform includes firmware source code, documentation, hardware schematics, and layout files. Firmware Application firmware for Nordic Thingy:91 3 Power supply adapter is not included in the safety certification test report, see separate test report according to IEC 62368. The power supply adapter you will use shall meet PS1 requirements. 4418_1336 v1.2 7 Kit content The hardware files can be downloaded from the Nordic Thingy:91 product page. The zip file and its subdirectories contain the hardware design files for the Nordic Thingy:91. The hardware files for the circuit board are available in the following folder in the hardware files zip package:
\Thingy91 - Hardware files x_x_x\PCA20035-Thingy91 Board x_x_x In this folder, you can find the following hardware design files:
2.2 Related documentation In addition to the information in this document, you may need to consult other Nordic documents. Precompiled HEX files nRF52840 USB to UART bridge nRF9160 modem firmware nRF Connect SDK PC tools nRF Connect LTE Link Monitor Segger Embedded Studio nRF Connect Programmer Web applications nRF Connect for Cloud Hardware files Altium Designer files Schematics and PCB layout files in PDF format Bill of materials Production files:
Drill files Assembly drawings Gerber files Pick-and-place files nRF9160 Product Specification nRF52840 Product Specification nRF9160 DK nRF52840 Development Kit nRF9160 Errata nRF52840 Errata nRF Connect SDK documentation nRF Connect for Cloud nRF Connect LTE Link Monitor nRF Connect Programmer nRF91 AT Commands Reference Guide 4418_1336 v1.2 8 3 Getting started Setting up Nordic Thingy:91 requires completing the following steps. Before you start:
page 15. Unpack Nordic Thingy:91. Make sure to update the Nordic Thingy:91 firmware as explained in the section Firmware update on Make sure you have an nRF Connect for Cloud account and sign in to nRF Connect for Cloud. Once you are signed in, perform the following steps. 1. Add new LTE device. 2. Verify and activate the SIM card. Figure 2: Adding new LTE device in nRF Cloud Input SIM ICCID and Personal Unblocking Key (PUK) from the SIM card, and add personal information. 3. Gently remove the rubber overlay to reveal the power switch and the top of Nordic Thingy:91. Insert Figure 3: Placement of PUK and SIM ICCID on the SIM card the SIM card. 4418_1336 v1.2 9 Getting started 4. Once the SIM card is inserted, power on Nordic Thingy:91. You will find the power switch next to the micro-USB port. Figure 4: Inserting the SIM card Figure 5: Nordic Thingy:91 Power switch Wait for yellow breathing in the indicator LED. If the LED does not turn yellow, check Table 2: Nordic Thingy:91 Operating modes and LED indications on page 14 to determine the present state of Nordic Thingy:91. 5. Associate the Nordic Thingy:91 to your user account. Enter the IMEI and PIN information that is found on the sticker on the Nordic Thingy:91 PCB. Wait for blue breathing which means that your Nordic Thingy:91 is associated and connected. Figure 6: Associating Nordic Thingy:91 to nRF Cloud 4418_1336 v1.2 10 Getting started 6. For optional activation of GPS, go outdoors and press the SW3 button for a minimum of 10 seconds until the indicator LED begins breathing purple. Purple breathing: GPS is active and searching Green breathing: GPS has fix Wait for green breathing in the indicator LED which indicates that your Nordic Thingy:91 has GPS fix. Check that the position data and the environment sensor data are sent to nRF Connect for Cloud. 3.1 Connecting LTE Link Monitor To get debug output and to send AT commands directly to the modem, you can connect to the Nordic Thingy:91 using nRF Connect LTE Link Monitor. Before you begin, install and open nRF Connect for Desktop. To download the latest version, go to nRF Connect for Desktop. For instructions, see nRF Connect LTE Link Monitor. To connect to the Nordic Thingy:91 using LTE Link Monitor, perform the following steps. Install and launch LTE Link Monitor. 1. 2. Connect your Nordic Thingy:91 to your computer with a USB cable. 3. Make sure that Nordic Thingy:91 is powered on. 4. Click Select device and select the device entry from the drop-down list in the LTE Link Monitor. 5. Verify the connection to the Nordic Thingy:91 modem by sending the command AT to the modem from the LTE Link Monitor terminal and observing that the modem responds with OK. All asset tracker debug output shows up in the terminal view, and you can send AT commands to the modem to try out different settings. For further details on available AT commands, see nRF91 AT Commands Reference Guide. 4418_1336 v1.2 11 4 Firmware The firmware of Nordic Thingy:91 has been developed using the nRF Connect SDK. It is open source, and can be modified according to specific needs. The asset tracker application firmware, which is pre-loaded in the Nordic Thingy:91, enables the device to use the environment sensors as described in Environment sensors on page 33, and provides an option of tracking the device using GPS. The data, along with information about the device, is transmitted to Nordic Semiconductor's cloud solution, nRF Cloud, where it can be visualized. For more information on the asset tracker application, see nRF9160 Asset Tracker. 4.1 Getting the firmware Firmware on the Nordic Thingy:91 can be updated after obtaining the corresponding firmware images. The different ways to obtain the firmware images are:
Download pre-compiled firmware images Compile the source code 4.1.1 Download pre-compiled firmware images You can update the firmware on Nordic Thingy:91 by direct download of the compiled versions of firmware images. To obtain pre-compiled firmware images, perform the following steps:
1. Navigate to Firmware for the Thingy:91 under the Downloads tab on the Nordic Thingy:91 product page. 2. Download the latest Nordic Thingy:91 firmware package. 3. Unzip the downloaded firmware package zip file. 4. Check the CONTENTS.txt file in the extracted folder for the location and names of the different firmware images. 4.1.2 Compile the source code Another way to update the firmware on a Nordic Thingy:91 is by using the firmware images obtained by compiling the code in an nRF Connect SDK environment. Nordic Thingy:91 ships with the nRF9160 Asset Tracker application which runs on the nRF9160 SiP and the USB-UART bridge sample which runs on the nRF52840 SoC. Follow nRF Connect SDK Getting Started guide to set up your system to be able to compile a compatible firmware image. There are two compile targets of interest for Nordic Thingy:91 in nRF Connect SDK, namely:
nrf9160_pca20035ns nrf52840_pca20035 The compile target nrf9160_pca20035ns should be used when compiling the application code for the nRF9160 SiP and the compile target nrf52840_pca20035 should be used when compiling the application code for the onboard nRF52840 SoC. To compile the source code, perform the following steps:
4418_1336 v1.2 12 Go to the desired application folder. For example, the folder path is ncs/nrf/applications/
asset_tracker when compiling the source code for the asset tracker application on the nrf9160_pca20035ns target and ncs/nrf/samples/usb/usb_uart_bridge when compiling the source code for the USB-UART bridge sample on the nrf52840_pca20035 target. Make sure that you have the latest version of nRF Connect SDK repository by pulling the nRF Connect SDK repository on GitHub repository using the command:
Firmware Run the west command to get the rest of the dependencies:
git pull west update Compile the code using west command as follows:
For the asset tracker on nRF9160:
west build -b nrf9160_pca20035ns For the USB-UART bridge on nRF52840:
west build -b nrf52840_pca20035 The various firmware image files that can be used for the application firmware update can be located here: build/zephyr/. File File format and update scenario merged.hex Full image, HEX format. Used in the application firmware update using debug probe. app_signed.hex MCUboot compatible image, HEX format. Used in the application firmware update using nRF Connect Programmer. app_update.bin MCUboot compatible image, binary format. Used in the application firmware update using the mcumgr command line tool and for FOTA updates. Table 1: Firmware image files 4.2 Operating modes Nordic Thingy:91 contains RGB indicator LEDs which indicate the operating state of the device. The following table shows the various operating modes and the LED indications in Nordic Thingy:91. 4418_1336 v1.2 13 Firmware
1 2 3 4 5 6 7 Mode Connecting Connected Low Battery Error LED White breathing Yellow breathing Blue breathing Waiting for user association Environment data only GPS Searching Purple breathing GPS fix Green breathing Red slow breathing Red fast breathing Table 2: Nordic Thingy:91 Operating modes and LED indications 4.3 GPS Nordic Thingy:91 has GPS which, if activated, allows the device to be located globally using GPS signals. To activate GPS long press button SW3 (> 10 seconds) until the LED starts breathing purple. The LED starts breathing green when a GPS fix is achieved, and it starts breathing purple again when GPS is active and searching. To turn off GPS long press button SW3 (> 10 seconds) until the LED starts breathing blue. 4.4 LTE Band Lock The modem within Nordic Thingy:91 can be configured to use specific LTE bands by using the band lock AT command. The pre-flashed firmware configures the modem to use the bands currently certified on the Nordic Thingy:91 hardware. The bands to enable can be configured when compiling the firmware. For more information see:
Band lock AT command nRF Connect SDK Band Lock 4.5 LTE-M / NB-IoT switching Nordic Thingy:91 has a multimode modem which enables it to support automatic switching between LTE-
M and NB-IoT. A built-in parameter in the Nordic Thingy:91 firmware determines whether the modem first attempts to connect in LTE-M or NB-IoT mode. If the modem fails to connect using this preferred mode within the default timeout period (10 minutes), the modem switches to the other mode. 4418_1336 v1.2 14 5 Firmware update You can update the modem firmware and the application firmware on Nordic Thingy:91 using multiple methods. Modem firmware update can be done using an external debug probe such as nRF9160 DK. Application firmware update is supported through USB leveraging the built-in serial recovery mode of Nordic Thingy:91. The device also supports application firmware update using an external debug probe. 5.1 Updating modem firmware You can update the modem firmware on Nordic Thingy:91 by using an external debug probe such as nRF9160 DK or J-Link device supporting Arm Cortex-M33. To update the modem firmware, complete the steps in this section. 1. Download the latest modem firmware zip file. You can find it under the Compatible Downloads tab that is halfway down the nRF9160 product page. 2. Connect the Nordic Thingy:91 to the debug out port on a 10-pin external debug probe, for example, nRF9160 DK, using a 10-pin JTAG cable as shown in the following figure. Figure 7: Connecting Nordic Thingy:91 to the external debug probe Note: If using nRF9160 DK as the debug probe, make sure VDD_IO (SW11) is set to 1.8 V. 3. Power on both the devices. 4. Start nRF Connect Programmer. 5. Connect the external debug probe to the PC with a USB cable. 4418_1336 v1.2 15 Firmware update 6. Click Select device and select the appropriate debug probe entry from the drop-down list in the nRF 7. Click Update Modem in the Cellular Modem pane on the right and choose the zip file with the latest Connect Programmer. modem release. 8. Click Write in the Device pane on the right and wait for the update to complete. Note: If you have issues updating modem firmware, then do Erase All before trying to update the modem again. 5.2 Updating application firmware Application firmware update on a Nordic Thingy:91 can be done either on the main nRF9160 SiP component or on the nRF52840 SoC component. The selection of the target to be updated is based on the switch and the buttons in Nordic Thingy:91 which form part of its hardware technology. 5.2.1 Updating application firmware on nRF9160 Application firmware update on the nRF9160 SiP in Nordic Thingy:91 can be done in multiple ways. Using USB (MCUboot) Using an external debug probe 5.2.1.1 Updating application firmware on nRF9160 using USB (MCUboot) Firmware updates can be done directly on the nRF9160 SiP of Nordic Thingy:91 by putting the device into serial recovery mode. To update the application firmware on nRF9160 using USB (MCUboot) and the built-in serial recovery mode, complete the steps in this section. 1. Connect Nordic Thingy:91 to the PC using USB. 2. Put the Nordic Thingy:91 into application serial recovery mode by pushing the SW3 button while powering on. 3. Start nRF Connect Programmer. 4. Click Select device and select the appropriate device entry from the drop-down list in the nRF Connect Programmer as shown in the following figure. 4418_1336 v1.2 16 Firmware update Figure 8: Connecting to Nordic Thingy:91 using nRF Connect Programmer 5. Click Add HEX file on the right pane (named as File). Figure 9: Selecting the firmware image file using Add HEX file option in the nRF Connect Programmer 4418_1336 v1.2 17 6. Click Browse from the drop-down list that appears as a result of the previous step in the nRF Connect Programmer as shown in the following figure. Firmware update Figure 10: Selecting the firmware image file using Add HEX file (Browse) option in the nRF Connect Programmer 7. Select the MCUboot compatible HEX file from the file browser that opens up. 8. Click Write on the Device pane in the right as shown in the following figure. 4418_1336 v1.2 18 Firmware update Figure 11: Updating the application firmware using Write option in nRF Connect Programmer The MCUboot DFU dialogue box appears as shown in the following figure. Figure 12: MCUboot DFU dialogue box 4418_1336 v1.2 19 Firmware update 9. Click Write in the MCUboot DFU dialogue box and wait for the update to finish. 5.2.1.2 Updating application firmware on nRF9160 using an external debug probe Firmware updates on the nRF9160 SiP of Nordic Thingy:91 can be performed by using an externally connected debug probe. To update the application firmware on nRF9160 using an external debug probe, complete the steps in this section. 1. Set the Nordic Thingy:91 SWD selection switch (SW2) to nRF91. Refer Figure 35: SWD SELECT switch on 2. Connect the Nordic Thingy:91 to the debug out port on a 10-pin external debug probe, for example, nRF9160 DK, using a 10-pin JTAG cable. Refer Figure 7: Connecting Nordic Thingy:91 to the external debug probe on page 15. Note: If using nRF9160 DK as the debug probe, make sure that VDD_IO (SW11) is set to 1.8 V. 3. Make sure that the Nordic Thingy:91 and the external debug probe are powered on. 4. Update the application firmware using the nRF Connect Programmer by performing the following page 37. steps:
a. Start nRF Connect Programmer. b. Connect the external debug probe to the PC with a USB cable. c. Click Select device and select the appropriate entry for the external debug probe from the drop-
d. Click Add HEX file on the right pane (named as File) and click Browse from the drop-down list that down list in the nRF Connect Programmer. appears in the nRF Connect Programmer. e. Select the firmware image file in the file browser. f. Click Erase & write on the Device pane on the right and wait for the update to finish. 5.2.2 Updating application firmware on nRF52840 Application firmware update on the nRF52840 SoC in Nordic Thingy:91 can be done in multiple ways. Using USB (MCUboot) Using an external debug probe 5.2.2.1 Updating application firmware on nRF52840 using USB (MCUboot) Firmware updates can be done directly on the nRF52840 SoC of Nordic Thingy:91 by putting the device into serial recovery mode. To update the application firmware on nRF52840 using USB (MCUboot) and the built-in serial recovery mode, complete the steps in this section. 1. Connect Nordic Thingy:91 to the PC with a USB cable. 2. Put Nordic Thingy:91 into application serial recovery mode by pushing the SW4 button while powering on. 3. Start nRF Connect Programmer. 4. Click Select device and select the appropriate device entry from the drop-down list in the nRF Connect Programmer as shown in Figure 8: Connecting to Nordic Thingy:91 using nRF Connect Programmer on page 17. 5. Click Add HEX file on the right pane (named as File) as shown in Figure 9: Selecting the firmware image file using Add HEX file option in the nRF Connect Programmer on page 17. 4418_1336 v1.2 20 Firmware update 6. Click Browse from the drop-down list that appears as a result of the previous step in the nRF Connect Programmer as shown in Figure 10: Selecting the firmware image file using Add HEX file (Browse) option in the nRF Connect Programmer on page 18. 7. Select the MCUboot compatible HEX file from the file browser that opens up. 8. Click Write on the Device pane in the right as shown in Figure 11: Updating the application firmware using Write option in nRF Connect Programmer on page 19. The MCUboot DFU dialogue box appears as shown in Figure 12: MCUboot DFU dialogue box on page 19. 9. Click Write in the MCUboot DFU dialogue box and wait for the update to finish. 5.2.2.2 Updating application firmware on nRF52840 using an external debug probe Firmware updates on the nRF52840 SoC of Nordic Thingy:91 can be performed by using an externally connected debug probe. To update the application firmware on nRF52840 using an external debug probe, complete the steps in this section. 1. Set the Nordic Thingy:91 SWD selection switch (SW2) to nRF52. Refer Figure 35: SWD SELECT switch on 2. Connect the Nordic Thingy:91 to the debug out port on a 10-pin external debug probe, for example, nRF9160 DK. Refer Figure 7: Connecting Nordic Thingy:91 to the external debug probe on page 15. Note: If using nRF9160 DK as the debug probe, make sure that VDD_IO (SW11) is set to 1.8 V. 3. Make sure that the Nordic Thingy:91 and the external debug probe are powered on. 4. Update the application firmware using the nRF Connect Programmer by performing the following page 37. steps:
a. Start nRF Connect Programmer. b. Connect the external debug probe to the PC with a USB cable. c. Click Select device and select the appropriate entry for the external debug probe from the drop-
d. Click Add HEX file on the right pane (named as File) and click Browse from the drop-down list that down list in the nRF Connect Programmer. appears in the nRF Connect Programmer. e. Select the firmware image file in the file browser. f. Click Erase & write on the Device pane on the right and wait for the update to finish. 4418_1336 v1.2 21 6 Hardware description This chapter focuses on the hardware components of Nordic Thingy:91 with detailed descriptions of the various hardware blocks that are present on the device. The sensors available in Nordic Thingy:91 are not calibrated in production. Nordic Semiconductor does not specify the accuracy of measurements. Users who want to reuse parts of this design to create measurement devices should conform to documentation of the specific sensors. 6.1 Block diagram The block diagram represents interactions between hardware components on Nordic Thingy:91. Button Buzzer driver NMOS transistors Buzzer SIM card Color sensor Environmental sensor LED driver Accelerometers LEDs 3.3 V 1.8 V USB Power switch Current measurement Battery Power switch PMIC nRF9160 Antenna Debug in SWD select Antenna GPS LNA RF switches/
matching network RF Matching network NFC passive tag antenna Current measurement Spare GPIO connector nRF52840 Button Figure 13: Nordic Thingy:91 hardware block diagram 6.2 Hardware figures The hardware figures show elements on both sides of the Nordic Thingy:91 PCB. 4418_1336 v1.2 22 Hardware description Figure 14: Nordic Thingy:91 PCB, top Figure 15: Nordic Thingy:91 PCB, bottom 6.3 nRF9160 The nRF9160 is the main device of Nordic Thingy:91. It is a compact, highly integrated SiP that makes use of the latest low-power LTE technology. It has advanced processing capabilities and security features. It also has the accessibility and flexibility to be used with a wide range of single-device low-power cellular IoT applications. For more information, see nRF9160 Product Specification. 4418_1336 v1.2 23 Hardware description Figure 16: nRF9160 schematic 6.3.1 Antenna tuning To improve antenna efficiency, Nordic Thingy:91 has dynamic antenna tuning. Different tuning components are used for different frequencies. This is achieved by using tuning components between two SP8T RF switches. The switches are automatically controlled by the nRF9160 LTE modem and set to the correct state based on the frequency of operation. Six paths are used for LTE frequency, and one path is used for GPS frequency. RF_SW3 RF_SW2 RF_SW1 State 0 0 0 0 1 1 1 1 0 0 1 1 0 0 1 1 0 1 0 1 0 1 0 1 RF2 - RFC RF7 - RFC RF5 - RFC RF3 - RFC RF1 - RFC RF8 - RFC RF6 - RFC RF4 - RFC Band Not used Frequency Not used 13U/D, 28D 746 MHz - 803 MHz 12U/D, 17U/D, 28U 698 MHz - 748 MHz 1U/D, 2U/D, 3U/D, 4U/D, 25U/D 1710 MHz - 2200 MHz 5D, 20U, 26D 824 MHz - 894 MHz 8U/D 880 MHz - 960 MHz 5U, 20D, 26U 791 MHz - 849 MHz Not used GPS Not used 1574 MHz - 1577 MHz Table 3: Antenna tuning bands 4418_1336 v1.2 24 Hardware description Figure 17: Antenna tuning circuitry schematic 6.3.2 RF measurements The LTE signals are propagated through a coaxial connector. This makes it possible to perform conducted measurements or attach external antennas. By default, when no cable is attached, the RF signal is routed to the onboard antenna. When connecting the adapter, the internal switch in the SWF connector will disconnect the onboard antenna and connect the RF signal from the nRF9160 to the adapter. The connector is of SWF type (Murata part no. MM8130-2600) with an internal switch. An adapter is available (Murata part no. MXHS83QE3000) with a standard SMA connection on the other end for connecting instruments. The adapter is not included in the kit. The insertion loss in the adapter cable is approximately 0.51 dB. Figure 18: Connecting a spectrum analyzer 6.3.3 GPS The nRF9160 has a dedicated GPS port to support global navigation, and the same antenna is used for both LTE and GPS. The GPS signal is RX only, and there is a low-noise amplifier (LNA) that amplifies the signal before it is fed to the GPS RF port on the nRF9160. The GPS signals are propagated through a coaxial connector located between the antenna and the LNA. This makes it possible to attach external antennas. The connector is of SWF type (Murata part no. MM8130-2600) with an internal switch. An adapter is available (Murata part no. MXHS83QE3000) with a standard SMA connection on the other end for connecting instruments. The adapter is not included in the kit. The insertion loss in the adapter cable is approximately 0.51 dB. 4418_1336 v1.2 25 Hardware description Figure 19: External GPS antenna connector The LNA enable signal is controlled by the logic circuitry. It is enabled only when the antenna tuning circuitry is set to operate at the GPS frequency band. The LNA makes the GPS receiver more sensitive to GPS signals and less sensitive to interference from other sources nearby. Figure 20: GPS circuit schematic Note: GPS signals do not usually penetrate ceilings or other structures. For best GPS performance, Nordic Thingy:91 should be used outside in an open space, far from sources of interference and other structures that may block the signals. 6.3.4 SIM card Nordic Thingy:91 is equipped with a nano-SIM (4FF) card slot. 4418_1336 v1.2 26 Hardware description Figure 21: SIM card schematic 6.4 nRF52840 For USB, Bluetooth, and NFC passive tag connectivity, Nordic Thingy:91 uses a nRF52840 SoC. It is a powerful, highly flexible, ultra-low power SoC that incorporates a Bluetooth Low Energy radio and a 32-bit Arm Cortex-M4F CPU. For more information on the SoC, see nRF52840 Product Specification. Figure 22: nRF52840 schematic 6.4.1 NFC passive tag Nordic Thingy:91 supports an NFC passive tag. NFC-A listen mode operation is supported on the nRF52840. The NFC passive tag antenna input is available on connector J5. 4418_1336 v1.2 27 Hardware description Figure 23: NFC passive tag antenna connector The NFC passive tag uses two pins, F1 (NFC1) and E2 (NFC2), to connect the antenna. These pins are shared with GPIOs (P0.09 and P0.10), and the PROTECT field in the NFCPINS register in UICR defines the usage of these pins and their protection level against abnormal voltages. The content of the NFCPINS register is reloaded at every reset. Note: The NFC passive tag pins are enabled by default. The NFC passive tag can be disabled and the GPIOs enabled by defining the CONFIG_NFCT_PINS_AS_GPIOS variable in the project settings. The way of doing this depends on the Integrated Development Environment (IDE) or toolchain in use. When using SEGGER Embedded Studio, go to Project > Edit Options > Code > Preprocessor >
Preprocessor Definitions and add the CONFIG_NFCT_PINS_AS_GPIOS variable. When using Keil, go to Project > Options for Target > C/C++ > Preprocessor Symbols > Define and add the CONFIG_NFCT_PINS_AS_GPIOS variable. 6.4.2 USB The Nordic Thingy:91 USB connector is connected to the USB interface of the nRF52840 SoC. This enables PC communication and battery charging. 6.5 Pin maps The pin assignments for the nRF9160 SiP and nRF52840 SoC are listed in the pin map tables. I/O P0.00 P0.01 P0.02 P0.03 P0.04 P0.05 P0.06 P0.07 Label Description SENSE_LED_RED Red color of the color sensor support LED SENSE_LED_GREEN Green color of the color sensor support LED SENSE_LED_BLUE Blue color of the color sensor support LED SCK MOSI MISO SPI clock line SPI master output, slave input data line SPI master input, slave output data line ADXL372_INT1 High-G accelerometer interrupt line ADXL372_CS High-G accelerometer chip select line 4418_1336 v1.2 28 I/O P0.08 P0.09 P0.10 P0.11 P0.12 P0.13 P0.14 P0.15 P0.16 P0.17 P0.18 P0.19 P0.20 P0.21 P0.22 P0.23 P0.24 P0.25 P0.26 P0.27 P0.28 P0.29 P0.30 P0.31 Hardware description Label Description ADXL362_CS Low-power accelerometer chip select line ADXL362_INT1 Low-power accelerometer interrupt line ADXL362_INT2 Accelerometer interrupt line 2, selectable by solder bridge I2C data line I2C clock line Gate of N-MOS transistor externally available Gate of N-MOS transistor externally available Gate of N-MOS transistor externally available Gate of N-MOS transistor externally available SDA SCL N-MOS_1 N-MOS_2 N-MOS_3 N-MOS_4 ADP_INT MCU_IF0 MCU_IF1 MCU_IF2 MCU_IF3 MCU_IF4 MCU_IF5 MCU_IF6 MCU_IF7 BUTTON BH_INT BUZZER PMIC interrupt line nRF52840 interface nRF52840 interface nRF52840 interface nRF52840 interface nRF52840 interface nRF52840 interface nRF52840 interface nRF52840 interface Button input Color sensor interrupt line Buzzer PWM signal LIGHTWELL_RED Red color of the lightwell LEDs LIGHTWELL_GREEN Green color of the lightwell LEDs LIGHTWELL_BLUE Blue color of the lightwell LEDs Table 4: nRF9160 pin map 4418_1336 v1.2 29 Hardware description Description Low frequency crystal Low frequency crystal Analog/digital GPIO externally available Analog/digital GPIO externally available Digital GPIO externally available Not used Not used Not used Not used Not used Not used NFC passive tag antenna NFC passive tag antenna MCU_IF0 nRF9160 interface IF_SWD_IO MCU_IF1 N.A. nRF9160 SWD interface data line nRF9160 interface Not used IF_SWD_CTRL nRF9160 SWD interface control nRF52840 reset line, available on test point nRF9160 interface nRF9160 interface nRF9160 interface nRF9160 interface Not used Not used MCU_IF5 nRF9160 interface Label XL1 XL2 N.A. SPARE7 N.A. SPARE2 SPARE1 N.A. N.A. NFC1 NFC2 N.A. N.A. RESET MCU_IF6 MCU_IF2 MCU_IF3 MCU_IF7 N.A. N.A. SPARE3 SPARE4 SPARE5 N.A. SPARE6 N.A. MCU_IF4 COEX2 Digital GPIO externally available Digital GPIO externally available Digital GPIO externally available Analog/digital GPIO externally available Not used Not used nRF9160 interface nRF9160 COEX interface I/O P0.00 P0.01 P0.02 P0.03 P0.04 P0.05 P0.06 P0.07 P0.08 P0.09 P0.10 P0.11 P0.12 P0.13 P0.14 P0.15 P0.16 P0.17 P0.18 P0.19 P0.20 P0.21 P0.22 P0.23 P0.24 P0.25 P0.26 P0.27 P0.28 P0.29 P0.30 P0.31 P1.00 P1.01 4418_1336 v1.2 30 Hardware description I/O P1.02 P1.03 P1.04 P1.05 P1.06 P1.07 P1.08 P1.09 P1.10 P1.11 P1.12 P1.13 P1.14 P1.15 IF_SWK_CLK nRF9160 SWD interface clock line Label N.A. N.A. COEX1 N.A. COEX0 SDA SCL N.A. SPARE8 N.A. BOOT N.A. N.A. Description Not used Not used nRF9160 COEX interface Not used nRF9160 COEX interface I2C data line I2C clock line Not used Digital GPIO externally available Not used Boot button Not used Not used Table 5: nRF52840 pin map 6.6 Motion sensors Nordic Thingy:91 includes a low-power accelerometer and a high-G accelerometer. 4418_1336 v1.2 31 Hardware description Figure 24: Low-power and high-G accelerometers schematic When Nordic Thingy:91 is in low-power sleep mode, any user interaction will be detected by the low-
power accelerometer. The accelerometer has an SPI interface and it can detect motion on three axes. By default, the INT2 line of the accelerometer is not connected to nRF9160. If you want to use the INT2 line, solder SB6. For detecting shocks, Nordic Thingy:91 uses a high-G accelerometer. The accelerometer has an SPI interface, and it can detect motion on three axes. By default, the INT2 line of the accelerometer is not connected to nRF9160. If you want to use the INT2 line, solder SB5. Figure 25: Low-power accelerometer and high-G accelerometer interrupt line 2 selection 4418_1336 v1.2 32 Hardware description 6.7 Environment sensors To monitor its surroundings, Nordic Thingy:91 has a multi-sensor chip that contains several sensors for detecting different environmental properties and a separate color and light sensor. The multi-sensor chip contains sensors for temperature, humidity, air quality, and air pressure. Figure 26: Environment sensor schematic The color sensor onboard Nordic Thingy:91 senses red, green, blue, and infrared light. The sensor faces towards the blue transparent bottom case with light pipes guiding the light towards the sensor. To measure the color on a surface, the color sensor is accompanied with an RGB LED that can illuminate the surface enabling the color sensor to read the color of the reflected light. The color sensor is accessed through I2C (slave address 0x38). Figure 27: Color sensor schematic 6.8 Buzzer For audio output, Nordic Thingy:91 has a magnetic buzzer. The buzzer is driven by a transistor using a PWM input. Figure 28: Buzzer schematic 4418_1336 v1.2 33 Hardware description 6.9 LEDs and buttons Nordic Thingy:91 user interface consists of RGB LEDs and two buttons. 6.9.1 RGB LED Nordic Thingy:91 is equipped with three RGB LEDs. Two of the LEDs are used to light up the light well and are controlled by the same signals using transistors as switches. The third LED is located near the color sensor and is used as auxiliary light for color measurements. Figure 29: LED schematic 6.9.2 Buttons Nordic Thingy:91 has two buttons. The main button, located underneath the Nordic Semiconductor logo, is termed as the SW3 button and it is used for user input. It is connected to the nRF9160 SiP. The second button, termed as SW4, is connected to the nRF52840 SoC. It is accessible only when the rubber cover on the device is removed. Refer the image Figure 4: Inserting the SIM card on page 10 to locate the buttons. Either of the two buttons, SW3 or SW4, can be used to activate the serial recovery mode of Nordic Thingy:91 to update the nRF9160 SiP or the nRF52840 SoC respectively. For more information, see the sections Updating application firmware on nRF9160 using USB (MCUboot) on page 16 and Updating application firmware on nRF52840 using USB (MCUboot) on page 20. 6.10 Power supply The main power source is a rechargeable lithium polymer (Li-Po) battery. The battery has a nominal capacity of 1400 mAh and can be recharged through USB. Nordic Thingy:91 has a power switch that physically disconnects the battery and the USB power from the rest of the circuits. This switch must be on for Nordic Thingy:91 to work and charge the battery. When the power switch is in the OFF position, it activates a circuit that drains the 1.8 V power domain. 4418_1336 v1.2 34 Hardware description Figure 30: Schematics for battery connector, and the power switch 6.10.1 PMIC Nordic Thingy:91 uses a power management IC (PMIC) as internal power management. The PMIC includes a battery charger, a fuel gauge and two regulator outputs. The PMIC has three voltage domain outputs that are used on Nordic Thingy:91:
VSYS used for the nRF9160 SiP One 1.8 V output used as GPIO voltage One 3.3 V output used for analog circuitry The 1.8 V domain supplies the nRF52840, the accelerometers, the environment sensors, and the GPIOs of the nRF9160. This domain must always be on for Nordic Thingy:91 to work. The 3.3 V domain supplies the LEDs, the color sensor, the buzzer, the RF switches and the GPS LNA. This power domain can be powered down to save power when Nordic Thingy:91 is in sleep mode. Figure 31: PMIC schematic 6.10.2 Current measurement It is possible to measure the current flowing to nRF9160 and nRF52840 by cutting the short on SB3
(nRF9160) and/or SB4 (nRF52840) and placing an ampere meter between the terminals of P1 (nRF9160) and terminals of P2 (nRF52840). 4418_1336 v1.2 35 Hardware description Figure 32: Measuring current to the nRF9160 Figure 33: Measuring current to the nRF52840 Figure 34: Current measurement schematic 6.11 Programming and debugging interface Nordic Thingy:91 is equipped with one programming and debugging interface connector (P8) that is shared between the nRF9160 and nRF52840. 4418_1336 v1.2 36 The device to be programmed is selected by the SWD SELECT switch (SW2). The selection of device can also be controlled by connecting TP28 to 1.8 V or ground. Hardware description Figure 35: SWD SELECT switch The SWD interface of the nRF9160 can also be connected to the nRF52840. The enabling of this connection is controlled by the nRF52840. Figure 36: SWD interface and control schematic 6.12 Interface To enable the user to connect external hardware, Nordic Thingy:91 routes some of the GPIOs to connectors or test points and transistors to drive higher currents. 6.12.1 N-MOS transistors Nordic Thingy:91 is equipped with four N-MOS transistors that can be used to drive small DC motors or LEDs. The drain and source of the transistors are available on external connectors and the gate is connected directly to the nRF9160. 4418_1336 v1.2 37 Hardware description Figure 37: Schematics for the N-MOS transistors 6.12.2 Connectors In addition to the N-MOS drain and source on P7, power domains and extra GPIOs can be found on connectors P3-P6. For more information, see Connector pinouts on page 38. Figure 38: Nordic Thingy:91 external connectors Figure 39: Interface connectors 6.12.2.1 Connector pinouts Pin 1 2 1 2 Pin Signal GND VLi-Ion Signal GND 1V8 Table 6: Pinout of connector P3 Table 7: Pinout of connector P4 Description Ground Battery voltage Description Ground Regulated 1.8 V domain 4418_1336 v1.2 38 Pin Pin Pin 1 2 1 2 3 4 5 6 1 2 3 4 5 6 7 8 9 10 Table 8: Pinout of connector P5 Table 9: Pinout of connector P6 Signal GND 3V3 Signal SPARE1 SPARE2 SPARE3 SPARE4 SPARE5 SPARE6 Signal 1V8 GND MOS_1_D MOS_1_S MOS_2_D MOS_2_S MOS_3_D MOS_3_S MOS_4_D MOS_4_S Hardware description Description Ground Regulated 3.3 V domain Description GPIO of the nRF52840 GPIO of the nRF52840 GPIO of the nRF52840 GPIO of the nRF52840 GPIO of the nRF52840 GPIO of the nRF52840 Description Regulated 1.8 V domain Ground Drain of n-channel MOSFET 1 Source of n-channel MOSFET 1 Drain of n-channel MOSFET 2 Source of n-channel MOSFET 2 Drain of n-channel MOSFET 3 Source of n-channel MOSFET 3 Drain of n-channel MOSFET 4 Source of n-channel MOSFET 4 Table 10: Pinout of connector P7 6.12.3 Test points 4418_1336 v1.2 39 nRF91-P0.10 GPIO of the nRF9160 nRF52-P0.18/RESET Hardware description Bit 0 of RF switch control signals Bit 1 of RF switch control signals Bit 2 of RF switch control signals Description Reserved Reserved Reserved GPIO/RESET of the nRF52840 I2C clock line I2C data line USB voltage before power switch USB voltage after power switch Battery voltage before power switch Battery voltage after power switch Ground Ground Internal power domain of PMIC and default nRF9160 power supply Regulated 1.8 V domain Regulated 3.3 V domain Stop the buck regulator switching of PMIC PMIC manual reset input GPIO of the nRF52840 GPIO of the nRF52840 Programming interface data line Programming interface target select Programming interface clock line USB data line USB data line ADP_PGOOD1 PMIC output status indication pin 1 ADP_PGOOD2 PMIC output status indication pin 2 ADP_RESET PMIC reset output Test point Location TP1 TP2 TP3 TP4 TP5 TP6 TP7 TP8 TP9 TP10 TP11 TP12 TP13 TP14 TP15 TP16 TP17 TP18 TP19 TP20 TP21 TP22 TP23 TP24 TP25 TP26 TP27 TP28 TP29 TP30 TP31 TP32 Bottom Bottom Bottom Bottom Bottom Bottom Bottom Top Top Top Top Top Top Top Top Top Top Top Top Bottom Bottom Bottom Bottom Bottom Bottom Bottom Top Top Top Top Top Top Signal N.A. RF_SW1 RF_SW2 RF_SW3 N.A. N.A. SCL SDA VBUS'
VBUS VLi-Ion'
VLi-Ion GND GND VSYS 1V8 3V3 ADP_STP ADP_MR SPARE7 SPARE8 SWDIO SWDSEL SWDCLK D-
D+
nRF91-P0.13/AIN0 Analog/digital GPIO of the nRF9160, combined with N-MOS1 4418_1336 v1.2 40 Test point Location Signal Description TP33 TP34 TP35 TP36 TP37 TP38 Top Top Top Top Top Top Hardware description nRF91-P0.16/AIN3 Analog/digital GPIO of the nRF9160, combined with N-MOS4 SCK MOSI MISO ADXL372_CS ADXL362_CS SPI clock line SPI master output, slave input data line SPI master input, slave output data line High-G accelerometer chip select line Low-power accelerometer chip select line Table 11: Pinout of connector P3 4418_1336 v1.2 41 7 Regulatory notices The following regulatory notices apply to Nordic Thingy:91. 7.1 FCC regulatory notices Modification statement Nordic Semiconductor ASA has not approved any changes or modifications to this device by the user. Any changes or modifications could void the users authority to operate the equipment. Interference statement This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:
(1) this device may not cause interference, and (2) this device must accept any interference, including interference that may cause undesired operation of the device. Wireless notice This device complies with FCC radiation exposure limits set forth for an uncontrolled environment and meets the FCC radio frequency (RF) Exposure Guidelines. This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter. The antenna should be installed and operated with minimum distance of 20 cm between the radiator and your body. FCC Class B digital device notice This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
Reorient or relocate the receiving antenna. Increase the separation between the equipment and receiver. Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. Consult the dealer or an experienced radio/TV technician for help. 4418_1336 v1.2 42 A development platform used for application development. Glossary DK (Development Kit) GPIO General-Purpose Input/Output Global Positioning System (GPS) A satellite-based radio navigation system that provides its users with accurate location and time information over the globe. Integrated Development Environment (IDE) A software application that provides facilities for software development. MCUboot A secure bootloader for 32-bit microcontroller units, which is independent of hardware and operating system. Near Field Communication (NFC) A standards-based short-range wireless connectivity technology that enables two electronic devices to establish communication by bringing them close to each other. Personal Unblocking Key (PUK) A digit sequence required in 3GPP mobile phones to unlock a SIM that has disabled itself after an in correct personal identification number has been entered multiple times. A set of tools used for developing applications for a specific device or operating system. Software Development Kit (SDK) SEGGER Embedded Studio (SES) A cross-platform IDE for embedded C/C++ programming with support for Nordic Semiconductor devices, produced by SEGGER Microcontroller. Subscriber Identity Module (SIM) A card used in User Equipment (UE) containing data for subscriber identification. A number of integrated circuits, often from different technologies, enclosed in a single module that performs as a system or subsystem. A microchip that integrates all the necessary electronic circuits and components of a computer or other electronic systems on a single integrated circuit. System in Package (SiP) System on Chip (SoC) User Equipment (UE) Any device used by an end-user to communicate. The UE consists of the Mobile Equipment (ME) and the Universal Integrated Circuit Card (UICC). 4418_1336 v1.2 43 Universal Integrated Circuit Card (UICC) A new generation SIM used in UE for ensuring the integrity and security of personal data. Universal Serial Bus (USB) An industry standard that establishes specifications for cables and connectors and protocols for connection, communication, and power supply between computers, peripheral devices, and other computers. 4418_1336 v1.2 44 Acronyms and abbreviations These acronyms and abbreviations are used in this document. DK GPIO GPS IDE NFC PUK SDK SES SIM SiP SoC USB UICC Development Kit General-Purpose Input/Output Global Positioning System Integrated Development Environment Near Field Communication Personal Unblocking Key Software Development Kit SEGGER Embedded Studio Subscriber Identity Module System in Package System on Chip Universal Serial Bus Universal Integrated Circuit Card 4418_1336 v1.2 45 Legal notices By using this documentation you agree to our terms and conditions of use. Nordic Semiconductor may change these terms and conditions at any time without notice. Liability disclaimer Nordic Semiconductor ASA reserves the right to make changes without further notice to the product to improve reliability, function, or design. Nordic Semiconductor ASA does not assume any liability arising out of the application or use of any product or circuits described herein. Nordic Semiconductor ASA does not give any representations or warranties, expressed or implied, as to the accuracy or completeness of such information and shall have no liability for the consequences of use of such information. If there are any discrepancies, ambiguities or conflicts in Nordic Semiconductors documentation, the Product Specification prevails. Nordic Semiconductor ASA reserves the right to make corrections, enhancements, and other changes to this document without notice. Life support applications Nordic Semiconductor products are not designed for use in life support appliances, devices, or systems where malfunction of these products can reasonably be expected to result in personal injury. Nordic Semiconductor ASA customers using or selling these products for use in such applications do so at their own risk and agree to fully indemnify Nordic Semiconductor ASA for any damages resulting from such improper use or sale. RoHS and REACH statement Complete hazardous substance reports, material composition reports and latest version of Nordic's REACH statement can be found on our website www.nordicsemi.com. All trademarks, service marks, trade names, product names, and logos appearing in this documentation are the property of their respective owners. Trademarks Copyright notice 2019 Nordic Semiconductor ASA. All rights are reserved. Reproduction in whole or in part is prohibited without the prior written permission of the copyright holder. 4418_1336 v1.2 46
1 2 | 08. Internal photos | Internal Photos | 1.21 MiB | January 28 2020 / April 27 2020 | delayed release |
1 2 | 07. External photos | External Photos | 897.37 KiB | January 28 2020 / April 27 2020 | delayed release |
1 2 | 01. Agent letter thingy91 | Cover Letter(s) | 26.56 KiB | January 28 2020 |
a r agent in the preparation of this application for equipment certification, including the ll documents relating to these matters. resent authorization considers the development of documents on behalf of the clien under his own letterhead and related to the necessary information to be provided on hi f to complete the certification process. Iso hereby certify that neither we nor any party to this application are subject to a denial of
. Federal benefits, which include FCC benefits, pursuant to Section 5301 of the Anti-Drug e Act of 1988, U.S.C. 862 because of conviction for possession or distribution of controlled tance. instances where our authorized agent signs the application for certification on our behal a owledge that all responsibility for complying with the terms and conditions for Certificatio a___ ecified by DEKRA Testing and Certification, S. resides with us. ae 1e--Ub-eeR e ed en e pete ap Keti! Aas-Johansen Application Engineer Nordic Semiconductor ASA
+47 72898900 ketil.aas-johansen@ nordicsemi.no Date: 2019 08 07 DEKRA Testing and Certification S.A U Parque Tecnolgico de Andalucia C/ Severo Ochoa 2 & 6 29590 Campanillas Malaga, Espafia Ref: Agent letter for FCC ID: 2ANPOTHINGY91 Nordic Semiconductor ASA, Otto Nielsens vei 12 7052 Trondheim, Norway, DEKRA Testing and Certification, Parque Tecnolog co de Andaluc a C/ Severo Ochoa n 2 29590 Campanil as Malaga, Spain WALT La e-mail. kamal.seddik @dekra com signing of a The p PTAC}
behal OTe) US PN eI) Toh) eg ckn ssp SEMICONDUCTOR
1 2 | 10. EMC Test Set UP 60433REM.002 v2 | Test Setup Photos | 440.57 KiB | January 28 2020 / April 27 2020 | delayed release |
1 2 | 12. RF Test Set UP 60433RRF003 | Test Setup Photos | 1015.62 KiB | January 28 2020 / April 27 2020 | delayed release |
1 2 | 14. RF Test Set UP Colocation 60433RRF004 | Test Setup Photos | 592.41 KiB | January 28 2020 / April 27 2020 | delayed release |
1 2 | 01. Confidentiality request Thingy91 | Cover Letter(s) | 29.95 KiB | January 27 2020 / January 28 2020 |
identiality request for FCC | [oer AON ee may concern:
0 0.457(d)(1)(ii) and 0.459 of the Com ions Rules (47 C.F.R.) and 552 (b)(4) of the Freedom tion Act, Nordic Semiconductor ASA hereby requests that a part of the subject FCC application idential to avoid release of sensitive information of the product to the public. oduct stated above, we request that the following information be withheld from public disclose Type of Confidentiality Requested eat oUt aD) Puen Block Diagrams Se aera arate) PABST aI) OTF mad are els) PE aC) oreo ret Ue Oe eCiy UUs Parts List & Placement/BOM eeu ere Tune-Up Procedure mare) (Base PTH eu Ue}
prey aucuu Beene) PES] aI) ere em Uere|
Permanent Confidentialit The above materials contain trade secrets and proprietary information not customarily released to the public. BT -Me si) e) ode ste eict e-MO lM USS MEET CMI MMO Uno CU Mn LOLS Soe ea ComeL eevee Clio Short-Term Confidentiality:
We hereby request short-term confidentiality for the product stated above to avoid premature release of sensitive information prior to marketing or release of the product to the pul atc cr-tt Mell CROC M CULO -U-LIN Cl EW eee ee CRE ULC oO 90 days from grant date marked oO 135 days from grant date marked im 180 days from grant date marked 4]
Specific date:
We are also aware that we are responsible to notify DEKRA in the event information regarding the product o the product is made available to the public. DEKRA will then release the documents listed above for pu disclosure pursuant to FCC Public Notice DA 04-1705. Sincere!
Aas/Johansen Application Engineer Oreiiet- Ul Nordic Semiconductor ASA Telephone: +47 72898900 ketil.aas-johansen @ nordicsemi.no DEKRA Testing and Certification, Parque Tecnoldgico de Andalucia C/ Severo Ochoa 2 & 6 Plo ROr tans ec) Malaga, Espafia SEMICONDUCTOR Pursuant t of Informa be held co eed De od
frequency | equipment class | purpose | ||
---|---|---|---|---|
1 | 2020-01-28 | JBP - Part 15 Class B Computing Device Peripheral | Original Equipment | |
2 | 2402 ~ 2480 | DTS - Digital Transmission System |
app s | Applicant Information | |||||
---|---|---|---|---|---|---|
1 2 | Effective |
2020-01-28
|
||||
1 2 | Applicant's complete, legal business name |
Nordic Semiconductor ASA
|
||||
1 2 | FCC Registration Number (FRN) |
0026827089
|
||||
1 2 | Physical Address |
Otto Nielsens vei 12
|
||||
1 2 |
Trondheim, N/A
|
|||||
1 2 |
Norway
|
|||||
app s | TCB Information | |||||
1 2 | TCB Application Email Address |
a******@dekra.com
|
||||
1 2 | TCB Scope |
A1: Low Power Transmitters below 1 GHz (except Spread Spectrum), Unintentional Radiators, EAS (Part 11) & Consumer ISM devices
|
||||
1 2 |
A4: UNII devices & low power transmitters using spread spectrum techniques
|
|||||
app s | FCC ID | |||||
1 2 | Grantee Code |
2ANPO
|
||||
1 2 | Equipment Product Code |
THINGY91
|
||||
app s | Person at the applicant's address to receive grant or for contact | |||||
1 2 | Name |
K****** A****
|
||||
1 2 | Title |
Application Engineer
|
||||
1 2 | Telephone Number |
+4772********
|
||||
1 2 | Fax Number |
+4772********
|
||||
1 2 |
k******@nordicsemi.no
|
|||||
app s | Technical Contact | |||||
n/a | ||||||
app s | Non Technical Contact | |||||
n/a | ||||||
app s | Confidentiality (long or short term) | |||||
1 2 | Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | Yes | ||||
1 2 | Long-Term Confidentiality Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | Yes | ||||
1 2 | If so, specify the short-term confidentiality release date (MM/DD/YYYY format) | 04/27/2020 | ||||
1 2 | 04/26/2020 | |||||
if no date is supplied, the release date will be set to 45 calendar days past the date of grant. | ||||||
app s | Cognitive Radio & Software Defined Radio, Class, etc | |||||
1 2 | Is this application for software defined/cognitive radio authorization? | No | ||||
1 2 | Equipment Class | JBP - Part 15 Class B Computing Device Peripheral | ||||
1 2 | DTS - Digital Transmission System | |||||
1 2 | Description of product as it is marketed: (NOTE: This text will appear below the equipment class on the grant) | Thingy 91 | ||||
1 2 | Related OET KnowledgeDataBase Inquiry: Is there a KDB inquiry associated with this application? | No | ||||
1 2 | Modular Equipment Type | Does not apply | ||||
1 2 | Purpose / Application is for | Original Equipment | ||||
1 2 | Composite Equipment: Is the equipment in this application a composite device subject to an additional equipment authorization? | Yes | ||||
1 2 | Related Equipment: Is the equipment in this application part of a system that operates with, or is marketed with, another device that requires an equipment authorization? | No | ||||
1 2 | Grant Comments | Output power is conducted. This device is approved for mobile and fixed use with respect to RF exposure compliance. The antenna of thistransmitter must provide a separation distance of at least 20 cm from all persons. Multi-transmitter, supporting simultaneous transmission, configurations have been evaluated as described in this filling. Other multi-transmitter configurations have not been evaluated and shall be evaluated according to KDB Publication 447498 and §2.947(f), §15.31(h) and §15.31(k) composite system and §2.1 terms and concepts. | ||||
1 2 | Is there an equipment authorization waiver associated with this application? | No | ||||
1 2 | If there is an equipment authorization waiver associated with this application, has the associated waiver been approved and all information uploaded? | No | ||||
app s | Test Firm Name and Contact Information | |||||
1 2 | Firm Name |
DEKRA Testing and Certification, S.A.U.
|
||||
1 2 | Name |
F**** C****
|
||||
1 2 | Telephone Number |
34-95********
|
||||
1 2 | Fax Number |
34-95********
|
||||
1 2 |
f******@dekra.com
|
|||||
Equipment Specifications | |||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
1 | 1 | 15B | CC | ||||||||||||||||||||||||||||||||||||||
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
2 | 1 | 15C | CC | 2402.00000000 | 2480.00000000 | 0.0038000 |
some individual PII (Personally Identifiable Information) available on the public forms may be redacted, original source may include additional details
This product uses the FCC Data API but is not endorsed or certified by the FCC