T-MICRO32 User Guide Version 2.
About This Guide This document is intended to help users set up the basic software development environment for developing applications using hardware based on the T-MICRO32. Through a simple example, this document illustrates how to use ESP-IDF (Xinyuan IoT Development Framework), including the menu based configuration wizard, compiling the ESP-IDF and firmware download to the ESP32 module. Release Notes Date Version Release notes 2019.04 V2.0 First release.
Table of Contents 1. Introduction............................................................................................................................. 1 1.1. T-MICRO32 ................................................................................................................. 1 1.2. ESP-IDF .....................................................................................................................................1 1.3. Preparation .....................................................
1. Introduction ! 1. Introduction 1.1. T-MICRO32 T-MICRO32 is a powerful, generic Wi-Fi+BT+BLE MCU module that targets a wide variety of applications, ranging from low-power sensor networks to the most demanding tasks, such as voice encoding, music streaming and MP3 decoding. T-MICRO32 integrates a U.FL connector . 1.1.1 CE Part (1)Frequency Range:2.4G Wi-Fi: 2412~2472MHz/2422~2462MHz BLE:2402~2480MHz Bluetooth: 2402~2480MHz (2)Transmit Power: 2.4G Wi-Fi: 18.68dBm(802.11b),9.39dBm(802.11g) 9.94dBm(802.
2. Get Started ! 2. Get Started 2.1. Standard Setup of Toolchain for Linux The quickest way to start development with ESP32 is by installing a prebuilt toolchain. Pick up your OS below and follow provided instructions. 2.1.1.
2. Get Started ! Then when you need the toolchain you can type get_esp32 on the command line and the toolchain will be added to your PATH. 2.2. Get ESP-IDF Once you have the toolchain (that contains programs to compile and build the application) installed, you also need ESP32 specific API / libraries. They are provided by Espressif in ESP-IDF repository.
3. Start a Project ! 3. Start a Project Now you are ready to prepare your application for ESP32. To start off quickly, we will use :example:`get-started/hello_world project from :idf:`examples` directory in IDF. Copy :example:`get-started/hello_world` to ~/esp directory: cd ~/esp cp -r $IDF_PATH/examples/get-started/hello_world . You can also find a range of example projects under the :idf:`examples` directory in ESPIDF.
4. Connect ! 4. Connect You are almost there. To be able to proceed further, connect ESP32 board to PC, check under what serial port the board is visible and verify if serial communication works. If you are not sure how to do it, check instructions in section :doc:`establish-serial-connection`. Note the port number, as it will be required in the next step. Xinyuan ! /12 5 2019.
4. Configure ! 5. Configure Being in terminal window, go to directory of hello_world application by typing cd ~/esp/ hello_world. Then start project configuration utility menuconfig: cd ~/esp/hello_world make menuconfig If previous steps have been done correctly, the following menu will be displayed: ! In the menu, navigate to Serial flasher config > Default serial port to configure the serial port, where project will be loaded to.
5. Build and Flash ! 6. Build and Flash 6.1. Build and Flash Now you can build and flash the application. Run: make flash This will compile the application and all the ESP-IDF components, generate bootloader, partition table, and application binaries, and flash these binaries to your ESP32 board. esptool.py v2.0-beta2 Flashing binaries to serial port /dev/ttyUSB0 (app at offset 0x10000)... esptool.py v2.0-beta2 Connecting........___ Uploading stub... Running stub... Stub running...
5. Build and Flash ! If there are no issues, at the end of build process, you should see messages describing progress of loading process. Finally, the end module will be reset and “hello_world” application will start. If you'd like to use the Eclipse IDE instead of running make, check out the :doc:`Eclipse guide `. 6.2. Monitor To see if “hello_world” application is indeed running, type make monitor.
6. SSC Command Reference ! 7. SSC Command Reference Here lists some common Wi-Fi commands for you to test the module. 7.1. op Description op commands are used to set and query the Wi-Fi mode of the system. Example op -Q op -S -o wmode Parameter Table 6-1. op Command Parameter Parameter Description -Q Query Wi-Fi mode. -S Set Wi-Fi mode. There are 3 Wi-Fi modes: wmode • mode = 1: STA mode • mode = 2: AP mode • mode = 3: STA+AP mode 7.2.
6. SSC Command Reference ! Parameter Description -s ssid Scan or connect Access Points with the ssid. -b bssid Scan the Access Points with the bssid. -n channel Scan the channel. -h Show scan results with hidden ssid Access Points. -Q Show STA connect stutus. -D Disconnected with current Access Points. 7.3. ap Description ap commands are used to set the parameter of AP network interface.
6. SSC Command Reference ! Parameter Table 6-4. mac Command Parameter Parameter Description -Q Show MAC address. -o mode • mode = 1: MAC address in STA mode. • mode = 2: MAC address in AP mode. 7.5. dhcp Description dhcp commands are used to enable or disable dhcp server/client. Example dchp -S [-o mode] dhcp -E [-o mode] dhcp -Q [-o mode] Parameter Table 6-5. dhcp Command Parameter Parameter Description -S Start DHCP (Client/Server). -E End DHCP (Client/Server). -Q show DHCP status.
6. SSC Command Reference ! Parameter Table 6-6. ip Command Parameter Parameter Description -Q Show IP address. -o mode • mode = 1 : IP address of interface STA. • mode = 2 : IP address of interface AP. • mode = 3 : both -S Set IP address. -i ip IP address. -m mask Subnet address mask. -g gateway Default gateway. 7.7. reboot Description reboot command is used to reboot the board. Example reboot 7.8. ram ram command is used to query the size of the remaining heap in the system.
FCC Label: The FCC ID is on the front of the device. It is easily visible. The device FCC ID is 2ASYE-T-MICRO32. A label with the following statements must be attached to the host end product: This device contains FCC ID: 2ASYE-T-MICRO32. The manual provides guidance to the host manufacturer will be included in the documentation that will be provided to the OEM. The module is limited to installation in mobile or fixed applications.
FCC RF Exposure Requirements This device complies with FCC RF radiation exposure limits set forth for an uncontrolled enviroment. The antenna(s) used for this transmitter must not be co‐located or operating in conjunction with any other antenna or transmitter and must be installed to provide a separation distance of at least 20cm from all persons. FCC Regulations This device complies with part 15 of the FCC Rules.
