Microchip C18 - All versions

[metal]

New MPLAB C18 fake:

Created to make it possible to install MPLAB C18 compiler without the need to install the full compiler setup in order to save disk space and time waiting for the setup to finish!

It is possible to delete folder C:\MCC18 once you are done installing the latest compiler version.

MeTaL

[robban]

Anybody got hold of this? Crack or serial?

Thanx in adv. Robban

[Magnox]

Can it not be downloaded from microchip here:

http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en010014)

and installed over the old full version from here:

http://www.sonsivri.to/forum/index.php?topic=6167.0

That's what I did with 3.40. I have read though that there's a glitch that 3.41 fails to install over 3.40 - the fix was to revert to an older full version.

Edited to add

I just downloaded and installed 3.41 over 3.40 - seems to work fine for me.

[pumper]

I installed c18fake then old full version 3.10 and then 3.41 upgrade and it worked for me

[sertek]

1) Download C18FAKE.EXE from address below
    hxxp://math.haifa.ac.il/robotics/SWdevEnv/2007/MICROC~1.40_/?C=N;O=D

2) Run C18FAKE.EXE

3) Download Microchip C18 Compiler V3.35 Upgrade from microchip website.
     hxxp://ww1.microchip.com/downloads/en/DeviceDoc/MPLAB-C18-Upgrade-v3_35.exe

4) Installed 3.35 Upgrade (Selected C:\MCC18 as the directory to install to)

5) Download & Installed 3.38 Upgrade or later (Selected C:\MCC18 as the directory to install to)
   hxxp://ww1.microchip.com/downloads/en/DeviceDoc/mplabc18-v3_41-windows-upgrade-installer.exe

[mitsos]

hi

as the solution with c18fake.exe is not working at my place

according to post http://www.sonsivri.to/forum/index.php?topic=2374.msg126541#msg126541

I test this solution and finally success!

all that needed is here
http://ifile.it/mdr6jck

regards
mitsos

[mitsos]

hi

here

http://ftp://Compilers-RO:C0mP[email protected]/MPLAB%20C%20for%20PIC18/mplabc18-v3.40-windows-full-installer.zip

you can find the full version of mpabv18 compiler, after install it you can apply the updates.

regards
mitsos

[metal]

I don't know why you are still using this compiler. Microchip has already released XC compilers, and it seems that they got rid of PICC-18 and stick to c18 for which all the libs were originally written. Hi-Tech has taken over c18 development, so I expect XC to be better now concerning c18.

xc v1.0 doesn't mean the compilers within that setup are mature. But the strange thing is the release of two updates for c18 after releasing xc8, this is rather confusing.

seems I started to contradict myself here.

[spasbyspas]

I don't know why you are still using this compiler.

Because it's (XC) too new!
Once clear of the bugs will be actively used!
Viva C18!

[mitsos]

Metal

the first thing is a clean(or official) method to install without fake.exe or other tricks.
Second I know that these compilers are going to at its end as soon they are substituted with xc ones, so my post concerns the collectors.

I install xc8 and I see in installation folder known parts from both hitech and mplabc18 compilers. I think they mix the compilers. I see from time to time posts in various forums, personal opinions about what compiler is the best. I think the most experienced members here after a discussion, to post a sticky for this: how to test a compiler.

It is easily to say that the good compiler is that who

gives the smallest (in size) possible code
gives the fastest (in execution time) possible code
has as many as possible libraries (functions and peripheral chips)
has a very friendly and powerful debbuger
and so on

Sometime ago I see an application note from TI, in which I read how to implement the function sin(x) very effectively for signal proccesing purposes in dsp controllers. I see in the pic and avr compilers that sin(x) in most cases is approximated by Taylor series which is very time consuming.

regards
mitsos

[metal]

mitsos, I have nothing against your post, I do appreciate your posts and effort on the forum :- )

Experienced users know how to use small asm routines that do big jobs, as you 've already said, you can do existing functions with smaller codes, whether in asm or in C. Isn't it better to write your own functions that convert integers/decimals to char to display them on the LCD instead of using printf? It is not always necessary or a must to use existing compiler functions and libraries, look at this one function, I used it to display two digits only for a clock function:

Code:

char* bin2bcd( unsigned int val )
{
  char i;
  static char digit[2];
  
  val -= 100;
  i = '0' + 10;
  do
    i--;
  while( (val += 10) & 0x8000 );
  digit[0] = i;

  digit[1] = val | '0';  
  
  return digit;
}  

This is truly a nice routine to use instead of using % and / or even the printf function.

[omni]

v3.42 is out ...

http://ww1.microchip.com/downloads/en/DeviceDoc/mplabc18-v3_42-Upgrade-installer.exe

[Diecore]

v3.42 is out ...

http://ww1.microchip.com/downloads/en/DeviceDoc/mplabc18-v3_42-Upgrade-installer.exe

I don't get what's the point of C18 updates when XC18 is out? Well i know at least for compatibility reasons as i also tried to compile an old version of Microchips TCP/IP stack and i didn't work with the XC18 but i didn't expect that microchip will continue supporting C18 when they released XC18 v1.0

[metal]

I don't get what's the point of C18 updates when XC18 is out? Well i know at least for compatibility reasons as i also tried to compile an old version of Microchips TCP/IP stack and i didn't work with the XC18 but i didn't expect that microchip will continue supporting C18 when they released XC18 v1.0

answer is simple, XC8 is very buggy!!!

If microchip shows you the list of bugs they received in the last couple of weeks, you won't even think about downloading XC8 to use it with PIC18 :- )

Header files for many PICs were suddenly changed from v1.00 to v1.01, ironic indeed.. It is by far better to stick to C18.

If you have read the topic, and came across spasbyspas and mitsos answer, you would not have posted this question again... I have already fallen into the same trap, till I saw some bugs that made me revert back to what I was using in the past..

[odessa]

Hi,

This is C18 ver 3.10 Full

Requires no fix,no serial plus it can be updated using the updates from Microchip. Just remember to point the update to the install directory ( default is C:\MCC18 )

[tomywong]

v3.43 is out

http://ww1.microchip.com/downloads/en/DeviceDoc/mplabc18-v3.43-windows-upgrade-installer.exe

[jayanthd]

@mitsos

I am not able to download mplabc18-v3.40-windows-full-installer.zip
Please provide me a new link

[metal]

New MPLAB C18 fake:

Created to make it possible to install MPLAB C18 compiler without the need to install the full compiler setup in order to save disk space and time waiting for the setup to finish!

It is possible to delete folder C:\MCC18 once you are done installing the latest compiler version.

MeTaL

[towlerg]

Metal

probably a dim question but where (in the directory structure) do you put "mcc18-traditional.exe". If I execute it, it reports itself as "MPLAB C18 v3.10" which of course is the object of the exercise. If I rename the default C18 3.1 directory, C:\MCC18, to something else I am still able to build and make successfully. I'm clearly missing something!

Rgds
towlerg

[Magnox]

You do not need the fake at all, once a real version has been installed. The fake is only detected during the real installation process to allow the installation to happen. Afterwards, rename it, delete it, drop it in a lake... MPLAB doesn't care!

As MeTaL said:

It is possible to delete folder C:\MCC18 once you are done installing the latest compiler version.

[metal]

v3.45 is out:

http://ww1.microchip.com/downloads/en/DeviceDoc/mplabc18-v3.45-windows-upgrade-installer.exe

[odessa]

Hi,

There is a bug in the software library files of 3.45 that affects a few chips. I was using a 4520 and the SPI library and kept getting a compile error

Error - could not find definition of symbol 'WriteI2C1' in file.......

The fix is to copy the lib folder from 3.43 into 3.45 until its fixed. Or not to be lazy like me and write your own libraries 

[metal]

can you specify the line in the file that is causing the error?

[odessa]

Hi Metal,

Its when you try and include and use the SPI Library and I2C library. The commands WriteI2C and WriteSPI aren't recognised. I spent ages looking for the reason then found this:

http://www.microchip.com/forums/m710413.aspx

[CrankCase]

Can confirm here - we do a lot of PIC18 code, and for sure the Microchip XC version of this stuff is no that great.  For us the regular 8.30 ~ 8.80 IDE is much faster and easier on older machines.  The java stuff---is OK only on a newer machine that can handle it.

For now stick to the C18, don't upgrade unless you have to.  At least that's what we do at our shop.  Especially if you're using the TCP/IP stack.

[metal]

v3.46

http://ww1.microchip.com/downloads/en/DeviceDoc/mplabc18-v3.46-windows-upgrade-installer.exe

[Binary1955]

v3.47 is out

http://ww1.microchip.com/downloads/en/DeviceDoc/mplabc18-v3.47-windows-upgrade-installer.exe