PIC16f877A first 8 bytes destroyed after closing PicKit2 programmer app....


Closed Thread
Results 1 to 10 of 10

Hybrid View

  1. #1
    Join Date
    Aug 2006
    Location
    Look, behind you.
    Posts
    2,818


    Did you find this post helpful? Yes | No

    Default

    Hmm, I just put a chip on the breadboard, hooked up an LED, a resonator and the appropriate wires to the PICKIT2 and programmed it in place with the code posted, and it works. I actually used an 16F876A, so you MAY have more to do for a 877A.
    The PICKIT2 (at least mine ) can be a little temperamental sometimes, and tries to code protect the chip, a trick I found is to select another chip, then select the correct chip, then without loading a file, click the write button, then program in the file.
    Last edited by Archangel; - 9th February 2010 at 06:48.
    If you do not believe in MAGIC, Consider how currency has value simply by printing it, and is then traded for real assets.
    .
    Gold is the money of kings, silver is the money of gentlemen, barter is the money of peasants - but debt is the money of slaves
    .
    There simply is no "Happy Spam" If you do it you will disappear from this forum.

  2. #2
    Join Date
    Feb 2010
    Posts
    30


    Did you find this post helpful? Yes | No

    Default

    i re-edit the message some minutes ago , so you may not see it.

    At this time seems that PIC programmed ok
    , but leaving it in socket while opening the app destroys the 8 bytes.

    I dont have 876A

    going to work now to test another pickit2 programmer....
    Have a nice day!

  3. #3
    Join Date
    Feb 2010
    Posts
    30


    Did you find this post helpful? Yes | No

    Default

    Now at work ,
    another pc , another pickit2 (hardware) programmer same symptom !
    (pickit app same version , 2.61 , and OS 2.32.00)

  4. #4
    Join Date
    Feb 2010
    Posts
    30


    Did you find this post helpful? Yes | No

    Default

    Finally is pickit's app bug.

    Just installed pickit 2.01 with the according firmware and all ok!!

    (next up is to see in which version introduced this bug , i will post as soon as i have results...

    result: PICKIT 2.40 is the latest working ok.
    Last edited by LakisFM1; - 9th February 2010 at 08:49.

  5. #5
    Join Date
    Nov 2003
    Location
    Wellton, U.S.A.
    Posts
    5,924


    Did you find this post helpful? Yes | No

    Default

    Quote Originally Posted by LakisFM1 View Post
    Finally is pickit's app bug.
    I doubt that...
    ps....
    Found a strange solution...I program the PIC , i remove PIC from the socket , Close App , then Re-open App , Insert PIC in socket , Read PIC and data is now OK.
    Seems that something destroys the 8 bytes while closing or opening the PICKIT2 programer software..
    The PICkit2 does not have a socket. How do you have it connected?
    Dave
    Always wear safety glasses while programming.

  6. #6
    Join Date
    Feb 2010
    Posts
    30


    Did you find this post helpful? Yes | No

    Default

    with a small 40pin ICsocket > 6pin breadboard...

    I retried second time to use 2.55 still not working, so back to 2.40 for sure.

    I suspect is a bug of the Firmware 2.32.00 used both in 2.61 and 2.55.

  7. #7


    Did you find this post helpful? Yes | No

    Default

    I had the similar problem with PICkit 2 and 16F88. When PICkit 2's software was re-opened, a READ operation would erase some or all of the programming. The problem went away when I used chose Manual Device Select instead of automatic select. SW v2.61.

Similar Threads

  1. Help MCS with PICKIT2 programmer question
    By luminas in forum mel PIC BASIC Pro
    Replies: 9
    Last Post: - 1st February 2008, 17:57

Members who have read this thread : 0

You do not have permission to view the list of names.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts