Access violation, unable to compile

[keno]

I was just starting to play around with my new CCS USB demo kit (on XP with ICD-S40 and PCM/B 3.181 aand 16F877A) when I got the same message:

"Access violation at address 00405793 in module "Pcw.exe". Read of address 0000001C".

After looking at other posts for an hour and googling for clues, and reinstalling several times: I suddenly noticed that the drop down box on the top CCS compiler bar - where it says "Microchip 14 bit" was BLANK!

I clicked on the drop down box and chose "Microchip 14 bit" and the problem went away. NO MORE - "Access Violation..." - Sounds goofy but the compiler compiled immediately and my USB ex_usb_oscope.c works now.

Keno.

[SherpaDoug]

I have had really weird behavior when compiling code for a 12 bit chip with the 14 bit compiler selected in the drop down box, or vice versa. I use both frequently. Now that I know to check I don't have problems.
_________________
The search for better is endless. Instead simply find very good and get the job done.

[Alex]

I'm seeing the same error - "Access violation at address [x] in module 'Pcw.exe'. Read of address is [y]". The pull-down menu that usually contains "Microchip P18" or "Microchip 12 bit" is blank and cannot be changed.

I've tried all available CCS patches, tried the MPLab plugin, tried uninstalling and reinstalling, ensured the code I am trying to compile actually compiles fine on other machines, etc.

This is on a new (4 or 5 days old) IBM laptop.

Does anyone have any ideas? I will shortly be switching to C18 otherwise.

Thanks,
Alex

[PCM programmer]

Do you need to use the CCS IDE ? I haven't done this, but it's probably
possible to install the latest version of MPLAB and use it as the IDE
instead of the CCS one.
MPLAB has colored syntax, and CCS does offer a "plug-in" that you
can download and install, which allows easy integration into MPLAB.

[imET]

try deleting *.ini file in the isntalled folder
just something to try

[PCM programmer]

[pfournier]

I have been working with 3.242. All of a sudden I got:

"Access violation at address [x] in module 'pch.dll'. Read of address is [y]".

I tried everything in this thread to no effect. I finally went back to 3.236 and it flagged a missing bracket. I fixed it, returned to 3.242 (It is the only one that can complile for the 18F8622 correctly.) and it compiled fine!

I have reported this to CCS. But I thought I'd supply a "heads up".
_________________
-Pete

[dyeatman]

FWIW...

Every time I have ever gotten the "Access violation at address [x] in module 'pch.dll'. Read of address is [y]" type messages it has always been something in my C code that caused it.

I just start commenting out lines of code until the problem goes away and figure out what the compiler did not like. This has happened to me at least a dozen times so far.

[paul]

try opening the pcw.ini file in the program directory, and look for the line after "[compiler]". Change the index to 1 if it is not already.

It should look like this:
[compiler]
index=1

this did the trick for me, good luck

[GARY]

Hi
I bought PCM compiler last week. On start up for the first time it compiled with Access error. I found this forum and followed the advice given by pcm_programmer - ask for new registration files thanks for that). I emailed technical support which would of been 31 December 2006. A few hours later I got a reply asking me for my registation files!! I duly sent them and then on the 1st January 2007 they emailed me new registration files!! My PCM Compiler worked fine after that, and udated ok as well. I would like to add that CCS Technical Support was fantastic - I did not Expect this over the New Year holiday - thanks CCS Tech Support. So I would suggest anyone who has bought the PCM compiler and gets an Access error when compiling for the first time - contact Tech support.
Thanks
Gary