Ryan
HI-TECH team member
   
Reged: Jan 06 2004
Posts: 503
Loc: Brisbane, Australia
|
|
HI-TIDE^ v3.15 features:
- This release of HI-TIDE has been built upon the Europa Fall release (3.3.3) of Eclipse and CDT 4.0.3.
- Support for OS X Leopard
- Support for JAVA SE 6 (1.6).
- Support for HI-TECH C PRO for the Microchip PIC32 MCU Family beta.
- PIC32 Simulator and CWiz.
- Support for the HI-TECH C JTAG debug Interface for the PIC32.
Release Notes
The release notes, installed with HI-TIDE 3, detail the new enhancements, changes, fixes and limitations of this release of HI-TIDE 3. Please read this document before using this product.
Availability
HI-TIDE 3 is freely available to the public. Customers must register on HI-TECH Software's web site to download the product, however registration is free. To obtain HI-TIDE, just go to the downloads page and find "HI-TIDE 3 (compiler not included)" for the o/s of your choice.
The update site can not be used to upgrade to the 3.15 version of HI-TIDE.
~Registered trademark of HI-TECH Software Pty Ltd ^ Trademark of HI-TECH Software Pty Ltd
|
Guy Turcotte
stranger
Reged: Jun 19 2008
Posts: 1
|
|
Hi Ryan,
First, I would like to thank you for this new version. I'm still using Hi-Tide under Windows XP and I hope to migrate soon under OSX.
I started to work with version 3.13 and I'm now migrating to 3.15. To do that, I started from a brand new Workspace and created the project from scratch.
I've been having some issues with the management of compiler/linker options in the Project Properties Panel of version 3.15:
1) When I try to identify 24bit memory pointers, the compiler/linker command line output still show option --cp=16 instead of option --cp=24.
2) When I try to identify a Vector Offset (let say 800), the linker output still show --codeoffset=0 instead of --codeoffset=800.
In both cases, I've been able to get the problem resolved using the Advanced options for both the compiler and the linker.
Cheers!!
-- Guy
|
LateDeveloper
Tester - PICC PRO
Reged: Aug 20 2007
Posts: 197
|
|
hmm This does not accept projects written from ver 3.13 and migrating everything across is time consuming. Multiple conversion failures with errors such as failed to convert or yet another one telling me that a file is out of date or some such.
Can you tell me why this would be ?
This is such a pain to use I remain with version 3.13.
I would like to point out, this is not cleaning up after itself properly. Having created yet another copy of the project, only for it to fail, I cannot delete the directory structure, because it fails, and even exiting the program, the explorer cannot delete the directory due to the programme not having done its garbage collection, and is still hanging onto these files. The only way to actually delete them is to shutdown the machine, then delete. Very disappointed with this offering.
Actually fuming about this, it would appear that the programme has created 70 concatenated folders. ie control/control/control/control etc etc ....... Since win explorer won't go that deep to delete, it looks like I will have to do this manually.
Edited by LateDeveloper (Tue Jun 24 2008 10:06 AM)
|
holetse
stranger
Reged: Oct 27 2007
Posts: 2
|
|
This is awesome! Thanks so much for getting the Leopard issues resolved Ryan. I have HI-TIDE 3.15 running on OS X 10.5.3, and it works great. Glad to be able to switch back to OS X for my development.
For what its worth, I have had no trouble migrating projects from 3.13 to 3.15. HI-TIDE did throw a few cryptic errors, but they seem fine to ignore. All my old projects have been recompiled and work fine.
Edited by holetse (Fri Jun 27 2008 02:58 AM)
|
sdobi
Beta Tester
Reged: Feb 09 2008
Posts: 9
|
|
In this version of occurs the same problem as in 3.13. Namely, when the project sources are in subdirectory then the compiler in link phase cannot open the obj file because it is searching for them in the subdirectory.
Can we apply the same hotfix from 3.13 to 3.15? Of course we can rename the plugin files from 3.13 to 3.15....
-------------------- Sandor Dobi
AUTOCOM
HUNGARY
|
joemox
Reged: Dec 12 2006
Posts: 7
|
|
I think the object problem is related to http://www.htsoft.com/forum/all/showflat.php/Cat/0/Number/29651/an/0/page/0#Post29651
Could this be considered
|
Robert Gush
Reged: Mar 15 2005
Posts: 146
|
|
Does this version (series) of HiTide support the 8051 at all?
|
lucky
HI-TECH team member
   
Reged: Oct 06 2003
Posts: 1054
Loc: Brisbane, Australia
|
|
Quote:
Does this version (series) of HiTide support the 8051 at all?
No. Not yet. The Silicon Labs 8051 compiler that is currently being beta tested will integrate into Silicon Labs IDE however.
-------------------- Matt Luckman
HI-TECH Software
|
LateDeveloper
Tester - PICC PRO
Reged: Aug 20 2007
Posts: 197
|
|
I decided to put the new version on again and retry. I have XP64 as the O.S. so this may be part of the issue.
I try to create a new project and it tells me the old archived old project (same name) is version 3 and would I like to convert it to version 4, to which I reply yes, then the machine stops responding.
So I created a new project altogether and that went fine, until I imported the old files in, and it decided to throw a wobbly on a build, by telling me that <htc.h> does not exist in the project. It gives the project path rather than looking in the install path for the pro compiler. ?
Any help on this would be much appreciated, since I do like the new look and feel of the eclipse environment over the old version.
Further to this, it tell me that there is a syntax error in my setup file, which did not exist before.
__CONFIG(INTIO & WDTDIS & PWRTDIS & MCLREN & UNPROTECT & UNPROTECT & BORDIS & IESOEN & FCMEN);
I presume this is because paths are completely wrong after installing this product.
Ok I have fixed the above, by removing every vestige of both HiTide and PIC Pro from my system, then doing a clean install of everything.
I still get a problem with importing projects however, so have resolved to ignore the so called utilities for doing this, and created new projects and transferred the files into the new project. However this seriously needs looking into, given that I really don't want to do this on every new release.
Edited by LateDeveloper (Fri Jul 25 2008 06:06 PM)
|