Data Sheet
Table Of Contents
- Abstract
- 1. Introduction
- 2. Characteristic
- 3. Pin Definition
- 4. System memory space
- 5. ATE（RF Test Mode）
- 5.1. ATE Command
- 5.1.1. Start MP mode
- 5.1.2. Stop MP mode
- 5.1.3. Set Tx rate
- 5.1.4. Set operational channel
- 5.1.5. Set operational bandwidth
- 5.1.6. Set Tx power
- 5.1.7. Set antenna for Tx
- 5.1.8. Set antenna for Rx
- 5.1.9. Start air Rx mode
- 5.1.10. Start continuous Tx mode
- 5.1.11. Query air Rx statistics
- 5.1.12. Reset air Tx/Rx statistics
- 5.2. Example Command
- 5.1. ATE Command
- 6. Flash Programing
- 7. Electrical parameters
- 8. Antenna Information
- 9. Assembly size and PCB package
- 10. Production Guidelines
- 11. FCC and IC Information
- 11.1. FCC Warning
- 11.2. IC warning
- 11.3. Trace antenna designs
- 11.4. RF exposure considerations
- 11.5. Antennas
- 11.6. Label and compliance information
- 11.7. Information on test modes and additional testing requirements5
- 11.8. Additional testing, Part 15 Subpart B disclaimer
- 11.9. The module is limited to OEM installation ONLY.
- 11.10. The OEM integrator is responsible for ensuring that the end-user has no manual instructions to remove or install module.
- 11.11. The module is limited to installation in mobile or fixed applications
- 12. Package and Label
- Appendix 1: Sales and Technical Support Information
EMC328x Series Wireless Module Data Manual
Copyright of Shanghai MXCHIP Information Technology Co., Ltd.
19
Flash Programing
The module's Flash can be programmed in a variety of ways to burn firmware for specific functions. The
application scenarios and restrictions of various burning methods are as follows:
Table 7 Flash Programed Method
Methods
Interface
Communication
Pins
Enter
programming
mode
Ready for Work
PA7
Simulation debugger
SWD
PA28，PB3
-
Development environment and JTAG
debugger
Serial download mode
UART0/UART1
PA7，PA8
0
Image Tool Burning software
BAT Burning system
SWD
PA28，PB3
-
BAT
Burning system
注： PA7 Power-on default high
The application scenarios of each burning method are as follows:
⚫ Simulation debugger: burns in the development and debugging phase of the module.
⚫ Serial port download mode: Batch programming of modules on the production line.
⚫ BAT burning system: The module is secondarily burned on the production line of the module or
product, and can be used for the unique ID of the burning device.
In summary, it is recommended to introduce PA7, PA8, PA28, and PB3 as the burning test points on the
user's motherboard to facilitate development and production.
Burning with the emulator debugger
When developing module firmware using the MXOS system, the generated firmware can be directly
burned into the module by the compile command in the development environment MiCoder. Please
refer to the relevant documentation for the MiCoder development environment. The hardware emulator
usually chooses JLink, and the connection method is shown in Figure 5:
Figure 5 JLink Connection Diagram
You can download the currently compiled firmware by adding the download parameter to the compile
command. Due to the need to install the development environment, it is not suitable for module batch
factory burning.
For example, compile the Helloworld application and execute the command:
mxos make helloworld@emc328x download
Command run result:：