View Full Version : Unchanged progam does not compile today??
Gerald
- 28th March 2023, 07:46
I have been working with program for a number of days and suddenly this morning I get this compile error. I had also saved another version of that program earlier this morning, and that also fails now. It turns out any version that I save today has the problem. Does the Experimenter version have a cutoff date?
9343
richard
- 28th March 2023, 09:03
i hope you don't expect much help posting pictures of code.
there is every chance in that blurry pic that the config word is not correct for the chosen chip
Gerald
- 28th March 2023, 09:23
I have not changed anything in that part of the program for the last 50 revisions over a few days. If I take that line out, it objects to the next line, etc.
richard
- 28th March 2023, 09:52
you need to supply more information
pbp version ?
chip ?
actual code not a blurry picture
would a good start
Gerald
- 28th March 2023, 09:56
Uninstalled the compiler, downloaded a fresh Student edition and the problem is solved. Thanks for considering it anyway. (I can't help that this forum makes a blurry pic - https://www.picbasic.co.uk/forum/attachment.php?attachmentid=9343&d=1679985701 )
Ioannis
- 28th March 2023, 10:58
Are you sure you had the correct chip selected? I see a 16F1937 selected but that chip does not have ANSEL register.
It has ANSELA, ANSELB and ANSELE.
So the error message was correct!
Ioannis
Gerald
- 28th March 2023, 16:43
Are you sure you had the correct chip selected? I see a 16F1937 selected but that chip does not have ANSEL register.
It has ANSELA, ANSELB and ANSELE.
So the error message was correct!
Ioannis
Indeed! I must have changed the chip type by mistake with all the visits to the Compile button right next to it (The 16F1937 is the next one on the list)
See, my Australian friend, posting the pic in this case was far more enlightening than posting the code :)
Ioannis
- 28th March 2023, 18:29
Many times the chip type on MCS does change on its own! Be careful on that.
Ioannis
CuriousOne
- 29th March 2023, 05:11
Say you have your code window opened, ant it is set for 18F45K80 chip.
You click on "new" code window, it opens, and by default it is set to 16F628.
Now if you just switch to your code for 18F chip, MCU type for it will also change to 16F628, causing compile errors.
Powered by vBulletin® Version 4.1.7 Copyright © 2025 vBulletin Solutions, Inc. All rights reserved.