SPRUGR9H November 2010 – April 2015 66AK2E05 , 66AK2H06 , 66AK2H12 , 66AK2H14 , 66AK2L06 , AM5K2E02 , AM5K2E04 , SM320C6678-HIREL , TMS320C6652 , TMS320C6654 , TMS320C6655 , TMS320C6657 , TMS320C6670 , TMS320C6671 , TMS320C6672 , TMS320C6674 , TMS320C6678
The registers in this region program one of the queue manager’s descriptor memory regions.
NOTE
Software must assure that all three Descriptor Memory Setup Region registers are initialized prior to pushing and popping descriptors addressed in the region. If modifying a single region during runtime, it is good practice to write a zero to the Memory Region R Base Address Register first when disabling the region, and last (with a valid global address) when enabling the region.
Offset | Name | Description |
---|---|---|
0x00000000 +
16 × R |
Memory Region R Base Address Register (0...19, or 0...63 for KeyStone II) | The Memory Region R Base Address Register is written by the host to set the base address of memory region R. This memory region will store a number of descriptors of a particular size as determined by the Memory Region R Control Register. |
0x00000004 +
16 × R |
Memory Region R Start Index Register (0...19, or 0...63 for KeyStone II) | The Memory Region R Start Index Register is written by the host to configure index of the first descriptor in this memory region. |
0x00000008 +
16 × R |
Memory Region R Descriptor Setup Register (0...19, or 0...63 for KeyStone II) | The Memory Region R Descriptor Setup Register is written by the host to configure various descriptor related parameters of this memory region. |
NOTE
Memory regions and packet descriptors must be aligned to 16 byte boundaries. For performance reasons, it is preferable to align descriptors and data buffers to 64 byte boundaries if they are larger than 32 bytes. This allows data to flow through the chip with the fewest bus transactions.