The 8A3xxxx Family Programming Guide contains information on how to access internal registers and what those registers do in detail for all
devices in the 8A3xxxx family. Not all devices in the family support all the same features or quantities of logic blocks, however the register
blocks all behave and are addressed at the same locations in all device. Some devices will not make use of all register blocks since the
associated feature or block of circuitry may not be available in that particular device. A Programming Guide Addendum for each specific device
will indicate which register modules are support in that device.
In addition, there are several other pieces of documentation that describe specific functions or details for the family or individual devices.
Table 1 shows related documents.
Table 1: Related Documentation for Devices in the 8A3xxx Family
Document TitleDocument Description
<device name> DatasheetContains a functional overview of the device and hardware-design related details
including pinouts, AC & DC specifications and applications information related to
power filtering and terminations.
<device name>-<dash code> Datasheet AddendumIndicates pre-programmed power-up / reset configurations of this specific ‘dash
code’ part number
8A3xxxx Family Programming Guide (v4.7)Contains detailed register descriptions and address maps for all members of the
family of devices. Please check the <device name> datasheet to check the version
used by that device. All devices that use this version number use some subset of
this register map, as indicated in their device-specific Programming Guide
Addendum document..
Evaluation Board Reference ManualDescribes the Evaluation Board. Evaluation boards are available for the 8A34001
(144BGA) or 8A34002 (72QFN) devices. These devices contain a superset of the
functionality available in all other members of the 8A3xxxx Family. So they can
serve as evaluation tools for any of the less fully-featured family members.
Timing Commander Personality User ManualDetailed description of how to use IDT’s Timing Commander configuration tool. At
this time, a personality file is only available for 8A34001. This personality contains a
superset of the functionality available in all other members of the 8A3xxxx family.
Since all members of the 8A3xxxx family share register locations and resource
numbering, configurations generated using the 8A34001 personality can be used in
any member of the 8A3xxxx family. Functionality that is not available on the other
family members will of course not respond to any configuration of it that is made.
This document discusses the registers supported by a particular version of the Firmware (FW) running on the
internal micro-controller within the 8A3xxxx family of devices. Register maps may change between major releases
of the FW, so please check the Revision History section of this document to ensure this document aligns with the
FW revision being used on the device. FW version numbering follows the format:
▪ Introduction (this section) - describes documentation structure for the 8A3xxxx
▪ Serial Port Overview - repeating selected information from the 8A3xxxx Datasheet to discuss how the serial ports function, overall device
memory map and register addresses
▪ I2C Slave Operation - discusses register accessing topics related to I
2
C operation on a serial port
▪ SPI Operation - discusses register accessing topics related to SPI operation on a serial port
▪ Register Table Overview - discusses register table format and abbreviations
▪ Register Set Descriptions - describes a set of registers that is made available for users to quickly and simply access the commonly-used
The 8A3xxxx family supports up to 3 serial ports. One is a dedicated I
two are configurable slave
device. In some variants of the device, the
I2C or SPI ports that can be used at any time after the reset sequence is complete to monitor and/or configure the
I2C Master port share pins with an I2C slave port.
8A3xxxx Family Programming Guide
2
C Master port used for loading configuration data at reset and the other
Operation of the
I2C Master Port is only used by the device to access an external serial EEPROM and so won’t be discussed here.
Two slave ports have been provided to allow independent access to any of the device’s internal registers. This allows high priority accesses
not to be queued behind lower priority ones on a shared external serial interface. Note that internal to the device, both slave serial ports
access a single instance of each register over a shared internal bus. The device ensures that a burst access on one bus will complete
atomically once begun, before the other port can gain access to the shared internal bus or registers. However it does not guarantee the order
in which the two serial ports will be granted access to any shared resource.
Please refer to the appropriate section below for details on the operation of the slave
I2C or SPI ports.
Either slave port can be reconfigured over either serial port at any time by accessing the appropriate registers. This includes both configuration
options with each protocol or switching between protocols (
configuration, including page sizes for registers, for each serial port be set in the initial configuration data read from OTP or external EEPROM
(see Device Initial Configuration in the 8A3xxxx Datasheet for details).
Addressing Registers within a Device
The address space that is externally accessible within the device is 64kbytes in size and so needs 16-bits of address offset information to be
I2C to SPI or vice versa). However it is recommended that the full operating mode
provided during slave serial port accesses. Of that 64kbytes, only the upper 32kbytes contains user accessible registers.
The user may choose to operate either serial port providing the full offset address within each burst or to operate in a paged mode where part
of the address offset is provided in each transaction and part comes from an internal page register in each serial port. The decision may be
made independently on each slave serial port and each slave serial port has its own page register to avoid conflicts. Figure 1 shows how page
register and offset bytes from each serial transaction interact to address a register within the 8A3xxxx.
Figure 1: Register Addressing Modes via Serial Port
I2C Slave Operation
The I2C slave protocol of the 8A3xxx family complies with Version 2.1 of the I2C specification. Figure 2 shows the sequence of states on the
I2C SDATA signal for the supported modes of operation.
The Dev Addr shown in the figure represents the base address of the 8A3xxxx device. This 7-bit value can be set in an internal register which
can have a user-defined value loaded at reset from internal OTP memory or an external EEPROM. The default value if those methods are not
used is 0000000 (binary). Note that the levels on the S_A0 and S_A1 inputs can be used to control Bit 0 and Bit 1 (respectively) of this address.
These pins are available independently for each serial port. In I
functions when the part is in SPI mode. The resulting base address is the I
2
C operation these inputs are expected to remain static. They have different
2
C bus address that this device will respond to. The default address
may be over-written at any time.
When I2C operation is selected for either slave serial port, selection of 1-byte (1B) or 2-byte (2B) offset addressing must also be selected
independently for each slave serial port. These offsets are used in conjunction with the page register for each serial port to access registers
internal to the device. Because the I
2
C protocol already includes a read/write bit with the Dev Addr, all bits of the 1B or 2B offset field can be
used to address internal registers.
▪ In 1B mode, the lower 8-bits of the register offset address come from the Offset Addr byte and the upper 8-bits come from the page register
(see Table 2 for description of the 8-bit I
2
C Page Register).
The page register can be accessed at any time, no matter what page the serial port is currently on, using an offset byte value of FCh. This
4-byte register must be written in a single burst write transaction. The page register is replicated on every register page to always be
accessible.
▪ In 2B mode, the full 16-bit register address can be obtained from the Offset Addr bytes, so the page register only needs to be set once after
reset using a 3-byte burst access starting from address FFFDh (see Table 3 for description of the 16-bit I
Table 2: I2C 1B Mode Page Register Bit Field Locations and Descriptions
PAGE_ADDR[7:0]R/W00hThe values in this field are always replaced by the bits in I
C transaction itself
and so have no meaning.
PAGE_ADDR[15:8]R/W00hSelect which register page to access. Forms the upper 8-bits of the 16-bit
register address. Only values of 80h or higher should be used. Lower addresses
are not user-accessible
PAGE_ADDR[23:16]R/W10hMust be set to 10h in all cases
PAGE_ADDR[31:24]R/W20hMust be set to 20h in all cases
Table 3: I2C 2B Mode Page Register Bit Field Locations and Descriptions
Offset
I2C 2B Mode Page Register Bit Field Locations
Address
(Hex)
FFFD
1
D7D6D5D4D3D2D1D0
PAGE_ADDR[15:8]
FFFEPAGE_ADDR[23:16]
FFFFPAGE_ADDR[31:24]
1. Burst access must begin at this non-aligned offset and all 3 bytes must be written in the same I
2
C burst access. A burst beginning at the
32-bit aligned address of FFFCh will not correctly set this register.
I2C 2B Mode Page Register Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
2
PAGE_ADDR[15:8]R/W00hThe values in this field are always replaced by the bits in I
C transaction itself
and so have no meaning.
PAGE_ADDR[23:16]R/W10hMust be set to 10h in all cases
PAGE_ADDR[31:24]R/W20hMust be set to 20h in all cases
I2C burst mode operation is required to ensure data integrity of multi-byte registers. When accessing a multi-byte register, all data bytes must
be written or read in a single I
page (Offset Addr FFh in 1B mode, no limit in 2B mode). An internal address pointer is incremented automatically as each data byte is written
or read.
2
C burst access. Bursts may be of greater length if desired, but must not extend beyond the end of the register
2
C 1-byte (1B) Addressing Examples
8A3xxxx I2C 7-bit I2C address is 0x5B with LSB=R/W
Example Write “0x50” to register 0xCBE4
B6* FC 00 CB 10 20#Set Page Register, *I
B6 E4 50#Write data 5B to CB E4
C pointer to 0xC024, *I2C instruction should use “No Stop”
2
C Address is left-shifted one bit.)
B7 <read back data> #Send address with Read bit set.
SPI Operation
The 8A3xxxx Family devices support SPI operation on their main and alternate serial ports. Figure 3 shows the sequencing of address and
data on the serial port in SPI mode.
Figure 3: SPI Sequencing Diagram
Each serial port can be independently configured for the following settings. These settings can come from register defaults or from an internal
OTP or external EEPROM configuration loaded at reset:
— 1-byte (1B) or 2-byte (2B) offset addressing (see Figure 1)
– In 1B operation, the 16-bit register address is formed by using the 7-bits of address supplied in the SPI access and taking the upper
9-bits from the page register.The page register is accessed, no matter what page the serial port is currently on, using an Offset Address
of 7Ch - 7Fh. It must be accessed in a single 4-byte burst write transaction. The page register is replicated on every register page to
always be accessible.
– In 2B operation, the 16-bit register address is formed by using the 15-bits of address supplied in the SPI access and taking the upper
1-bit from the page register. Note that this bit will always be ‘1’ for register accesses, so the page register only needs to be set once
in 2B operation. The page register can be accessed, no matter what page the serial port is currently on, using an Offset Address of
7FFDh - 7FFFh. It should be accessed in a single 3-byte burst write transaction to set it. The page register is replicated on every
register page to always be accessible.
— Data sampling on falling or rising edge of SCLK
— Output (read) data positioning relative to active SCLK edge
— 4-wire (SCLK, SCSb, SDATA, SDO) or 3-wire (SCLK, SCSb, SDATA) operation
– In 3-wire mode, SDATA is a bi-directional data pin.
— Output signal protocol compatibility / drive strength and termination voltage
Table 4: SPI 1B Mode Page Register Bit Field Locations and Descriptions
Offset
SPI 1B Mode Page Register Bit Field Locations
Address
(Hex)
7CPAGE_ADDR
D7D6D5D4D3D2D1D0
PAGE_ADDR[6:0]
[7]
7DPAGE_ADDR[15:8]
7EPAGE_ADDR[23:16]
7FPAGE_ADDR[31:24]
SPI 1BMode Page Register Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
PAGE_ADDR[6:0]R/W-The values in this field are always replaced by the bits in SPI transaction itself
and so have no meaning.
PAGE_ADDR[15:7]R/W000000000bSelect which register page to access. Forms the upper 9-bits of the 16-bit
register address. Only values of 100000000b or higher should be used. Lower
addresses are not user-accessible
PAGE_ADDR[23:16]R/W10hMust be set to 10h in all cases
PAGE_ADDR[31:24]R/W20hMust be set to 20h in all cases
Table 5: SPI 2B Mode Page Register Bit Field Locations and Descriptions
8A3xxxx Family Programming Guide
Offset
SPI 2B Mode Page Register Bit Field Locations
Address
(Hex)
7FFD
1
D7D6D5D4D3D2D1D0
PAGE_ADDR
PAGE_ADDR[14:8]
[15]
7FFEPAGE_ADDR[23:16]
7FFFPAGE_ADDR[31:24]
1. Burst access must begin at this non-aligned offset and all 3 bytes must be written in the same SPI burst access. A burst beginning at the
32-bit aligned address of 7FFCh will not correctly set this register.
SPI 2B Mode Page Register Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
PAGE_ADDR[14:8]R/W0000000bThe values in this field are always replaced by the bits in SPI transaction itself
and so have no meaning.
PAGE_ADDR[15]R/W0bSelect which register page to access. Forms the most-significant bit of the 16-bit
register address. Only a value of 1b should be used. Lower addresses are not
user-accessible
PAGE_ADDR[23:16]R/W10hMust be set to 10h in all cases
PAGE_ADDR[31:24]R/W20hMust be set to 20h in all cases
SPI burst mode operation is required to ensure data integrity of multi-byte registers. When accessing a multi-byte register, all data bytes must
be written or read in a single SPI burst access. Bursts may be of greater length if desired, but must not extend beyond the end of the register
page. An internal address pointer is incremented automatically as each data byte is written or read.
SPI 1-byte (1B) Addressing Example
Example Write to “50” to register 0xCBE4
7C 80 CB 10 20#Set Page register
64* 50#*MSB is 0 for write transactions
Example Read from 0xC024:
7C 00 C0 10 20#Set Page register
A4* 00#*MSB is set, so this is a read command
SPI 2-byte (2B) Addressing Example
Example Write to “50” to register 0xCBE4
7F FD 80 10 20#Set Page register
4B E4* 50#*MSB is 0 for write transactions
Example Read from 0xC024:
7F FD 80 10 20#Set Page register
C0* 24 00#*MSB is set, so this is a read command
When programming an 8A3xxxx family device, it is necessary to read or write values to one or more ‘bit-fields’ within the device. A bit-field
provides status and/or control information on a single aspect of a single feature. A bit field may be as small as a single-bit or many bytes in
length. A bit-field should be treated as an indivisible entity and all bytes of each bit-field should be read or written in a single serial port burst.
Access to bit-fields is performed using byte-oriented addressing. A bit-field may take up multiple byte address and/or multiple bit-fields may
occupy a single byte. When there are multiple bit-fields within a single byte, all bit fields are read from or written to during an access to that
byte address over the serial port. When a bit-field spans multiple byte addresses, all bytes should be read or written in the same serial port
burst transaction to ensure consistency. For bit-fields spanning multiple bytes, the least-significant bits of that bit-field are contained in the byte
with the lowest address.
Bit-fields are grouped into registers and registers are in turn grouped into modules. In the documentation that follows, bit-fields are shown
mapped into register bytes in a table called a Bit-Field Location table. The function of each bit-field is shown in an associated Bit-Field Description table. One or more bit-fields are grouped into a register. Registers show an address offset for each byte within that register.
A number of registers are grouped together into a module. In general a module contains all the registers needed to interact with a functional
block within the device. Each module in the standard register set is listed in a Register Module Index table showing its module base address,
a brief description of the module’s function and a link to that module’s location in the document. In each module’s sub-section is a similar table
listing all the registers within that module, a brief description of the register and a link to that register’s detailed description. This is shown in
Figure 4
Many register modules include a trigger register at the end of the module that must be written to for any other
register changes within that module to take effect. This allows multiple parameters to be setup then all to take
effect at the same time for a particular function within the device. Where present, the trigger register is always the
last register in the module to allow a burst write to be used, triggering on the last write of the burst. Users must
ensure that the trigger register is written to, even if its contents don’t change to trigger the module update.
Figure 4: Finding a Register’s Detailed Description in this Document.
The device contains multiple copies of many functional blocks and each will have its own associated register module for status and control. To
keep the documentation clear and concise, only the first instance of a register module for a specific functional block will be shown in detail.
The module table will show all instantiations of the module with their unique base addresses, but the links will all point to the same descriptive
section (see blue arrows in Figure 5). Please ensure that when addressing a register that the base address of the correct instantiation of the
module is used (see red arrows in Figure 5). Note that the base address indicated in the table description is for the first instantiation of the
module only (see green arrow in Figure 5). For example, as shown below, to access the DPLL_MANUAL_HOLDOVER_VALUE bit-field for
DPLL4, take the base address of that instantiation (C480h) and add the register offset of that specific register (008h). Note that since this
bit-field is more than one byte, all bytes should be accessed in a single serial port burst transaction starting at C488h.
Figure 5: Determining the Address to Access a Specific Register.
The following terminology and abbreviations are used in the register tables.
If a bit-field has more than a single bit, the bit-field will be written as BIT_FIELD_NAME[msb:lsb] (e.g.
DPLL_MANUAL_HOLDOVER_VALUE[39:0]
Binary numbers will be written with a lowercase ‘b’ after them (e.g. 0101b )
Hexadecimal numbers will be written with a lowercase ‘h’ after them (e.g. C480h).
R/W indicates a register is readable and write-able by the user
R/O indicates that a register should only be read by the user. Writing to a R/O register has an undefined effect.
W/O indicates that a register should only be written to by the user. The read value is undefined and has no associated meaning.
RW1C indicates a register that can be read, but a ‘1’ needs to be written to the bit to clear it back to 0. This is generally used for ‘sticky’ status
bits that are latched high whenever a transient condition occurs. The user will need to write to clear the latched status.
N/A means Not Applicable. This is only used for Reserved bit-fields who’s behaviour is not defined.
Hardware Revision Information.Note that while this register can be accessed directly from the serial port by software, in IDT’s TIming
Commander GUI tool, it must be accessed indirectly since it is located in the hardware only register space.
Table 7: HW_REVISION Register Index
Register Module Base Address: 8180h
Offset
(Hex)
07AhHW_REVISION.REV_IDDevice Hardware Revision Number
HW_REVISION.REV_ID
Table 8: HW_REVISION.REV_ID Bit Field Locations and Descriptions
Individual Register NameRegister Description
Offset
HW_REVISION.REV_ID Bit Field Locations
Address
(Hex)
D7D6D5D4D3D2D1D0
07AhREV_ID[7:0]
HW_REVISION.REV_ID Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
REV_ID[7:0]R/O2Hardware Revision Register
1: RevA
2: RevB
Module: RESET_CTRL
Reset configuration.
Table 9: RESET_CTRL Register Index
Register Module Base Address: C000h
Offset
(Hex)
000hRESERVEDThis register must not be modified from the read value
Individual Register NameRegister Description
001hRESERVEDThis register must not be modified from the read value
002hRESERVEDThis register must not be modified from the read value
003hRESERVEDThis register must not be modified from the read value
004hRESERVEDThis register must not be modified from the read value
005hRESERVEDThis register must not be modified from the read value
006hRESERVEDThis register must not be modified from the read value
007hRESERVEDThis register must not be modified from the read value
008hRESERVEDThis register must not be modified from the read value
009hRESERVEDThis register must not be modified from the read value
00AhRESERVEDThis register must not be modified from the read value
00BhRESERVEDThis register must not be modified from the read value
00ChRESERVEDThis register must not be modified from the read value
00DhRESERVEDThis register must not be modified from the read value
00EhRESERVEDThis register must not be modified from the read value
00FhRESERVEDThis register must not be modified from the read value
010hRESERVEDThis register must not be modified from the read value
011hRESERVEDThis register must not be modified from the read value
012hRESET_CTRL.SM_RESETReset state machine.
RESET_CTRL.SM_RESET
Enable state machine reset.
TRIGGER: Writing to this byte triggers a read and activation in hardware of all the bytes of the RESET_CTRL module.
Table 10: RESET_CTRL.SM_RESET Bit Field Locations and Descriptions
Offset
RESET_CTRL.SM_RESET Bit Field Locations
Address
(Hex)
D7D6D5D4D3D2D1D0
012hRESET[7:0]
RESET_CTRL.SM_RESET Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
RESET[7:0]R/W0Reset state machine.
0x5a = initiate state machine reset
Write 0x5A to perform state machine reset. All other values are ignored. Self
clearing.
During a state machine reset, all registers starting from GENERAL_STATUS
returns to reset values and the device proceeds with the start-up sequence as if
the device was just powered on. The digital core is not reset.
0x000000 = no status
0x100000 = success
0x100001 = corrupted header
0x100002 = address out of range
0x100003 = corrupted section
0x100004 = invalid cluster index
0x100005 = redundant cluster not available
0x100006 = redundant cluster invalid index
0x100007 = redundant cluster program fail
0x100008 = cluster program fail
0x100009 = cluster read fail
0x10000A = main memory program fail
0x10000B = no header available
0x10000C = not enough space
0x10000D = header fail
0x10000E = invalid boot row index
0x10000F = invalid header index
0x100010 = header not found
0x100011 = more data available
0x100012 = wrong confirmation code
0x100013 = OTP programming locked
0x1000FE = OTP access modeI is disabled
0x1000FF = unknown command
8A3xxxx Family Programming Guide
GENERAL_STATUS.EEPROM_STATUS
Indicates status of EEPROM.
Table 13: GENERAL_STATUS.EEPROM_STATUS Bit Field Locations and Descriptions
Table 23: GENERAL_STATUS.EEPROM_CONFIG_STATUS Bit Field Locations and Descriptions
Offset
GENERAL_STATUS.EEPROM_CONFIG_STATUS Bit Field Locations
Address
(Hex)
D7D6D5D4D3D2D1D0
026hEEPROM_CONFIG_STATUS[7:0]
GENERAL_STATUS.EEPROM_CONFIG_STATUS Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
EEPROM_CONFIG_STAT
US[7:0]
R/O0Status code.
0x0 = success
0x1 = not found
0x2 = incomplete
0x3 = wrong offset
0x4 = wrong length
0x5 = SCSR out of range
0x6 = CRC error
0xA = corrupt header
0xB = EEPROM out of range
Module: STATUS
Live status of alarms and events.
Table 24: STATUS Register Index
Register Module Base Address: C03Ch
Offset
(Hex)
Individual Register NameRegister Description
000hSTATUS.I2CM_STATUSI2C master status.
001hRESERVEDThis register must not be modified from the read value
002hSTATUS.SER0_STATUSStatus of serial interface 0.
003hSTATUS.SER0_SPI_STATUSStatus of serial interface 0 SPI.
004hSTATUS.SER0_I2C_STATUSStatus of serial interface 0 I2C.
005hSTATUS.SER1_STATUSStatus of serial interface 1.
006hSTATUS.SER1_SPI_STATUSStatus of serial interface 1 SPI.
007hSTATUS.SER1_I2C_STATUSStatus of serial interface 1 I2C.
RESERVEDN/A-This field must not be modified from the read value
DPLL0_HOLDOVER_STAT
E_CHANGE_STICKY[5]
R/O0Holdover state change sticky bit.
Indicates whether any transition to or from Holdover state occurred.
0 = no transition to or from Holdover state
1 = transition to or from Holdover state
DPLL0_LOCK_STATE_CH
ANGE_STICKY[4]
R/O0Lock state change sticky bit.
Indicates whether any transition to or from Locked state occurred.
0 = no transition to or from Locked state
1 = transition to or from Locked state
Table 49: STATUS.DPLL1_STATUS Bit Field Locations and Descriptions
Offset
STATUS.DPLL1_STATUS Bit Field Locations
Address
(Hex)
D7D6D5D4D3D2D1D0
019hRESERVED[7:6]DPLL1_HOL
DOVER_STA
TE_CHANG
E_STICKY[5]
DPLL1_LOC
K_STATE_C
HANGE_STI
CKY[4]
STATUS.DPLL1_STATUS Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
RESERVEDN/A-This field must not be modified from the read value
DPLL1_HOLDOVER_STAT
E_CHANGE_STICKY[5]
R/O0Holdover state change sticky bit.
Indicates whether any transition to or from Holdover state occurred.
0 = no transition to or from Holdover state
1 = transition to or from Holdover state
Table 50: STATUS.DPLL2_STATUS Bit Field Locations and Descriptions
Offset
STATUS.DPLL2_STATUS Bit Field Locations
Address
(Hex)
01AhRESERVED[7:6]DPLL2_HOL
D7D6D5D4D3D2D1D0
DPLL2_LOC
DOVER_STA
TE_CHANG
E_STICKY[5]
K_STATE_C
HANGE_STI
CKY[4]
DPLL2_STATE[3:0]
STATUS.DPLL2_STATUS Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
RESERVEDN/A-This field must not be modified from the read value
DPLL2_HOLDOVER_STAT
E_CHANGE_STICKY[5]
R/O0Holdover state change sticky bit.
Indicates whether any transition to or from Holdover state occurred.
0 = no transition to or from Holdover state
1 = transition to or from Holdover state
DPLL2_LOCK_STATE_CH
ANGE_STICKY[4]
R/O0Lock state change sticky bit.
Indicates whether any transition to or from Locked state occurred.
0 = no transition to or from Locked state
1 = transition to or from Locked state
Table 51: STATUS.DPLL3_STATUS Bit Field Locations and Descriptions
8A3xxxx Family Programming Guide
Offset
STATUS.DPLL3_STATUS Bit Field Locations
Address
(Hex)
01BhRESERVED[7:6]DPLL3_HOL
D7D6D5D4D3D2D1D0
DPLL3_LOC
DOVER_STA
TE_CHANG
E_STICKY[5]
K_STATE_C
HANGE_STI
CKY[4]
STATUS.DPLL3_STATUS Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
RESERVEDN/A-This field must not be modified from the read value
DPLL3_HOLDOVER_STAT
E_CHANGE_STICKY[5]
R/O0Holdover state change sticky bit.
Indicates whether any transition to or from Holdover state occurred.
0 = no transition to or from Holdover state
1 = transition to or from Holdover state
DPLL3_LOCK_STATE_CH
ANGE_STICKY[4]
R/O0Lock state change sticky bit.
Indicates whether any transition to or from Locked state occurred.
0 = no transition to or from Locked state
1 = transition to or from Locked state
RESERVEDN/A-This field must not be modified from the read value
DPLL4_HOLDOVER_STAT
E_CHANGE_STICKY[5]
R/O0Holdover state change sticky bit.
Indicates whether any transition to or from Holdover state occurred.
0 = no transition to or from Holdover state
1 = transition to or from Holdover state
DPLL4_LOCK_STATE_CH
ANGE_STICKY[4]
R/O0Lock state change sticky bit.
Indicates whether any transition to or from Locked state occurred.
0 = no transition to or from Locked state
1 = transition to or from Locked state
Table 53: STATUS.DPLL5_STATUS Bit Field Locations and Descriptions
Offset
STATUS.DPLL5_STATUS Bit Field Locations
Address
(Hex)
D7D6D5D4D3D2D1D0
01DhRESERVED[7:6]DPLL5_HOL
DOVER_STA
TE_CHANG
E_STICKY[5]
DPLL5_LOC
K_STATE_C
HANGE_STI
CKY[4]
STATUS.DPLL5_STATUS Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
RESERVEDN/A-This field must not be modified from the read value
DPLL5_HOLDOVER_STAT
E_CHANGE_STICKY[5]
R/O0Holdover state change sticky bit.
Indicates whether any transition to or from Holdover state occurred.
0 = no transition to or from Holdover state
1 = transition to or from Holdover state
Table 54: STATUS.DPLL6_STATUS Bit Field Locations and Descriptions
Offset
STATUS.DPLL6_STATUS Bit Field Locations
Address
(Hex)
01EhRESERVED[7:6]DPLL6_HOL
D7D6D5D4D3D2D1D0
DPLL6_LOC
DOVER_STA
TE_CHANG
E_STICKY[5]
K_STATE_C
HANGE_STI
CKY[4]
DPLL6_STATE[3:0]
STATUS.DPLL6_STATUS Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
RESERVEDN/A-This field must not be modified from the read value
DPLL6_HOLDOVER_STAT
E_CHANGE_STICKY[5]
R/O0Holdover state change sticky bit.
Indicates whether any transition to or from Holdover state occurred.
0 = no transition to or from Holdover state
1 = transition to or from Holdover state
DPLL6_LOCK_STATE_CH
ANGE_STICKY[4]
R/O0Lock state change sticky bit.
Indicates whether any transition to or from Locked state occurred.
0 = no transition to or from Locked state
1 = transition to or from Locked state
Table 55: STATUS.DPLL7_STATUS Bit Field Locations and Descriptions
8A3xxxx Family Programming Guide
Offset
STATUS.DPLL7_STATUS Bit Field Locations
Address
(Hex)
01FhRESERVED[7:6]DPLL7_HOL
D7D6D5D4D3D2D1D0
DPLL7_LOC
DOVER_STA
TE_CHANG
E_STICKY[5]
K_STATE_C
HANGE_STI
CKY[4]
STATUS.DPLL7_STATUS Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
RESERVEDN/A-This field must not be modified from the read value
DPLL7_HOLDOVER_STAT
E_CHANGE_STICKY[5]
R/O0Holdover state change sticky bit.
Indicates whether any transition to or from Holdover state occurred.
0 = no transition to or from Holdover state
1 = transition to or from Holdover state
DPLL7_LOCK_STATE_CH
ANGE_STICKY[4]
R/O0Lock state change sticky bit.
Indicates whether any transition to or from Locked state occurred.
0 = no transition to or from Locked state
1 = transition to or from Locked state
RESERVEDN/A-This field must not be modified from the read value
DPLL_SYS_HOLDOVER_
STATE_CHANGE_STICKY
[5]
R/O0Holdover state change sticky bit.
Indicates whether any transition to or from Holdover state occurred.
0 = no transition to or from Holdover state
1 = transition to or from Holdover state
DPLL_SYS_LOCK_STATE
_CHANGE_STICKY[4]
R/O0Lock state change sticky bit.
Indicates whether any transition to or from Locked state occurred.
0 = no transition to or from Locked state
1 = transition to or from Locked state
Table 94: STATUS.OUTPUT_TDC_CFG_STATUS Bit Field Locations and Descriptions
Offset
STATUS.OUTPUT_TDC_CFG_STATUS Bit Field Locations
Address
(Hex)
D7D6D5D4D3D2D1D0
0AChRESERVED[7:2]STATE[1:0]
STATUS.OUTPUT_TDC_CFG_STATUS Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
RESERVEDN/A-This field must not be modified from the read value
STATE[1:0]R/O0Indicates whether the output TDC is ready to be used.
Output TDC is by default disabled.
Need to enable with OUTPUT_TDC_CFG_GBL_2.enable. After enabling, it
takes time for the output TDC clock to stabilize.
Output TDC is ready for use when in Ready state.
0 = disabled
1 = initializing
2 = ready
STATUS.OUTPUT_TDC0_STATUS
Indicates the hardware output TDC instance assigned and the status code.
Table 95: STATUS.OUTPUT_TDC0_STATUS Bit Field Locations and Descriptions
Offset
STATUS.OUTPUT_TDC0_STATUS Bit Field Locations
Address
(Hex)
D7D6D5D4D3D2D1D0
0ADhVALID[7]RESERVED[6:4]STATUS[3:0]
STATUS.OUTPUT_TDC0_STATUS Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
VALID[7]R/O0Indicates a valid measurement or alignment has met target phase offset.
When go bit is set, valid is cleared.
Measurement mode: Indicates when OUTPUT_TDCn_MEASUREMENT is
valid.
Alignment mode: Indicates when all the alignment targets are within the
OUTPUT_TDC_CTRL_1.TARGET_PHASE_OFFSET.
0 = invalid
1 = valid
RESERVEDN/A-This field must not be modified from the read value
STATUS[3:0]R/O0Status code.
When output TDC is not enabled, this shows 'Disabled'.
When OUTPUT_TDC_CTRL_4.GO is set and the configuration is valid, this
transitions to 'In progress'. When the operation completes successfully, status
transitions back to 'Idle' and OUTPUT_TDC_CTRL_4.GO will be cleared.
When OUTPUT_TDC_CTRL_4.GO is set and there is an invalid configuration,
then OUTPUT_TDC_CTRL_4.GO will be cleared and this will indicate the error
condition encountered.
0 = disabled
1 = idle
2 = in progress
3 = error - invalid source/target
4 = error - non-uniform master divider freq
5 = error - start failed
6 = error - measurement timeout
STATUS.OUTPUT_TDC1_STATUS
Indicates the hardware output TDC instance assigned and the status code.
Table 96: STATUS.OUTPUT_TDC1_STATUS Bit Field Locations and Descriptions
Offset
STATUS.OUTPUT_TDC1_STATUS Bit Field Locations
Address
(Hex)
D7D6D5D4D3D2D1D0
0AEhVALID[7]RESERVED[6:4]STATUS[3:0]
STATUS.OUTPUT_TDC1_STATUS Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
VALID[7]R/O0Indicates a valid measurement or alignment has met target phase offset.
When go bit is set, valid is cleared.
Measurement mode: Indicates when OUTPUT_TDCn_MEASUREMENT is
valid.
Alignment mode: Indicates when all the alignment targets are within the
OUTPUT_TDC_CTRL_1.TARGET_PHASE_OFFSET.
0 = invalid
1 = valid
RESERVEDN/A-This field must not be modified from the read value
STATUS[3:0]R/O0Status code.
When output TDC is not enabled, this shows 'Disabled'.
When OUTPUT_TDC_CTRL_4.GO is set and the configuration is valid, this
transitions to 'In progress'. When the operation completes successfully, status
transitions back to 'Idle' and OUTPUT_TDC_CTRL_4.GO will be cleared.
When OUTPUT_TDC_CTRL_4.GO is set and there is an invalid configuration,
then OUTPUT_TDC_CTRL_4.GO will be cleared and this will indicate the error
condition encountered.
0 = disabled
1 = idle
2 = in progress
3 = error - invalid source/target
4 = error - non-uniform master divider freq
5 = error - start failed
6 = error - measurement timeout
STATUS.OUTPUT_TDC2_STATUS
Indicates the hardware output TDC instance assigned and the status code.
Table 97: STATUS.OUTPUT_TDC2_STATUS Bit Field Locations and Descriptions
Offset
STATUS.OUTPUT_TDC2_STATUS Bit Field Locations
Address
(Hex)
D7D6D5D4D3D2D1D0
0AFhVALID[7]RESERVED[6:4]STATUS[3:0]
STATUS.OUTPUT_TDC2_STATUS Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
VALID[7]R/O0Indicates a valid measurement or alignment has met target phase offset.
When go bit is set, valid is cleared.
Measurement mode: Indicates when OUTPUT_TDCn_MEASUREMENT is
valid.
Alignment mode: Indicates when all the alignment targets are within the
OUTPUT_TDC_CTRL_1.TARGET_PHASE_OFFSET.
0 = invalid
1 = valid
RESERVEDN/A-This field must not be modified from the read value
STATUS[3:0]R/O0Status code.
When output TDC is not enabled, this shows 'Disabled'.
When OUTPUT_TDC_CTRL_4.GO is set and the configuration is valid, this
transitions to 'In progress'. When the operation completes successfully, status
transitions back to 'Idle' and OUTPUT_TDC_CTRL_4.GO will be cleared.
When OUTPUT_TDC_CTRL_4.GO is set and there is an invalid configuration,
then OUTPUT_TDC_CTRL_4.GO will be cleared and this will indicate the error
condition encountered.
0 = disabled
1 = idle
2 = in progress
3 = error - invalid source/target
4 = error - non-uniform master divider freq
5 = error - start failed
6 = error - measurement timeout
STATUS.OUTPUT_TDC3_STATUS
Indicates the hardware output TDC instance assigned and the status code.
Table 98: STATUS.OUTPUT_TDC3_STATUS Bit Field Locations and Descriptions
Offset
STATUS.OUTPUT_TDC3_STATUS Bit Field Locations
Address
(Hex)
D7D6D5D4D3D2D1D0
0B0hVALID[7]RESERVED[6:4]STATUS[3:0]
STATUS.OUTPUT_TDC3_STATUS Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
VALID[7]R/O0Indicates a valid measurement or alignment has met target phase offset.
When go bit is set, valid is cleared.
Measurement mode: Indicates when OUTPUT_TDCn_MEASUREMENT is
valid.
Alignment mode: Indicates when all the alignment targets are within the
OUTPUT_TDC_CTRL_1.TARGET_PHASE_OFFSET.
0 = invalid
1 = valid
RESERVEDN/A-This field must not be modified from the read value
STATUS[3:0]R/O0Status code.
When output TDC is not enabled, this shows 'Disabled'.
When OUTPUT_TDC_CTRL_4.GO is set and the configuration is valid, this
transitions to 'In progress'. When the operation completes successfully, status
transitions back to 'Idle' and OUTPUT_TDC_CTRL_4.GO will be cleared.
When OUTPUT_TDC_CTRL_4.GO is set and there is an invalid configuration,
then OUTPUT_TDC_CTRL_4.GO will be cleared and this will indicate the error
condition encountered.
0 = disabled
1 = idle
2 = in progress
3 = error - invalid source/target
4 = error - non-uniform master divider freq
5 = error - start failed
6 = error - measurement timeout
STATUS.OUTPUT_TDC0_MEASUREMENT
Indicates output TDC 0 measurement.
Table 99: STATUS.OUTPUT_TDC0_MEASUREMENT Bit Field Locations and Descriptions
Offset
STATUS.OUTPUT_TDC0_MEASUREMENT Bit Field Locations
Address
(Hex)
D7D6D5D4D3D2D1D0
0B4hPHASE[7:0]
0B5hPHASE[15:8]
0B6hPHASE[23:16]
0B7hPHASE[31:24]
0B8hPHASE[39:32]
0B9hPHASE[47:40]
STATUS.OUTPUT_TDC0_MEASUREMENT Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
PHASE[47:0]R/O0Output TDC measurement.
Signed 48-bit integer in picoseconds.
Measurement = sum of samples / number of samples
A sample is collected every 100us.
Positive value indicates the target edge leads the source edge.
i.e.. source edge is to the left of the target edge
Table 100: STATUS.OUTPUT_TDC1_MEASUREMENT Bit Field Locations and Descriptions
Offset
STATUS.OUTPUT_TDC1_MEASUREMENT Bit Field Locations
Address
(Hex)
D7D6D5D4D3D2D1D0
0C4hPHASE[7:0]
0C5hPHASE[15:8]
0C6hPHASE[23:16]
0C7hPHASE[31:24]
0C8hPHASE[39:32]
0C9hPHASE[47:40]
STATUS.OUTPUT_TDC1_MEASUREMENT Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
PHASE[47:0]R/O0Output TDC measurement.
Signed 48-bit integer in picoseconds.
Measurement = sum of samples / number of samples
A sample is collected every 100us.
Positive value indicates the target edge leads the source edge.
i.e.. source edge is to the left of the target edge
STATUS.OUTPUT_TDC2_MEASUREMENT
Indicates output TDC 2 measurement.
Table 101: STATUS.OUTPUT_TDC2_MEASUREMENT Bit Field Locations and Descriptions
Offset
STATUS.OUTPUT_TDC2_MEASUREMENT Bit Field Locations
STATUS.OUTPUT_TDC2_MEASUREMENT Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
PHASE[47:0]R/O0Output TDC measurement.
Signed 48-bit integer in picoseconds.
Measurement = sum of samples / number of samples
A sample is collected every 100us.
Positive value indicates the target edge leads the source edge.
i.e.. source edge is to the left of the target edge
STATUS.OUTPUT_TDC3_MEASUREMENT
Indicates output TDC 3 measurement.
Table 102: STATUS.OUTPUT_TDC3_MEASUREMENT Bit Field Locations and Descriptions
Offset
STATUS.OUTPUT_TDC3_MEASUREMENT Bit Field Locations
Address
(Hex)
D7D6D5D4D3D2D1D0
0D4hPHASE[7:0]
0D5hPHASE[15:8]
0D6hPHASE[23:16]
0D7hPHASE[31:24]
0D8hPHASE[39:32]
0D9hPHASE[47:40]
STATUS.OUTPUT_TDC3_MEASUREMENT Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
PHASE[47:0]R/O0Output TDC measurement.
Signed 48-bit integer in picoseconds.
Measurement = sum of samples / number of samples
A sample is collected every 100us.
Positive value indicates the target edge leads the source edge.
i.e.. source edge is to the left of the target edge
Table 111: STATUS.DPLL0_PHASE_PULL_IN_STATUS Bit Field Locations and Descriptions
Offset
STATUS.DPLL0_PHASE_PULL_IN_STATUS Bit Field Locations
Address
(Hex)
D7D6D5D4D3D2D1D0
11ChREMAINING_TIME[7:0]
STATUS.DPLL0_PHASE_PULL_IN_STATUS Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
REMAINING_TIME[7:0]R/O0Unsigned 8-bit phase pull-in time to finish in seconds.
If the value of this field < 255, the actual remaining time is between
(remaining_time) and (remaining_time + 1) seconds. If the value = 255, it
implies the actual remaining time >= 255 seconds.
STATUS.DPLL1_PHASE_PULL_IN_STATUS
DPLL1 phase pull-in status
Table 112: STATUS.DPLL1_PHASE_PULL_IN_STATUS Bit Field Locations and Descriptions
Offset
STATUS.DPLL1_PHASE_PULL_IN_STATUS Bit Field Locations
Address
(Hex)
D7D6D5D4D3D2D1D0
11DhREMAINING_TIME[7:0]
STATUS.DPLL1_PHASE_PULL_IN_STATUS Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
REMAINING_TIME[7:0]R/O0Unsigned 8-bit phase pull-in time to finish in seconds.
If the value of this field < 255, the actual remaining time is between
(remaining_time) and (remaining_time + 1) seconds. If the value = 255, it
implies the actual remaining time >= 255 seconds.
STATUS.DPLL2_PHASE_PULL_IN_STATUS
DPLL2 phase pull-in status
Table 113: STATUS.DPLL2_PHASE_PULL_IN_STATUS Bit Field Locations and Descriptions
Offset
STATUS.DPLL2_PHASE_PULL_IN_STATUS Bit Field Locations
STATUS.DPLL2_PHASE_PULL_IN_STATUS Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
REMAINING_TIME[7:0]R/O0Unsigned 8-bit phase pull-in time to finish in seconds.
If the value of this field < 255, the actual remaining time is between
(remaining_time) and (remaining_time + 1) seconds. If the value = 255, it
implies the actual remaining time >= 255 seconds.
STATUS.DPLL3_PHASE_PULL_IN_STATUS
DPLL3 phase pull-in status
Table 114: STATUS.DPLL3_PHASE_PULL_IN_STATUS Bit Field Locations and Descriptions
Offset
STATUS.DPLL3_PHASE_PULL_IN_STATUS Bit Field Locations
Address
(Hex)
D7D6D5D4D3D2D1D0
11FhREMAINING_TIME[7:0]
STATUS.DPLL3_PHASE_PULL_IN_STATUS Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
REMAINING_TIME[7:0]R/O0Unsigned 8-bit phase pull-in time to finish in seconds.
If the value of this field < 255, the actual remaining time is between
(remaining_time) and (remaining_time + 1) seconds. If the value = 255, it
implies the actual remaining time >= 255 seconds.
STATUS.DPLL4_PHASE_PULL_IN_STATUS
DPLL4 phase pull-in status
Table 115: STATUS.DPLL4_PHASE_PULL_IN_STATUS Bit Field Locations and Descriptions
Offset
STATUS.DPLL4_PHASE_PULL_IN_STATUS Bit Field Locations
Address
(Hex)
D7D6D5D4D3D2D1D0
120hREMAINING_TIME[7:0]
STATUS.DPLL4_PHASE_PULL_IN_STATUS Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
REMAINING_TIME[7:0]R/O0Unsigned 8-bit phase pull-in time to finish in seconds.
If the value of this field < 255, the actual remaining time is between
(remaining_time) and (remaining_time + 1) seconds. If the value = 255, it
implies the actual remaining time >= 255 seconds.
Table 116: STATUS.DPLL5_PHASE_PULL_IN_STATUS Bit Field Locations and Descriptions
Offset
STATUS.DPLL5_PHASE_PULL_IN_STATUS Bit Field Locations
Address
(Hex)
D7D6D5D4D3D2D1D0
121hREMAINING_TIME[7:0]
STATUS.DPLL5_PHASE_PULL_IN_STATUS Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
REMAINING_TIME[7:0]R/O0Unsigned 8-bit phase pull-in time to finish in seconds.
If the value of this field < 255, the actual remaining time is between
(remaining_time) and (remaining_time + 1) seconds. If the value = 255, it
implies the actual remaining time >= 255 seconds.
STATUS.DPLL6_PHASE_PULL_IN_STATUS
DPLL6 phase pull-in status
Table 117: STATUS.DPLL6_PHASE_PULL_IN_STATUS Bit Field Locations and Descriptions
Offset
STATUS.DPLL6_PHASE_PULL_IN_STATUS Bit Field Locations
Address
(Hex)
D7D6D5D4D3D2D1D0
122hREMAINING_TIME[7:0]
STATUS.DPLL6_PHASE_PULL_IN_STATUS Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
REMAINING_TIME[7:0]R/O0Unsigned 8-bit phase pull-in time to finish in seconds.
If the value of this field < 255, the actual remaining time is between
(remaining_time) and (remaining_time + 1) seconds. If the value = 255, it
implies the actual remaining time >= 255 seconds.
STATUS.DPLL7_PHASE_PULL_IN_STATUS
DPLL7 phase pull-in status
Table 118: STATUS.DPLL7_PHASE_PULL_IN_STATUS Bit Field Locations and Descriptions
Offset
STATUS.DPLL7_PHASE_PULL_IN_STATUS Bit Field Locations
STATUS.DPLL7_PHASE_PULL_IN_STATUS Bit Field Descriptions
Bit Field NameField TypeDefault ValueDescription
REMAINING_TIME[7:0]R/O0Unsigned 8-bit phase pull-in time to finish in seconds.
If the value of this field < 255, the actual remaining time is between
(remaining_time) and (remaining_time + 1) seconds. If the value = 255, it
implies the actual remaining time >= 255 seconds.