Searching \ for 'Programming problems..' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/devprogs.htm?key=programming
Search entire site for: 'Programming problems..'.

Truncated match.
PICList Thread
'Programming problems..'
1995\08\01@110355 by Stammnes V.G.S

flavicon
face
I am trying to program a PIC16c84 chip with serial mode. I have tried three
different programmers (all based on David Taits programmer). However, I have
not succedid to get any of them to work. The hardware is mega simple, and I
have checked the hardware many times, but cant find any errors.

Have anybody any clue what might be wrong. I get a verify error when I try
to program a PIC.

(Is David Taits programmer supposed to work ??)

I am using a TIKI 486 DX 33 PC.

tobias

1995\08\01@121821 by David Tait

flavicon
face
Stammnes V.G.S. wrote:

> (Is David Taits programmer supposed to work ??)

I'm sorry to hear you have had a problem, but it's probably better to
e-mail me directly than trouble the list.  Anyway, the short answer to
the question above is: Yes! :-).  Just in case anybody else is stuck,
it's probably worth repeating that there is a FAQ on the programmer
available as:

ftp://ftp.luth.se/pub/misc/microchip/third-party/others/pic84faq.zip
ftp://ftp.ee.ualberta.ca/pub/cookbook/comp/ibm/pic84faq.zip

Please grab this file and see if the information it contains helps
you.  (You'll find some PCB artwork - pic84art.zip - in the same
places and you might consider using that).

If you are convinced the hardware is OK you could have more luck by
using the more advanced software from Silicon Studio.  Have a look
around their FTP/WWW site:

ftp://rasi.lr.ttu.ee/pub/sis/
http://rasi.lr.ttu.ee/~sis/

Good luck,

David
--
spam_OUTdavid.taitTakeThisOuTspamman.ac.uk

1995\08\01@133444 by Rolan

flavicon
face
On Tue, 1 Aug 1995, Stammnes V.G.S wrote:

> I am trying to program a PIC16c84 chip with serial mode. I have tried three
> different programmers (all based on David Taits programmer). However, I have
> not succedid to get any of them to work. The hardware is mega simple, and I
> have checked the hardware many times, but cant find any errors.
>
> Have anybody any clue what might be wrong. I get a verify error when I try
> to program a PIC.
>
> (Is David Taits programmer supposed to work ??)

I built a programmer which REALLY oddly enough, would simply not work
on my computer. I switched and tried 3 different parallel ports, booting
off a disk, and many other things. It just didn't like my CPU or something.
It works on every other computer though. I did notice that my parallel port
was putting out 3.5 V instead of the usualy 5V on other people's parallel
ports. I probably blew something up with my other projects.

-()---()---()---()---()---()---()---()---()---()---()---()---()---()---()-
Rolan Yang            http://hertz.njit.edu/~rxy5310   Electrical Engineer
.....rxy5310KILLspamspam@spam@hertz.njit.edu                             kyuriusspamKILLspamtsb.weschke.com
VR,ROBOTICS,FENCING,HACKING,INDUSTRIAL MUSIC,ART,EXPLOSIVES,INLINE SKATING
                   THESE ARE A FEW OF MY FAVORITE THINGS.
-()---()---()---()---()---()-----()-()---()---()---()---()---()---()---()-
4 out of 10 people are annoyed by ^ this.

1995\08\10@012335 by Antti Lukats

flavicon
face
Hi Tobias,

D. Taits soft usually works. However you are not the first one saying
he cant get it working. Try to slow down your PC both the CPU clock
and BUS speed, don run D. Tait software in a Windows DOS box!

there are no good ways (yet) to merge the two files together you may
save a dummy file with PICSER, take a text editor copy paste and
fixup up the start addresses. Or you could write the chip once
without CP with taits software and then readback with PICSER,
ok taits software doesnt run on _your_ PC, use the neighbours.

I just uploaded DISASM like stuff to
/pub/sis/prod/microchip/disasm/
nothing very good but something useable amongst.
look yourself, have fun

I have DISASM84 written myself but very early stage.
well works. not uploaded anywhere

antti

----------------------------------------------------------
-- Antti Lukats                          Silicon Studio --
-- .....sisKILLspamspam.....rasi.lr.ttu.ee                    PO Box 3500    --
-- ftp://rasi.lr.ttu.ee/pub/sis          Tallinn EE0001 --
-- http://rasi.lr.ttu.ee/~sis            Estonia        --
----------------------------------------------------------

1995\08\10@061227 by David Tait

flavicon
face
Tobias wrote:
I can not get D. Taits software to work.

and Antti replied:
D. Taits soft usually works. However you are not the first one saying
he cant get it working.

I always find such statements a bit confusing; that is because I
provide software in three different forms: Turbo-C source (PP.C),
QBasic source (PP.BAS) and an executable (PP.EXE).  Which of these
don't work?  All of them?

Tobias:

If the hardware works with PICSER then I expect my QBasic program will
work too.  Did you try that?  If you tried it but it didn't work, fit
a 10k pullup on the ACK pin and have another go.  My PCs don't seem to
need one but apparently some do.  Antti tells me his software makes
special provision for the lack of a pullup.  With PP.BAS working you
can then take Antti's advice to program a PIC using your separate
program and data files and use PICSER to dump a merged file.  After
that you can throw my software in the bin and use PICSER from then on.

I want to point out that there is nothing wrong with PP.C either.  The
same can't be said of PP.EXE though.  In my FAQ I mentioned that I
thought my compiler (Turbo-C V2.0) had a bug in the routine used to
determine the vital programming delay.  I can now confirm that.

I compiled and ran this simple program on several different machines:

#include <stdio.h>
#include <dos.h>

void main()
{
    int i;

    printf("start\n");
    for ( i=0; i<2000; ++i)
       delay(10);
    printf("finish\n");
}

This should print "start" then wait 20 seconds before printing
"finish".  This works as expected on my old 386DX-20.  On a 486DX-33
the waiting period dropped to 9 seconds and on a 486DX4-75 it was only
3 seconds.  Compiling and running the same program using a more recent
version of Turbo-C (actually Turbo-C++ now) gave a uniform 20 seconds
delay on all PCs.

If you don't have access to a C compiler just let me know and I'll
send you a new PP.EXE as uuencoded mail (that also goes for anybody
else bitten by this problem); make sure you tell me whether you are
using inverting (7406) or non-inverting (7407) buffers.  I will
replace the archived copies of PP.EXE in the next few weeks.

David
--
EraseMEdavid.taitspam_OUTspamTakeThisOuTman.ac.uk

More... (looser matching)
- Last day of these posts
- In 1995 , 1996 only
- Today
- New search...