>> OK now that you gave an approximate circuit diagram, what code is in the
>> chip? Read it from the chip, and give the resulting .hex file. The one
>> read from the chip, not the one you put into it.
> 
> I see where you're heading with this... Are you suggesting that the
> code got corrupted on its way into the chip?

You have tried to get it work, so I assume that you tried everything 
that was (in your opinion) probable. So the next candidates are the 
things that you deem unprobable.

Reading back the code and posting it here serves checks a lot of things

- did the code really get into that chip (great fun in class: two 
students have their USB cables crossed and are wondering why their 
target boards do not work as expected)

- do you have fuses info (and the correct fuses info) in your chip (when 
there is no fuses info in a .hex file some programmers/pc software will 
not complain, and leave you with a non-configured chip)

- others can load the .hex into a chip to see whether it works

- if your code is simple the .hex can easily be read and interpreted

-- 

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: www.voti.nl/hvu

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist