It's something stupid - I've written 10's of K's of LOC in 4-bit paged assembly in my life but I'm having a tough time 'letting' PBP in MicroCode Studio do the work for me. After cranking out a bunch of code 'by the book', I've now retreated back to BLINK.BAS. The particulars...
PBP Ver.2.50c, MCS Ver.3.0.0.5, target uC= PIC16F506
I put 'LIST P=16F506' (no, not the single-quotes too) at the top and it bombs out with that as the first syntax error in BLINK.BAS.
Then it moves on to my next line - INCLUDE "P16F506.INC" (or M16F506.INC) - which seems OK 'cause all the errors now are in P16F506.INC.
Starting with the first line, whatever it is, every line is an excuse for it to fail the 'syntax test' - starting with ...
IFNDEF __16F506 on line 37 in P16F506.inc and
the first 'DEFINE... ' in M16F506.INC.
I've turned 'Use MPASM' on and off - no diff.
I'm a tidy sort - I like MY files to be in MY folder - have told MCS what my favorite default folder is - and have put all 'called for' files in there. This wouldn't be one of those 'MCS programmer is a dictator' things, would it?
If one of you fine fellow 'code spewers' could clue me in - or spell out EVERYTHING I need -and where I need it to be - to get BLINK.BAS to compile and run on a PIC16F506 , I'll appreciate it and probably not have to bother anyone here again.;-)
PS. While I'm here - I'm using PicStart Plus that's been upgraded with the latest flash firmware/module. Is there some reason why MCS has left it off the drop-down list of 'Available Programmers'?
Bookmarks