View previous topic :: View next topic |
Author |
Message |
dmccric
Joined: 07 Dec 2009 Posts: 7 Location: Bradford, West Yorkshire
|
Compiler Issues with fuses on 18F4431 |
Posted: Thu Jun 17, 2010 3:57 am |
|
|
I have been invoking the ccs compiler from the MPLAB IDE on my current project and have run into some compiler issues, I have set my fuses to what I want but the compiler will not use them and puts in its own in, when I do this on another computer it works ok.
I have all the latest versions of the compiler & MPLAB plug-ins but I cant seem to find the cause of this, I cant use the '#rom' directive to change the fuses directly but this is not good. |
|
![](templates/subSilver/images/spacer.gif) |
PCM programmer
Joined: 06 Sep 2003 Posts: 21708
|
|
![](templates/subSilver/images/spacer.gif) |
ckielstra
Joined: 18 Mar 2004 Posts: 3680 Location: The Netherlands
|
|
Posted: Thu Jun 17, 2010 3:07 pm |
|
|
Also check your MPLAB. Maybe you have an option set to ignore or clear the configuration bits.
For example in MPLAB 8.46 with PicKit3: Programmer - Settings - Program Memory |
|
![](templates/subSilver/images/spacer.gif) |
dmccric
Joined: 07 Dec 2009 Posts: 7 Location: Bradford, West Yorkshire
|
|
Posted: Fri Jun 18, 2010 4:46 am |
|
|
This also happens when not in debug mode, the compiler version is 4.108.
I have checked the program settings in MPLAB and the ICD3 is set to automatically set the memory ranges.
When I compile the same code on another machine with the same compiler version and I then import that hex file into MPLAB on my machine and the configuration fuses change to what they should be but if I simply compile it on mine then they are messed up.
If the fuses are not setting correctly it doesn't give me confidence when writing code as I spend more time debugging errors that should not be there. |
|
![](templates/subSilver/images/spacer.gif) |
dmccric
Joined: 07 Dec 2009 Posts: 7 Location: Bradford, West Yorkshire
|
|
Posted: Fri Jun 18, 2010 4:48 am |
|
|
Also I forgot to mention that when I wrote the code it was working in debug mode as normal then simply changed for no reason (they must be a reason), once I write code that works I dont go around changing it later. |
|
![](templates/subSilver/images/spacer.gif) |
Ttelmah
Joined: 11 Mar 2010 Posts: 19360
|
|
Posted: Fri Jun 18, 2010 8:57 am |
|
|
Do a re-install on the problem machine.
A corruption in the device database, can cause silly fuse values.
Best Wishes |
|
![](templates/subSilver/images/spacer.gif) |
|