|
|
|
| R2012a Documentation → Embedded Coder | |
Learn more about Embedded Coder |
|
| Contents | Index |
Embedded Coder/ Embedded Targets/ Processors/ Texas Instruments C6000/ C6455 EVM
SRIO transmit blocks add the ability to transmit SRIO packets to another processor. Each transmit block has an input Ptr port, and an optional Stat output port controlled by the Show output port for status option.
Writing data between DSPs is more efficient than reading because SRIO write can handle up to 4kB per write request without stalling the processor while SRIO read only handles up to 256 bytes per read request. Thus, the time needed to transfer data by reading from the remote device can be much longer than that required for writing from the remote device. SRIO read may require multiple requests. Use the doorbell interrupt options signal remote devices and to coordinate the data transfer between the processors.
The Stat port reports SRIO operating status as shown in the following table.
| Value at Stat Port | Description |
|---|---|
| 1 | SRIO request is done (success) |
| 0 | SRIO request is pending |
| -1 | SRIO request failed |
| -2 | SRIO request was not sent because the SRIO request queue is full |
To see the SRIO blocks in use, refer to the Interprocessor Communications via Serial Rapid I/O (SRIO) demo in the online help system demos for Embedded Coder software.
Enter the ID of the remote device in 16-bit hexadecimal format to configure the remote ID field in the generated code. When you configure SRIO Transmit blocks for this communication link, the remote device ID in this field must match the local device ID for the SRIO Config block on the receiving end of the transmission.
Enables the doorbell interrupt operation for the bloc, which sends a doorbell interrupt after writing data to the remote device. Selecting this option enables Doorbell interrupt ID.
Sets the interrupt ID for the doorbell to set the doorbell INFO field of the SRIO packet. Select a value from the list. If your model contains more than one SRIO transmit block, each transmit block must use a different ID. IDs range from 0 to 15 with a default value of 0. SRIO Receive and SRIO Transmit blocks are paired together by this ID. Create an SRIO Receive block with this ID to receive the doorbell interrupt. The block uses this value to set the doorbell INFO field in an SRIO packet.
Selecting this option tells the block to perform a burst write using Direct IO to the device at the address in Remote device ID. If you clear this option, you must select Send doorbell interrupt to remote device. Selecting this option enables the Remote address (32-bit hex aligned to an 8–byte boundary option.
Enter the address to write the output data to at the remote device.
Clearing Write to remote device disables this option. It becomes and do not care field.
For efficient data transfers, enter an address that aligns to an 8–byte boundary in memory.
Select this option to enable you to specify the local address for the input data to this block. Select his option if you are pairing this block with an SRIO Receive block that performs burst-read operation. The SRIO Receive block needs to know the specific address to read the data from. When you select this option, you enable Local address (32-bit hex aligned to an 8 byte boundary) where you enter the local address.
This address specifies the location of the incoming data. For burst write operations, this value is a local address that SRIO uses to form the direct I/O packets.
For efficient data transfers, enter an address that aligns to an 8–byte boundary in memory.
When you select this parameter, the output port Stat appears on the block. Stat returns the status of the write transmit operation.
For more information about SRIO, refer to TMS320TCI648x Serial RapidIO User's Guide, Literature Number: SPRUE13. Texas Instruments Incorporated.
Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.
| © 1984-2012- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |
