User Manual
Table Of Contents
- M6e-31.5dBm Hardware Guide
- Contents
- Mercury6e Introduction
- Hardware Overview
- Firmware Overview
- Communication Protocol
- Functionality of the Mercury6e
- Appendix A: Error Messages
- Common Error Messages
- FAULT_MSG_WRONG_NUMBER_OF_DATA – (100h)
- FAULT_INVALID_OPCODE – (101h)
- FAULT_UNIMPLEMENTED_OPCODE – 102h
- FAULT_MSG_POWER_TOO_HIGH – 103h
- FAULT_MSG_INVALID_FREQ_RECEIVED (104h)
- FAULT_MSG_INVALID_PARAMETER_VALUE - (105h)
- FAULT_MSG_POWER_TOO_LOW - (106h)
- FAULT_UNIMPLEMENTED_FEATURE - (109h)
- FAULT_INVALID_BAUD_RATE - (10Ah)
- Bootloader Faults
- Flash Faults
- Protocol Faults
- FAULT_NO_TAGS_FOUND – (400h)
- FAULT_NO_PROTOCOL_DEFINED – 401h
- FAULT_INVALID_PROTOCOL_SPECIFIED – 402h
- FAULT_WRITE_PASSED_LOCK_FAILED – 403h
- FAULT_PROTOCOL_NO_DATA_READ – 404h
- FAULT_AFE_NOT_ON – 405h
- FAULT_PROTOCOL_WRITE_FAILED – 406h
- FAULT_NOT_IMPLEMENTED_FOR_THIS_PROTOCOL – 407h
- FAULT_PROTOCOL_INVALID_WRITE_DATA – 408h
- FAULT_PROTOCOL_INVALID_ADDRESS – 409h
- FAULT_GENERAL_TAG_ERROR – 40Ah
- FAULT_DATA_TOO_LARGE – 40Bh
- FAULT_PROTOCOL_INVALID_KILL_PASSWORD – 40Ch
- FAULT_PROTOCOL_KILL_FAILED - 40Eh
- FAULT_PROTOCOL_BIT_DECODING_FAILED - 40Fh
- FAULT_PROTOCOL_INVALID_EPC – 410h
- FAULT_PROTOCOL_INVALID_NUM_DATA – 411h
- FAULT_GEN2 PROTOCOL_OTHER_ERROR - 420h
- FAULT_GEN2_PROTOCOL_MEMORY_OVERRUN_BAD_PC - 423h
- FAULT_GEN2 PROTOCOL_MEMORY_LOCKED - 424h
- FAULT_GEN2 PROTOCOL_INSUFFICIENT_POWER - 42Bh
- FAULT_GEN2 PROTOCOL_NON_SPECIFIC_ERROR - 42Fh
- FAULT_GEN2 PROTOCOL_UNKNOWN_ERROR - 430h
- Analog Hardware Abstraction Layer Faults
- Tag ID Buffer Faults
- System Errors
- Common Error Messages
- Appendix B: Getting Started - Devkit
Hardware Interfaces
Hardware Overview 19
General Purpose Input/Output (GPIO)
The four GPIO connections, provided through the M6e Digital Connector Signal Definition,
may be configured as inputs or outputs using the MercuryAPI. The GPIO pins connect
through 100 ohm resistors to the high current PA0 to PA3 pins of the AT91SAM7X
processor. The processor data sheet can be consulted for additional details.
Pins configured as inputs must not have input voltages that exceed voltage range of -0.3
volts to +5.5 volts. In addition, during reset the input voltages should not exceed 3.3V.
Outputs may source and sink 16 mA. Voltage drop in the series 100 ohm resistor will
reduce the delivered voltage swing for output loads that draw significant current.
Input Mode
– TTL compatible inputs,
– Logic low < 0.8 V,
– Logic high > 2.0V.
– 5V tolerant
Output Mode
– 3.3 Volt CMOS Logic Output with 100 ohms in series.
– Greater than 1.9 Volts when sourcing 8 mA.
– Greater than 2.9 Volts when sourcing 0.3 mA.
– Less than 1.2 Volts when sinking 8 mA.
– Less than 0.2 Volts when sinking 0.3 mA.
Module power consumption can be adversely affected by incorrect GPIO configuration.
Similarly, the power consumption of external equipment connected to the GPIOs can also
be adversely affected. The following instructions will yield specification compliant
operation.
On power up, the M6E module configures its GPIOs as outputs to avoid contention from
user equipment that may be driving those lines. The input configuration is as a 3.3 volt
logic CMOS input and will have a leakage current not in excess of 400 nA. The input is in
an undetermined logic level unless pulled externally to a logic high or low. Module power
consumption for floating inputs is unspecified. With the GPIOs configured as inputs
and individually pulled externally to either high or low logic level, module power
consumption is as listed in the M6e Power Consumption
table.
GPIOs may be reconfigured individually after power up to become outputs. This
configuration takes effect either at API execution or a few tens of milliseconds after power
up if the configuration is stored in nonvolatile memory. The configuration to outputs is