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.
21
⚫ If you use the compilation tool provided by MXCHIP, xxxx@emc328x.all.bin is usually generated,
and the corresponding download address is 0x08000000.
⚫ If you use other compilation tools, you should query the relevant settings of the compilation system.
The commonly generated km0_boot_all.bin is downloaded to 0x08000000, km4_boot_all.bin is
downloaded to 0x08004000, and km0_km4_image2.bin is downloaded to 0x08006000.
Figure 8 Image Tool Interface
Click the Download button to complete the download.
Using BAT burning system
BAT is a production tool for factory batch burning by MXCHIP. It can not only implement firmware
burning, but also burn unique ID for each module, such as cloud service verification code, security key,
certificate, token and so on.
The BAT system uses a server client architecture. Firmware and ID can be imported in batches on the
server to create production tasks and manage the production system in a unified manner. The client
synchronizes production tasks from the server, and one client can burn four modules at the same time.
The client can also interface with automation systems such as loading machines and robot arms to
achieve fully automated production.
For the usage of the BAT system, please refer to the usage documentation related to the BAT system.
The EMC328x module interacts with the BAT system via the SWD interface. The following is a block
diagram of the application of the BAT system: