CCS IDE - Revision history

LIMS at 00:08, 27 December 2007

2007-12-27T00:08:27Z

← Older revision		Revision as of 19:08, 26 December 2007
Line 25:		Line 25:
	Sometimes the PIC will run when the ICD is connected, but inexplicably not run when the ICD is not connected. If this happens, try adding the NOBROWNOUT fuse at the top of your program, with the other fuses. We think this has something to do with a small change of supply voltage.		Sometimes the PIC will run when the ICD is connected, but inexplicably not run when the ICD is not connected. If this happens, try adding the NOBROWNOUT fuse at the top of your program, with the other fuses. We think this has something to do with a small change of supply voltage.

	That short cable from the ICD to the PIC has 6 conductors, unlike telephone (4) or ethernet (8). It has to be short, or it won't work. The clips on the ends are on the same face of the flat cable; won't work if on opposite ~~sides~~.		That short cable from the ICD to the PIC has 6 conductors, unlike telephone (4) or ethernet (8). It has to be short, or it won't work. The clips on the ends are on the same face of the flat cable; won't work if on opposite faces.

LIMS at 00:08, 27 December 2007

2007-12-27T00:08:06Z

← Older revision		Revision as of 19:08, 26 December 2007
Line 24:		Line 24:

	Sometimes the PIC will run when the ICD is connected, but inexplicably not run when the ICD is not connected. If this happens, try adding the NOBROWNOUT fuse at the top of your program, with the other fuses. We think this has something to do with a small change of supply voltage.		Sometimes the PIC will run when the ICD is connected, but inexplicably not run when the ICD is not connected. If this happens, try adding the NOBROWNOUT fuse at the top of your program, with the other fuses. We think this has something to do with a small change of supply voltage.

			That short cable from the ICD to the PIC has 6 conductors, unlike telephone (4) or ethernet (8). It has to be short, or it won't work. The clips on the ends are on the same face of the flat cable; won't work if on opposite sides.

LIMS at 00:05, 27 December 2007

2007-12-27T00:05:20Z

← Older revision		Revision as of 19:05, 26 December 2007
Line 1:		Line 1:
	The installation CD will walk you through installing 6 software components. ~~There is no license key required.~~		The installation CD will walk you through installing 6 software components.

	[[Image:icd-u40.jpg\|right]]		[[Image:icd-u40.jpg\|right]]

LIMS at 00:04, 27 December 2007

2007-12-27T00:04:57Z

← Older revision		Revision as of 19:04, 26 December 2007
Line 4:		Line 4:


	<b>~~PC-to-PIC~~ in-circuit debugger ~~(ICD)~~</b>		<b>ICD in-circuit debugger and programmer</b>

	To program the PIC you need a USB device called an ICD-U40; ICD is an in-circuit debugger (and programmer). Download and install the <b>drivers</b> for the ICD from the [http://www.ccsinfo.com/content.php?page=ICD CCS web page on the ICD-U40]		To program the PIC you need a USB device called an ICD-U40; ICD is an in-circuit debugger (and programmer). Download and install the <b>drivers</b> for the ICD from the [http://www.ccsinfo.com/content.php?page=ICD CCS web page on the ICD-U40]

LIMS at 00:04, 27 December 2007

2007-12-27T00:04:23Z

← Older revision		Revision as of 19:04, 26 December 2007
Line 17:		Line 17:

	The CCS compiler does not keep good track of projects and source files, or at least not in a clear way. It is easy to think you are working on source file newcode.c while the compiler is still working with oldcode.c. To avoid such pitfalls, make a new folder for each C program you write. Put all the code, including interrupt routines and functions (subroutines), in just one ".c" source file. Do not use "save as" to change the name of the file you are working with, even for such a worthy purpose as saving along-the-way versions. Instead, close the compiler, make a new folder with your source code in it (and with a new name if you wish) and restart the compiler by double-clicking the source code file.		The CCS compiler does not keep good track of projects and source files, or at least not in a clear way. It is easy to think you are working on source file newcode.c while the compiler is still working with oldcode.c. To avoid such pitfalls, make a new folder for each C program you write. Put all the code, including interrupt routines and functions (subroutines), in just one ".c" source file. Do not use "save as" to change the name of the file you are working with, even for such a worthy purpose as saving along-the-way versions. Instead, close the compiler, make a new folder with your source code in it (and with a new name if you wish) and restart the compiler by double-clicking the source code file.


	<b>FAQ for the ICD</b>		<b>FAQ for the ICD</b>

LIMS at 00:04, 27 December 2007

2007-12-27T00:04:15Z

← Older revision		Revision as of 19:04, 26 December 2007
Line 6:		Line 6:
	<b>PC-to-PIC in-circuit debugger (ICD)</b>		<b>PC-to-PIC in-circuit debugger (ICD)</b>

	To program the PIC you need a USB device called an ICD-U40; ICD is an in-circuit debugger (and programmer). Download and install the drivers for the ICD from the [http://www.ccsinfo.com/content.php?page=ICD CCS web page on the ICD-U40]		To program the PIC you need a USB device called an ICD-U40; ICD is an in-circuit debugger (and programmer). Download and install the <b>drivers</b> for the ICD from the [http://www.ccsinfo.com/content.php?page=ICD CCS web page on the ICD-U40]



Line 17:		Line 18:
	The CCS compiler does not keep good track of projects and source files, or at least not in a clear way. It is easy to think you are working on source file newcode.c while the compiler is still working with oldcode.c. To avoid such pitfalls, make a new folder for each C program you write. Put all the code, including interrupt routines and functions (subroutines), in just one ".c" source file. Do not use "save as" to change the name of the file you are working with, even for such a worthy purpose as saving along-the-way versions. Instead, close the compiler, make a new folder with your source code in it (and with a new name if you wish) and restart the compiler by double-clicking the source code file.		The CCS compiler does not keep good track of projects and source files, or at least not in a clear way. It is easy to think you are working on source file newcode.c while the compiler is still working with oldcode.c. To avoid such pitfalls, make a new folder for each C program you write. Put all the code, including interrupt routines and functions (subroutines), in just one ".c" source file. Do not use "save as" to change the name of the file you are working with, even for such a worthy purpose as saving along-the-way versions. Instead, close the compiler, make a new folder with your source code in it (and with a new name if you wish) and restart the compiler by double-clicking the source code file.

			<b>FAQ for the ICD</b>
⚫	~~tip -~~ Often when programming a PIC repeatedly, the "program PIC" function will fail to find the ICD device on its USB port, and ask you to choose a COM port instead. Close the dialog, disconnect and then reconnect the ICD's USB cable, and now the "program PIC" function should work again. Annoying.

		⚫	Often when programming a PIC repeatedly, the "program PIC" function will fail to find the ICD device on its USB port, and ask you to choose a COM port instead. Close the dialog, disconnect and then reconnect the ICD's USB cable, and now the "program PIC" function should work again. Annoying.

	~~tip -~~ Sometimes the PIC will run when the ICD is connected, but inexplicably not run when the ICD is not connected. If this happens, try adding the NOBROWNOUT fuse at the top of your program, with the other fuses. We think this has something to do with a small change of supply voltage.		Sometimes the PIC will run when the ICD is connected, but inexplicably not run when the ICD is not connected. If this happens, try adding the NOBROWNOUT fuse at the top of your program, with the other fuses. We think this has something to do with a small change of supply voltage.

LIMS at 00:02, 27 December 2007

2007-12-27T00:02:55Z

← Older revision		Revision as of 19:02, 26 December 2007
Line 7:		Line 7:

	To program the PIC you need a USB device called an ICD-U40; ICD is an in-circuit debugger (and programmer). Download and install the drivers for the ICD from the [http://www.ccsinfo.com/content.php?page=ICD CCS web page on the ICD-U40]		To program the PIC you need a USB device called an ICD-U40; ICD is an in-circuit debugger (and programmer). Download and install the drivers for the ICD from the [http://www.ccsinfo.com/content.php?page=ICD CCS web page on the ICD-U40]


	<b>The development cycle</b>		<b>The development cycle</b>

LIMS at 00:02, 27 December 2007

2007-12-27T00:02:46Z

← Older revision		Revision as of 19:02, 26 December 2007
Line 3:		Line 3:
	[[Image:icd-u40.jpg\|right]]		[[Image:icd-u40.jpg\|right]]


			<b>PC-to-PIC in-circuit debugger (ICD)</b>

	To program the PIC you need a USB device called an ICD-U40; ICD is an in-circuit debugger (and programmer). Download and install the drivers for the ICD from the [http://www.ccsinfo.com/content.php?page=ICD CCS web page on the ICD-U40]		To program the PIC you need a USB device called an ICD-U40; ICD is an in-circuit debugger (and programmer). Download and install the drivers for the ICD from the [http://www.ccsinfo.com/content.php?page=ICD CCS web page on the ICD-U40]

			<b>The development cycle</b>

	The development cycle is quick. Write your source code (yourcode.c file) using the built-in editor. Compile it with Compile/compile. Load it onto the PIC with Compile/ProgramChip/ICD. That's it.		The development cycle is quick. Write your source code (yourcode.c file) using the built-in editor. Compile it with Compile/compile. Load it onto the PIC with Compile/ProgramChip/ICD. That's it.

LIMS at 00:00, 27 December 2007

2007-12-27T00:00:27Z

← Older revision		Revision as of 19:00, 26 December 2007
Line 1:		Line 1:
	The installation CD will walk you through installing 6 software components. There is no license key required.		The installation CD will walk you through installing 6 software components. There is no license key required.

			[[Image:icd-u40.jpg\|right]]
⚫	To program the PIC you need a USB device called an ICD-U40; ICD is an in-circuit debugger (and programmer). Download and install the drivers for the ICD from [~~URL~~]


		⚫	To program the PIC you need a USB device called an ICD-U40; ICD is an in-circuit debugger (and programmer). Download and install the drivers for the ICD from the [http://www.ccsinfo.com/content.php?page=ICD CCS web page on the ICD-U40]

	The development cycle is quick. Write your source code (yourcode.c file) using the built-in editor. Compile it with Compile/compile. Load it onto the PIC with Compile/ProgramChip/ICD. That's it.		The development cycle is quick. Write your source code (yourcode.c file) using the built-in editor. Compile it with Compile/compile. Load it onto the PIC with Compile/ProgramChip/ICD. That's it.

LIMS at 03:04, 26 December 2007

2007-12-26T03:04:03Z

New page

The installation CD will walk you through installing 6 software components. There is no license key required.

To program the PIC you need a USB device called an ICD-U40; ICD is an in-circuit debugger (and programmer). Download and install the drivers for the ICD from [URL]

The development cycle is quick. Write your source code (yourcode.c file) using the built-in editor. Compile it with Compile/compile. Load it onto the PIC with Compile/ProgramChip/ICD. That's it.

Don't start from scratch. Start with a simple program that works, such as FlashingLights.c

The CCS compiler does not keep good track of projects and source files, or at least not in a clear way. It is easy to think you are working on source file newcode.c while the compiler is still working with oldcode.c. To avoid such pitfalls, make a new folder for each C program you write. Put all the code, including interrupt routines and functions (subroutines), in just one ".c" source file. Do not use "save as" to change the name of the file you are working with, even for such a worthy purpose as saving along-the-way versions. Instead, close the compiler, make a new folder with your source code in it (and with a new name if you wish) and restart the compiler by double-clicking the source code file.

tip - Often when programming a PIC repeatedly, the "program PIC" function will fail to find the ICD device on its USB port, and ask you to choose a COM port instead. Close the dialog, disconnect and then reconnect the ICD's USB cable, and now the "program PIC" function should work again. Annoying.

tip - Sometimes the PIC will run when the ICD is connected, but inexplicably not run when the ICD is not connected. If this happens, try adding the NOBROWNOUT fuse at the top of your program, with the other fuses. We think this has something to do with a small change of supply voltage.