> Ooops Exactly my words > Ooops The second time I was a bit more colourfull > Have you tried another chip ? A reasonable investigative step Unfortunately I don't have them floating around spare, this is my first PIC project, next time I will pad my order with some other parts for this reason... > At first glance it looks OK and seems to compile alright. Assuming > no other electrical horrors have been or are currently inflicted on the > poor thing it should work It might be the batteries in my programmer, I am having all sorts of problems getting it programmed. > There are a few things you could do to make the code a little more > readable and quicker/easier to type Usually I am better with my code, but this was a throw it together, see it work thing. > XORLW 0XFF ;or b'11111111' I keep forgetting the side effect of the XOR operator, I rarely use it at all. In this case I will just do the literals, all I want is to see that square wave. > eg #DEFINE testpoint1 PORTA,0 I am unfortunately one of those that believes that some macros are good, but not the more macros are better. > CLRF instead of MOVLW 0X00, MOVWF Yes, my PIC asm is showing :) > RETFIE instead of GOTO END_INT (saves reader looking for END_INT) Now my C experience is showing, there should be at most 2 returns in a function (once the parameter checking is done), it's easier to keep all the allocations straight. > BANKSEL TRISA to go to Bank1 > BANKSEL PORTA to go to Bank0 I wish these would turn off the Register in operand not in bank 0 message, I like warnings to warn, but if I get it right they shouldn't be there. Thanks! -- Anthony Toft -- http://www.piclist.com hint: To leave the PICList mailto:piclist-unsubscribe-request@mitvma.mit.edu