Hi-Tech PIC Compiler latest versions

[Top]

HI-TECH Universal RSA Keygen

* HI-TECH Universal RSA Keygen generates real RSA signed activation data.
* Replaces HI-TECH RSA public key with self-generated RSA key - different every time!
* Generates permanent PRO key - no expiry date!
* Tested with:

• HI-TECH C Compiler for PIC10-12-16 MCUs
• HI-TECH C PRO for the PIC18 MCU Family
• HI-TECH C PRO for the PIC32 MCU Family
• HI-TECH for dsPIC-PIC24
• HI-TECH C PRO for the Silicon Labs 8051 MCU Family
• HI-TECH C PRO for the PSoC Mixed-Signal Array
• HI-TECH C for Holtek MCU
• HI-TECH PICC-18 STD

* New in version 2.2

• Enhanced error detection & reporting.
• 64-bit version included.
• Includes CLEAN.BAT to remove HI-TECH data from VirtualStore.
  See http://www.sonsivri.com/forum/index.php?topic=935.msg99989#msg99989

* New in version 2.3

• Updated to support HI-TECH C Compiler for PIC10-12-16 MCUs V9.71a.
  See http://www.sonsivri.com/forum/index.php?topic=935.msg101920#msg101920

HI-TECH Universal RSA Keygen (v2.0)
http://depositfiles.com/files/kj9mws7yh

HI-TECH Universal RSA Keygen (v2.1)
http://depositfiles.com/files/oy699bhti

HI-TECH Universal RSA Keygen (v2.2)
http://depositfiles.com/files/2mhscdmb4

HI-TECH Universal RSA Keygen (v2.3)
http://depositfiles.com/files/v6vup2azq


You can find 50caliber post here, the older sticky:
http://www.sonsivri.com/forum/index.php?topic=935.msg69111#msg69111

[SpaleKG]

Can I obtain source code of linux keygen version, I want to try keygen on OSX version of HI-TECH.

Best regards.

[Top]

Can I obtain source code of linux keygen version, I want to try keygen on OSX version of HI-TECH.

Here is an old OSX port; should still be working:

http://ifile.it/qbdhnye/HT_Keygen

[SpaleKG]

Here is an old OSX port; should still be working:

http://ifile.it/qbdhnye/HT_Keygen

It said activation success but seems it doesnt work

spale@spale:~$ picc18 --ver
(1273) Omniscient Code Generation not available in Lite mode (warning)
HI-TECH C Compiler for PIC18 MCUs (Lite Mode)  V9.80
Copyright (C) 2011 Microchip Technology Inc.
spale@spale:~$ picc --ver
(1273) Omniscient Code Generation not available in Lite mode (warning)
HI-TECH C Compiler for PIC10/12/16 MCUs (Lite Mode)  V9.83
Copyright (C) 2011 Microchip Technology Inc.
spale@spale:~$

Maybe I need to know for what version of compiler keygen is and try to use that version.
Can you provide that info?

[Top]

Maybe I need to know for what version of compiler keygen is and try to use that version.

It should work on any version but you need to manually search and replace RSA key.

[SpaleKG]

It should work on any version but you need to manually search and replace RSA key.

If you mean to replace activate.dat I did that (I overwrite original one in /Applications/HI-TECH/picc-18/9.80/bin/).
Here is complete procedure:

spale@spale:~$ ./HT_Keygen
HI-TECH Universal RSA Keygen for OSX v1.0
==> Enter serial number [e.g. HCPIC18P-654321]: HCPIC18P-654321
==> Generating new RSA key.
==> Saving new RSA key to activate.dat
==> Writing key file to keyfile.dat

spale@spale:~$ cp activate.dat /Applications/HI-TECH/picc-18/9.80/bin/

spale@spale:~$ /Applications/HI-TECH/picc-18/9.80/bin/activate --keyfile=keyfile.dat --serial=HCPIC18P-654321

HI-TECH Product Activator v1.1
Copyright (C) 2011 Microchip Technology Inc.

Activation successful.

spale@spale:~$ picc18 --ver
(1273) Omniscient Code Generation not available in Lite mode (warning)
HI-TECH C Compiler for PIC18 MCUs (Lite Mode)  V9.80
Copyright (C) 2011 Microchip Technology Inc.

UPDATE:

Thanks to Top I finally did it.
All executable files need to be searched for RSA key (old one) and replaced with context (binary) with generated one (from activate.dat). Now I receive:

spale@spale:~$ picc18 --ver
HI-TECH C Compiler for PIC18 MCUs (PRO Mode)  V9.80
Copyright (C) 2011 Microchip Technology Inc.
Serial number: HCPIC18P-654321 (PRO)
spale@spale:~$

I will make patcher for auto patching. When I finish that I will let you know.

[leosedf]

Can someone help me get the Hi-Tech compiler running in Flowcode PIC version?

I was wondering that too, is there any option to use hitech with flowcode?

[shila]

Hi ,
i'm in trouble.

The command :
>Picc --ver
sais :

c:\Programmi\HI-TECH Software\PICC\9.83\bin>picc --ver
HI-TECH C Compiler for PIC10/12/16 MCUs (PRO Mode)  V9.83
Copyright (C) 2011 Microchip Technology Inc.
Serial number: HCPICP-171073 (PRO)

but when i build a project it sais:

HI-TECH C Compiler for PIC10/12/16 MCUs (Lite Mode)  V9.83
Copyright (C) 2011 Microchip Technology Inc.
Serial number: HCPICP-171073 (PRO)

please help me.
Thanks

[Top]

but when i build a project it sais:

HI-TECH C Compiler for PIC10/12/16 MCUs (Lite Mode)  V9.83
Copyright (C) 2011 Microchip Technology Inc.
Serial number: HCPICP-171073 (PRO)

1. Uninstall.
2. Run CLEAN.BAT.
3. Re-install.
4. Run HI-TECH Universal RSA Keygen.

[Sideshow Bob]

I get the same then running the compiler in lite mode from MPLAB. In MPLAB select (toolbar) project->buil options->peoject Then select the compiler tab and set operation mode to pro or whatever you feel you can handle

[shila]

Perfect!

Just as Sideshow Bob  said.
Now it work in pro mode:

HI-TECH C Compiler for PIC10/12/16 MCUs (PRO Mode)  V9.83
Copyright (C) 2011 Microchip Technology Inc.
Serial number: HCPICP-171073 (PRO)

[shila]

Hi,

which is a valid alternative to "mplab ide" as Ide to program with Htsoft. Mplab X is too heavy , and Mplab Ide 8 is too skinny. I mean an ide with compiler option and auto indent etc.

Thanks

[tavioman]

I use Visual Studio.

[metal]

how do you configure it, explain to us plz.

[tavioman]

Create a file called project.cmd(name is not important);

Code:

--CHIP=18F4431 
--ERRFORMAT="%f(%l) : error %n: %s"
--WARNFORMAT="%f(%l) : warning %n: %s (%a)"
--MSGFORMAT="%f(%l) : message %n: %s"
--OPT=speed
--TIME
-Q
--WARN=-9
--ASMLIST
--OUTPUT=mcof
--IDE=MPLAB
--ERRORS=10
--CALLGRAPH=full
--ECHO
-M5_0_0_slave_debug.map
-N100
-X
-DFOSC=40000000UL
-DGLOBAL_DEBUG=1
-DVERSION_NUMBER=800
-O"Debug\project.hex" 
--OBJDIR="obj\slave\debug\8_0_0"

-I"..\..\..\source\drv\PIC18F4431"
-I"..\..\..\source\sys\PIC18F4431" 
-I"..\..\..\source\err"
-I"..\..\..\source\std"
-I"..\..\..\source\app\2009\adv\slave"
-I"src"

..\..\..\source\app\2009\adv\slave\AppBrake.c
..\..\..\source\app\2009\adv\slave\AppMain.c 
..\..\..\source\app\2009\adv\slave\AppMotor.c
..\..\..\source\app\2009\adv\slave\AppIsr.c
..\..\..\source\app\2009\adv\slave\AppAdc.c
..\..\..\source\app\2009\adv\slave\AppSpi.c

..\..\..\source\drv\PIC18F4431\DrvAdc.c 
..\..\..\source\drv\PIC18F4431\DrvQei.c
..\..\..\source\drv\PIC18F4431\DrvPwm.c
..\..\..\source\drv\PIC18F4431\DrvTimer.c
..\..\..\source\drv\PIC18F4431\DrvEusart.c
..\..\..\source\drv\PIC18F4431\DrvGpio.c
..\..\..\source\drv\PIC18F4431\DrvSsp.c
..\..\..\source\drv\PIC18F4431\DrvCcp.c

..\..\..\source\std\Controller\StdPi.c

Configure PIC used:

Code:

--CHIP=18F4431

Configure messages to be understood by Visual Studio and to be displayed in standard output.

Code:

--ERRFORMAT="%f(%l) : error %n: %s"
--WARNFORMAT="%f(%l) : warning %n: %s (%a)"
--MSGFORMAT="%f(%l) : message %n: %s"

Compile optimize for speed:

Code:

--OPT=speed

In output display total time it took for compiling the project

Code:

--TIME

Warning level

Code:

--WARN=-9

Forgot these, but can be found on user manual of compiler

Code:

--ASMLIST
--OUTPUT=mcof

This will output files compatible with MPLAB and PROTEUS.
Useful for simulation.

Code:

--IDE=MPLAB

Stop compilation after this number of errors:

Code:

--ERRORS=10

--CALLGRAPH=full
--ECHO

Output MAP file:

Code:

-Mproject.map

This one tells compiler the maximum identifier length:
For example if you have a function called MyFunc(),this one has identifier length of 6 (1M 2y 3F 4u 5n 6c)

Code:

-N100

-X

Global defines:
These are similar to:
#define OSC 40000000UL
#define GLOBAL_DEBUG 1
#define VERSION_NUMBER 800

Code:

-DFOSC=40000000UL
-DGLOBAL_DEBUG=1
-DVERSION_NUMBER=800

Output HEX:

Code:

-O"Debug\project.hex" 

Object files output folder:

Code:

--OBJDIR="obj\slave\debug\8_0_0"

Include folders(as you can see,these can be relative paths):

Code:

-I"..\..\..\source\drv\PIC18F4431"
-I"..\..\..\source\sys\PIC18F4431" 
-I"..\..\..\source\err"
-I"..\..\..\source\std"
-I"..\..\..\source\app\2009\adv\slave"
-I"src"

These are project c files:

Code:

..\..\..\source\app\2009\adv\slave\AppBrake.c
..\..\..\source\app\2009\adv\slave\AppMain.c 
..\..\..\source\app\2009\adv\slave\AppMotor.c
..\..\..\source\app\2009\adv\slave\AppIsr.c
..\..\..\source\app\2009\adv\slave\AppAdc.c
..\..\..\source\app\2009\adv\slave\AppSpi.c

..\..\..\source\drv\PIC18F4431\DrvAdc.c 
..\..\..\source\drv\PIC18F4431\DrvQei.c
..\..\..\source\drv\PIC18F4431\DrvPwm.c
..\..\..\source\drv\PIC18F4431\DrvTimer.c
..\..\..\source\drv\PIC18F4431\DrvEusart.c
..\..\..\source\drv\PIC18F4431\DrvGpio.c
..\..\..\source\drv\PIC18F4431\DrvSsp.c
..\..\..\source\drv\PIC18F4431\DrvCcp.c

..\..\..\source\std\Controller\StdPi.c

After you configure this file you should tell VS:
PICC18.exe @project.cmd

This line you should provide it in configuration of your VS project.
Sadly on this PC I don't have VS installed to show you a screenshot, but I'msure you will find your way.
If there still is interest I'll provide it tomorrow.

Have fun!

[allunderthesun]

looking for the OSX version. the link is dead?

[allunderthesun]

Can I use the windows version and copy the key to OSX? is it possible?

[robban]

With the risc of getting warned; Let's face it, MPLABX is a mess, and they use us as ginny pigs. I never use it as a default IDE, only when I try to import an already fine .mcp file. Even my MPLAB ICD3 protest when I try to import a project.
The only thing that's working alright is the driver switch, but on the other hand, who needs another switch? Me? Microchip?

[danielausparis]

First impressions about Hi-Tech PICC on Archlinux:

- installation is smooth as per forum instructions. It has to be made very clear that a working eth0 connection is mandatory for the key management process.
- it has to be noted that the dynamically-linked keygen refers to ssl libraries that are quite "old" in Archlinux terms (being a rolling release distribution, it features always latest packages compared to other distros). Workaround: cheat by creating symbolic links from the actual ssl libraries to the libraries asked for by the keygen program. It works, although with a warning. A long term solution would be a source release of the keygen, or a statically linked one.

The PICC package, even once installed and validated PRO with the keygen, runs in PRO mode only as long as a working eth0 is available. If not, it reverts to LITE mode (and back). This might be surprising for laptop users.

I did a small benchmark of PICC against CC5X (full optimizing version available elsewhere in this forum). I was surprised to find out that CC5X produces about 20% smaller code.

The next step will be to deploy the PIC18 version of the compiler.

[SpaleKG]

looking for the OSX version. the link is dead?

This is RSA key generator, but you need to use some HEX editor and change/replace RSA keys from executables with generated ones.

http://turbobit.net/7imhp5fv8el5.html

EDIT:

This is very strange on MacOSX.

In terminal when I check version it said:

spale@macpro:/Applications/HI-TECH/picc-18/9.80/bin$ ./picc18 --ver
HI-TECH C Compiler for PIC18 MCUs (PRO Mode)  V9.80
Copyright (C) 2011 Microchip Technology Inc.
Serial number: HCPIC18P-720066 (PRO)

In MPLABX when I select toolchain it said:




But when compile in MPLABX then I receive this:




Does this seems that MPLABX have original Microchip RSA keys in binaries ?
Or how to fix this issue?

[SpaleKG]

Forget about the tar.gz and run files, I have it installed and have the 'whole filesystem tree'.

I'll try and explain again

It looks like the Linux ELF executable files, activate and picc are now packed or protected with something and I am having trouble running them in a debugger. If you try to load activate into a disassembler you'll see what I mean. I don't know anything about unpacking Linux ELF executable files but if you can unpack them then a patch will be simple.

At this moment UPX packer for executables is the only one for Linux platforms. Try to unpack binary with UPX.

[Top]

Does this seems that MPLABX have original Microchip RSA keys in binaries ?
Or how to fix this issue?

I think I remember seeing a setting somewhere in the IDE that allows you to switch between different versions of the compiler. I guess you have it set to Lite mode so look for this switch and set it to PRO mode and you should be okay.

At this moment UPX packer for executables is the only one for Linux platforms. Try to unpack binary with UPX.

Seems like you missed my later post saying "Please disregard my last few posts about the Linux ELF files being packed/protected. Somehow the v9.81 download got corrupted and it made things look wierd in IDA."

[SpaleKG]

I think I remember seeing a setting somewhere in the IDE that allows you to switch between different versions of the compiler. I guess you have it set to Lite mode so look for this switch and set it to PRO mode and you should be okay.

In MPLABX IDE I can click on search and IDE adding all toolchains which are founded to be installed (also can be manually added but that is always about path to bin/ folder).

So everywhere it said PRO but when compile/build it mentioning Lite mode colored by red in Output window.

However I cant find anything in whole IDE about selecting/switching between Lite/PRO mode. If anyone have this issues on MPLABX with HI-TECH compilers, and find solution, please share.

[Top]

However I cant find anything in whole IDE about selecting/switching between Lite/PRO mode. If anyone have this issues on MPLABX with HI-TECH compilers, and find solution, please share.

You need to look a little harder

[Okada]

Hi Top

I have a problem using Hi Tech Compilers latest version registered with v2.3 RSA Keygen. See the attached image. If I select Pre Process assembler and Assembler check boxes and Compile I get wrong hex files which doesn't work properly. It is the same with all Hi Tech C compilers.

[Top]

Please provide a complete project that highlights the problem.