Compiling a Flowchart to a Chip - Revision history

MartinW: /* Compiling to Chip */

2023-10-05T13:52:42Z

Compiling to Chip

2023-10-05T13:23:06Z

Compile to Hex

2023-10-05T13:15:24Z

Compile to Hex

2023-10-05T13:13:19Z

Compile to C

2019-07-02T08:24:32Z

2016-07-06T10:36:43Z

2014-03-07T17:09:22Z

2013-09-24T08:03:30Z

2013-09-05T10:58:33Z

2013-09-05T10:51:26Z

@@ Line 47: / Line 47: @@
 ==Compiling to Chip==
-Unlike the previous two methods Compile to chip actually programs the chip after compiling the machine code file.
+Unlike the previous two methods Compile to target actually programs the chip after compiling the machine code file.
-Compile to chip compiles the Flowchart to C code, then ASM code, then assembles the ASM to Machine code and launches the Programmer application to download the program into the chip.
+Compile to chip compiles the Flowchart to C code to Machine code and launches the Programmer application to download the program into the chip.
@@ Line 56: / Line 56: @@
 Flowcharts must be saved before they can be transferred and Flowcode will prompt you if this is the case.
-You can also use the 'Compile to Chip' [[File:CompileToChip.png|border]] icon on the toolbar.
+You can also use the 'Compile to Chip' [[File:CompileToChip.png|border]] icon on the ribbon.
@@ Line 65: / Line 65: @@
 If the compiler detects any errors during compilation, these errors will be displayed within the [[Using the Icon Lists Pane|Icon Lists]] panel.
 ====Compiling with non standard applications====
 Flowcode is optimized for use with the Microchip XC8 (PIC8), Microchip XC16 (PIC16), Microchip XC32 (PIC32) and GCC compilers (AVR, ARM). The C code generated may not be appropriate for other compilers.

@@ Line 36: / Line 36: @@
 Compiles the Flowchart to C code and then compiles the C code to Assembly and Machine code.
 The resulting machine code file is also saved in the program directory with a .hex, .s19 or .bin extension.
 Select the 'Compile to HEX' option from the 'Build' menu (Build > Compile to HEX...).
@@ Line 46: / Line 43: @@
 Flowcharts must be saved before they can be transferred and Flowcode will prompt you if this is the case.
-You can also use the 'Compile to HEX' [[File:CompileToHex.png|border]] icon on the toolbar.
+You can also use the 'Compile to HEX' [[File:CompileToHex.png|border]] icon on the Ribon.
 ==Compiling to Chip==

@@ Line 48: / Line 48: @@
 You can also use the 'Compile to HEX' [[File:CompileToHex.png|border]] icon on the toolbar.
-If the program has already been compiled and the flowchart has not been edited then you can force a re-compilation by holding down the left shift button while clicking the 'Compile to HEX' icon on the toolbar.
+If the program has already been compiled and the flowchart has not been edited then you can force a re-compilation by holding down the left shift button while clicking the 'Compile to HEX' icon on the ribbon.
 ==Compiling to Chip==

@@ Line 31: / Line 31: @@
 Flowcharts must be saved before they can be transferred and Flowcode will prompt you if this is the case.
-You can also use the 'Compile to C' [[File:CompileToC.png|border]] icon on the toolbar.
+You can also use the 'Compile to C' [[File:CompileToC.png|border]] icon on the ribbon.
 ==Compile to Hex==

← Older revision		Revision as of 08:24, 2 July 2019
Line 1:		Line 1:
−	~~<sidebar>Sidebar: Flowcode Help Overview:ChipSpecific</sidebar>~~
	Chips can only execute code that is in hexadecimal (hex.) format. Flowcode needs to process your flowcharts (for example TEST.FCF) into a format that a chip can execute Flowcode takes a number of steps:		Chips can only execute code that is in hexadecimal (hex.) format. Flowcode needs to process your flowcharts (for example TEST.FCF) into a format that a chip can execute Flowcode takes a number of steps:

← Older revision		Revision as of 17:09, 7 March 2014
Line 1:		Line 1:
−	<sidebar>Sidebar: ~~Adding Finishing Touches~~</sidebar>	+	<sidebar>Sidebar: Flowcode Help Overview:ChipSpecific</sidebar>
	Chips can only execute code that is in hexadecimal (hex.) format. Flowcode needs to process your flowcharts (for example TEST.FCF) into a format that a chip can execute Flowcode takes a number of steps:		Chips can only execute code that is in hexadecimal (hex.) format. Flowcode needs to process your flowcharts (for example TEST.FCF) into a format that a chip can execute Flowcode takes a number of steps:

← Older revision		Revision as of 10:58, 5 September 2013
Line 70:		Line 70:


−	~~<font style="color:#008000">~~
	====Compiler errors====		====Compiler errors====

−	If the compiler detects any errors during compilation, these errors will be displayed within the [[Using the Icon Lists Pane\|Icon Lists]] panel. ~~</font>~~	+	If the compiler detects any errors during compilation, these errors will be displayed within the [[Using the Icon Lists Pane\|Icon Lists]] panel.

← Older revision		Revision as of 10:51, 5 September 2013
Line 70:		Line 70:


−	<font style="color:#008000">====Compiler errors====	+	<font style="color:#008000">
		+	====Compiler errors====

	If the compiler detects any errors during compilation, these errors will be displayed within the [[Using the Icon Lists Pane\|Icon Lists]] panel. </font>		If the compiler detects any errors during compilation, these errors will be displayed within the [[Using the Icon Lists Pane\|Icon Lists]] panel. </font>