Can fd controller with integrated transceiver providing microcontrollers without an integrated can fd controller (33 pages)
Summary of Contents for Texas Instruments OMAP5910
Page 1
OMAP5910 Dual-Core Processor Memory Interface Traffic Controller Reference Guide Literature Number: SPRU673 October 2003...
Page 2
TI for that product or service voids all express and any implied warranties for the associated TI product or service and is an unfair and deceptive business practice. TI is not responsible or liable for any such statements. Following are URLs where you can obtain information on other Texas Instruments products and application solutions: Products...
Page 3
40 hexadecimal (decimal 64): 40h. Related Documentation From Texas Instruments The following documents describe the OMAP5910 device and related peripherals. Copies of these documents are available on the Internet at www.ti.com. Tip: Enter the literature number in the search box provided at www.ti.com.
Page 4
Trademarks Related Documentation From Texas Instruments / Trademarks OMAP5910 Dual-Core Processor Universal Serial Bus (USB) and Frame Adjustment Counter (FAC) Reference Guide (literature number SPRU677) OMAP5910 Dual-Core Processor Clock Generation and System Reset Management Reference Guide (literature number SPRU678) OMAP5910 Dual-Core Processor General-Purpose Input/Output (GPIO)
OMAP5910 system memory resources (SRAM, SDRAM, flash, ROM, etc.). The TC also manages accesses by the MPU or the USB host. The USB host is an internal OMAP5910 peripheral connected on the local bus, so the TC contributes to managing USB host accesses.
Introduction Figure 2. Traffic Controller To/from To/from DSP MMU MPUI port MPUI Traffic controller ROM SRAM Flash MPU bus SBFlash Slow MPU TI Slow Slow I/F DMA MPUI- peripheral port bus (public) port Fast I/F DMA SDRAM Fast Fast port TIPB port MPU bus...
Single and burst access The memories accessed by the TC are separated into two groups: External memory is memory that is not part of the OMAP5910 device. It can be SDRAM, flash, ROM, RAM, etc. External memory is accessed using the external memory interface (EMIF). The TC has two separate memory interfaces to access the external memories.
Memory Map The TC provides each of the four hosts with: 8-/16-/32-bit single access and burst access, except the LCD controller channel. 16- or 32-bit access must start from the 16- or 32-bit boundary address. Size adaptation for 8-, 16-, or 32-bit words, with the requirement that address must be aligned on the correct bit boundary.
The interface to these memory devices is activated via internal address decoding. There is no external chip select. The OMAP5910 peripherals are mapped on the MPU memory space in two different segments: through STROBE0 (public peripherals) and STROBE1 (private peripherals). Each peripheral has a range of 2K bytes.
Page 15
Memory Map Table 3. MPU Memory Map (Continued) † Device Name Start Address End Address Size in Bytes Data Access DSP Processor Address Space DSP MPUI Interface MPUI Port RAM E000:0000 E0FF:FFFF 16M bytes 16/32 R/W MPUI DSP Peripherals I/O Space E100:0000 E101:FFFF 128K bytes...
Page 16
Memory Map Table 3. MPU Memory Map (Continued) † Device Name Start Address End Address Size in Bytes Data Access MPU Address Space (Continued) Reserved E102:0004 EFFF:FFFF Reserved F000:0000 FFFD:0000 MPU Public TIPB Peripherals (Strobe 0) UART1 FFFB:0000 FFFB:07FF 2K bytes 8 R/W UART2 FFFB:0800...
IMIF Priority Handler This memory interface has two software-selectable priority algorithms for resolving simultaneous access requests: least recently used and dynamic priority. The priority scheme is shared with the EMIFS and EMIFF and is set OMAP5910 configuration registers (bit LRU_SEL FUNC_MUX_CTRL_0).
15 −0 Flash data bus from external device † FLASH.CS2 and FLASH.BAA are multiplexed on the same device pin. Pin function is selected using the OMAP5910 configu- ration register, FUNC_MUX_CRTL_0. The FLASH.CS2 functionality is default. Memory Interface Traffic Controller SPRU673...
3 −0 External byte enable † FLASH.CS2 and FLASH.BAA are multiplexed on the same device pin. Pin function is selected using the OMAP5910 configu- ration register, FUNC_MUX_CRTL_0. The FLASH.CS2 functionality is default. Note: OMAP5910 multiplexes the FLASH.CS2 and FLASH.BAA pin functionality to the same device pin.
Memory Interfaces The low-priority queue order is: Local bus DMA (all channels excluding LCD) The high-priority queue order is: Local bus DMA transfer involving channels other than LCD channel Fixed priority is a special case of dynamic priority. To create a fixed priority, all time-out registers must have a value of 0.
Memory Interfaces 3.2.3 Device Initialization Depending on the flash memory or RAM device associated with each chip- select, the EMIFS interface must be initialized. If the device used is a flash, the flash may have to be initialized in the correct protocol to achieve maximum performance.
In synchronous modes a selectable retiming feature enables read data to be latched by a delayed EMIFS reference clock. The retiming feature accounts for delays through the OMAP5910 input/output pins by feeding back FLASH.CLK to offer optimum data and clock alignment. You can select the retiming mode using the RT bit in the EMIFS chip-select configuration registers.
Memory Interfaces Figure 3. Asynchronous 16-Bit Read Operation on a 16-Bit Width Device TC Clock (internal) EMIFS Ref (internal) FLASH.CLK N cycles FLASH.CS_[X] FLASH.ADV FLASH.A(24:1) Address valid FLASH.D(15:0) Valid data D0 FLASH.OE FLASH.BE(1:0) High FLASH.RDY 3.2.6 Asynchronous Page Mode Read Operation The asynchronous page mode read operation is similar to the asynchronous read, except that the number of wait states is different between the first access and the subsequent accesses within the page.
Memory Interfaces As in asynchronous mode, device interface signals are referenced to the internal EMIFS reference clock, which is divided from the TC clock using FCLKDIV in the EMIF slow interface configuration register. The FLASH.CLK signal is not externally driven in asynchronous page operating mode. Figure 4 shows typical timing for an asynchronous page mode 8x16-bit read operation on a 16-bit width device with RDWST = 2, PGWST = 0, FCLKDIV = 01, and RDMODE = 2.
The synchronous read mode is selected for each device by setting the RDMODE configuration bit field to 100b. In this mode of operation, FLASH.CLK is driven on the OMAP5910 device pin. Both AMD burst flash and Intel burst flash have three modes of operation:...
Page 28
Note: Intel Burst Flash Operation Intel burst flash (such as the Intel 28FxxxK3, 28FxxxK18, and 28FxxxW18), requires the OMAP5910 FLASH.RDY pin to be pulled up instead of being tied to the flash’s WAIT pin. The traffic controller properly handles all timing requirements without the WAIT pin assertion.
Memory Interfaces 3.2.8 Asynchronous Write With WE Operation The asynchronous write is used for both file flash and burst flash devices. Figure 7 shows the timing diagram. Burst write operation is not supported. Figure 7. Asynchronous Write With WE Operation FLASH.CLK (internal) Address valid...
3.2.9 EMIFS Dual-Port RAM Interface Mode The OMAP5910 EMIFS includes a programmable mode associated with the FLASH.CS2 chip select pin to support external devices that require a valid flash address before chip select is active. An example of such a device is a dual port RAM (DPRAM).
EMIFF Priority Handler This memory interface has two software-selectable priority algorithms for resolving simultaneous access requests: least recently used and dynamic priority. The priority scheme is shared with the EMIFS and IMIF and it is set in OMAP5910 configuration registers (bit LRU_SEL FUNC_MUX_CTRL_0).
Memory Interfaces The low-priority queue order is: Local bus DMA (all channels including LCD) The high-priority queue order is: DMA transfer involving LCD channel Local bus DMA transfer involving channels other than LCD channel Fixed priority is a special case of dynamic priority. To create a fixed priority, all time-out registers must have a value of 0.
MRS command on the pins of the SDRAM interface. When the command is issued, the content of the OMAP5910 MRS register is placed on the SDRAM address bus and latched by the SDRAM into its internal MRS register.
SDRAM. The OMAP5910 device can support subdividing the autorefresh of the SDRAM into bursts of 1, 4, or 8 rows. It is recommended to set this parameter to 8 rows.
Memory Interfaces beyond 64 milliseconds, and the SDRAM controller does not autorefresh during reset, data is corrupted. Setting the RFRSH_RST bit in the EMIF fast interface SDRAM configuration register 2 (EMIFF_SDRAM_CONFIG_2) avoids SDRAM data corruption for this case by automatically placing the SDRAM in self-refresh mode prior to warm reset being applied to the traffic controller.
Memory Interfaces Figure 8. SDRAM Write Single 32-Bit Word With Burst Stop ACTV0 WRITE STOP ACCESS_REG ACCESS_GRANT COMMAND ADDRESS B0/R0 B0/C0 Ignored C0+1 C0+2 CURRENT_COL C0+1 CURRENT_SIZE DVALID SAVE_ADD LAST_DATE WRITE (burst reduced to 2) is interrupted by a STOP command because no new request is pending. Note: SPRU673 Memory Interface Traffic Controller...
Memory Interfaces Figure 11. SDRAM Read Single 16-Bit Half-Word With Burst Stop ACTV0 READ STOP ACCESS_REG ACCESS_GRANT COMMAND ADDRESS B0/R0 B0/C0 L = 3 C0+1 CURRENT_COL CURRENT_SIZE DVALID SAVE_ADD LAST_DATE READ (burst reduced to 1) is interrupted by a STOP command because no new request is pending. Note: Memory Interface Traffic Controller SPRU673...
Memory Interfaces Figure 16. SDRAM Read Single Half-Word Followed by a Write Byte ACTV0 READ ACTV0 WRIT STOP ACCESS_REG ACCESS_GRANT COMMAND ADDRESS B0/R0 B0/C0 B0/R0 B0/R5 B0/C5 L = 3 DQMU DQMx DQML C0+1 C5+1 CURRENT_COL CURRENT_SIZE DVALID SAVE_ADD LAST_DATE READ (burst reduced to 1) is followed by a single-byte WRITE in the same bank but on a different page.
Traffic Controller Memory Interface Registers Table 11. EMIF Slow Priority Register (EMIFS_PRIO) Reset Value Field Description Access 31−16 Reserved Reserved. These pins must always be written as 0. All 0s 15−12 LB host: Number of consecutive transfers while other ports are 0000 waiting + 1.
Traffic Controller Memory Interface Registers Table 13. EMIF Slow Interface Configuration Register (EMIFS_CONFIG_REG) Reset Value Field Value Description Access 31−5 Reserved Read is undefined. Writes must be zero. All 0 Ready signal. This bit is a copy of the FLASH.RDY input pin as sampled by TC clock.
31−22 Reserved Read is undefined. Writes must be zero. All 0 Specifies how EMIFS handles addressing when performing 32-bit writes to the OMAP5910 16-bit data bus. The address is incremented for the second 16-bit access (default). The address is not incremented for the second 16-bit access.
Traffic Controller Memory Interface Registers Table 14. EMIF Slow Chip-Select Configuration Registers (EMIFS_CS0_CONFIG...EMIFS_CS3_CONFIG) (Continued) Reset Value Field Value Description Access Reserved Read is undefined. Writes must be zero. Retiming control register: The data is not retimed. The data coming from the external bus is retimed with the CLK.
Traffic Controller Memory Interface Registers Table 16. Wait Cycles Insertion RDWST Number of Cycles Inserted There is no automatic hardware adjustment of the programmed latencies when the system clock frequency changes. The following restrictions apply when synchronous burst read Intel protocol is selected: Only full-page burst mode is supported Only sequential data access order is supported...
Page 55
Traffic Controller Memory Interface Registers Table 17. EMIF Fast Interface SDRAM Configuration Register 1 (EMIFF_SDRAM_CONFIG) (Continued) Reset Value Field Value Description Access SDRAM power-down enable. Controls power-down state of SDRAM interface: SDRAM interface is not powered down. SDRAM interface is powered down. PWD is one of the prerequisites to meet TC idle.
SDRAM. Data from SDRAM is double buffered. Data is first clocked on return clock from SDRAM, then with the OMAP5910 internal SDRAM clock. SLRF When set, places the SDRAM in self-refresh mode. Mode is automatically exited upon the generation of any SDRAM access.
Page 57
Traffic Controller Memory Interface Registers Table 18. SDRAM Internal Organization (Continued) Memory Size Number Of (M Bits) Banks SDRAM_TYPE Size Of Data Bus † 1010 1011 † 1100 1101 † 1110 1111 † Unavailable bank number (not supported). Do not use this setting. Table 19.
Reserved (must be set to 111, only full page burst length is supported). When the CONF_MOD_EMRS_CTRL bit field (bit 13) of the OMAP5910 control register (MOD_CONF_CTRL_0) is Note: set, the device reconfigures bank settings to write out the EMIFF_MRS register as EMRS commands (see Table 22).
Traffic Controller Memory Interface Registers Table 22. EMIF Fast Interface SDRAM MRS Register—EMRS Mode (EMIFF_MRS) Reset Value Field Value Description Access 31−5 Reserved Read is undefined. Writes must be zero. Note 1 4−3 TCSR SDRAM EMRS register temperature compensated self-refresh setting: Note 1 70 degrees Celsius maximum case temperature 45 degrees Celsius maximum case temperature...
Traffic Controller Memory Interface Registers Table 23. Time-Out 1 Register (TIMEOUT1) Reset Value Field Description Access 31−24 Reserved Read is undefined. Writes must be zero. All 0 23−16 Local bus 0x00 15:8 Reserved Read is undefined. Writes must be zero. All 0 0x00 Table 24.
Page 62
Traffic Controller Memory Interface Registers Table 27. EMIF Fast Interface SDRAM Configuration Register 2 (EMIFF_SDRAM_CONFIG_2) Reset Value Field Value Description Access 31−2 Reserved Read is undefined. Writes must be zero. All 0 RFRSH_ SDRAM self-refresh on warm reset. RFRSH_RST determines what action the TC SDRAM controller takes toward setting SDRAM to self-refresh mode in the event of a warm system reset.
Interfacing Memories With the OMAP5910 Device This section provides two examples of how to connect memories to the OMAP5910 device. Many scenarios can be considered using different kinds of memories. For flash memories, Intel and Hitachi products are used. For SDRAM and SRAM, Hitachi and Toshiba products are used, respectively.