Studio:SCL Structure - Revision history

Timd: Text replace - 'Category: SCL' to 'Category:Studio:SCL'

2009-08-21T00:10:33Z

Text replace - 'Category: SCL' to 'Category:Studio:SCL'

← Older revision		Revision as of 00:10, 21 August 2009
Line 148:		Line 148:
	* Refer to the SCL Wizard section of the STRIDE Online Help for information on how to create SCL pragmas.		* Refer to the SCL Wizard section of the STRIDE Online Help for information on how to create SCL pragmas.

	[[Category: SCL]]		[[Category:Studio:SCL]]

Timd: SCL Structure moved to Studio:SCL Structure

2009-08-18T22:48:14Z

SCL Structure moved to Studio:SCL Structure

← Older revision	Revision as of 22:48, 18 August 2009
(No difference)

Ivailop: /* See Also */

2008-10-02T17:48:07Z

Ivailop: /* Access Class (AC) Attributes */

2008-10-02T00:01:42Z

Access Class (AC) Attributes

Ivailop: /* See Also */

2008-08-06T00:56:52Z

Stevel at 18:04, 16 July 2008

2008-07-16T18:04:13Z

← Older revision		Revision as of 18:04, 16 July 2008
Line 146:		Line 146:
	* [[SCL_Pragmas]]		* [[SCL_Pragmas]]
	* Refer to the SCL Wizard section of the STRIDE Online Help for information on how to create SCL pragmas.		* Refer to the SCL Wizard section of the STRIDE Online Help for information on how to create SCL pragmas.

			[[Category: SCL_Reference]]

Stevel at 19:28, 15 July 2008

2008-07-15T19:28:17Z

← Older revision		Revision as of 19:28, 15 July 2008
Line 142:		Line 142:
	== STRIDE Trace Point ID (STPID) ==		== STRIDE Trace Point ID (STPID) ==
	The '''STPID''' consists of a unique 32-bit ID and an optional payload, and is used for trace points. The STPID value of zero (0) is reserved for the system. There are no constraints on different application threads using the same trace point. The trace point payload is used to define the format of the data associated with it. The only additional constraint unique to trace point payloads versus message payloads is that there is no support for embedded pointers. The memory block pointed to is not transferred over to the host Runtime environment. Trace points also use payloads to represent debug information that is being provided to the host Runtime environment.		The '''STPID''' consists of a unique 32-bit ID and an optional payload, and is used for trace points. The STPID value of zero (0) is reserved for the system. There are no constraints on different application threads using the same trace point. The trace point payload is used to define the format of the data associated with it. The only additional constraint unique to trace point payloads versus message payloads is that there is no support for embedded pointers. The memory block pointed to is not transferred over to the host Runtime environment. Trace points also use payloads to represent debug information that is being provided to the host Runtime environment.

			== See Also ==
			* [[SCL_Pragmas]]
			* Refer to the SCL Wizard section of the STRIDE Online Help for information on how to create SCL pragmas.

Stevel at 18:52, 15 July 2008

2008-07-15T18:52:42Z

← Older revision		Revision as of 18:52, 15 July 2008
Line 1:		Line 1:
			The STRIDE Communication Language (SCL) defines several identifiers and their formats that are required for remote function calls, messaging, and tracing operations.

	== The STRIDE Message ID (SMID) ==		== The STRIDE Message ID (SMID) ==
	The '''SMID''' is a 32-bit structure consisting of a unique ID and a set of message attributes. The STRIDE Communication Model (SCM) defines the [[#The_STRIDE_Unique_ID_.28SUID.29\|SUID]] portion as the first 24 bits of the SMID (bits 0 — 23), allowing unique identifiers up to 16,777,215. The message attributes use the highest 8 bits of the SMID (bits 24 — 31).		The '''SMID''' is a 32-bit structure consisting of a unique ID and a set of message attributes. The STRIDE Communication Model (SCM) defines the [[#The_STRIDE_Unique_ID_.28SUID.29\|SUID]] portion as the first 24 bits of the SMID (bits 0 — 23), allowing unique identifiers up to 16,777,215. The message attributes use the highest 8 bits of the SMID (bits 24 — 31).

Stevel at 18:47, 15 July 2008

2008-07-15T18:47:33Z

← Older revision		Revision as of 18:47, 15 July 2008
Line 1:		Line 1:
	== The STRIDE Message ID (SMID) ==		== The STRIDE Message ID (SMID) ==
	The '''SMID''' is a 32-bit structure consisting of a unique ID and a set of message attributes. The SCM defines the [[#The_STRIDE_Unique_ID_.28SUID.29\|SUID]] portion as the first 24 bits of the SMID (bits 0 — 23), allowing unique identifiers up to 16,777,215. The message attributes use the highest 8 bits of the SMID (bits 24 — 31).		The '''SMID''' is a 32-bit structure consisting of a unique ID and a set of message attributes. The STRIDE Communication Model (SCM) defines the [[#The_STRIDE_Unique_ID_.28SUID.29\|SUID]] portion as the first 24 bits of the SMID (bits 0 — 23), allowing unique identifiers up to 16,777,215. The message attributes use the highest 8 bits of the SMID (bits 24 — 31).

	Each SCL-compliant message within the system must be assigned a unique message ID.		Each SCL-compliant message within the system must be assigned a unique message ID.

Stevel at 18:38, 15 July 2008

2008-07-15T18:38:26Z

← Older revision		Revision as of 18:38, 15 July 2008
Line 1:		Line 1:
	== The STRIDE Message ID (SMID) ==		== The STRIDE Message ID (SMID) ==
	The SMID is a 32-bit structure consisting of a unique ID and a set of message attributes. The SCM defines the [[#The_STRIDE_Unique_ID_.28SUID.29\|SUID]] portion as the first 24 bits of the SMID (bits 0 — 23), allowing unique identifiers up to 16,777,215. The message attributes use the highest 8 bits of the SMID (bits 24 — 31).		The '''SMID''' is a 32-bit structure consisting of a unique ID and a set of message attributes. The SCM defines the [[#The_STRIDE_Unique_ID_.28SUID.29\|SUID]] portion as the first 24 bits of the SMID (bits 0 — 23), allowing unique identifiers up to 16,777,215. The message attributes use the highest 8 bits of the SMID (bits 24 — 31).

	Each SCL-compliant message within the system must be assigned a unique message ID.		Each SCL-compliant message within the system must be assigned a unique message ID.
Line 129:		Line 129:

	== The STRIDE Unique ID (SUID) ==		== The STRIDE Unique ID (SUID) ==
	The SUID is a unique 24-bit value used to identify interfaces such as remote function calls and messages. A SUID is required when using a two-way message in order to identify the message user and allow the response payload to be routed correctly. The message user provides this unique ID to the STRIDE Runtime, which in turn sends it to the message owner. The message owner is then required to supply this same unique ID when sending a response back to the STRIDE Runtime, so that the response payload can be routed correctly.		The '''SUID''' is a unique 24-bit value used to identify interfaces such as remote function calls and messages. A SUID is required when using a two-way message in order to identify the message user and allow the response payload to be routed correctly. The message user provides this unique ID to the STRIDE Runtime, which in turn sends it to the message owner. The message owner is then required to supply this same unique ID when sending a response back to the STRIDE Runtime, so that the response payload can be routed correctly.

	== STRIDE Transactor ID (STID) ==		== STRIDE Transactor ID (STID) ==
	The STID is a unique 8-bit value used to represent messaging and tracing operations associated with a native thread as defined by an operating system. STIDs provide a link between the STRIDE transactor and application native transactor IDs.		The '''STID''' is a unique 8-bit value used to represent messaging and tracing operations associated with a native thread as defined by an operating system. STIDs provide a link between the STRIDE transactor and application native transactor IDs.

	The STRIDE Runtime allocates resources for each STID created within the system, as well as configures the maximum size of a STID name (via #define srCFG_STID_NAME_SIZE in ''srcfg.h'') for the target.		The STRIDE Runtime allocates resources for each STID created within the system, as well as configures the maximum size of a STID name (via #define srCFG_STID_NAME_SIZE in ''srcfg.h'') for the target.
Line 139:		Line 139:

	== STRIDE Trace Point ID (STPID) ==		== STRIDE Trace Point ID (STPID) ==
	The STPID consists of a unique 32-bit ID and an optional payload, and is used for trace points. The STPID value of zero (0) is reserved for the system. There are no constraints on different application threads using the same trace point. The trace point payload is used to define the format of the data associated with it. The only additional constraint unique to trace point payloads versus message payloads is that there is no support for embedded pointers. The memory block pointed to is not transferred over to the host Runtime environment. Trace points also use payloads to represent debug information that is being provided to the host Runtime environment.		The '''STPID''' consists of a unique 32-bit ID and an optional payload, and is used for trace points. The STPID value of zero (0) is reserved for the system. There are no constraints on different application threads using the same trace point. The trace point payload is used to define the format of the data associated with it. The only additional constraint unique to trace point payloads versus message payloads is that there is no support for embedded pointers. The memory block pointed to is not transferred over to the host Runtime environment. Trace points also use payloads to represent debug information that is being provided to the host Runtime environment.

← Older revision		Revision as of 17:48, 2 October 2008
Line 148:		Line 148:
	* Refer to the SCL Wizard section of the STRIDE Online Help for information on how to create SCL pragmas.		* Refer to the SCL Wizard section of the STRIDE Online Help for information on how to create SCL pragmas.

	[[Category: ~~SCL_Reference~~]]		[[Category: SCL]]

← Older revision		Revision as of 00:01, 2 October 2008
Line 95:		Line 95:

	The following is an excerpt of the installed header file, ''sr.h'', showing the definitions of the SMID attributes:		The following is an excerpt of the installed header file, ''sr.h'', showing the definitions of the SMID attributes:
			<source lang=c>
	/* Message Types (MT) */		/* Message Types (MT) */
	#define srMT_ONE_CMD 0x00000000		#define srMT_ONE_CMD 0x00000000
	#define srMT_ONE_RSP 0x01000000		#define srMT_ONE_RSP 0x01000000
	#define srMT_TWO 0x02000000		#define srMT_TWO 0x02000000
	#define srMT_BRD 0x03000000		#define srMT_BRD 0x03000000

	/* Abbreviations MT */		/* Abbreviations MT */
	#define srMT_ONE srMT_ONE_CMD		#define srMT_ONE srMT_ONE_CMD
	#define srMT_ONEc srMT_ONE_CMD		#define srMT_ONEc srMT_ONE_CMD
	#define srMT_ONEr srMT_ONE_RSP		#define srMT_ONEr srMT_ONE_RSP

	/* Send Type for Command (ST_CMD) */		/* Send Type for Command (ST_CMD) */
	#define srST_CMD_PTR 0x00000000		#define srST_CMD_PTR 0x00000000
	#define srST_CMD_VAL 0x04000000		#define srST_CMD_VAL 0x04000000

	/* Send Type for Response (ST_RSP) */		/* Send Type for Response (ST_RSP) */
	#define srST_RSP_PTR 0x00000000		#define srST_RSP_PTR 0x00000000
	#define srST_RSP_VAL 0x08000000		#define srST_RSP_VAL 0x08000000

	/* Pointer Usage for Command (PU_CMD) */		/* Pointer Usage for Command (PU_CMD) */
	#define srPU_CMD_POL 0x00000000		#define srPU_CMD_POL 0x00000000
	#define srPU_CMD_PRI 0x10000000		#define srPU_CMD_PRI 0x10000000

	/* Pointer Usage for Response (PU_RSP) */		/* Pointer Usage for Response (PU_RSP) */
	#define srPU_RSP_POL 0x00000000		#define srPU_RSP_POL 0x00000000
	#define srPU_RSP_PRI 0x20000000		#define srPU_RSP_PRI 0x20000000

	/* Access Class (AC) */		/* Access Class (AC) */
	#define srAC_MSG 0x00000000		#define srAC_MSG 0x00000000
	#define srAC_FUNCTION 0x40000000		#define srAC_FUNCTION 0x40000000
	#define srAC_SYS 0x80000000		#define srAC_SYS 0x80000000
			</source>

	Refer to the [[http://www.s2technologies.com/pdf/s2sRuntime.pdf STRIDE Runtime Developer's Guide]] for additional information and usage of these definitions.		Refer to the [http://www.s2technologies.com/pdf/s2sRuntime.pdf STRIDE Runtime Developer's Guide] for additional information and usage of these definitions.

	== The STRIDE Unique ID (SUID) ==		== The STRIDE Unique ID (SUID) ==

← Older revision		Revision as of 00:56, 6 August 2008
Line 144:		Line 144:

	== See Also ==		== See Also ==
	* [[SCL_Pragmas]]		* [[SCL_Pragmas\|SCL Pragmas]]
	* Refer to the SCL Wizard section of the STRIDE Online Help for information on how to create SCL pragmas.		* Refer to the SCL Wizard section of the STRIDE Online Help for information on how to create SCL pragmas.

	[[Category: SCL_Reference]]		[[Category: SCL_Reference]]