P2 Datasheet

Functional description

Overview

The P2 is a SMD module with a microcontroller and Wi-Fi networking. The form-factor is the same as the P1, but the P2 supports 2.4 GHz and 5 GHz Wi-Fi, BLE, and has much larger RAM and flash that can support larger applications.

Features

• 802.11a/b/g/n Wi-Fi, 2.4 GHz and 5 GHz
  • Integrated PCB antenna
  • Integrated U.FL connector for external antenna
  • Integrated RF switch
• BLE 5 using same antenna as Wi-Fi
• Realtek RTL8721DM MCU
  • ARM Cortex M23 CPU, 200 MHz
• 2048 KB (2 MB) user application maximum size
• 2 MB flash file system
• FCC, IC, and CE certified

Interfaces

Block Diagram

RF

• The P2 includes an on-module PCB trace antenna and a U.FL connector that allows the user to connect an external antenna.
• The antenna is selected in software. The default is the PCB trace antenna.
• The area surrounding the PCB antenna on the carrier PCB should be free of ground planes and signal traces for maximum Wi-Fi performance when using the trace antenna.
• Device operation in the 5150-5250 MHz band is only for indoor use to reduce the potential for harmful interference to co-channel mobile satellite systems.

FCC Approved Antennas

SWD/JTAG

The P2 module supports programming and debugging use SWD (Serial Wire Debug) on pins D6 and D7.

When the bootloader starts, for a brief period of time a weak pull-up is applied to pin D7 and pull-down to pin D6 to detect whether a SWD debugger is attached. After boot, you can use these pins for regular GPIO, but beware of a possible GPIO state change caused by the pull-up or pull-down when using these pins as output.

Note that SWD is shared with GPIO pins D6 and D7, and by default SWD is only enabled while the bootloader is running, immediately at boot, and when in DFU mode (blinking yellow). Only Debug builds in Particle Workbench have SWD enabled in when user firmware is running.

Memory Map

Flash Layout Overview

• The location of the user binary is dependent on the size of the user binary and is not flashed to a fixed location.

• Do not chip erase the RTL872x under any circumstances! Also do not flash anything to address 0 (prebootloader-mbr). The prebootloader-mbr is factory configured for your specific device with the private keys necessary for secure boot. If you erase or overwrite this portion of the flash you will not be able to program or use the device again.

DCT Layout

[This information is from the P1, and is likely to remain the same, but is subject to change.]

The DCT area of flash memory has been mapped to a separate DFU media device so that we can incrementally update the application data. This allows one item (say, server public key) to be updated without erasing the other items.

DCT layout in release/stable found here in firmware.

Note: Writing 0xFF to offset 34 (DEFAULT) or 3106 (ALTERNATE) will cause the device to re-generate a new private key on the next boot. Alternate keys are currently unsupported on the P1 but are used on the Electron as UDP/ECC keys. You should not need to use this feature unless your keys are corrupted.

// Regenerate Default Keys
echo -en "\xFF" > fillbyte && dfu-util -d 2b04:d00a -a 1 -s 34 -D fillbyte
// Regenerate Alternate Keys
echo -en "\xFF" > fillbyte && dfu-util -d 2b04:d00a -a 1 -s 3106 -D fillbyte

Pin and button definition

Pin markings

GPIO and port listing

ADC (Analog to Digital Converter)

The P2 supports six ADC inputs.

• ADC inputs are single-ended and limited to 0 to 3.3V
• Resolution is 12 bits

UART serial

The P2 supports three UART serial interfaces.

• The UART pins are 3.3V and must not be connected directly to a RS-232C port or to a 5V TTL serial port
• Hardware flow control is optional; if not used then the RTS and CTS pins can be used as regular GPIO
• Serial1 uses the RTL872x UART_LOG peripheral
• Serial2 uses the RTL872x HS_UART0 peripheral
• Serial3 uses the RTL872x LP_UART peripheral
• Supported baud rates: 110, 300, 600, 1200, 9600, 14400, 19200, 28800, 38400, 57600, 76800, 115200, 128000, 153600, 230400, 500000, 921600, 1000000, 1382400, 1444400, 1500000, 1843200, 2000000, 2100000, 2764800, 3000000, 3250000, 3692300, 3750000, 4000000, 6000000

SPI

The P2 supports two SPI (serial peripheral interconnect) ports.

• The SPI port is 3.3V and must not be connected directly to devices that drive MISO at 5V
• If not using a SPI port, its pins can be used as GPIO
• Any pins can be used as the SPI chip select
• Multiple devices can generally share a single SPI port
• SPI uses the RTL872x SPI1 peripheral (25 MHz maximum speed)
• SPI1 uses the RTL872x SPI0 peripheral (50 MHz maximum speed)

I2C

The P2 supports one I2C (two-wire serial interface) port.

• The I2C port is 3.3V and must not be connected directly a 5V I2C bus
• Maximum bus speed is 400 kHz
• External pull-up resistors are required for I2C
• If not using I2C, pins D0 and D1 can be used as GPIO or analog input.

PWM

The P2 supports PWM (pulse-width modulation) on the following pins:

All available PWM pins on the P2 share a single timer. This means that they must all share a single frequency, but can have different duty cycles.

USB

The P2 supports a USB interface for programming the device and for USB serial (CDC) communications. The module itself does not contain a USB connector; you typically add a micro USB or USB C connector on your base board. It is optional but recommended.

RGB LED

The P2 supports an external common anode RGB LED.

One common LED that meets the requirements is the Cree CLMVC-FKA-CL1D1L71BB7C3C3 which is inexpensive and easily procured. You need to add three current limiting resistors. With this LED, we typically use 1K ohm current limiting resistors. These are much larger than necessary. They make the LED less blinding but still provide sufficient current to light the LEDs. If you want maximum brightness you should use the calculated values - 33 ohm on red, and 66 ohm on green and blue.

A detailed explanation of different color codes of the RGB system LED can be found here.

The use of the RGB LED is optional, however it is highly recommended as troubleshooting the device without the LED is very difficult.

Boot mode pins

These pins have a special function at boot. Beware when using these pins as input as they can trigger special modes in the MCU.

SETUP and RESET button

It is highly recommended that you add MODE (SETUP) and RESET buttons to your base board using momentary switches that connect to GND. These are necessary to change the operating mode of the device, for example to enter listening or DFU mode.

The MODE button does not have a hardware pull-up on it, so you must add an external pull-up (2.2K to 10K) to 3V3, or connect it to 3V3 if not using a button.

The RST pin does have an internal weak pull-up, but you may want to add external pull-up on that as well, especially if you use an off-board reset button connected by long wires.

BLE (Bluetooth LE)

BLE Central Mode on the P2 and Photon 2 is only supported in Device OS 5.1.0 and later. Earlier versions only supported BLE Peripheral Mode.

Complete module pin listing

Technical specification

Recommended operating conditions

Power consumption

¹The min, and particularly peak, values may consist of very short transients. The typical (typ) values are the best indicator of overall power consumption over time. The peak values indicate the absolute minimum capacity of the power supply necessary, not overall consumption.

Mechanical specifications

Module Dimensions

• P1 module dimensions are: 0.787"(28mm) (W) x 1.102"(20mm) (L) x 0.0787"(2.0mm) (H) +/-0.0039"(0.1mm) (includes metal shielding)
• The P2 should have the same width and length but the height may be slightly different as it has different metal shielding

Recommended PCB land pattern

The P2 can be mounted directly on a carrier PCB with following PCB land pattern:

A P1/P2 part for EAGLE can be found in the Particle EAGLE library.

Recommended solder reflow profile

[This information is from the P1, and is likely to remain the same, but is subject to change.]

Ordering information

P2 modules are available from store.particle.io as cut tape in quantities of 10 each.

Qualification and approvals

• RoHS
• CE
• FCC ID: 2AEMI-P2
• IC: 20127-P2

Product handling

Moisture sensitivity levels

The Moisture Sensitivity Level (MSL) relates to the packaging and handling precautions required. The P1 module is rated level 3. In general, this precaution applies for Photons without headers. When reflowing a P1 directly onto an application PCB, increased moisture levels prior to reflow can damage sensitive electronics on the P1. A bake process to reduce moisture may be required.

For more information regarding moisture sensitivity levels, labeling, storage and drying see the MSL standard see IPC/JEDEC J-STD-020 (can be downloaded from www.jedec.org).

ESD Precautions

The P1 module contains highly sensitive electronic circuitry and is an Electrostatic Sensitive Device (ESD). Handling a P1 module without proper ESD protection may destroy or damage it permanently. Proper ESD handling and packaging procedures must be applied throughout the processing, handling and operation of any application that incorporates P1 modules. ESD precautions should be implemented on the application board where the P1 module is mounted. Failure to observe these precautions can result in severe damage to the P1 module!

Default settings

The P2 module comes pre-programmed with a bootloader and a user application called Tinker. This application works with an iOS and Android app also named Tinker that allows you to very easily toggle digital pins, take analog and digital readings and drive variable PWM outputs.

The bootloader allows you to easily update the user application via several different methods, USB, OTA, Serial Y-Modem, and also internally via the Factory Reset procedure. All of these methods have multiple tools associated with them as well.

You may use the Particle Web IDE to code, compile and flash a user application OTA (Over The Air). Particle Workbench is a full-featured desktop IDE for Windows, Mac, and Linux based on VSCode and supports both cloud-based and local gcc-arm compiles. The Particle CLI provides a command-line interface for cloud-based compiles and flashing code over USB.

Intended applications

The P2 module is intended to be used for Wi-Fi based Internet-of-Things (IoT) applications such as environment, weather, HVAC, equipment, and security monitoring.

The P2 is not certified for use as a wearable device.

Glossary

FCC IC CE Warnings and End Product Labeling Requirements

The FCC, IC, and CE certifications are radio module certifications only. Additional certification will be required for your completed system.

United States (FCC)

Federal Communication Commission Interference Statement 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 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.

FCC Caution: Any changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate this equipment. This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:

1. This device may not cause harmful interference, and
2. This device must accept any interference received, including interference that may cause undesired operation.

FCC Radiation Exposure Statement: This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment. This transmitter module must not be co-located or operating in conjunction with any other antenna or transmitter. This End equipment should be installed and operated with a minimum distance of 20 centimeters between the radiator and your body.

IMPORTANT NOTE: In the event that these conditions can not be met (for example certain laptop configurations or co-location with another transmitter), then the FCC authorization is no longer considered valid and the FCC ID can not be used on the final product. In these circumstances, the OEM integrator will be responsible for re-evaluating the end product (including the transmitter) and obtaining a separate FCC authorization.

End Product Labeling The final end product must be labeled in a visible area with the following:

Contains FCC ID: 2AEMI-P2

Manual Information to the End User The OEM integrator has to be aware not to provide information to the end user regarding how to install or remove this RF module in the user’s manual of the end product which integrates this module.

Canada (IC)

Canada Statement This device complies with Industry Canada’s licence-exempt RSSs. 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.

Le présent appareil est conforme aux CNR d’Industrie Canada applicables aux appareils radio exempts de licence.

L’exploitation est autorisée aux deux conditions suivantes:

1. l’appareil ne doit pas produire de brouillage;
2. l’utilisateur de l’appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d’en compromettre le fonctionnement.

Caution Exposure: This device meets the exemption from the routine evaluation limits in section 2.5 of RSS102 and users can obtain Canadian information on RF exposure and compliance. Le dispositif répond à l'exemption des limites d'évaluation de routine dans la section 2.5 de RSS102 et les utilisateurs peuvent obtenir des renseignements canadiens sur l'exposition aux RF et le respect.

The final end product must be labelled in a visible area with the following: The Industry Canada certification label of a module shall be clearly visible at all times when installed in the host device, otherwise the host device must be labelled to display the Industry Canada certification number of the module, preceded by the words “Contains transmitter module”, or the word “Contains”, or similar wording expressing the same meaning, as follows:

Contains transmitter module IC: 20127-P2

This End equipment should be installed and operated with a minimum distance of 20 centimeters between the radiator and your body. Cet équipement devrait être installé et actionné avec une distance minimum de 20 centimètres entre le radiateur et votre corps.

The end user manual shall include all required regulatory information/warning as shown in this manual.

European Union (CE)

We, Particle Industries,Inc, declare under our sole responsibility that the product, P2, to which this declaration relates, is in conformity with RED Directive 2014/53/EU and (EU) 2015/863 RoHS Directive 2011/65/EU (Recast).

The full text of the EU declaration of conformity is available at the followingInternet address: https://www.particle.io/

Radiation Exposure Statement: This equipment complies with radiation exposure limits set forth for an uncontrolled environment.

The operating frequency bands and the maximum transmitted power limit are listed below:

• BLE 2402-2480MHz 10dBm
• WiFi 2.4GHz band 2412-2484MHz 20dBm
• WiFi 5GHz band 5180-5825MHz 23dBm

United Kingdom

UKCA Conformity:

Radio Equipment Regulations 2017 (S.I. 2017/1206)

Revision history

D Pin Change (2022-02-25)

The names of pins D9 - D22 have been changed to D8 - D21, eliminating the odd situation where there was previously no pin D8. This prevented being able to use a loop to initialize pins. This should not affect the hardware in any way, but software that used the D pin names instead of their more common names like TX (was D9, now D8) would need to be updated.

Known Errata

Contact

Web

https://www.particle.io

Community Forums

https://community.particle.io

Email

https://support.particle.io