gnupic: more on first picprog attempt
Subject:
more on first picprog attempt
From:
"Maxim Wexler" ####@####.####
Date:
18 Jun 2006 01:56:36 +0100
Message-Id: <a0811460606171754m3336657cp8b5dd25be964b477@mail.gmail.com>
Hi, Somebody said to use sudo w/ picprog. So I did. This time it spit out a
bit more info:
booyah@ubuntu:~/docs/pic/toggle$ sudo picprog --burn --erase --input
Toggle.hex -p /dev/ttyS0 -d pic16f874
Picprog version 1.8.1, Copyright (c) 2006 Jaakko Hyvätti <
####@####.####
Picprog comes with ABSOLUTELY NO WARRANTY; for details
type `picprog --warranty'. This is free software,
and you are welcome to redistribute it under certain conditions;
type `picprog --copying' for details.
Device pic16f874, program memory: 4096, data memory: 128.
CPU clock speed: 930 MHz
Erased and removed code protection.
Burning program memory,/dev/ttyS0:0000: programmed=018a, read=3fff:unable to
verify pic while programming.
Is code protection enabled, or does the chip need to be
erased completely before programming?
Use --erase option to disable code protection.
So why didn't erase option work after saying that it did? Is this a problem
with the PG2 programmer? The port? I tried the code with _CONFIG LVP_OFF
(above) and ON(below):
booyah@ubuntu:~/docs/pic/toggle$ sudo picprog --burn --erase --input
Toggle.hex -p /dev/ttyS0 -d pic16f874
Picprog version 1.8.1, Copyright (c) 2006 Jaakko Hyvätti <
####@####.####
Picprog comes with ABSOLUTELY NO WARRANTY; for details
type `picprog --warranty'. This is free software,
and you are welcome to redistribute it under certain conditions;
type `picprog --copying' for details.
Device pic16f874, program memory: 4096, data memory: 128.
CPU clock speed: 930 MHz
Erased and removed code protection.
Burning program memory,/dev/ttyS0:PIC programmer missing or chip fault
/dev/ttyS0:0000:unable to read pic while programming
This time it doesn't contradict itself vis-a-vis code protection...but it
still don't work:(.
I just checked the pins on the chip in the programmer in the static state,
ie, while not in use but connected to COM1. MCLRnot, RB3, VSS have -5.6V on
them, for example. VDD is at gnd potential. Is this correct?
-Maxim
