Using a Custom Bitfile in C Code - Revision history

Cnel711: /* Reusing Code */

2012-09-13T00:57:05Z

Reusing Code

← Older revision		Revision as of 00:57, 13 September 2012
Line 8:		Line 8:
	Don't copy and paste your code to use with Convey; instead, use the __CONVEY preprocessor directive (the cnycc compiler always defines __CONVEY). You can then compile the same source code with both gcc and cnycc. For example:		Don't copy and paste your code to use with Convey; instead, use the __CONVEY preprocessor directive (the cnycc compiler always defines __CONVEY). You can then compile the same source code with both gcc and cnycc. For example:

	<nowiki>		<nowiki>
	#ifdef __CONVEY		#ifdef __CONVEY
	int *bigarray = cny_cp_malloc(10000);		int *bigarray = cny_cp_malloc(10000);

Cnel711 at 00:56, 13 September 2012

2012-09-13T00:56:46Z

← Older revision		Revision as of 00:56, 13 September 2012
Line 4:		Line 4:

	If you want to pass parameters to your function call, you use an assembly file to marshal registers back and forth between the processor's registers (starting at A8) and the coprocessor's AEG registers. If you must pass a lot of data, it's better to pass a pointer to the data and allocate memory on the coprocessor board.		If you want to pass parameters to your function call, you use an assembly file to marshal registers back and forth between the processor's registers (starting at A8) and the coprocessor's AEG registers. If you must pass a lot of data, it's better to pass a pointer to the data and allocate memory on the coprocessor board.

			=== Reusing Code ===
			Don't copy and paste your code to use with Convey; instead, use the __CONVEY preprocessor directive (the cnycc compiler always defines __CONVEY). You can then compile the same source code with both gcc and cnycc. For example:

			<nowiki>
			#ifdef __CONVEY
			int *bigarray = cny_cp_malloc(10000);
			#else
			int *bigarray = malloc(10000);
			#endif
			</nowiki>

	=== Getting the Signature ===		=== Getting the Signature ===

Cnel711: /* Getting the Signature */

2012-02-27T16:19:27Z

Getting the Signature

← Older revision		Revision as of 16:19, 27 February 2012
Line 7:		Line 7:
	=== Getting the Signature ===		=== Getting the Signature ===
	The standard way to get a signature is using:		The standard way to get a signature is using:
			<nowiki>
	cny_image_t sig1, sig2;		cny_image_t sig1, sig2;
	int stat;		int stat;
Line 15:		Line 15:
	else		else
	fprintf(stderr, "ERROR: cny_get_signature not found\n");		fprintf(stderr, "ERROR: cny_get_signature not found\n");
			</nowiki>

	* '''stat''' returns 0 on success		* '''stat''' returns 0 on success

Cnel711: /* Getting the Signature */

2012-02-27T16:19:09Z

Getting the Signature

← Older revision		Revision as of 16:19, 27 February 2012
Line 10:		Line 10:
	cny_image_t sig1, sig2;		cny_image_t sig1, sig2;
	int stat;		int stat;

	if (cny_get_signature)		if (cny_get_signature)
	cny_get_signature("your personality name", &sig1, &sig2, &stat);		cny_get_signature("your personality name", &sig1, &sig2, &stat);

Cnel711: /* Getting the Signature */

2012-02-27T16:19:01Z

Getting the Signature

← Older revision		Revision as of 16:19, 27 February 2012
Line 7:		Line 7:
	=== Getting the Signature ===		=== Getting the Signature ===
	The standard way to get a signature is using:		The standard way to get a signature is using:
	~~char * personality_name = "yourpersonalityname";~~
	cny_image_t sig1, sig2;		cny_image_t sig1, sig2;
	int stat;		int stat;
	if (cny_get_signature)		if (cny_get_signature)
	cny_get_signature(personality, &sig1, &sig2, &stat);		cny_get_signature("your personality name", &sig1, &sig2, &stat);
	else		else
	fprintf(stderr, "ERROR: cny_get_signature not found\n");		fprintf(stderr, "ERROR: cny_get_signature not found\n");

Cnel711: /* References */

2012-02-21T03:40:42Z

References

← Older revision		Revision as of 03:40, 21 February 2012
Line 55:		Line 55:

	== References ==		== References ==
	* [[Media:ConveyPDKReferenceManual.pdf \| Convey PDK Reference Manual (.pdf)]] - Appendix D
	* [[Media:ConveyProgrammersGuide.pdf \| Convey Programmers Guide (.pdf)]] - Chapter 9 and Appendix G		* [[Media:ConveyProgrammersGuide.pdf \| Convey Programmers Guide (.pdf)]] - Chapter 9 and Appendix G

Cnel711 at 23:15, 20 February 2012

2012-02-20T23:15:56Z

@@ Line 28: / Line 28: @@
   act_sum = l_copcall_fmt(sig1, cpVadd, "AAAA", a1, a2, a3, size);
-In this case, the 'l' at the beginning of l_copcall_fmt means the return type is a long (64 bits).  The first two arguments are always (1) the bitfile signature and (2) a assembly function name.  The third argument lists the type and number of optional arguments that are passed and whether the get stored in the application hub's A or S registers.  For example, "AAAA" means there are 4 long (64 bit) variables that are stored starting in register A8; suitable for the address of a location in the coprocessor's memory system.
+The first two arguments are always (1) the bitfile signature and (2) a assembly function name.  The third argument lists the type and number of optional arguments that are passed and whether the get stored in the application hub's A or S registers.  For example, "AAAA" means there are 4 long (64 bit) variables that are stored starting in register A8; suitable for the address of a location in the coprocessor's memory system.
 == References ==
 * [[Media:ConveyPDKReferenceManual.pdf | Convey PDK Reference Manual (.pdf)]] - Appendix D
 * [[Media:ConveyProgrammersGuide.pdf | Convey Programmers Guide (.pdf)]] - Chapter 9 and Appendix G

Cnel711: /* Making a Coprocessor Call */

2012-02-16T05:09:25Z

Making a Coprocessor Call

← Older revision		Revision as of 05:09, 16 February 2012
Line 28:		Line 28:
	act_sum = l_copcall_fmt(sig1, cpVadd, "AAAA", a1, a2, a3, size);		act_sum = l_copcall_fmt(sig1, cpVadd, "AAAA", a1, a2, a3, size);

	In this case, the l at the beginning of l_copcall_fmt means the return type is a long (64 bits). The first two arguments are always (1) the bitfile signature and (2) a assembly function name. The third argument lists the type and number of optional arguments that are passed ~~(starting at register A8)~~. For example, "AAAA" means there are 4 long variables ~~passed to~~ the coprocessor ~~call~~.		In this case, the 'l' at the beginning of l_copcall_fmt means the return type is a long (64 bits). The first two arguments are always (1) the bitfile signature and (2) a assembly function name. The third argument lists the type and number of optional arguments that are passed and whether the get stored in the application hub's A or S registers. For example, "AAAA" means there are 4 long (64 bit) variables that are stored starting in register A8; suitable for the address of a location in the coprocessor's memory system.

	== References ==		== References ==
	* [[Media:ConveyPDKReferenceManual.pdf \| Convey PDK Reference Manual (.pdf)]] - Appendix D		* [[Media:ConveyPDKReferenceManual.pdf \| Convey PDK Reference Manual (.pdf)]] - Appendix D
	* [[Media:ConveyProgrammersGuide.pdf \| Convey Programmers Guide (.pdf)]] - Chapter 9 and Appendix G		* [[Media:ConveyProgrammersGuide.pdf \| Convey Programmers Guide (.pdf)]] - Chapter 9 and Appendix G

Cnel711: /* Making a Coprocessor Call */

2012-02-15T21:02:26Z

Making a Coprocessor Call

← Older revision		Revision as of 21:02, 15 February 2012
Line 26:		Line 26:
	=== Making a Coprocessor Call ===		=== Making a Coprocessor Call ===
	The vector adder example uses:		The vector adder example uses:
	act_sum = l_copcall_fmt(~~sig~~, cpVadd, "AAAA", a1, a2, a3, size);		act_sum = l_copcall_fmt(sig1, cpVadd, "AAAA", a1, a2, a3, size);

	In this case, the l at the beginning of l_copcall_fmt means the return type is a long (64 bits). The first two arguments are always (1) the bitfile signature and (2) a assembly function name. The third argument lists the type and number of optional arguments that are passed (starting at register A8). For example, "AAAA" means there are 4 long variables passed to the coprocessor call.		In this case, the l at the beginning of l_copcall_fmt means the return type is a long (64 bits). The first two arguments are always (1) the bitfile signature and (2) a assembly function name. The third argument lists the type and number of optional arguments that are passed (starting at register A8). For example, "AAAA" means there are 4 long variables passed to the coprocessor call.

Cnel711 at 21:02, 15 February 2012

2012-02-15T21:02:04Z

← Older revision		Revision as of 21:02, 15 February 2012
Line 1:		Line 1:
	~~My current understanding is that~~ running a routine on the coprocessor requires two parts:		In the simplest form, running a routine on the coprocessor requires two parts:
	* A call to the '''cny_get_signature''' function to get the signature of the custom personality you created		* A call to the '''cny_get_signature''' function to get the signature of the custom personality (bitfile) you created
	* A ~~cny~~ coprocessor funcation call (ex: l_copcall_fmt, d_copcall_fmt, etc)		* A coprocessor funcation call (ex: l_copcall_fmt, d_copcall_fmt, etc)

	If you want to pass parameters to your function call, ~~the vector adder set the standard of using~~ an assembly file to marshal registers back and forth between the processor / coprocessor, ~~though there may be other ways~~.		If you want to pass parameters to your function call, you use an assembly file to marshal registers back and forth between the processor's registers (starting at A8) and the coprocessor's AEG registers. If you must pass a lot of data, it's better to pass a pointer to the data and allocate memory on the coprocessor board.

	=== Getting the Signature ===		=== Getting the Signature ===
	~~cny_image_t sig2~~;		The standard way to get a signature is using:
	cny_image_t ~~sig~~;		char * personality_name = "yourpersonalityname";
			cny_image_t sig1, sig2;
	int stat;		int stat;
	if (cny_get_signature)		if (cny_get_signature)
	cny_get_signature(~~"your custom~~ personality ~~name"~~, &~~sig~~, &sig2, &stat);		cny_get_signature(personality, &sig1, &sig2, &stat);
	else		else
	fprintf(stderr,"ERROR: cny_get_signature not found\n");		fprintf(stderr, "ERROR: cny_get_signature not found\n");

			* '''stat''' returns 0 on success
			* '''sig1''' is required, and contains a 64 bit signature for your custom bitfile/personality/AE.
			* '''sig2''' is not used, but may have use in the future.

	=== Allocated Memory on the Coprocessor Board ===		=== Allocated Memory on the Coprocessor Board ===
	System memory and memory used for the coprocessor are physically separate. In the example C file, function calls such as '''cny_cp_malloc''' and '''ny_cp_posix_memalign'''.		System memory and memory used for the coprocessor are physically separate. In the example C file, function calls such as '''cny_cp_malloc''' and '''ny_cp_posix_memalign''' are used to allocate memory on the coprocessor.

	See: [[Media:ConveyProgrammersGuide.pdf \| Convey Programmers Guide (.pdf)]] - Chapter 9		See: [[Media:ConveyProgrammersGuide.pdf \| Convey Programmers Guide (.pdf)]] - Chapter 9