all | frequencies |
|
exhibits | applications |
---|---|---|---|---|
manual |
app s | submitted / available | |||||||
---|---|---|---|---|---|---|---|---|
1 |
|
Users Manual | Users Manual | 2.86 MiB | ||||
1 | Cover Letter(s) | |||||||
1 | External Photos | |||||||
1 | ID Label/Location Info | |||||||
1 | Internal Photos | |||||||
1 | Cover Letter(s) | |||||||
1 | Cover Letter(s) | |||||||
1 | Test Setup Photos | |||||||
1 | Test Report |
1 | Users Manual | Users Manual | 2.86 MiB |
ESP-WROOM-02U Getting Started Guide Version 1.0 Copyright 2017 About This Guide This document takes ESP-LAUNCHER and ESP-WROOM-02U as examples to introduce how to use the ESP8266 SDK. The contents include preparations before compilation, SDK compilation and rmware download. The document is structured as follows. Chapter Title Chapter 1 Overview Chapter 2 Preparing the Hardware Chapter 3 Preparing the Software Chapter 4 Flash Maps Chapter 5 Compiling the SDK Chapter 6 Downloading the Firmware Appendix A Conguring ISSI & MXIC Flash QIO Mode Appendix B Learning Resources Content Introduction to the overall procedure of using the SDK, and familiarization with the HDK, FW and toolkit of the ESP8266. Hardware conguration and setup for programming, illustrated with two examples, ESP-LAUNCHER and ESP-WROOM-02U. Presentation of the non-OS SDK and RTOS SDK. Information on the tools for compiling the SDK and downloading the rmware. Addresses and layout specications for downloading the rmware to ash memory. Explanation of the OTA and non-OTA rmware. Introductions on how to compiling the SDK using the relevant tools. Introductions on how to download the rmware with download tools. Introduction to ISSI & MXIC Flash QIO mode. List of ESP8266-related must-read documents and must-have resources. Release Notes Date 2017.11 Version Release notes V1.0 First release. Table of Contents 1. Overview 1.3.1. Non-OS SDK 1.3.2. RTOS SDK 1.1. Procedure Overview 1.2. ESP8266 HDK 1.3. ESP8266 SDK
................................................................................................................................ .................................................................................................................. ........................................................................................................................... ........................................................................................................................... ................................................................................................................ ................................................................................................................... ............................................................................................................................. ........................................................................................................................ ...................................................................................................................... ............................................................................................. ................................................................................................. 1.4. ESP8266 FW 1.5. ESP8266 Toolkit 1.5.1. Compiler 1.5.2. Firmware Download Tool 1.5.3. Serial Port Debug Tool 1 1 1 2 2 2 2 3 3 3 3 2. Preparing the Hardware 2.1. ESP-LAUNCHER 2.2. ESP-WROOM-02U
........................................................................................................ ....................................................................................................................... .................................................................................................................... 5 5 6 3. Preparing the Software 3.1. Non-OS SDK 3.2. RTOS SDK 3.3. ESP8266 Toolkit 3.3.1. Compiler 3.3.2. Firmware Download Tool
.......................................................................................................... ............................................................................................................................. ................................................................................................................................ ...................................................................................................................... .................................................................................................................... ........................................................................................... 8 8 8 10 10 12 4. Flash Maps 4.1. Non-OTA 4.1.1. Flash Map 4.1.2. Download Addresses
........................................................................................................................... ................................................................................................................................. .................................................................................................................. ................................................................................................. .......................................................................................................................... .................................................................................................................. ................................................................................................. 4.2.1. Flash Map 4.2.2. Download Addresses 13 14 14 15 15 15 16 4.2. OTA Firmware 5. Compiling the SDK 5.1. Preparations
.............................................................................................................. ............................................................................................................................ .................................................................................................. 17 17 17 5.1.1. Modifying SDK Files 5.2. Compilation 5.1.2. Downloading SDK Files
.............................................................................................. ............................................................................................................................. ................................... ................................................ 5.2.1. Compile ESP8266_NONOS_SDK_v0.9.5 and Later Versions 5.2.2. ESP8266_NONOS_SDK_v0.9.4 and Earlier Versions 18 19 19 20 6. Downloading the Firmware 6.1. Download Procedure 6.2. Check Log File 6.2.1. ESP8266 IOT Demo 6.2.2. ESP8266 AT
................................................................................................. .............................................................................................................. ........................................................................................................................ ................................................................................................... ............................................................................................................... ............................................................................. ..................................................................... ................................................................ ............................................................................................ 6.3.1. Conguration of RF InitCong Options 6.3.2. Conguration of RF InitCong Parameters 6.3.3. Conguration Examples 21 21 23 23 24 24 25 26 28 6.3. Conguration of RF initialization (Optional) A. AppendixConguring ISSI & MXIC Flash QIO Mode
...................................................... 30 B. AppendixLearning Resources B.1. Must-Read Documents B.2. Must-Have Resources
......................................................................................... ........................................................................................................... ............................................................................................................. 31 31 32 1. 1. Overview Overview 1.1. Procedure Overview Figure 1-1 shows the overall procedure of the SDK compilation. Chapter 3. Preparing the Software Chapter 2. Preparing the Hardware Tool Download SDK Download Chapter 4. Flash Map ESP-WROOM-02 ESP-LAUNCHER Compiler ESP8266 SDK Chapter 5. Compiling the SDK Tool Download ESP8266 FW ESP8266 HDK ESP8266 Toolkit Chapter 6. Downloading the Firmware Figure 1-1 Procedure Overview 1.2. ESP8266 HDK The ESP8266 HDK (Hardware Development Kit) includes the chipESP8266EX, the moduleESP-WROOM-02U and the development boardESP-LAUNCHER. Users can download the pre-compiled rmware using ESP-WROOM-02U or ESP-LAUNCHER. Notes:
If users use other development boards or modules that integrate ESP8266EX, please use the development rmware provided by the corresponding manufacturers. If users would like to purchase ESP-WROOM-02U or ESP-LAUNCHER, please visit Espressifs ofcial online store at: https://espressif.taobao.com, Espressif
! /331 2017.11
!
!
1. Overview 1.3. ESP8266 SDK The ESP8266 Software Development Kit (SDK) is an Internet of Things (IoT) application development platform developed by Espressif for developers. It includes such examples of application development as Smart Lights and Smart Plugs. Depending on whether they are based on an operating system (OS), SDKs can be categorized into two types: Non-OS SDK and RTOS SDK. 1.3.1. Non-OS SDK Non-OS SDK is not based on an operating system. It supports the compilation of IOT_Demo and AT commands. Non-OS SDK uses timers and callbacks as the main way to perform various functions such as nested events and functions triggered by certain conditions. Non-OS SDK uses the espconn network interface; users need to develop their software according to usage rules of the espconn interface. 1.3.2. RTOS SDK RTOS SDK is based on FreeRTOS, open-source software development on Github. The FreeRTOS SDK is based on FreeRTOS , a multi-tasking OS. Users can use standard interfaces to realize resource management, recycling operations, execution delays, inter-task messaging and synchronization, and other task-oriented process design approaches. For the specics of interface methods, please refer to the ofcial website of FreeRTOS or USING THE FreeRTOS REAL TIME KERNELA Practical Guide The network operation interface in RTOS SDK is the standard lwIP API. RTOS SDK provides a package which enables a BSD Socket API interface. Users can directly use the socket API to develop software applications; and port to ESP8266 other applications from other platforms using the socket API, effectively reducing the learning costs arising from switching platforms. RTOS SDK introduces cJSON library whose functions make it easier to parse JSON packets. RTOS is compatible with non-OS SDK in Wi-Fi interfaces, SmartCong interfaces, Sniffer related interfaces, system interfaces, timer interfaces, FOTA interfaces and peripheral driver interfaces, but does not support AT implementation. 1.4. ESP8266 FW ESP8266 FW (Firmware) has been provided in binary format les (.BIN) that can be downloaded directly to the HDK. Users can choose between Over-The-Air (OTA) and non-
OTA rmware. For detailed information, please refer to Table 1-1. Espressif
! /332 2017.11
!
1. Overview Table 1-1. ESP8266 FW Binaries Compulsory or optional Description Non-OTA OTA master_device_key.bin Optional esp_init_data_default.bin Compulsory blank.bin Compulsory Users can apply for it from Espressif Cloud to get Espressif Cloud service. Default system parameters provided in SDK. Default system parameters provided in SDK. eagle.flash.bin Compulsory Main program compiled from SDK. eagle.irom0text.bin Compulsory Main program compiled from SDK. user1.bin user2.bin Compulsory for rst usage. Used in rmware upgrade. Main program compiled from SDK. Main program compiled from SDK. Notes:
For the contents of SDK, please refer to Chapter 3, "Preparing the Software". For SDK compilation, please refer to Chapter 5, "Compiling the SDK". For the addresses of binaries in the ash, please refer to Chapter 4, "Flash Maps". 1.5. ESP8266 Toolkit 1.5.1. Compiler Linux OS is required to compile the ESP8266 SDK. When using Windows OS, we recommend VirtualBox as the virtual machine for ESP8266. In order to simplify the compilation procedure, we have installed the compiling tools on the virtual machine. Users can directly compile the ESP8266 SDK by importing the ESP8266 compiler (OVA image) into the virtual machine. 1.5.2. Firmware Download Tool The ESP8266 DOWNLOAD TOOL is the ofcial rmware download tool developed by Espressif. Users can download multiple binaries to the SPI Flash of the ESP8266 mother board (ESP-LAUNCHER or ESP-WROOM-02U) at the same time according to the actual compilation mode and ash size. 1.5.3. Serial Port Debug Tool The serial port debug tool can be used to directly communicate with the ESP8266 module over a standard RS-232 port. For PCs that do not have a physical serial port, a virtual com port (USB-to-serial converter) can be used. Espressif
! /333 2017.11
!
1. Overview Users may directly input commands into the terminal and view or record responses in real time. Note:
We recommend CoolTerm (for Windows and Mac OS) and Minicom (for Linux OS) as the serial port debug tool. Espressif
! /334 2017.11
!
2. Preparing the Hardware 2. Preparing the Hardware Depending on whether the ESP-LAUNCHER or the ESP-WROOM-02U is used, users will need either of the hardware mentioned in Table 2-1 below:
Table 2-1. Hardware Preparations ESP-LAUNCHER ESP-WROOM-02U 1 ESP-LAUNCHER 1 USB cable OR 1 ESP-WROOM-02U 1 USB-to-TTL converter (FT232R recommended) 6 Dupont lines 1 soldering tool suite 1 PC with pre-installed Windows OS Notice:
The ESP8266 Wi-Fi module needs a 3.3V power supply and may draw a minimum current of 500 mA. 2.1. ESP-LAUNCHER 1. Connect PC to the USB-UART interface of ESP-LAUNCHER using the USB cable. 2. Set ESP-LAUNCHER to download mode. Steps Slide Power Switch towards the outer side as the gure on the right shows. Slide GPIO0 Control towards the inner side to enable ESP-LAUNCHER's download mode. Notice:
J82 must be shorted by a jumper, otherwise code cannot be downloaded to the board. Result GPIO0 Control Chip Switch 1 USB-UART USB-serial Cable Power Switch J82 1 3. Connect the USB-to-TTL converter to the PC. Note:
Make sure that the proper driver for the USB-to-TTL converter is installed and recognized by the PC. 4. Power on ESP-LAUNCHER by sliding the Power Switch towards the inner side. Espressif
! /!5 33 2017.11
!
!
2. Preparing the Hardware 5. Power on the chip by sliding the Chip Switch towards the outer side. 6. Download rmware to ash with the ESP8266 DOWNLOAD TOOL. Note:
On how to download rmware, please refer to Chapter 4, "Flash Map" and Chapter 6, "Downloading the Firmware". 7. After downloading, slide the GPIO0 Control towards the outer side to enable ESP-
LAUNCHER's working mode. 8. Power on the chip again with the Chip Switch and the chip will read and run programs from the ash. For more information on the ESP-LAUNCHER hardware, please refer to ESP8266 System Description. 2.2. ESP-WROOM-02U 1. Lead out the pins of the ESP-WROOM-02U, as shown in Table 2-2. Pin EN 3V3 IO15 IO0 GND RXD TXD Table 2-2. ESP-WROOM-02U Pins Pin status Pull up 3.3V power supply (VDD) Pull down UART download: pull down;
Flash boot: oating/pull up GND Receive-end in UART download Transmit-end in UART download; oating/pull up 2. Connect ESP-WROOM-02U to the USB-to-TTL converter, using Dupont lines, as shown in Figure 2-1. Espressif
! /!6 33 2017.11
!
2. Preparing the Hardware ESP-WROOM-02 3V3 EN RXD TXD GND IO15 IO0 USB-to-TTL converter 3V3 TXD RXD GND PC Figure 2-1. ESP-WROOM-02U Download Mode 3. Connect the USB-to-TTL converter to the PC. 4. Download rmware to ash with the ESP8266 DOWNLOAD TOOL. Note:
On how to download rmware, please refer to Chapter 4, "Flash Maps" and Chapter 6, "Downloading the Firmware". 5. After downloading, switch ESP-WROOM-02U to working mode. Set IO0 as oating or pull-up. 6. Power on ESP-LAUNCHER again and the chip will read and run programs from the ash. Notes:
IO0 is an internal pull-up pin. For more information on ESP-WROOM-02U hardware, please refer to ESP8266 System Description and ESP-WROOM-02 Datasheet. Espressif
! /!7 33 2017.11
!
!
!
3. Preparing the Software 3. Preparing the Software 3.1. Non-OS SDK Users can download the non-OS SDK (including application examples) from:
http://www.espressif.com/en/support/download/sdks-demos?
keys=&eld_type_tid%5B%5D=14. Figure 3-1 shows the directory structure of the non-OS SDK. Figure 3-1. Non-OS SDK Directory Structure bin: compiled binaries to be downloaded directly into the flash. documents: SDK-related documents or links. driver_lib: library les that drive peripherals, such as UART, I2C and GPIO. examples: sample codes for secondary development, for example, IoT Demo. include: header les pre-installed in SDK. The les contain relevant API functions and other macro denitions. Users do not need to modify them. ld: linker scripts. We suggest users not modifying them without any specic reasons. lib: library les provided in SDK. tools: tools needed for compiling binaries. Users do not need to modify them. 3.2. RTOS SDK Users can download RTOS SDK and its application examples (ESP8266_IOT_PLATFORM) from:
RTOS SDK https://github.com/espressif/ESP8266_RTOS_SDK Espressif
! /!8 33 2017.11
!
!
ESP8266_IOT_PLATFORM https://github.com/espressif/ESP8266_IOT_PLATFORM Table 3-2 shows the directory structure of the RTOS SDK. 3. Preparing the Software Figure 3-2. RTOS SDK Directory Structure bin: boot and initialization rmware. documents: ESP8266_RTOS_SDK les. driver_lib: sample codes of drivers. examples: sample codes for Espressifs application programs.
- openssl_demo: sample codes of the openssl API function.
- project_template: sample codes of project templates.
- smart_config: sample codes of SmartCong.
- spiffs_test: sample codes of the spiffs le system function.
- websocket_demo: sample codes of web socket. include: header les of ESP8266_RTOS_SDK, including software interfaces and macro functions for users to use. ld: link les used when compiling; users do not need to modify them. lib: library le of ESP8266_RTOS_SDK. third_party: third-party library of Espressifs open-source codes, currently including free RTOS, JSON, lwIP, mbedTLS, noPoll, OpenSSL, spiffs, and SSL. tools: tools needed for compiling binaries; users do not need to modify them. Espressif
! /!9 33 2017.11
!
!
3. Preparing the Software 3.3. ESP8266 Toolkit 3.3.1. Compiler Please download VirtualBox from: https://www.virtualbox.org/wiki/Downloads. Note:
Please choose the right version of VirtualBox according to the host machine's OS. Please download the compiler ESP8266_lubuntu_20141021.ova from:
http://downloads.espressif.com/FB/ESP8266_GCC.zip Steps Results 1. Start Windows OS and install the virtual machine. Double-click VirtualBox-5.0.16-105871-Win.exe and install VirtualBox. Note:
VirtualBox has different versions. We are using Windows V.5.0.16 as an example. Double-click Oracle VM VirtualBox.exe to run the program, and the system will show the main menu . Tip:
The ESP8266 virtual machine takes up much space (memory). Please reserve enough space for it. 2. Import the image le. Espressif
/!10 33 2017.11
!
!
!
Steps Results 3. Preparing the Software Select File > Import Appliance, and a dialog box will show up . Select the image le to import, for example, C:
\ESP8266_lubuntu_20141021.ova, and click Next. Click Import to conrm the settings. 3. Create a shared folder. Create a new folder named D:
\VM\share. Select Machine > Settings >
Shared Folders, and a dialog box will show up . Select the shared folder in Machine Folders, for example, D:\VM\share. 4. Run the virtual machine. Espressif
/!11 33 2017.11
!
!
Steps Results 3. Preparing the Software After importing, a virtual machine named ESP8266_lubuntu shows up
. Double-click ESP8266_lubuntu or Start to run the virtual machine. The system shows the ESP8266 virtual machine . If a dialog box like the one below shows up, please enter the password: espressif. 3.3.2. Firmware Download Tool Please download the ESP8266 DOWNLOAD TOOL from:
http://www.espressif.com/support/download/other-tools. Espressif
/!12 33 2017.11
!
!
!
4. 4. Flash Maps Flash Maps This chapter provides the ash maps for OTA rmware and non-OTA rmware in ash memories with a different capacity. Users can modify the map as needed. Figure 4-1 shows the ash maps for the two different types of rmware. Non-FOTA Partition 1 Partition 2 System Program eagle.ash.bin User Data System Program eagle.irom0text.bin User Data User Param master_device_key.bin FOTA Partition 1 Partition 2 System Param (16 kB) blank.bin esp_init_data_default.bin System Program
1.bin User Data System Program
2.bin User Data Boot Data User Param master_device_key.bin Reserved Figure 4-1. Flash Maps Note:
For ESP8266 rmware, please refer to Section 1.3, "ESP8266 FW". System Param (16 kB) blank.bin esp_init_data_default.bin System Program: this area stores the rmware necessary for the system to run. User Data: If system data do not take up all the ash memory, the remaining area can be used to store user data. User Param: Users can dene the address. In IOT_Demo, the four sectors starting from 0x3C000 are dened as the user parameter area. Users can dene any available address for this area. Espressif
/!13 33 2017.11
!
!
!
4. Flash Maps
- master_device_key.bin: In IOT_Demo, it is located in the third sector of user parameter area. System Param: this area contains the last four sectors of the ash.
- blank.bin: the download address is the second-to-last sector in the ash.
- esp_init_data_default.bin: the download address is the fourth-to-last sector of ash. Boot Data: It is located in Partition 1 of OTA rmware, and stores OTA-related data. Reserved: It is a reserved area in Partition 2 of OTA rmware, corresponding to the Boot data area in Partition 1 of OTA rmware. Notes:
Each sector of the ash is 4 KB. For detailed download addresses, please refer to the following sections.. 4.1. Non-OTA 4.1.1. Flash Map For ash memories with different capacity levels, the storage space of eagle.irom0text.bin is limited. Users can change the limit by modifying ESP8266_NONOS_SDK/ld/
eagle.app.v6.ld. Users can modify the len eld in irom0_0_seg, as shown in Figure 4-2 (red rectangle). The location of irom0.text varies across different versions of SDK. Users must consult the eagle.app.v6.ld le and ensure that they are downloading eagle.irom0.text.bin to the correct offset in the ash. The address in the blue rectangle marks the location of eagle.irom0.text.bin in the ash. Table 4-1 shows the storage limits of eagle.irom0text.bin with different len values. Figure 4-2. Location for irom0.text Table 4-1. Non-OTA Flash Map (unit: KB) Flash capacity 512 1024 eagle.ash.bin eagle.irom0text.bin User data len User/System Param 64 64 240 752 176 176 0x3C000 0xBC000 16 16 Espressif
/!14 33 2017.11
!
!
!
4. Flash Maps User/System Param Flash capacity 2048 4096 8192 16*1024 eagle.ash.bin eagle.irom0text.bin User data len 64 64 64 64 768 768 768 768 176 176 176 176 0xC0000 0xC0000 0xC0000 0xC0000 16 16 16 16 Note:
ESP8266 presently only supports a System Param area of up to 1024 KB. 4.1.2. Download Addresses Table 4-2 lists the download addresses for non-OTA rmware. Table 4-2. Download Address for Non-OTA Firmware (unit: KB) Binaries Download addresses in ash with different capacities 512 1024 2048 4096 8192 16*1024 master_device_key.bin esp_init_data_default.bin 0x7C000 0x3E000 0xFC000 0x1FC000 0x3FC000 0x7FC000 0xFFC000 blank.bin eagle.flash.bin eagle.irom0text.bin Notes:
0x7E000 0xFE000 0x1FE000 0x3FE000 0x7FE000 0xFFE000 0x00000 0x10000 In general, ESP Flash Download Tool can be used to download rmware into ash. But for 8 MB or 16 MB ash, please use esptool instead. 4.2. OTA Firmware 4.2.1. Flash Map Table 4-3 lists the download addresses for the OTA rmware. Table 4-3. OTA Flash Map (unit: KB) Flash capacity boot user1.bin user2.bin User/System Param User data 512 1024 4 4 236 492 236 492 16 16 0 0 Espressif
/!15 33 2017.11
!
!
4. Flash Maps Flash capacity boot user1.bin user2.bin User/System Param User data 2048 (Partition 1 = 512) 2048 (Partition 1 = 1024) 4096 (Partition 1 = 512) 4096 (Partition 1 = 1024) 8192 (Partition 1 = 1024) 4 4 4 4 4 16384 (Partition 1 = 1024) 4 492 1004 492 1004 1004 1004 492 1004 492 1004 1004 1004 16 16 16 16 16 16 1024 0 3072 2048 6144 14336 4.2.2. Download Addresses Table 4-4 lists the download addresses for the OTA rmware. Table 4-4. Download Addresses for OTA Firmware (unit: KB) Download addresses in ash with different capacities Binaries 512 1024 2048 4096 8192 16384 512+512 1024+102 4 512+512 1024+1024 1024+1024 1024+1024 master_device_key
.bin esp_init_data _default.bin blank.bin boot.bin user1.bin user2.bin 0x3E000 0x7E000 0x7E000 0xFE000 0x7E000 0xFE000 0xFE000 0xFE000 0x7C000 0xFC000 0x1FC000 0x7E000 0xFE000 0x1FE000 0x3FC000 0x3FE000 0x7FC000 0xFFC000 0x7FE000 0xFFE000 0x00000 0x01000 0x41000 0x81000 0x81000 0x101000 0x81000 0x101000 0x101000 0x101000 Notes:
In general, ESP Flash Download Tool can be used to download rmware into ash. But for 8 MB or 16 MB ash, please use esptool instead. For OTA rmware, users do not need to download user2.bin, but upgrade the rmware via the cloud server. For details on the functional description of OTA rmware, please refer to ESP8266 FOTA Guide. Espressif
/!16 33 2017.11
!
!
5. 5. Compiling the SDK Compiling the SDK Notes:
IoT_Demo as an example. This chapter demonstrates how to compile the SDK by taking ESP8266_NONOS_SDK/examples/
IoT_Demo denes three types of devices, i.e., LIGHT_DEVICE, PLUG_DEVICE and SENSOR_DEVICE in examples>IoT_Demo/include/user_config.h. Users can only congure one device at a time. The default device for conguration is LIGHT_DEVICE. 5.1. Preparations 5.1.1. Modifying SDK Files Note:
Users need to modify the SDK les if using the OTA rmware. 1. Start Windows OS. 2. Modify les in ESP8266_NONOS_SDK/examples/IoT_Demo/include according to the ash map. Modify #define PRIV_PARAM_START_SEC in user_light.h and user_plug.h. Modify #define ESP_PARAM_START_SEC in user_esp_platform.h. Table 5-1 lists the modied values. Table 5-1. Modify the Field Values in the "include" File (unit: kB) Modied values 512 1024 2048 2048 4096 4096 8192 16384
(512+512)
(1024+1024)
(512+512)
(1024+1024)
(1024+1024)
(1024+1024)
-
-
0x7C 0x7D 0x7C 0x7D 0xFC 0xFD 0x7C 0x7D 0xFC 0xFD 0xFC 0xFD 0xFC 0xFD Default value
(512) 0x3C 0x3D Espressif
/!17 33 2017.11
!
!
!
!
5. Compiling the SDK Note:
Users need not modify the SDK les if using a 512-KB ash. 5.1.2. Downloading SDK Files 1. Start Linux OS. 2. Run LXTerminal on the desktop of the virtual machine. 3. Copy the les to be compiled to the shared folder. Steps Results Copy ESP8266_NONOS_SDK folder to the shared directory, for example, C:\VM\share. Copy IoT_Demo folder to C:
\VM\share\ESP8266_NONOS_SDK, as shown in the gure on the right . 4. Download shared directory. Steps Results Execute ./mount.sh. Input the password: espressif. Downloading shared les is completed. Open the shared directory ESP8266_NONOS_SDK in the virtual machine and conrm whether the download has been successful.
-
If successful, the directory contains such les as those in the gure on the right . If not, the directory will be empty, and users will need to go over this step again.
-
Notice:
If users use the RTOS SDK, please continue with the following steps; if use the non-OS SDK, please skip Step 5. 5. Set the variable PATH to point to SDK and binaries. export SDK_PATH=~/Share/ESP8266_RTOS_SDK export BIN_PATH=~/Share/ESP8266_RTOS_SDK/bin Espressif
/!18 33 2017.11
!
!
5. Compiling the SDK Note:
Users can add it to .bashrc le, otherwise Step 5 needs to be repeated each time the compiler is restarted. 5.2. Compilation 5.2.1. Compile ESP8266_NONOS_SDK_v0.9.5 and Later Versions 1. Switch to the /Share/ESP8266_NONOS_SDK/IoT_Demo directory in the terminal. cd /home/esp8266/Share/ESP8266_NONOS_SDK/IoT_Demo
./gen_misc.sh The system shows the following information:
gen_misc.sh version 20150511 Please follow below steps(1-5) to generate specific bin(s):
2. Select the required options as shown in Figure 5-1. FOTA?
Y New version?
N 0 First-time usage?
Y 1 1 N Y 1 1 2 2 2 0 STEP 1: choose boot version
(0=boot_v1.1, 1=boot_v1.2+, 2=none) enter(0/1/2, default 2) STEP 2: choose bin generate
(0=eagle.ash.bin+eagle.irom0text.bin
, 1=user1.bin, 2=user2.bin) enter (0/1/2, default 0) Choose as required 3 STEP 3: choose spi speed
(0=20MHz, 1=26.7MHz, 2=40MHz, 3=80MHz) enter (0/1/2/3, default 2) Choose as required 3 STEP 4: choose spi mode
(0=QIO, 1=QOUT, 2=DIO, 3=DOUT) enter (0/1/2/3, default 0) Choose as required 2 3 4 5 6 STEP 5: choose spi size and map 0= 512KB( 256KB+ 256KB) enter (0/2/3/4/5/6, default 0) Example Option Figure 5-1. Compile SDK N 2 0 0 0 Espressif
/!19 33 2017.11
!
!
!
5. Compiling the SDK Notes:
The sample options are marked in green. Users can select the right options as needed. For OTA and non-OTA rmware, please refer to Section 1.4, "ESP8266 FW". Only sdk_v1.1.0 + boot 1.4 + ash download tool_v1.2 and higher versions support options 5 and 6 in Step 5. After compiling user1.bin, execute make clean rst to clear the temporary les generated by the last compilation, and then compile user2.bin. For the ash map in Step 5, please refer to Chapter 4, "Flash Maps". 3. After compilation, the generated binaries and the addresses in ash are shown as follows:
Generate user1.2048.new.3.bin successfully in folder bin/upgrade. boot.bin------------>0x00000 user1.2048.new.3.bin--->0xSupport boot_v1.2 and +
01000
!!!
Note:
Users can open the /home/esp8266/Share/ESP8266_NONOS_SDK/bin directory and check the compiled binaries. 5.2.2. ESP8266_NONOS_SDK_v0.9.4 and Earlier Versions For ESP8266_NONOS_SDK_v0.9.4 and previous versions, the compilation process is as follows:
1. Execute ./gen_misc_plus.sh 1 to generate user1.bin under the
/ESP8266_NONOS_SDK/bin/upgrade path. 2. Execute make clean to clear previous compilation data. 3. Execute ./gen_misc_plus.sh 2 to generate user2.bin under the
/ESP8266_NONOS_SDK/bin/upgrade path. Note:
ESP8266_NONOS_SDK_v0.7 and earlier are non-OTA rmware. Espressif
/!20 33 2017.11
!
!
6. Downloading the Firmware 6. Downloading the Firmware 6.1. Download Procedure 1. Start Windows OS. 2. Double-click ESP_DOWNLOAD_TOOL.exe to open Flash tool. Figure 6-1. ESP8266 DOWNLOAD TOOLSPIDownload SPIDownload For SPI Flash download. HSPIDownload For HSPI Flash download. RFCong RF initialization Conguration. MutiDownload For multi-mother boards download. Espressif
/!21 33 2017.11
!
!
6. Downloading the Firmware 3. Double-click !
in Download Path Config panel to select the binaries to be downloaded. Set the corresponding download addresses in ADDR. 4. Congure SPIDownload. Note:
The binaries to be downloaded and the corresponding addresses vary with different SPI Flash sizes and actual demands. For details, please refer to Chapter 4, "Flash Maps". Items Table 6-1. SPIDownload Conguration Description SPI FLASH CONFIG CrystalFreq Select the crystal frequency according to the crystal oscillator used. CombineBin Combine the selected binaries into target.bin with the address 0x0000. Default SPI SPEED SPI MODE FLASH SIZE SpiAutoSet DoNotChgBin Set the SPI Flash to the default value. Select SPI read/write speed with the maximum value of 80 MHz. Select SPI mode according to the SPI Flash used. If the ash is Dual SPI, select DIO or DOUT. If the ash is Quad SPI, select DIO or DOUT. Notice:
If ISSI Flash is used, please refer to Appendix, "Congure ISSI & MXIC Flash QIO Mode". Select the ash size according to the ash type. Note:
16Mbit-C1 refers to 1024+1024 ash map and 32Mbit-C1 1024+1024 ash map as well. We recommend not checking SpiAutoSet, but conguring the flash manually as needed. If users select SpiAutoSet, the binaries will be downloaded according to the default ash map. The ash map of 16 Mbit and 32 Mbit will be 512 KByte + 512 KByte. If users select DoNotChgBin, the ash working frequency, mode, and ash map will be based on the conguration when compiling. If users do not select DoNotChgBin, the ash working frequency, mode, and ash map will be dened by the nal conguration of the compiler. Download Panel START STOP MAC Address Click START to start download. When the download completes, FINISH will appear in the green area on the left. Click STOP to stop download. If download is successful, the system will show the MAC addresses of ESP8266 STA and ESP8266 AP. COM PORT Select the actual COM port of ESP8266. Espressif
/!22 33 2017.11
!
!
6. Downloading the Firmware Items Description SPI FLASH CONFIG BAUDRATE Select the baud rate of downloading. The default value is 115200. 5. After downloading, turn GPIO0 Control on ESP-LAUNCHER to the outer side and power the board on to enable the working mode. 6.2. Check Log File After downloading rmware, users can check the log printed in the terminal by using the serial port debug tool. Users need to congure the settings of the serial port debug tool, as follows:
Table 6-2. Serial Port Debug Tool Conguration Items Protocol Serial port. Conguration Description Port number Set the port number according to the connected device. Baud rate The baud rate at which the device is running, related to the crystal oscillator. 69120 (24 M crystal oscillator) 74880 (26 M crystal oscillator) 115200 (40 M crystal oscillator) The ESP8266 AT example supports the baud rate of 115200 by default. Users cannot modify it. The ESP8266 IOT Demo example supports the baud rate of 74880. Users can modify it. Data bit Calibration Flow control 8 None. None. 6.2.1. ESP8266 IOT Demo If users download ESP8266 IOT Demo rmware, the system in working mode will show the initialization information including the SDK version, etc. Finish means the rmware works properly. SDK version:X.X.X(e67da894) IOT VERSION = v1.0.5t45772(a) reset reason: 0 PWM version: 00000003 mode: sta(18:fe:34:a4:8c:a3) + softAP(1a:fe:34:a4:8c:a3) Espressif
/!23 33 2017.11
!
!
6. Downloading the Firmware add if0 add if1 dhcp server start:(ip:192.168.4.1,mask:255.255.255.0,gw:192.168.4.1) bcn 100 finish 6.2.2. ESP8266 AT If users download the ESP8266 AT rmware, or the default rmware in ESP-LAUNCHER or ESP-WROOM-02U, the system in working mode will display Ready at the end. Input command AT in the terminal and the system will return OK, which means that the rmware works properly. Notes:
The baud rate in AT rmware is congured as 115200 manually, however, the default baud rate of ESP8266 is 74880, due to this discrepancy, the system initialization information will be displayed as mojibake. It is a normal phenomenon as long as the system shows Ready at the end. For more information on AT commands, please refer to ESP8266 AT Instruction Set. 6.3. Conguration of RF initialization (Optional) Before downloading binaries to ash, users can modify the RF initialization settings in the RF InitConfig tab. The newly-generated esp_init_data_setting.bin can be downloaded to the ash instead of esp_init_data_default.bin. Users can congure both the options and the parameters of the RF settings. Espressif
/!24 33 2017.11
!
!
6. Downloading the Firmware Figure 6-2. ESP8266 DOWNLOAD TOOL - RF InitCong 6.3.1. Conguration of RF InitCong Options RF InitCong options are listed in the upper part of Figure 6-2. Please refer to Table 6-3 for a description of this conguration. Table 6-3. Conguration of RF InitCong Options Items Description TxTargetPowerCong Users need not congure this. It varies with the options in LowPowerMode. LowPowerMode CrystalFreq Congure the low power mode as required. LowPowerEn: enable low power mode, set a power value for all data rates. PowerLimtEn: set a limit for output power. BackOEn: set backoff value for each data rate. Note:
Users cannot congure LowPowerEn and PowerLimtEn at the same time. Select the crystal oscillator frequency according to the crystal oscillator used. Note:
If a different option is selected when downloading, it will override this conguration. Espressif
/!25 33 2017.11
!
!
!
Items Description 6. Downloading the Firmware TOUT PinConf FreqOset RFInt mode Congure the TOUT pin according to the actual TOUT pin status. We recommend the default value. TOUT_ADC_EN: When the TOUT pin connects to an external circuit, measure the external voltage (0V - 1V) through the internal ADC. TOUT_VDD_EN: When TOUT pin is left oating, measure VDD33 voltage through uint16 system_get_vdd33(void). Notice:
Users cannot congure TOUT_ADC_EN and TOUT_VDD_EN at the same time. When users use TOUT_ADC_EN, they need to input the actual voltage on VDD3P3 pin 3 and pin 4. SetFreqEnable: Set the frequency offset manually.
- PracticalFreqOset: the option is valid when selecting SetFreqEnable. AutoCalEn: Set the frequency offset automatically. Users can select the RF initialization mode:
LoadRFCalParam: During the RF initialization, RF data are loaded directly from the ash without any calibration. It takes about 2 ms and the least initial current. TxPwrCtrl in init: During the RF initialization, only Tx Power calibration will be performed, and other data are loaded from ash. It takes about 20 ms and small initial current. FullRFCal in RFInit: All calibrations are performed during the RF initialization. It takes 200 ms and large initial current. 6.3.2. Conguration of RF InitCong Parameters RF InitConfig parameters are listed in the lower part of Figure 6-2. The description of parameters conguration is shown in Table 6-4. Table 6-4. Conguration of RF InitCong Parameters Description The byte in esp_init_data_setting.bin (0 ~ 127 byte). For example, A = 0 represents Byte 0 in esp_init_data_setting.bin. The item name. Users cannot modify it if marked as Reserved. The item name. Users cannot modify it if marked as Reserved. Data types of conguration items, including unsigned and signed data types. The hexadecimal value of a conguration item. Items A B C D E Notice:
Please do not modify the parameters marked as Reserved. Espressif
/!26 33 2017.11
!
!
The following section introduces how to modify the 112 ~ 114 byte parameters. Figure 6-3 shows the initial conguration. 6. Downloading the Firmware Figure 6-3. 112 114 Byte Parameters Modify the RF Initialization Parameters Byte 114 is used to control THE RF initialization when ESP8266 is powered on. Table 6-5 provides the parameter conguration. Note:
Supported by ESP8266_NONOS_SDK_V1.5.3 and ESP8266_RTOS_SDK_V1.3.0 and higher. Option byte 114 = 0 byte 114 = 1 Table 6-5. Modify RF Initialization Parameters Description Only a VDD33 calibration is performed during the RF initialization. It takes about 2 ms and the least initial current. The default value is 1. VDD33 and TX power calibrations are performed during the RF initialization. It takes about 18 ms and small initial current. byte 114 = 2 The same as when byte 114 = 0. byte 114 = 3 All calibrations are performed during the RF initialization. It takes about 200 ms and large initial current. Correct Frequency Offset Byte 112 and byte 113 relate to the frequency offset correction. Table 6-6 provides the parameter conguration. Note:
Supported by ESP8266_NONOS_SDK_V1.4.0 and ESP8266_RTOS_SDK_V1.3.0 and higher. Table 6-6. Options for Frequency Offset Correction Option bit 0 Description The default value of byte 112 is 0. This bit is of the highest priority. bit 0 = 0: frequency offset cannot be corrected. bit 0 = 1: frequency offset can be corrected. Espressif
/!27 33 2017.11
!
!
!
6. Downloading the Firmware Option bit 1
{bit 3bit 2}
Description The default value of byte 112 is 0. When value = 0, it means that the bbpll is 168 M. Both positive and negative frequency offsets can be corrected. However, this may effect the digital peripheral performance and, therefore, it is not recommended. When value = 1, it means that the bbpll is 160 M. Only the positive frequency offset can be corrected. When value = 0, it means that the chip will track and correct the frequency offset automatically. The initial correction value is 0. When value = 1, it means that the chip is manually programmed to change the frequency offset to that of byte 113, so the chip will not track and correct the frequency offset automatically. When value = 2, it means that the chip will track and correct the frequency offset automatically. The initial correction value is that of byte 113. The default value of byte 113 is 0. 113 byte It is the value when the frequency offset is corrected manually or the initial correction value in frequency tracking. The data type is sign int8, in multiples of 8 kHz. 6.3.3. Conguration Examples The conguration of bytes 112 and 113 depends depends on users' specic needs. We provide some examples below:
1. The module works at ambient temperature, and needs no correction of the frequency offset. Set byte 112 = 0, byte 113 = 0. 2. The module works at ambient temperature and needs no automatic tracking and correction of the frequency offset; yet the frequency offset is large. In this case, a manual correction of the frequency offset is recommended. If the frequency offset is +160 KHz (at ambient temperature), users can set byte 112
= 0x07, byte 113 = (256 - 160/8) = 236 = 0xEC. If the frequency offset is -160 KHz (at ambient temperature), users can set byte 112 =
0x05, byte 113 = 160/8 = 20 = 0x14. This may effect the digital peripheral performance, so we do not recommend it. 3. Applications, such as smart lights, work at a wide temperature range of -40 C to 125 C, and need to track and correct the frequency offset automatically. The frequency offset at ambient temperature is small, so the initial offset correction value is not needed. Set byte 112 = 0x03, byte 113 = 0. Espressif
/!28 33 2017.11
!
!
6. Downloading the Firmware 4. Applications, such as smart lights, work at a wide temperature range of -40 C to 125 C, and need to track and correct the frequency offset automatically. The frequency offset at ambient temperature is large, so the initial offset correction value is needed. If the frequency offset is +160 kHz (at ambient temperature), users can set byte 112
= 0x0B, byte 113 = (256 - 160/8) = 236 = 0xEC. If the frequency offset is -160 kHz (at ambient temperature), users can set byte 112
= 0x09, byte 113 = 160/8 = 20 = 0x14. But this may effect the digital peripheral performance and needs substantive tests, so we do not recommend it. We recommend Example 3. When the conguration of RF initialization is done, click GenInitBin button to generate esp_init_data_setting.bin. In addition, users can click Default button to set the value of frequency offset to default, or click LoadInitBin button to import a binary le for conguration. Espressif
/!29 33 2017.11
!
!
A. AppendixConguring ISSI &
MXIC Flash QIO Mode Appendix A Notice:
Choose DIO or DOUT mode when downloading, otherwise errors may occur. There is no need to modify binaries in DIO or DOUT mode. When using QIO mode of ISSI ash or MXIC ash, users need to modify the rst two bytes in blank.bin, as shown in Table A-1. During initialization, ESP8266 will automatically check the rst two bytes and switch to QIO mode to read ISSI_FLASH or MXIC_FLASH. The structure of blank.bin is shown below:
strcut boot_hdr{
char user_bin:2; //low_bit char boot_status:1;
char to_qio:1;
char reverse:4;
char version:5; //low bit char test_pass_flag:1;
char test_start_flag:1;
char enhance_boot_flag:1;
}
Table A-1. blank.bin Conguration Option Description Without secondary boot loader With secondary boot loader Modify to_qio to 0. Modify use_bin to 0 and to_qio to 0, as well. Modify version according to the current boot version. Example:
If users use the secondary boot_v1.5.bin, please modify the rst two bytes FF FF to F4 E5. Espressif
/!30 33 2017.11
!
!
B. Appendix B AppendixLearning Resources B.1. Must-Read Documents ESP8266EX Datasheet Description: This document introduces the specications of ESP8266EX, including an overview of the features, protocols, technical parameters and applications. It also describes the pin layout, as well as major functional modules integrated in ESP8266EX
(CPU, ash and memory, clock, radio, Wi-Fi, and low-power management). Additionally, it provides descriptions of peripheral interfaces integrated on ESP8266EX, lists the electrical data of ESP8266EX and illustrates the package details of ESP8266EX. ESP8266 Hardware Resources Description: This zip package includes the manufacturing specications of the ESP8266 board and its modules, manufacturing BOM and schematics. ESP8266 Non-OS SDK IoT_Demo Guide Description: This documents provides simple demo implementations of three types of smart devices: Smart Light, Smart Power Plug, and Sensor Device. It also introduces the readers to curl toolkits, functions in LAN and WAN. ESP8266 RTOS SDK Programming Guide Description: This document provides sample codes based on ESP8266_RTOS_SDK, including basic examples, networking protocol examples and advanced examples. ESP8266 AT Command Examples Description: This document introduces some specic examples of how to use Espressif AT commands, including single connection as a TCP client, UDP transmission and transparent transmission, and multiple connection as a TCP server. ESP8266 AT Instruction Set Description: This document provides lists of AT commands based on ESP8266_NONOS_SDK, including user-dened AT commands, basic AT commands, Wi-Fi AT commands and TCP/IP-related AT commands. It also introduces the downloading of AT rmware into ash. ESP8266 Non-OS SDK API Reference Description: This document lists ESP8266_NONOS_SDK APIs, provides an overview of ESP8266_NONOS_SDK and introduces the readers to system APIs, TCP/UDP APIs, mesh APIs, application specic APIs, denitions and data structures, and APIs for peripheral interfacing. ESP8266 RTOS SDK API Reference Espressif
/!31 33 2017.11
!
!
Description: This document lists ESP8266_RTOS_SDK APIs, including functions for Wi-
Fi related APIs, boot APIs, etc. Appendix B FAQ B.2. Must-Have Resources ESP8266 SDKs Description: This webpage provides links to the latest version of ESP8266 SDK and the older ones. RTOS Sample Code Description: This webpage provides the sample code for the commonly used functions. Non-OS Sample Code Description: This webpage provides the sample code for the commonly used functions. ESP8266 Tools Description: This webpage provides links to the ESP8266 ash download tools and ESP8266 performance evaluation tools. ESP8266 APK ESP8266 Certication and Test Guide ESP8266 BBS ESP8266 Resources FCC Caution:
Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the 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 equipment should be installed and operated with minimum distance 20cm between the radiator& your body. FCC & ISED Label Instructions The outside of final products that contains this module device must display a label referring to the enclosed module. This exterior label can use wording such as: Contains Transmitter Module FCC ID:2AC7Z-ESPWROOM02U,IC:21098-ESPWROOM02U" or Contains FCC ID:2AC7Z-ESPWROOM02U,IC:21098-ESPWROOM02U Any similar wording that expresses the same meaning may be used. Espressif
/!32 33 2017.11
!
!
ISED RSS Warning:
This device complies with Innovation, Science and Economic Development Canada licence-exempt RSS standard(s). 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 prsent appareil est conforme aux CNR d'ISED applicables aux appareils radio exempts de licence. L'exploitation est autorise aux deux conditions suivantes:
(1) l'appareil ne doit pas produire de brouillage, et
(2) l'utilisateur de l'appareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible d'en compromettre le fonctionnement. ISED RF exposure statement:
This equipment complies with ISED radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with minimum distance 20cm between the radiator& your body.This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter. Le rayonnement de la classe b repecte ISED fixaient un environnement non contrls.Installation et mise en uvre de ce matriel devrait avec changeur distance minimale entre 20 cm ton corps.Lanceurs ou ne peuvent pas coexister cette antenne ou capteurs avec dautres. Disclaimer and Copyright Notice Information in this document, including URL references, is subject to change without notice. THIS DOCUMENT IS PROVIDED AS IS WITH NO WARRANTIES WHATSOEVER, INCLUDING ANY WARRANTY OF MERCHANTABILITY, NON-INFRINGEMENT, FITNESS FOR ANY PARTICULAR PURPOSE, OR ANY WARRANTY OTHERWISE ARISING OUT OF ANY PROPOSAL, SPECIFICATION OR SAMPLE. All liability, including liability for infringement of any proprietary rights, relating to use of information in this document is disclaimed. No licenses express or implied, by estoppel or otherwise, to any intellectual property rights are granted herein. The Wi-Fi Alliance Member logo is a trademark of the Wi-Fi Alliance. The Bluetooth logo is a registered trademark of Bluetooth SIG. All trade names, trademarks and registered trademarks mentioned in this document are property of their respective owners, and are hereby acknowledged. Copyright 2017 Espressif Inc. All rights reserved. Espressif IOT Team www.espressif.com
frequency | equipment class | purpose | ||
---|---|---|---|---|
1 | 2017-12-28 | 2412 ~ 2462 | DTS - Digital Transmission System | Original Equipment |
app s | Applicant Information | |||||
---|---|---|---|---|---|---|
1 | Effective |
2017-12-28
|
||||
1 | Applicant's complete, legal business name |
ESPRESSIF SYSTEMS (SHANGHAI) CO., LTD
|
||||
1 | FCC Registration Number (FRN) |
0023938848
|
||||
1 | Physical Address |
Suite 204, Block 2, 690 Bibo Road, Zhang Jiang Hi-Tech Park
|
||||
1 |
Suite 204, Block 2, 690 Bibo Road
|
|||||
1 |
Shanghai, N/A
|
|||||
1 |
China
|
|||||
app s | TCB Information | |||||
1 | TCB Application Email Address |
b******@baclcorp.com
|
||||
1 | TCB Scope |
A4: UNII devices & low power transmitters using spread spectrum techniques
|
||||
app s | FCC ID | |||||
1 | Grantee Code |
2AC7Z
|
||||
1 | Equipment Product Code |
ESPWROOM02U
|
||||
app s | Person at the applicant's address to receive grant or for contact | |||||
1 | Name |
C**** L******
|
||||
1 | Telephone Number |
(8621********
|
||||
1 | Fax Number |
(8621********
|
||||
1 |
l******@espressif.com
|
|||||
app s | Technical Contact | |||||
n/a | ||||||
app s | Non Technical Contact | |||||
n/a | ||||||
app s | Confidentiality (long or short term) | |||||
1 | 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 | 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?: | No | ||||
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 | Is this application for software defined/cognitive radio authorization? | No | ||||
1 | Equipment Class | DTS - Digital Transmission System | ||||
1 | Description of product as it is marketed: (NOTE: This text will appear below the equipment class on the grant) | Wi-Fi Internet of Things Module | ||||
1 | Related OET KnowledgeDataBase Inquiry: Is there a KDB inquiry associated with this application? | No | ||||
1 | Modular Equipment Type | Single Modular Approval | ||||
1 | Purpose / Application is for | Original Equipment | ||||
1 | Composite Equipment: Is the equipment in this application a composite device subject to an additional equipment authorization? | No | ||||
1 | 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 | Grant Comments | Modular approval. Output power listed is peak conducted. This grant is valid only when the module is sold to OEM or OEM integrator. Modular approval for use as a module in mobile-only RF exposure conditions. The antenna(s) used for this device must be installed to provide a separation distance of at least 20 cm from all persons and must not be co-located with any other transmitters, except in accordance with FCC multi-transmitter product procedures. Compliance of this device in all final host configurations is the responsibility of the Grantee. End-users must be provided with specific information required to satisfy RF exposure compliance for the final host device. Installation of this device into portable RF Exposure category host devices requires the submission of a Class II permissive change or new application. | ||||
1 | Is there an equipment authorization waiver associated with this application? | No | ||||
1 | 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 | Firm Name |
Bay Area Compliance Laboratories Corp. (Kunshan)
|
||||
1 | Name |
M**** C********
|
||||
1 | Telephone Number |
+86 0********
|
||||
1 |
q******@baclcorp.com
|
|||||
Equipment Specifications | |||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
1 | 1 | 15C | 2412.00000000 | 2462.00000000 | 0.1870000 |
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