User Guide
Table Of Contents
- Contents
- Introduction to the Mercury6e- Transcore Module
- Functionality of the Embedded Modules
- Overview of the Communication Protocol
- Command Set
- Boot Loader Commands
- Multi-Protocol Tag Commands
- Allegro/Title-21 Tag Commands
- eGo/SeGo Tag Command Set
- ATA Tag Command Set
- Gen2 Tag Commands
- Get Configuration Commands
- Get Hardware Version (10h)
- Get Antenna Configuration (61h)
- Get Read TX Power (62h)
- Get Current Tag Protocol (63h)
- Get Write TX Power (64h)
- Get Frequency Hop Table (65h)
- Get User GPIO Inputs (66h)
- Get Current Region (67h)
- Get Power Mode (68h)
- Get User Mode (69h)
- Get Reader Configuration(6Ah)
- Get Protocol Configuration (6Bh)
- Get Reader Statistics (6Ch)
- Get Available Protocols (70h)
- Get Available Regions (71h)
- Get Current Temperature (72h)
- Set Configuration Commands
- FCC Test Commands
- Appendix A: Hardware Details
- Appendix B: Using the ArbSer Application
- Appendix C: 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
- FPGA 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_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 D: FPGA Support
Creating an FPGA Image DAT File
Appendix D: FPGA Support 199
C:\>datgen tm_fpga_top.stp
DirectC Version 2.x
Copyright (C) 2002 - 2007 Actel Corporation
Checking STAPL file CRC value..
Actual CRC = 7D55
Reading STAPL file...
Generating .dat files...
Image size = 129680
Data compression = 0
Stapl Target ID = 3A121CF
Tool version = 1
Map version = 1
Core Support = 1
FROM support = 0
NVM support = 0
NVM_Block0 support = 0
NVM_Block1 support = 0
NVM_Block2 support = 0
NVM_Block3 support = 0
NVM verifiy = 0
Pass key support = 0
AES key support = 0
Core security Status = 0
From Security Status = 0
NVM_BLOCK0 Security Status = 0
NVM_BLOCK1 Security Status = 0
NVM_BLOCK2 Security Status = 0
NVM_BLOCK3 Security Status = 0
Image CRC = 244B
Done.
C:\>dir *.dat
03/13/2009 02:15 PM 129,680 tm_fpga_top.dat
1 File(s) 129,680 bytes
0 Dir(s) 23,756,279,808 bytes free
3. The resulting tm_fpga_top.dat can now be loaded onto the M6e-TC using the
process described in Loading an FPGA Image
.
WARNING!
When loading an FPGA Image onto the M6e-TC, the Verification process
checks the 16 most significant bits of the FPGA TM and TC version
numbers. To pass, the TM and TC versions must start with 0x1234xxxx
and 0x0010xxxx, respectively. When incrementing version numbers in
the Verilog/VHDL files be sure to only change the 16 least significant
bits.