PIC12F508 -- trivial program fails to compile to hex

A forums to allow bugs and problems with Flowcode v6 to be reported and resolved.

Moderator: Benj

Post Reply
gtc
Posts: 69
Joined: Mon Mar 23, 2015 5:34 am
Has thanked: 30 times
Been thanked: 15 times
Contact:

PIC12F508 -- trivial program fails to compile to hex

Post by gtc »

Similar problem to the one I reported here:

http://www.matrixtsl.com/mmforums/viewt ... 59&t=16833

Don't know what you guys did to fix the 12F609 chip config file, but it seems the same needs to be done for the 12F508 and maybe also for its cousins 12F509 and 16F505.

User avatar
Benj
Matrix Staff
Posts: 15312
Joined: Mon Oct 16, 2006 10:48 am
Location: Matrix TS Ltd
Has thanked: 4803 times
Been thanked: 4314 times
Contact:

Re: PIC12F508 -- trivial program fails to compile to hex

Post by Benj »

Hello,

The BoostC compiler we are using does not currently support the 12F5xx and 16F5xx devices which is why your getting compilation errors.

For Flowcode v4 we allowed these devices to be used by allowing Flowcode to work with the HiTech compiler which did support everything.

Since then the HiTech compiler has been bought by Microchip and is no longer available, however we left the devices in for v5 and v6 just for anyone already using the solution with HiTech installed.

The XC8 compiler is very similar to HiTech but we make no promises that everything or even anything will work as is.

We have a plan in motion to support more of the PIC range of devices and so hopefully we will have a workable solution available to our users again soon.

gtc
Posts: 69
Joined: Mon Mar 23, 2015 5:34 am
Has thanked: 30 times
Been thanked: 15 times
Contact:

Re: PIC12F508 -- trivial program fails to compile to hex

Post by gtc »

Benj wrote:Hello,

The BoostC compiler we are using does not currently support the 12F5xx and 16F5xx devices which is why your getting compilation errors.
Bummer. I'm trying to do a like-for-like on this job.
We have a plan in motion to support more of the PIC range of devices and so hopefully we will have a workable solution available to our users again soon.
Good to know and can't come quickly enough for me. If I never again see the infamous "error code 1" it will be too soon!

Post Reply