XC16Toolsuite

FirewingUser.XC16Toolsuite History

Hide minor edits - Show changes to output

April 16, 2014, at 02:48 PM by David Barker -
Changed line 13 from:
*[[Attach:optimise.microchip16.zip | Microchip 16 toolsuite]] for [[Firewing.Download | Firewing 1.0.0.4 or above]]
to:
*[[Attach:microchip16.zip | Microchip 16 toolsuite]] for [[Firewing.Download | Firewing 1.0.0.4 (B2) or above]]
April 11, 2014, at 12:11 PM by David Barker -
Changed lines 11-15 from:
Next, you need to install the XC16 toolsuite.  Download and unzip [[Attach:microchip16.zip | Microchip 16 toolsuite 1.0.0.5]] into the following folder:
to:
Next, you need to install the XC16 toolsuite. 

*
[[Attach:optimise.microchip16.zip | Microchip 16 toolsuite]] for [[Firewing.Download | Firewing 1.0.0.4 or above]]

Download and unzip the above file
into the following folder:
April 05, 2014, at 12:05 PM by David Barker -
Changed line 11 from:
Next, you need to install the XC16 toolsuite.  Download and unzip [[Attach:microchip16.zip | this file]] into the following folder:
to:
Next, you need to install the XC16 toolsuite.  Download and unzip [[Attach:microchip16.zip | Microchip 16 toolsuite 1.0.0.5]] into the following folder:
Added lines 50-55:
!!!Update 10-01-2014
I built some code today using the xc16 1.20 toolsuite and it's definitely not working correctly in my opinion. When I build with xc16 1.11 the code works as expected. For the time being, I would personally stick to 1.11 as the Firewing xc16 toolsuite. Fortunately, you can have both xc16 1.11 and 1.20 installed on your machine so you can switch between the two as required, see above. If you do not have xc16 1.11 installed, there is a version here:

*[[http://ww1.microchip.com/downloads/en/DeviceDoc/xc16-v1.11-windows-installer.exe | XC16 version 1.11 ]]

I'm not sure how long Microchip will keep this link live - if it goes dead, let me know...
Added lines 37-50:

!!!Using Different Versions of XC16

You can install multiple versions of XC16 (I have 1.0, 1.11 and now 1.20) on a PC. You can get the Microchip 16 toolsuite to point to any installed version, rather than just using the most recently installed. To do this, create an *.ini file in your "Microchip16" toolsuite folder and call it "tsMicrochip16.ini". Then have the following entries:

 [application]
 Name=Microchip XC16 1.11
 Path=C:\Program Files\Microchip\xc16\v1.11\bin
 GCC=xc16-gcc.exe
 GCCBinToHex=xc16-bin2hex.exe

the path setting can be used to point to different installations - don't forget to update the "Name" attribute to reflect a different version number.

!!!Finally...
Changed line 1 from:
By default, Firewing only supports the 24HJ128GP502 device.  However, installing the Microchip XC16 toolsuite will allow you to compile your Firewing projects for many other devices. That's right, you can have a completely free, fully functional Firewing PIC compiler that can target over 200 PIC24 devices. Awesome!
to:
Installing the Microchip XC16 toolsuite will allow you to compile your Firewing projects for many other devices. That's right, you can have a completely free, fully functional Firewing PIC compiler that can target over 200 PIC24 devices. Awesome!
August 24, 2013, at 10:21 AM by David Barker -
Changed lines 9-10 from:
!!!Install the XC16 Toolsuite
to:
!!!Install the XC16 Toolsuite into Firewing
Changed line 18 from:
!!!Install a Device File
to:
!!!Install a Device File into Firewing
August 24, 2013, at 10:13 AM by David Barker -
Changed line 38 from:
'''Please note that people at the nest don't currently have the resources to support all of the device files and toolsuites that fall outside of the standard Firewing installation. The above will work but any problems and you need to post on the forum and look for user support.  If posting on the forum, make it clear you are using a different device file and toolsuite. Thanks.'''
to:
'''Please note that people at the nest don't currently have the resources to support all of the device files and toolsuites that fall outside of the standard Firewing installation. The above will work but any problems and you need to post on the forum and look for user support.  If posting on the forum, make it clear you are using a different device file and toolsuite from the standard install. Thanks.'''
August 24, 2013, at 10:12 AM by David Barker -
Changed line 13 from:
 <install-dir>\bin\toolsuite
to:
 <firewing-install-dir>\bin\toolsuite
August 24, 2013, at 10:12 AM by David Barker -
Changed line 1 from:
By default, Firewing only supports the 24HJ128GP502 device.  However, installing the Microchip XC16 toolsuite will allow you to compile your Firewing projects for many other devices. That's right, you can have a completely free, fully functional Firewing PIC compiler that can target multiple PIC24 devices. Awesome!
to:
By default, Firewing only supports the 24HJ128GP502 device.  However, installing the Microchip XC16 toolsuite will allow you to compile your Firewing projects for many other devices. That's right, you can have a completely free, fully functional Firewing PIC compiler that can target over 200 PIC24 devices. Awesome!
August 24, 2013, at 10:11 AM by David Barker -
Changed line 36 from:
Please take some time to look at the file generated. Remember, it may need tweaking as it has been automatically generated - refer to the datasheet. Also note that Microchip, on occasions, have the wrong information supplied in their own files!
to:
Please take some time to look at the file generated. Remember, it may need tweaking as it has been automatically generated - refer to the datasheet. Also note that Microchip, on occasions, have the wrong information supplied in their own files! If the device you want to use is not included in the above download, try using the [[FirewingUser.SystemGenerator | system generator]] to create your own.
August 24, 2013, at 10:09 AM by David Barker -
Changed line 20 from:
To add new devices, you need to [[Attach:NewIncludes.zip | download the following]] and select the device you want to use and place in the Firewing includes folder.  For example,
to:
To add new devices, you need to [[Attach:NewInclude.zip | download the following]] and select the device you want to use and place in the Firewing includes folder.  For example,
August 24, 2013, at 10:08 AM by David Barker -
Changed lines 18-29 from:
!!!Create a Device File

To add new devices, you need to download the following software:

**[[Attach:sysgen16.zip | sysgen16.zip
]] - Automatic device creation software.

You must have the latest version of MPLAB installed. The above program '''has not''' been tested with MPLABX. Just unzip the software and place in a folder that can be written to. It is '''essential''' you have write permissions, as the new files will be dumped in a sub-folder called "NewIncludeBASIC".

Attach:sysgen.jpg

When you have generated the new files, place the device you want to use
in the Firewing includes folder.  For example,
to:
!!!Install a Device File

To add new devices, you need to [[Attach:NewIncludes.zip | download the following]] and select the device you want to use and place in the Firewing includes folder.  For example,
Changed line 28 from:
The above generator will build a file needed by Firewing.  To use the new device in your code, just use:
to:
To use the new device in your code, just use:
Changed lines 36-40 from:
Here are some pre-generated files you can use for testing:

*[[Attach:24FJ64GA002
.zip | 24FJ64GA002]]
*[[Attach:24FJ128GA010.zip | 24FJ128GA010]]
*[[Attach:24F16KL402.zip | 24F16KL402 ]]
to:
Please take some time to look at the file generated. Remember, it may need tweaking as it has been automatically generated - refer to the datasheet. Also note that Microchip, on occasions, have the wrong information supplied in their own files!
August 24, 2013, at 09:52 AM by David Barker -
Changed line 1 from:
By default, Firewing only supports the 24HJ128GP502 device.  However, installing the Microchip XC16 toolsuite will allow you to compile your Firewing projects for many other devices.
to:
By default, Firewing only supports the 24HJ128GP502 device.  However, installing the Microchip XC16 toolsuite will allow you to compile your Firewing projects for many other devices. That's right, you can have a completely free, fully functional Firewing PIC compiler that can target multiple PIC24 devices. Awesome!
August 24, 2013, at 09:49 AM by David Barker -
Changed line 50 from:
to:
'''Please note that people at the nest don't currently have the resources to support all of the device files and toolsuites that fall outside of the standard Firewing installation. The above will work but any problems and you need to post on the forum and look for user support.  If posting on the forum, make it clear you are using a different device file and toolsuite. Thanks.'''
August 24, 2013, at 09:44 AM by David Barker -
Changed lines 1-2 from:
By default, Firewing only supports the 24HJ128GP502 device.  However, installing the Microchip XC16 toolsuite will allow you to compile your Firewing projects for many other devices.  Some examples include
the 24FJ128GA010 and 24F16KL402
.
to:
By default, Firewing only supports the 24HJ128GP502 device.  However, installing the Microchip XC16 toolsuite will allow you to compile your Firewing projects for many other devices.
August 24, 2013, at 09:43 AM by David Barker -
Changed lines 47-49 from:
*[[Attach:24FJ64GA002.bas | 24FJ64GA002]]
*[[Attach:24FJ128GA010.bas | 24FJ128GA010]]
*[[Attach:24F16KL402.bas | 24F16KL402 ]]
to:
*[[Attach:24FJ64GA002.zip | 24FJ64GA002]]
*[[Attach:24FJ128GA010.zip | 24FJ128GA010]]
*[[Attach:24F16KL402.zip | 24F16KL402 ]]
August 24, 2013, at 09:41 AM by David Barker -
Added lines 44-49:

Here are some pre-generated files you can use for testing:

*[[Attach:24FJ64GA002.bas | 24FJ64GA002]]
*[[Attach:24FJ128GA010.bas | 24FJ128GA010]]
*[[Attach:24F16KL402.bas | 24F16KL402 ]]
August 24, 2013, at 09:36 AM by David Barker -
Changed lines 25-28 from:
You must have the latest version of MPLAB installed. The above program '''has not''' been tested with MPLABX. You will also need to ensure you have Microchips XC16 compiler installed. The software uses various files supplied by MPLAB (*.dev files) and XC16 (*.gld and *.inc) to try and construct the files required by the compiler.

Just unzip the software and place in a folder that can be written to. It is '''essential''' you have write permissions, as the new files will be dumped in a sub-folder called "NewIncludeBASIC".
to:
You must have the latest version of MPLAB installed. The above program '''has not''' been tested with MPLABX. Just unzip the software and place in a folder that can be written to. It is '''essential''' you have write permissions, as the new files will be dumped in a sub-folder called "NewIncludeBASIC".
Changed lines 37-55 from:
!!!Adding Support for GCC

The above generator will build a file needed by Firewing, but you will still need to add some support files to the backend generator toolsuite folder in order for everything to work.  Here is what you need to do:

Locate the XC16 installation folder for the device you are interested in.  For example:

 %color=#4088b8% '''c:\program files\microchip\xc16\v1.11\support\PIC24F'''

you need to copy the *.gld and *.h files to the toolsuite bin folder.  For example:

 %color=#4088b8% '''c:\program files\microchip\xc16\v1.11\support\PIC24F\gld\p24FJ48GA002.gld'''
 %color=#4088b8% '''c:\program files\microchip\xc16\v1.11\support\PIC24F\h\p24FJ48GA002.h'''

needs to be copied to

 %color=#4088b8% '''c:\program files\mecanique\firewing\bin\toolsuite\firewing16\gcc\gld\p24FJ48GA002.gld'''
 %color=#4088b8% '''c:\program files\mecanique\firewing\bin\toolsuite\firewing16\gcc\h\p24FJ48GA002.h'''

if using Windows 7, the files will be located under "program files (x86)" and not "program files".  And that's it - you should be good to go.
To use the new device in your code, just use:
to:
The above generator will build a file needed by Firewing.  To use the new device in your code, just use:
Deleted lines 43-49:

!!!A Word Of Warning


**'''Don't just copy''' all of the files to the include folder. The main device file supplied by Firewing has been hand edited. You don't want to break it.
**'''Take a look at the file generated'''. Remember, it may need tweaking - refer to the datasheet. Also note that Microchip, on occasions, have the wrong information supplied in their own files!

August 24, 2013, at 09:30 AM by David Barker -
Added lines 18-69:

!!!Create a Device File

To add new devices, you need to download the following software:

**[[Attach:sysgen16.zip | sysgen16.zip]] - Automatic device creation software.

You must have the latest version of MPLAB installed. The above program '''has not''' been tested with MPLABX. You will also need to ensure you have Microchips XC16 compiler installed. The software uses various files supplied by MPLAB (*.dev files) and XC16 (*.gld and *.inc) to try and construct the files required by the compiler.

Just unzip the software and place in a folder that can be written to. It is '''essential''' you have write permissions, as the new files will be dumped in a sub-folder called "NewIncludeBASIC".

Attach:sysgen.jpg

When you have generated the new files, place the device you want to use in the Firewing includes folder.  For example,

 %color=#4088b8% '''c:\program files\mecanique\firewing\includes\24FJ64GA002.bas'''

Please note that for Windows 7 users, the paths to the include files will be a little different. Something like:

 %color=#4088b8% '''c:\programdata\mecanique\firewing\includes\24FJ64GA002.bas'''

!!!Adding Support for GCC

The above generator will build a file needed by Firewing, but you will still need to add some support files to the backend generator toolsuite folder in order for everything to work.  Here is what you need to do:

Locate the XC16 installation folder for the device you are interested in.  For example:

 %color=#4088b8% '''c:\program files\microchip\xc16\v1.11\support\PIC24F'''

you need to copy the *.gld and *.h files to the toolsuite bin folder.  For example:

 %color=#4088b8% '''c:\program files\microchip\xc16\v1.11\support\PIC24F\gld\p24FJ48GA002.gld'''
 %color=#4088b8% '''c:\program files\microchip\xc16\v1.11\support\PIC24F\h\p24FJ48GA002.h'''

needs to be copied to

 %color=#4088b8% '''c:\program files\mecanique\firewing\bin\toolsuite\firewing16\gcc\gld\p24FJ48GA002.gld'''
 %color=#4088b8% '''c:\program files\mecanique\firewing\bin\toolsuite\firewing16\gcc\h\p24FJ48GA002.h'''

if using Windows 7, the files will be located under "program files (x86)" and not "program files".  And that's it - you should be good to go. To use the new device in your code, just use:
=firewing [=
device = 24FJ64GA002
=]
at the very top of your program. You should see the device change in the code explorer window, like this:

Attach:explorer.jpg

!!!A Word Of Warning


**'''Don't just copy''' all of the files to the include folder. The main device file supplied by Firewing has been hand edited. You don't want to break it.
**'''Take a look at the file generated'''. Remember, it may need tweaking - refer to the datasheet. Also note that Microchip, on occasions, have the wrong information supplied in their own files!
August 24, 2013, at 09:28 AM by David Barker -
Deleted line 16: