Event Compile.AddVar - Revision history

Wiki bot at 12:32, 16 January 2023

2023-01-16T12:32:01Z

2023-01-16T12:25:32Z

2023-01-16T12:12:28Z

2023-01-16T11:55:38Z

2023-01-16T11:42:10Z

2014-01-23T11:24:40Z

Examples

2014-01-22T16:39:45Z

Examples

2014-01-22T16:12:57Z

Examples

2014-01-22T16:00:33Z

Examples

2014-01-22T15:59:54Z

Examples

@@ Line 24: / Line 24: @@
 | width="10%" align="center" style="border-top: 2px solid #000;" | [[File:Fc9-u32-icon.png]] - ULONG
 | width="90%" style="border-top: 2px solid #000;" | ''Return''
 | colspan="2" | Non-zero to include definition - initialised on call&nbsp;
 |}

@@ Line 22: / Line 22: @@
 | colspan="2" | The expanded string to inline to the code&nbsp;
 |-
-| width="10%" align="center" style="border-top: 2px solid #000;" | [[File:Fc9-void-icon.png]] - Non-zero to include definition - initialised on call
+| width="10%" align="center" style="border-top: 2px solid #000;" | [[File:Fc9-u32-icon.png]] - ULONG
 | width="90%" style="border-top: 2px solid #000;" | ''Return''
 |}

← Older revision		Revision as of 12:12, 16 January 2023
Line 25:		Line 25:
	\| width="90%" style="border-top: 2px solid #000;" \| ''Return''		\| width="90%" style="border-top: 2px solid #000;" \| ''Return''
	\|}		\|}
		+
		+
		+	Details on using Event Macros can be found here: [[Simulation Events\|Event Macros]]

← Older revision		Revision as of 11:55, 16 January 2023
Line 28:		Line 28:

	==Detailed description==		==Detailed description==
−	~~''<span style="color:red;">No additional information</span>''~~	+

@@ Line 1: / Line 1: @@
-<sidebar>Event Contents</sidebar>
+{| class="wikitable" style="width:60%; background-color:#FFFFFF;"
-Sent to a component to allow dynamic amendment of global constant declarations
+|-
+| width="10%" align="center" style="background-color:#D8C9D8;" align="center" | [[File:Fc9-comp-macro.png]]
-This event is part of the [[Event class Compile|Compile]] class
+| width="90%" style="background-color:#D8C9D8; color:#4B008D;" | '''AddVar'''
+|-
-__TOC__
+| colspan="2" | Sent to a component to allow dynamic amendment of global constant declarations&nbsp;
+|-
-==Parameters==
+|-
-[[Variable Types|STRING]] ''VarName''
+| width="10%" align="center" | [[File:Fc9-string-icon.png]] - STRING
-:The original Flowcode variable
+| width="90%" | VarName
+|-
-[[Variable Types|STRING]] ''ExpandName''
+| colspan="2" | The original Flowcode variable&nbsp;
-:The expanded variable name
+|-
+| width="10%" align="center" | [[File:Fc9-string-icon.png]] - STRING
-[[Variable Types|STRING]] ''Expansion''
+| width="90%" | ExpandName
-:The expanded string to inline to the code
+|-
-:''This parameter is returned back to Flowcode''
+| colspan="2" | The expanded variable name&nbsp;
+|-
+| width="10%" align="center" | [[File:Fc9-string-icon.png]] - STRING
-==Return value==
+| width="90%" | Expansion
-[[Variable Types|ULONG]]
+|-
-Non-zero to include definition - initialised on call
+| colspan="2" | The expanded string to inline to the code&nbsp;

← Older revision		Revision as of 11:24, 23 January 2014
Line 98:		Line 98:
	Here is the file as a demonstration.		Here is the file as a demonstration.

−	~~[[File:~~FarMem.fcfx]]	+	{{fcfile\|FarMem.fcfx\|Far Mem demo}}

← Older revision		Revision as of 16:39, 22 January 2014
Line 31:		Line 31:

	On some PIC devices there are sometimes two types of RAM memory due to bus limitations, near and far. Near memory is fast to access but is limited by the size of the internal bus. Far memory is much less limited but means additional overhead when fetching or storing values.		On some PIC devices there are sometimes two types of RAM memory due to bus limitations, near and far. Near memory is fast to access but is limited by the size of the internal bus. Far memory is much less limited but means additional overhead when fetching or storing values.
		+
		+
		+
		+	[[File:FarMem.jpg]]
		+

@@ Line 37: / Line 37: @@
-C:\Users\BenR\Desktop\FarMem.o: Link Error: Could not allocate section .nbss, size = 4118 bytes, attributes = bss near
+'''C:\Users\BenR\Desktop\FarMem.o: Link Error: Could not allocate section .nbss, size = 4118 bytes, attributes = bss near'''
-Link Error: Could not allocate data memory
+'''Link Error: Could not allocate data memory'''
@@ Line 47: / Line 47: @@
-__attribute__((far)) unsigned char data[4096];
+'''__attribute__((far)) unsigned char data[4096];'''
@@ Line 55: / Line 55: @@
-MX_GLOBAL MX_UINT8 FCV_DATA[FCVsz_DATA]; // Large Data Array
+'''MX_GLOBAL MX_UINT8 FCV_DATA[FCVsz_DATA]; // Large Data Array'''
@@ Line 75: / Line 75: @@
-__attribute__((far)) MX_GLOBAL MX_UINT8 FCV_DATA[FCVsz_DATA]; // Large Data Array
+'''__attribute__((far)) MX_GLOBAL MX_UINT8 FCV_DATA[FCVsz_DATA]; // Large Data Array'''
@@ Line 83: / Line 83: @@
-Total data memory used (bytes):         0x1116  (4374) 15%''
+'''Total data memory used (bytes):         0x1116  (4374) 15%'''
-...
+'''...'''
-HEX file creation successful!
+'''HEX file creation successful!'''

@@ Line 34: / Line 34: @@
 When creating Flowcode variables these will default to being stored in near memory to optimise the time to fetch and store values. If you run out of room in near memory then you may get a message like this during compilation.
@@ Line 39: / Line 40: @@
 Link Error: Could not allocate data memory
 To tell the compiler to move the variable into FAR memory in C you would do something like this.
 __attribute__((far)) unsigned char data[4096];
 The Flowcode variable defaults to something like this.
 MX_GLOBAL MX_UINT8 FCV_DATA[FCVsz_DATA]; // Large Data Array
@@ Line 66: / Line 72: @@
 After saving the project and refreshing the C code window the variable now looks like this.
 __attribute__((far)) MX_GLOBAL MX_UINT8 FCV_DATA[FCVsz_DATA]; // Large Data Array
@@ Line 74: / Line 82: @@
 Total data memory used (bytes):         0x1116  (4374) 15%''
@@ Line 87: / Line 88: @@
 HEX file creation successful!

← Older revision		Revision as of 15:59, 22 January 2014
Line 75:		Line 75:

	section address alignment gaps total length (dec)		section address alignment gaps total length (dec)
−
−	~~------- ------- -------------- -------------------~~

	.nbss 0x1000 0 0x16 (22)		.nbss 0x1000 0 0x16 (22)