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
20 Hardware Overview
defeated if the module is held in the boot loader by Reset Line being held low. Lines
configured as outputs consume no excess power if the output is left open. Specified
module power consumption is achieved for one or more GPIO lines set as output and left
open. Users who are not able to provide external pull ups or pull downs on any given
input, and who do not need that GPIO line, may configure it as an output and leave it
open to achieve specified module power consumption.
Configuring GPIO Settings
The GPIO lines are configured as inputs or outputs through the MercuryAPI by setting the
reader configuration parameters /reader/gpio/inputList and /reader/gpio/outputList. Once
configured as inputs or outputs the state of the lines can be Get or Set using the gpiGet()
and gpoSet() methods, respectively. See the language specific reference guide for more
details.
Reset Line
Upon power up the RESET (pin 15) line is configured as an input. The input value will
determine whether the Boot Loader
will wait for user commands or immediately load the
Application Firmware
image and enter application mode. After that action is completed, this
line is configured as an output line. While the unit continues to be in bootloader the line is
driven high.
Once in application mode, the RESET line is driven low. if the module returns to the
bootloader mode, either due to an assert or “boot bootloader”, the RESET line will again
be driven high.
To minimize power consumption in the application, the RESET line should be either left
open or pulled weakly low (10k to ground).