No it's running at 31.25kHz (default if I recall, I'll have to read the datasheet OSCCON)
You have to set OSCCON to 0x72 (8MHz)
Since you're using the 16F88 download the Firefly assembly instructions. It uses the 16F88 and has some tips in the manual. My favorite is the color instruction set.
Last edited by blueroomelectronics; 9th June 2008 at 03:25 AM.
I could easily be wrong, but I don't think File | Export gives you anything useful unless you have already asembled your source (that is by Project | Make, Project | Build All or Project | Quickbuild).Originally Posted by Hank Fletcher
Once you have assembled the source, you'll have a .hex file in the directory, and File | Export isn't needed in normal circumstances.
Yes, I don't know how everyone missed this? Your assembly source is a series of human readable mnemonics which the *** assembler translates to machine instructions *** - binary. We find it much easier to read hex, than binary, but the data is the same. It is the way the data is presented which makes it binary or hex. Understanding this will help you understand the micro.
You can take a look at an assembled hex file in an editor, in concert with the Instruction Set - PICmicro Mid-Range MCU Family, found here:
Reference Manuals
and understand how the assembler works. There is a pdf, floating around the net, which explains the intel hex file, which mpasm spits out. If you want this, I'll find it for you.
Most compilers or assemblers interpret angle brackets to mean 'search the default path,' and quotation marks mean 'search project directory.'
By now, I think you have figured out that your include file wasn't found, as the path was not correct.
do you guys have psudocodes for electronic pin code lock door with LCd display and interface to computer database via VB. net
Reply With Quote
