Hi-Tech Usage

[tavioman]

Hi everybody.
If anyone is intersested in using HiTech compilers for PIC say your vote here.

My goal is to make HiTech as easy as CCS. This will be an advantage because Hi Tech is not that buggy as CCS.

Here is an example:

http://www.sonsivri.com/forum/index.php?topic=10827.msg46283#msg46283

[shobits1]

I agree with tavioman, Hi-Tech is the most powerfull complier for pics, less bugs, more code effecient, better code optimisation, less in using space, the only inconvenient was you must do everything by your self

[omni]

Also it's an ANSI C compliant compiler which is yet another reason to use it, beside being available on all platforms. I wanted to make the switch so many times but lack of drivers kept me away and CCS C was so much easier to use because of it.

[mcnscott]

I downloaded the student version of hi-tech, it's amazing how different compilers can be that do the same thing.  Looking at the examples so far I'm a bit confused how the fuses are set I'm use to writing each fuse out individually.

[tavioman]

It's quite easy, here is a small example for PIC18F4520:

Code:

__CONFIG(1, HSPLL & FCMEN & IESODIS);
__CONFIG(2, PWRTEN & BOREN & BORV27 & WDTEN & WDTPS256);
__CONFIG(3, CCP2RC1 & PBDIGITAL & LPT1DIS & MCLREN);
__CONFIG(4, XINSTDIS & STVREN & LVPDIS & DEBUGDIS);
__CONFIG(5, CP0 & CP1 & CP2 & CP3 & CPB);
__CONFIG(6, UNPROTECT);
__CONFIG(7, UNPROTECT);

For every configuration register you will find values in PIC header.

[robban]

Hmm... Tavioman, do You know how to calculate the different fuse combinations into a single hex value?
Thanx

[tavioman]

Well... every configuration word has different settings.
As you can see in my example different settings are and-ed together.

Code:

__CONFIG(1, HSPLL & FCMEN & IESODIS);

This is equal to:

Code:

__CONFIG(1, 0xF6FF & 0xFFFF & 0x7FFF);

Wich is equal to:

Code:

__CONFIG(1, 0x76FF);

All values are defined in processor specific header.