Russ,
Take it to the step where you actually program the chip, press "view" and open the "configuration" window, and post what the settings are, here, would you? I'm interested in what it's telling you.....
By default, they should match -exactly- the listing in the 12f675.inc file in c:\pbp (or wherever it lives)
If you've changed them in the config window and saved it, then the saved values will be the default.
By way of example, you should have an option for setting the osc. The default may be XT, but you can change it to INTOSC and save the settings. Quite handy (I can see Dave cringing right now - sorry) handy if you never plan to use any other compiler...... not so handy if the code needs to be portable.
I am having quite a time with some code that makes Thomas the Tank Engine look complex. Oddly enough it's a 12f675. AND, the routines are simple and have been used a few times, not precisely the same, but the methodology. Now it won't run. I loaded a working file into the same chip on the same development board and it won't run either. The working file was built last week, and the MeProg software upgraded shortly thereafter.
Gary
Any time I try to program a 12F675, the default configuration is LP osc and code protected.
If I change the configuration to EXTOSC and NOT PROTECTED and try to program, I get a configuration error.
Now, when I read the part, the configuration changes to LP osc and code protected.
I am using the Melabs programmer. I can make a jpg image of the configuration window but don't know how to post it.
Below the message box when you reply there is a "manage attachment" button.
Dave
Always wear safety glasses while programming.
Sounds like a programming cable problem.
If you have nothing connected to the programmer, and try to read back a 12F675, it'll show these configs.
And it'll show all 0000's in the code window.Code:Oscillator LP Watchdog timer Disabled Powerup timer Enabled MCLR Pin Input Pin Brown out Disabled Code protect Protected Data EEPROM Protected
Check the connections again, especially at the 10-pin connector on the programmer.
Make sure the connector is alligned correctly.
<br>
DT
Thanks, Darryl but the connector has not been messed with and it worked OK before. The read does read the hex file that was loaded.
OK, if it reads the memory then it wasn't the cable.
You might try the latest version of meProg which is up to version 4.31 now.I am using melabs programmer version 4.01 ...
The beta can be downloaded here ...
http://www.melabs.com/support/progsoft.htm
hth,
DT
Bookmarks