Latest version of MPASMwin

CharlieM · Post by **CharlieM** » Thu Jan 06, 2011 10:37 am

Hello All,

Just updated to the latest version of MPLAB. So I figured I would update the MPASMWIN in the SF/Bin folder. Well I di that and now programs that did compile ... don't. So I reverted back to the previous version and now my programs compile. Anyone else seeing this?

Jerry Messina · Post by **Jerry Messina** » Thu Jan 06, 2011 2:08 pm

Did you see my post just below this one?

http://www.sfcompiler.co.uk/forum/viewtopic.php?t=1385

Senacharim · Post by **Senacharim** » Thu Jan 06, 2011 2:38 pm

Haven't updated mine yet--not broke, no need to fix it.

Plus, I'm in the midst of a fairly hefty project and the last thing I need is something inexplicably effing up due to an update.

I plan to later though, thanks for the 'heads up.'

CharlieM · Post by **CharlieM** » Thu Jan 06, 2011 10:24 pm

Hi Jerry,

Thanks. I will give it a shot.

be80be · Post by **be80be** » Sat Jan 15, 2011 5:09 am

Will this let you use it with 18f14k50
It give error with 18f452

I guess it works LOl you have to fix all the error in the include file there is no
25 in this it's 20 BORV(BORV) = [45, 42, 27, 20],

be80be · Post by **be80be** » Sat Jan 15, 2011 6:28 am

Maybe it will not be to bad 4 out 5 complied ok

Maybe I try the 18f14k50 and changing the inc files I sure hope that works I got swordfish just to use them and usb

Jerry Messina · Post by **Jerry Messina** » Sat Jan 15, 2011 9:31 am

You might want to look at updating the device INC and BAS files using the SystemConvert utility.

The new mpasm has a number of corrections.

be80be · Post by **be80be** » Sat Jan 15, 2011 7:26 pm

I remade all of them last night using System Convert so it would be safe to save old ones and replace them with the new ones.?

Jerry Messina · Post by **Jerry Messina** » Sat Jan 15, 2011 7:36 pm

Probably, but you might want to keep a copy of the old ones somewhere. That way you have something to compare the new ones to.

Even though the conversions are automatic, once in a while some of the values are hand-tweaked as I understand it.

You could always just replace the one or two that you're having problems with. That might be the safest way to go.

Rickado · Post by **Rickado** » Tue Jan 18, 2011 7:28 am

Beware when converting pic18f46k22.

In 18F46K22.bas file
#variable _maxram = $0F60 // 3936 bytes of user RAM

will have to be changed to
#variable _maxram = $0F38 // 3896 bytes of user RAM from DataSheet

Rickado · Post by **Rickado** » Tue Jan 18, 2011 9:39 pm

Looks like the pic18f26k22 has an incorrect
#variable _maxram

also or is there something I'm missing

Senacharim · Post by **Senacharim** » Tue Jan 18, 2011 9:48 pm

Rickado wrote:Looks like the pic18f26k22 has an incorrect
#variable _maxram

also or is there something I'm missing

I've been using the 26K22 for a few weeks now, and not had any oddities with the RAM.

(In mine it's #variable _maxram = $0F00 // 3840 bytes of user RAM)

Rickado · Post by **Rickado** » Tue Jan 18, 2011 10:18 pm

It should work fine, it just means you wont be able to use the full amount of ram $0F38. SF will think $0F00 is the max amount of ram

breakthrough · Post by **breakthrough** » Sat Feb 26, 2011 10:02 pm

Hmm- I've had the same problem but still don't know how to resolve it. I upgraded MPASMWin to the recent version and read the thread about this at

http://www.sfcompiler.co.uk/forum/viewtopic.php?t=1385

And followed all the instructions. PIC18F452 chips won't compile. Editing the include file doesn't fix it -- only generates more errors.

Where is a clear solution for this problem?

Jerry Messina · Post by **Jerry Messina** » Mon Feb 28, 2011 1:01 pm

PIC18F452 chips won't compile. Editing the include file doesn't fix it -- only generates more errors.

What error(s) are you getting, and how did you change the include file?