Two Versions of MPASM in the Same Computer???

[rsocor01]

Hi all,

I have installed two versions of PBP in my computer, 2.50c and 2.60c. Whenever I need to use either one I would go to the "Compiler" tab in the "Compile and Program Options" in Microcode Studio and chose either one of them.

Now, I have some 18F4550 programs in PBP 2.50 that are working fine and I would like to keep them the way they are. They require MPASM v8.15 to assemble, which is what I have installed in my PC. I believe newer versions of MPASM won't work with PBP 2.50. Lately, I have been working in a project with a PIC16F1939 that requires PBP 2.60. The old version (v8.15) of MPASM that I have won't work with this chip. I need to have a newer version of MPASM installed.

Now comes my question. Can I install a newer version of MPASM in a different folder and use either one of them as I need them by selecting the appropiate folder in the "Assembler" tab in MCS? Does anybody else do this? Is there a workaround for this issue?

Thank you all for your help,

Robert

[mackrackit]

I have not tried it with MPLAB, but when you install select another directory, but I am saying that without knowing what MPLAB does to the registry. (make an image of your drive first, something may break..)

2.5 -- 2.6 should not be a problem if LOOP is not used as a label. Why not try making a copy of the old code and try it in 2.6?

[rsocor01]

Dave,

Thank you for your response. Yes, I'm afraid to mess my computer up if I install two versions of MPASM. In another computer I have installed PBP 2.60c and MPASM v8.60 and my 16F1939 PBP program compiles without any errors.

Now, in my other PC where I have PBP 2.60c and MPASM v8.15 I get a bunch of errors when compiling.




I assume that the cause of the errors might be the older version of MPASM, but I'm not sure if this is the cause. I checked for the file 16f1939.inc and it is in the directory where it's supposed to be. Any ideas what might be wrong?

Robert

[mackrackit]

I looked at MPLAB 8.00 on one of my machines and the P16F1939.inc is not there. I skipped 8.15...

I checked for the file 16f1939.inc

I will assume that was in the PBP directory.
Goto - program files - microchip - MPASAM suite- and look for P16F1939.inc

But again I have not had a problem with old code moving forward with the exception of having a label named something that is now a reserved word (LOOP for example).

[rsocor01]

Dave,

The first error states "c:\pbp2-60\16f1939.inc 18 : Unknown processor (16F1939)", so I checked in the PBP directory. I wasn't aware that there was another 16f1939.inc file in the MPASM Suite directory.

Goto - program files - microchip - MPASAM suite- and look for P16F1939.inc

I checked in the computer with MPASM v8.15 and the file was not there. However, the file exist in the computer that has MPASM v8.60. Do you think it would work if I transfer that file over to my other computer?

But again I have not had a problem with old code moving forward with the exception of having a label named something that is now a reserved word (LOOP for example).

So, you are saying that the code with a 18F4550 and a USB interface that I wrote in PBP 2.50 and MPASM v8.15 should work in PBP 2.60? I thought that the whole USB handling changed with PBP 2.60.

Robert

[mackrackit]

So, you are saying that the code with a 18F4550 and a USB interface that I wrote in PBP 2.50 and MPASM v8.15 should work in PBP 2.60? I thought that the whole USB handling changed with PBP 2.60.

I am pretty sure even the USB is backwards compatible, but I would ask Darrel to be sure. I do not have a way to test my old USB code, my old files and hardware are at a different location. I do not remember a problem during the last upgrade, but anything I had in progress I changed to the new way because the new way works better and takes less code space.