Programming HID Bootloader on PIC32 - Revision history

Lynch: /* Notes for Loading Bootloader with Own Board */

2009-12-18T06:31:03Z

Notes for Loading Bootloader with Own Board

← Older revision		Revision as of 01:31, 18 December 2009
Line 237:		Line 237:

	= Notes for Loading Bootloader with Own Board =		= Notes for Loading Bootloader with Own Board =
	If you are ~~loading~~ a bootloader ~~with~~ a board that is not included in the HardwareProfile header file. You will need to do the following tasks.		These directions are for the case that you are putting a bootloader on a board that is not included in the HardwareProfile header file. You will need to do the following tasks.
	*Define a board constant in MPLAB PIC32 C Compiler Tab in Project -> Build options (ex. PIC32_NU32)		*Define a board constant in MPLAB PIC32 C Compiler Tab in Project -> Build options (ex. PIC32_NU32)
	*Put the following line in the HardwareProfile under the correct compiler (ex __C32__) and PIC (ex __32MX460F512L__)		*Put the following line in the HardwareProfile under the correct compiler (ex __C32__) and PIC (ex __32MX460F512L__)

Lynch: /* Programming with ICD2 */

2009-12-18T06:30:13Z

Programming with ICD2

← Older revision		Revision as of 01:30, 18 December 2009
Line 232:		Line 232:
	* Release the RESET button		* Release the RESET button
	* Release the PROGRAM button		* Release the PROGRAM button
			The LEDs should be alternating. You can now disconnect the ICD2 from the PC and from the NU32 board. You should not need the ICD2 again, unless you accidentally overwrite the bootloader.
	LEDs should be alternating

	If getting started click [[Getting Started with PIC32\|here]] to return to the instructions.		If getting started click [[Getting Started with PIC32\|here]] to return to the instructions.

Lynch: /* Programming with ICD2 */

2009-12-18T06:28:34Z

Programming with ICD2

← Older revision		Revision as of 01:28, 18 December 2009
Line 179:		Line 179:
	These instructions assume you already have installed and connected the ICD2 to the board and have a hex file created.		These instructions assume you already have installed and connected the ICD2 to the board and have a hex file created.

			* Connect your NU32 board to your computer with the USB cable and switch the board ON (red LED should be on). '''Note: the USB cable is merely providing 5V power to your NU32 board; no data is being transmitted back and forth on the cable.''' So you should now have the NU32 board connected directly to one USB port on the PC (for power); and the NU32 board should also be connected to the ICD2 programmer, which is in turn connected to a second USB port on your PC.
	* Plug in the NU32 board to your computer with the USB cable and turn it on (RED LED should be on).

	* With the board connected to the ICD2, click Programmer -> Connect.		* With the board connected to the ICD2, click Programmer -> Connect.
Line 198:		Line 198:
	ICD0042: API: Error response (Device not ready (0x12))		ICD0042: API: Error response (Device not ready (0x12))
	MPLAB ICD 2 ready for next operation		MPLAB ICD 2 ready for next operation
	I ~~find that if you turn off~~ the board and ~~turn it~~ back on, and while holding the cable click Programmer->Connect. The connection may be loose.		try turning the board off and then back on, and while holding the cable tight to the board, click Programmer->Connect. The connection may be loose.



	*Click File ->Import and find the hex file you created above.		*Click File ->Import and find the hex file you created above.

Lynch: /* Loading Bootloader on PIC with ICD2 */

2009-12-18T06:19:38Z

Loading Bootloader on PIC with ICD2

← Older revision		Revision as of 01:19, 18 December 2009
Line 120:		Line 120:

	These directions assume the following things:		These directions assume the following things:
	*Circuit capable of programming the PIC already exists(discussed below)		*Circuit capable of programming the PIC already exists (discussed below)
	*You have an ICD2		*You have an ICD2
	*You already have a hex file to load (the bootloader hex file was created with the above instructions)		*You already have a hex file to load (the bootloader hex file was created with the above instructions)

Lynch: /* Creating Bootloader Hex File */

2009-12-18T06:18:42Z

Creating Bootloader Hex File

← Older revision		Revision as of 01:18, 18 December 2009
Line 105:		Line 105:
	*Click Project -> Build Options and click on the MPLAB PIC32 C Compiler Tab as before		*Click Project -> Build Options and click on the MPLAB PIC32 C Compiler Tab as before
	*Click on the Category "Optimization"		*Click on the Category "Optimization"
	*Select the dot 's' for smallest size as shown below		*Select the dot 's' for smallest size as shown below (if this is not available, choose the smallest code size available)
	[[Image:MPLAB_Optimize.jpg\|thumb\|300 px\|left]]		[[Image:MPLAB_Optimize.jpg\|thumb\|300 px\|left]]
	*Click OK		*Click OK

Lynch: /* Creating Bootloader Hex File */

2009-12-18T06:17:14Z

Creating Bootloader Hex File

← Older revision		Revision as of 01:17, 18 December 2009
Line 110:		Line 110:
	<br clear=all>		<br clear=all>

	If you are using the PIC32_NU32, you are ready to compile the project. If you are using a board other than the PIC32_NU32, make sure you follow all the directions in Notes for Loading Bootloader with Own Board.		If you are using the PIC32_NU32, you are ready to compile the project. If you are using a board other than the PIC32_NU32, make sure you follow all the directions in Notes for Loading Bootloader with Own Board at the bottom of this page.
	*Choose Project -> Build All		*Choose Project -> Build All
	This compiles and creates a Hex File in the project folder to be loaded on to the PIC. There may be some warnings about the academic version, but as long as the Build is Successful you can continue.		This compiles and creates a Hex File in the project folder to be loaded on to the PIC. There may be some warnings about the academic version, but as long as the Build is Successful you can continue.

Lynch: /* Creating Bootloader Hex File */

2009-12-18T06:15:39Z

Creating Bootloader Hex File

← Older revision		Revision as of 01:15, 18 December 2009
Line 66:		Line 66:

	==Creating Bootloader Hex File==		==Creating Bootloader Hex File==
	After clicking finish, MPLAB should appear as below. The project window ~~which~~ contains all of the files you have added to the project. The procdefs.ld file is located under the linker file folder. This file is not the only linker file, so it needs to be moved (dragged) to the 'Other Files' folder. The procdefs.ld file tells the programmer or bootloader where to put the files. The bootloader will have a different procdefs file than the files you will load with the bootloader because you want the new programs to be put in a different spot than the bootloader on the PIC. If you use the same procdefs file as the bootloader procdefs, the bootloader will try to put the new program where the bootloader code is stored, essentially erasing the bootloader and not installing the new program. If you ~~accidently~~ use the bootloader procdefs file, you will have to reinstall the bootloader on the PIC.		After clicking finish, MPLAB should appear as below. The project window contains all of the files you have added to the project. The procdefs.ld file is located under the linker file folder. This file is not the only linker file, so it needs to be moved (dragged) to the 'Other Files' folder. The procdefs.ld file tells the programmer or bootloader where to put the files. The bootloader will have a different procdefs file than the files you will load with the bootloader because you want the new programs to be put in a different spot than the bootloader on the PIC. If you use the same procdefs file as the bootloader procdefs, the bootloader will try to put the new program where the bootloader code is stored, essentially erasing the bootloader and not installing the new program. If you accidentally use the bootloader procdefs file, you will have to reinstall the bootloader on the PIC.
	[[Image:MPLAB_StartWindow.jpg\|thumb\|500 px\|left]]		[[Image:MPLAB_StartWindow.jpg\|thumb\|500 px\|left]]
	<br clear=all>		<br clear=all>

Lynch at 06:13, 18 December 2009

2009-12-18T06:13:25Z

← Older revision		Revision as of 01:13, 18 December 2009
Line 1:		Line 1:
	The bootloader is used to install programs on the PIC32 without using an external programmer like ICD2 and does not require any drivers on the computer. The PC software for the bootloader for the PC has already been installed with the [http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=2680&dDocName=en537044 Microchip Applications Library].		The bootloader is used to install programs on the PIC32 without using an external programmer like an ICD2 and does not require any drivers on the computer. The PC software for the bootloader for the PC has already been installed with the [http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=2680&dDocName=en537044 Microchip Applications Library].

	= Software =		= Software =
	== PIC Source Code ==		== PIC Source Code ==

	For each new program, you will need to make a folder that will contain the source code and the project.		For each new program, you will need to make a folder that will contain the source code files and the ''project'' file, which keeps all the details about your program that are not in the source code files.

	- ~~Create a new folder in a spot that you want all of your code to be located and call it Bootloader.~~ I recommend making a folder called PIC32_Code to hold all of your project folders.		- I recommend making a folder called PIC32_Code to hold all of your project folders.

			- Create a new folder in your PIC32_Code folder and call it Bootloader.

	- Download the PIC32 bootloader zip file [[Media:HID_Bootloader_PIC32.zip \| here]].		- Download the PIC32 bootloader zip file [[Media:HID_Bootloader_PIC32.zip \| here]].
Line 18:		Line 20:
	In order to load files with the bootloader, you will have to run a PC application called HID Bootloader. This bootloader should have been installed with the applications library.		In order to load files with the bootloader, you will have to run a PC application called HID Bootloader. This bootloader should have been installed with the applications library.

	- Verify that there is a HID Bootloader located under the ~~start~~ menu Programs -> Microchip -> MCHPFSUSB v2.6 -> Tools -> HIDBootLoader		- Verify that there is a HID Bootloader located under the Start menu Programs -> Microchip -> MCHPFSUSB v2.6 -> Tools -> HIDBootLoader. '''Do not run this program now, just verify that it is there.'''

	Running ~~this~~ requires a sufficiently recent version of the .NET Framework, which you may not have if you are running XP or earlier versions of Windows. This issue should have been resolved when installing the Applications Library. You can download a sufficiently recent version here (the install takes a while): [http://www.microsoft.com/downloads/details.aspx?FamilyId=333325FD-AE52-4E35-B531-508D977D32A6&displaylang=en .NET Framework download].		Running the HIDBootLoader requires a sufficiently recent version of the .NET Framework, which you may not have if you are running XP or earlier versions of Windows. This issue should have been resolved when installing the Applications Library. You can download a sufficiently recent version here (the install takes a while): [http://www.microsoft.com/downloads/details.aspx?FamilyId=333325FD-AE52-4E35-B531-508D977D32A6&displaylang=en .NET Framework download].

	= Installing a Bootloader on the PIC32 with ICD2=		= Installing a Bootloader on the PIC32 with ICD2=
Line 47:		Line 49:
	[[Image:MPLAB_ProjectWizardNewProject.jpg\|thumb\|300 px\|left]]		[[Image:MPLAB_ProjectWizardNewProject.jpg\|thumb\|300 px\|left]]
	<br clear=all>		<br clear=all>
	* Add the following ~~the c~~ files to the project. These files should be located in the Bootloader folder.		* Add the following C files to the project. These files should already be located in the Bootloader folder.
	**HardwareProfile.h (generic header file for many different boards)		**HardwareProfile.h (generic header file for many different boards)
	**HardwareProfile_NU32.h (hardware profile for the NU32, if you have your own hardware profile you will need to add it to the generic HardwareProfile.h)		**HardwareProfile_NU32.h (hardware profile for the NU32, if you have your own hardware profile you will need to add it to the generic HardwareProfile.h)

Andrew Long: /* Programming with ICD2 */

2009-12-15T19:45:55Z

Programming with ICD2

← Older revision		Revision as of 14:45, 15 December 2009
Line 228:		Line 228:
	The bootloader is now installed on the PIC.		The bootloader is now installed on the PIC.

			To test that the bootloader was installed correctly,
⚫	If getting started click [[Getting Started with PIC32\|here]] to return to the instructions.
			* Hold down the RESET and PROGRAM buttons.
			* Release the RESET button
			* Release the PROGRAM button
			LEDs should be alternating

		⚫	If getting started click [[Getting Started with PIC32\|here]] to return to the instructions.
	See [[Directions to Load Files to PIC32 with HID Bootloader]]

	= Notes for Loading Bootloader with Own Board =		= Notes for Loading Bootloader with Own Board =

Andrew Long: /* Programming with ICD2 */

2009-12-15T19:40:50Z

Programming with ICD2

← Older revision		Revision as of 14:40, 15 December 2009
Line 196:		Line 196:
	ICD0042: API: Error response (Device not ready (0x12))		ICD0042: API: Error response (Device not ready (0x12))
	MPLAB ICD 2 ready for next operation		MPLAB ICD 2 ready for next operation
	I find that if you turn off the board and turn it back on, and click Programmer->Connect.		I find that if you turn off the board and turn it back on, and while holding the cable click Programmer->Connect. The connection may be loose.