Mark Pappin
Reged: Nov 01 2004
Posts: 599
Loc: Brisbane, Australia
|
|
A new plugin for MPLAB is available for testing. After installation, the "HI-TECH Universal ToolSuite" should be available for selection on the MPLAB Toolsuite list, and this will auto-detect any version 9.x PIC-family compilers (PICC, PICC Lite, PICC-18, PICC-18 PRO, or dsPICC) that you have installed.
At this stage we haven't got a nice installer for it - extract the attached file into a directory and run "regsvr32 HTSOFT.dll" from that directory to tell Windows and thus MPLAB about it.
We would like to hear any feedback you may have about this new plugin.
edit: updated toolsuite name to reduce future confusion
Edited by Mark Pappin (Mon Jun 04 2007 05:31 PM)
|
G.Neiss
Reged: Dec 26 2004
Posts: 474
Loc: germany
|
|
As usual....
I got trubles 
After doing as stated (unzip, then "regsvr32 HTSOFT.dll"),
there are now 4 entries for HI-TECH under MPLAB/Toolsuite...
But with the following problems:
1. One seams to be tautologous (HI-TECH PICC Compiler Suite & HI-TECH PICC-18 Tooluite).
2. an entry for PRO is missing
3. Selecting options in the MPLAB dialog still uses old syntax
1. This seams to be the rest of an old setting !?!
Which keys (in registry) can/must be deleted to remove all entries for the former Suite_*.dll ?
2. Didn't know why it is missing. I had installed PRO under:
D:\Programme\HI-TECH\PIC18Pro\bin\picc18p.exe
and it is working within HI-Tide
3. Using my existing project I change the optimisation setting inside
MPLAB/Project/Build Options/PICC-18 Compiler
from 'OFF' to 9
This will result in '-Zg9' given in the comandline.
AFAIK the new compiler needs(likes) '--OPT=all,asm'
Just to show what happens:
I got the following entries under MPLAB/Toolsuite:
HI-TECH dsPICC Toolsuite
- dsPICC Compiler (dspicc.exe): D:\Programme\HI-TECH\DSPICC\bin\dspicc.exe
- dsPICC Assembler (dspicc.exe): D:\Programme\HI-TECH\DSPICC\bin\dspicc.exe
- dsPICC Linker (dspicc.exe): D:\Programme\HI-TECH\DSPICC\bin\dspicc.exe
HI-TECH PICC Compiler Suite
- HI-TECH C Compiler: D:\Programme\HI-TECH\PIC18\bin\picc18.exe
HI-TECH PICC Tooluite
- PICC Compiler (picc.exe): D:\Programme\HI-TECH\PICC\BIN\PICC.EXE
- PICC Assembler (picc.exe): D:\Programme\HI-TECH\PICC\BIN\PICC.EXE
- PICC Linker (picc.exe): D:\Programme\HI-TECH\PICC\BIN\PICC.EXE
HI-TECH PICC-18 Tooluite
- PICC-18 Compiler (picc18.exe): D:\Programme\HI-TECH\PIC18\BIN\PICC18.EXE
- PICC-18 Assembler (picc18.exe): D:\Programme\HI-TECH\PIC18\BIN\PICC18.EXE
- PICC-18 Linker (picc18.exe): D:\Programme\HI-TECH\PIC18\BIN\PICC18.EXE
Edited by G.Neiss (Tue Mar 13 2007 11:08 AM)
|
Hans
Tester
Reged: Jun 09 2004
Posts: 13
Loc: Belgium
|
|
I tried it using MPLAB 4.50.
The first problem I had was selecting the right language toolsuite. The one named "Hi-tech picc compiler suite" seemed to be the right one. After that I could select the right compiler in the project build options on the driver tab.
Next problem was that it had not taken the compiler define macros from the old plugin. So I added those manually.
Next problem was that the program did not want to compile. When I did build or rebuild, it just started the linker, not the compiler, so it stopped with "can't open object file". Saving the workspace, closing mplab and starting it again fixed this.
Next problem was that all compiles failed because of missing header files. The field and browse button for the Include and library path are grayed out in the General tab, so I can not enter them there.
I tried adding the path in the additional command-line options ("-I"C:\..."), but it did not add that to the compiler command line, only to the linker.
So this is where it ends... Seems like there is some work to do on this plugin...
Regards,
Hans
|
Mark Pappin
Reged: Nov 01 2004
Posts: 599
Loc: Brisbane, Australia
|
|
Quote:
After doing as stated (unzip, then "regsvr32 HTSOFT.dll"),
there are now 4 entries for HI-TECH under MPLAB/Toolsuite...
Precisely: the 3 you had before, plus a single new one.
Quote:
1. One seams to be tautologous (HI-TECH PICC Compiler Suite & HI-TECH PICC-18 Tooluite).
HI-TECH PICC Compiler Suite, now renamed HI-TECH Universal ToolSuite is the new plugin. Ignore the others.
Quote:
2. an entry for PRO is missing
Use HI-TECH Universal ToolSuite.
Quote:
3. Selecting options in the MPLAB dialog still uses old syntax
Use HI-TECH Universal ToolSuite.
Quote:
HI-TECH PICC Compiler Suite
- HI-TECH C Compiler: D:\Programme\HI-TECH\PIC18\bin\picc18.exe
Select this plugin for your project, and look in the Project / Build Options dialog - you should be able to select any of the HI-TECH compilers that you have installed from within there.
(Edited to update the new toolsuite name ... thought I had done it earlier)
--------------------
Mark Pappin - HI-TECH Software
Edited by Mark Pappin (Mon Jun 18 2007 09:48 AM)
|
clyde
Microchip staff
Reged: Oct 16 2003
Posts: 696
|
|
Thanks for the feedback;
Quote:
I tried it using MPLAB 4.50.
We haven't tested it with older versions of MPLAB and don't intend doing so. If it works with 4.50, that's fine, but we can't guarantee that.
Quote:
Next problem was that it had not taken the compiler define macros from the old plugin.
That's correct - the old plugin stored the options in a manner which is completely incompatible, and conversion is not practical (the old format had serious problems).
Quote:
Next problem was that the program did not want to compile. ... closing mplab and starting it again fixed this.
This sounds a little strange - not sure how to reproduce this.
Quote:
The field and browse button for the Include and library path are grayed out in the General tab, so I can not enter them there.
Good point - we will enable these fields.
Quote:
Seems like there is some work to do on this plugin
For sure - and your feed back is very helpful. Expect an update in a couple of days.
Regards, Clyde
|
clyde
Microchip staff
Reged: Oct 16 2003
Posts: 696
|
|
The new plugin has been updated in response to feedback received. The changes are:
- Include path now available and used for compile and link stages
- Name of plugin has changed to "HI-TECH Universal ToolSuite" to emphasise that it should be used for all HI-TECH Compilers.
- Some extra diagnostic messages will be produced if there are internal failures during the compile process
- The "Intermediates directory" option has been disabled, since it's not used by HI-TECH compilers.
The updated DLL is attached to this message (see above).
Some other notes:
- If additional libraries are used, they should be added to the "Library files" project folder. The "Library path" setting is not used (or available).
- To install the plugin, run the command "regsvr32 HTSOFT.dll" in the directory where you downloaded it.
- To remove older plugins, you need to locate the DLL and run the command "regsvr32/u filename.dll". When the new plugin is included with a compiler release, we will automatically install it and optionally uninstall older plugins.
Please keep providing your feedback.
Clyde
Edited by clyde (Thu Mar 15 2007 08:26 PM)
|
G.Neiss
Reged: Dec 26 2004
Posts: 474
Loc: germany
|
|
First:
Thanks for You clarifications.
Quote:
Precisely: the 3 you had before, plus a single new one.
Oh, I think, now I understood...
The new plugin will be (in future) the only one!
It will cover all kind of PICs (dsPIC & PIC12..24).
So if I use the enterprise version (as I do) I simply select HI-TECH Suite for my project and didn't have to change this even if I move from (for ex.) a PIC16xxx to PIC18xxx device. I only need to select my new device and the plugin will do the rest.
This is great !
(and now I know why it takes a bit longer to get the new plugin ready )
Did I understood this right now ?
After I do as You mentioned, I found it working as You stated.
I was a little bit confused the first time, because there is
- only an entry for 'Compiler' (none for 'Assembler' or 'Linker')
AND
- this entry shows the path to PICC-18 (STD)
when I select the new 'HI-TECH PICC Compiler Suite'.
So I think this is just a problem/limitation of MPLAB/new plugin, it's not forseen (in MPLAB) to have this kind of 'automatic compiler selection', so the path show in this dialog is just one possible one.
After I select this Toolsuite MPLAB frozes for some seconds (it searchs the available HI-TECH compilers ?), then I get a totaly new Options-Dialog (the new plugin!).
OK, I will try again (with the updated plugin).
If there are still questions I will report them here.
Just one more question (clarification):
Inside the new Options-Dialog on the 'Driver'-Tab I had all 4 (dsPIC, PICC, PICC-18 & PICC-18 PRO) HI-TECH Compilers listed.
Just to understand it right.
1. There is a Checkbox 'Automatic'
- If I select this the compiler used will be determined from the device selected (under Configure/Select Device) in the order they are listed in the 'Available drivers' Memo.
So if PICC-18 PRO is listed above PICC-18 STD the PRO will be used for PIC18xxx devices (and vice versa).
- If I uncheck it, the driver selcted manualy will be used (may the wrong one if I select dsPIC compiler and use a PIC18)
Is this correct ?
2. If I select a driver, there is some information given below 'Selected driver information'.
This is mainly the serial number.
For the PRO compiler there is althougth displayed:
'this licence will expire on Sun, 15 Apr 2007'
Because I am migrating my current project to PRO (as You know), I will run into trouble if the licence expires.
As mentioned from someone of Your staff (can't remember if it was You Mark or Jeff), the PRO will be freely available for enterprise customers.
Does it mean, that this licence limitation will be removed after PRO has reached its final stage ?
Or if it doesn't reach it till 15 Apr, there will be another trial period ?
This is very important for my project, because if there is any change, that the PRO compiler isn't available (for me) in the near future, I can't continue my 'migrating to PRO' because the changes to the project that I now had to do will result in incompatibilities with the STD.
|
G.Neiss
Reged: Dec 26 2004
Posts: 474
Loc: germany
|
|
Quote:
Include path now available and used for compile and link stages
Unfortunaly still not working (correct) 
With the old Plugin I use:
.;..\Common;..\..\PicInc
as the setting for $(INCDIR)
By using this I got the error:
Error [141] D:\Prj\X2_Hw7x\Sw\X2\X2_Defines.h; 22.30 die include Datei "BE_X2_CommonTypes.h" kann nicht geöffnet werden: No such file or directory
Even if I make the dirs absolute it will not work.
It seams, that it works only for one single directory!
If I use:
..\Common
the file BE_X2_CommonTypes.h will be found, but the the other once (with are in ..\..\PicInc) not.
It seams,. that the -I option is passed wrong.
The former plugin splits the given dirs at the ';' and pass every dir a a seperate -I option to the driver
e.g.:
-I. -I..\Common -I..\..\PicInc
The new one simply passes the complete string
-I.;..\Common;..\..\PicInc
Either the driver/compiler should be modified to handle multiple dirs or the plugin should work as the prev. one (splitting before pasing to driver).
|
clyde
Microchip staff
Reged: Oct 16 2003
Posts: 696
|
|
Quote:
The new plugin will be (in future) the only one!
That's correct - it automatically detects all your installed compilers and chooses the appropriate one to use for the selected chip.
Quote:
- this entry shows the path to PICC-18 (STD)
when I select the new 'HI-TECH PICC Compiler Suite'.
The location display that MPLAB provides is not used for anything important - but we have to fill it in otherwise MPLAB shows the tool as not being available. It will display the path to the compiler driver that will be used for the currently selected chip.
Quote:
1. There is a Checkbox 'Automatic'
This has now been removed - it was not used anyway. The plugin selects the first driver from the list, in order, that supports the selected chip. So to control which driver, you must use the "move up" and "move down" buttons to select the desired order.
This order is saved in the project file, so it can be different for different projects. Any new compilers installed will go to the end of the list, so nothing should change unless you want it to.
Quote:
For the PRO compiler there is althougth displayed:
'this licence will expire on Sun, 15 Apr 2007'
Because I am migrating my current project to PRO (as You know), I will run into trouble if the licence expires.
You will be able to download the final release and activate it with your Enterprise serial number. The temporary serial number for pre-release testing was issued to allow anyone to test it, but to prevent the pre-release version from being used in the future.
A new version of the plugin can now be downloaded from the same link. It has the following changes:
- The Include path can have semi-colon separated multiple paths
- The Driver tab on the options now also lists the chips supported by each driver
- Other minor changes
Clyde
|
Hans
Tester
Reged: Jun 09 2004
Posts: 13
Loc: Belgium
|
|
Thanks,
The new plugin seems to work very well.
Some minor comments:
- Is it really necessary to do a Reset Target of the icd2 after the build? Because of this reset, the output window ends up in the ICD 2 tab after the build instead of the Build tab which I would expect and want to see at that time.
Or is this a behavior of mplab and not the plugin?
- Is there a way to suppress the "Executing ..." lines in the Build output window? I would like to see only the errors and warning in there (most of which I generate in my code using #warning).
Regards,
Hans
|
Previous
Index
Next
Threaded
Edit
Reply
Quote
