new install of PCM 3.245: unknown version number?

rbgorbet · Joined: 15 Feb 2007 Posts: 17

I've just done a clean install of PCM 3.245 and MPLAB 7.50 after removing MPLAB 6.40 and PCM 3.098. Whether I run ccsc.exe via the MPLAB IDE or from the command line, I get an "Access violation at address 00000000. Read of address 00000000."

Running from MPLAB results in the following output after the Access violation:

Clean: Deleting intermediary and output files.
Clean: Done.
Executing: "C:\Program Files\PICC\Ccsc.exe" "i_you.c" +FM +DF +LN +T -A +M -Z +Y=9 +EA
Error: The selected compiler: "PCM" is not installed on this PC
Halting build on first failure as requested.
BUILD FAILED: Sat Feb 17 00:52:30 2007

Here's a screen shot: http://tarsas.uwaterloo.ca/rbgorbet/pic_code/screenshot.jpg

The PCM dialog window has a title bar which shows "Version ???", and the registration information shows as ???, ???. I've looked at the .crg file (that came with the install CD) and it contains my "reference number", P328682895.

Also open in the screen shot is the little "version number" dialog which comes up when you run ccsc.exe +V. Notice it's empty.

What you can't see in the screen shot is that the little listing "ticker" keeps on tickering (it's still animated), but it will just sit there forever doing that until closed.

I'm assuming the access violation and empty registration/version info are related. Any thoughts are greatly appreciated.

Rob.

PCM programmer · Joined: 06 Sep 2003 Posts: 21708

I don't have your exact environment, but I tried to emulate it as closely
as I could.

1. I don't have MPLAB 7.50 here. I do have 7.41. I installed it in
Windows 2000. This is a fresh install. It's never been on that
drive before. I let be installed in the default directory, which is
c:\Program Files\Microchip

2. I installed the PCM compiler, vs. 3.245. I installed it in the default
directory of c:\Program Files\Picc
The installation program installed the PCM.CRG license file into that
same directory, at the time of the installation.

3. I downloaded the latest CCS "plugin" program from the CCS website:
http://www.ccsinfo.com/downloads/setup_mplab_plugin.exe
I installed it, and let it use the default directory given in item #2.

4. I started MPLAB and created a new project.
One important thing -- I normally put my projects in the compiler
directory of c:\Program Files\Picc\Projects. Then within that directory,
I have my individual folders for each project. You're using the
"My Documents" folder, which gives you a very long path.
Maybe it will work, but I wouldn't do it that way right now.
Do it the way I did it.

5. In this thread, I give the steps to setup a project in MPLAB.
In this particular case, the project is based on a CCS example file,
so I use c:\Program Files\Picc\Examples as the directory.
http://www.ccsinfo.com/forum/viewtopic.php?t=22956

Make sure you do everything in the correct order, as shown above.

This thread talks about the Access Violation problem.
http://www.ccsinfo.com/forum/viewtopic.php?t=27344

I don't recognize the format of that number in your .CRG file at all.
My PCM.CRG file doesn't have a number of that length, with a letter
stuck in front of it. Is this CD-ROM from some special version of
the compiler, that came with a book ? That might explain it.
But then, it should work.

rbgorbet · Joined: 15 Feb 2007 Posts: 17

Thanks, PCM Programmer. I will try what you suggest with the shorter filenames.

The compiler was purchased through Microchip. It came shrink-wrapped with the PIC MCU C Compiler Reference Manual, and had a sticker on it with CCS's logo which says "PCM v3.245 Licensed to: Reference Number P328682895."

I suppose it is possible that they "pre-license" a bunch of copies for resale through distributors, but then these copies need to be "registered" before they can be used. So I went through the "compiler registration" process on the CCS website just now, although that appears to be only for updates. Of course, I won't get the files until Monday at the earliest. :-(

The link you sent about the Acces Violation was no good ("The topic or post you requested does not exist"). I do know there are a bunch of threads on an access violation in the *.DLL when the wrong compiler type or device type is selected. I think this one is different (because of the zero address) and I tried searching the forums but didn't find anything, so if you have found something please send a working link.

Thanks again. I have to go out for an hour but will try later this AM.

Rob.

PCM programmer · Joined: 06 Sep 2003 Posts: 21708

I just clicked on all the links in my post. They all work.

rbgorbet · Joined: 15 Feb 2007 Posts: 17

PCM programmer · Joined: 06 Sep 2003 Posts: 21708

Here's a thread where they say the problem is the registration file:
http://www.ccsinfo.com/forum/viewtopic.php?t=26155

rbgorbet · Joined: 15 Feb 2007 Posts: 17

Thanks PCM Programmer. I need to get better at finding keywords that work! I honestly did what I thought was a good search but I guess I missed that one; it is exactly my problem. I strongly suspect that compilers sold through distributors are "pre-licenced" but need to have the registration files "verified" when installed. I expect on Monday that I will get working registration files.

For now, I'm learning about PCL and PCLATH and going to have a look at what might be a workaround that will allow me to test over the (rest of) the weekend.

Thanks again! The speed and quality of response in this forum is excellent, and I suspect that's entirely due to you. You're the only one who picked up my posts, then monitored them religiously and put up with my (somewhat panicked) rambling. Normally I'm more level-headed. If there is a forum award, I nominate you!

Rob.

rbgorbet · Joined: 15 Feb 2007 Posts: 17

I've traced through the LST file after reading about PCLATH and memory paging in the 16F87xA datasheet. Here is what I've found (comments added):

rbgorbet · Joined: 15 Feb 2007 Posts: 17

I found the opcode in the hex and modified it to BCF A.4 instead of BSF A.4, and fixed the checksum in the hex file. The code got further, but didn't run properly still. Must be something else somewhere...

PCM programmer · Joined: 06 Sep 2003 Posts: 21708

Vs. 3.098 has got bank select bugs. This affects the RAM banks.
The bug that you found affects the Program Address Counter.
Based on this post (previously referenced), the compiled code likely
has bank select bugs as well:
http://www.ccsinfo.com/forum/viewtopic.php?t=27813

rbgorbet · Joined: 15 Feb 2007 Posts: 17

CCS sent me the new registration files for 3.245 this morning and things appear to be resolved. Now I just need to finish the code. Thanks again for all your help.

Rob.