Truncated match.
PICList
Thread
'AN589 Programmer'
1997\08\15@041412
by
Jacques Vrey
|
Hi to all out there
I'm a newbie to PIC's and would appreciate some assistance.
I built a programmer in accordance with Microchip's AN589 spec's -
with a few extra's (essentially a power supply and LED's to monitor
output etc. i.e. Prototyping board)
I need programming software that works on an AN589 programmer and
uses *.HEX files generated by MPASM/MPASMWIN.
Alternatively, if someone can give me an example(s) of how to write
source for assembly into *.OBJ files for Andy Errington's
Programming software (preferred option) I would appreciate it. I've
never coded assembler for PIC's before so please bear with me.
I have source for a program "WALK" I don't recall who wrote it but it
"WALKS" LED's on PORTB, If someone could make the necessary changes
to it for assembly into a *.OBJ file, that would be great (SEE
ATTACHMENT)
Thanks
Jacques Vrey
Iscor Profile Products Newcastle
Tel:27-(0)3431-48759
spam_OUTjvreyTakeThisOuT
it.new.iscorltd.co.za
1997\08\15@041418
by
Jacques Vrey
* This message contains the file 'walk.asm', which has been
* uuencoded. If you are using Pegasus Mail, then you can use
* the browser's eXtract function to lift the original contents
* out to a file, otherwise you will have to extract the message
* and uudecode it manually.
Attachment converted: wonderland:walk.asm (????/----) (00004335)
1997\08\15@180929
by
Don McKenzie
|
Jacques Vrey wrote:
> I'm a newbie to PIC's and would appreciate some assistance.
snip-----
> I have source for a program "WALK" I don't recall who wrote it but it
> "WALKS" LED's on PORTB, If someone could make the necessary changes
> to it for assembly into a *.OBJ file, that would be great (SEE
> ATTACHMENT)
It's not a direct equivalent Jacques, but you will find a port b walking
led program
(source and HEX file) at:
http://dontronics.com/84.html
And
Send a blank message to .....basicsKILLspam
@spam@dontronics.com for general info
about the basics of getting involved in PIC's. Also covers the "Basic"
language from both a compiler and Interpreter point of view.
Have a look at:
http://dontronics.com/picnpoke.html
This has a Multimedia 16C84 Simulator, Assembler and Binary Tutorial for
the beginner that may also be of interest to you.
Don McKenzie don
KILLspamdontronics.com http://www.dontronics.com
SimmStick(tm) Atmel & PIC proto PCB's. 30 pin Simm Module Format.
SLI, the serial LCD that auto detects baud rates from 100 to 125K bps.
Send a blank message to .....infoKILLspam
.....dontronics.com for more details.
1997\08\17@023347
by
Mal Goris
Jacques Vrey writes:
> Hi to all out there
>
> I need programming software that works on an AN589 programmer and
> uses *.HEX files generated by MPASM/MPASMWIN.
> Thanks
>
> Jacques Vrey
I modified David Tait's programmer to work with the AN589 hardware. I
will mail it to you on Monday.
Mal Goris
--
http://www.nfra.nl/~mgoris/
'AN589 Programmer'
1998\06\10@135144
by
Andrius Tamulis
|
I am a PIC neophyte, trying to put together the AN589 programmer Microchip
tells you about. And it seems to not be working. Specifically, transistor
Q3, the one that is supposed to pull \bar {MCLR} down, keeps burning out.
Specifically, it's OK while D4/pin 6 is low; \bar {MCLR} is at
programming voltage. Then I pull D4 high, which is supposed to pull \bar
MCLR low, but \bar MCLR goes to about 11 volts, and transistor Q3 starts
to overheat and occasionally smokes. (Well, each _individual_ transistor
smokes only once, then I replace it, and its replacement smokes too).
I see two possibilities:
1) It's my as-of-yet unregulated power supply. It's at 15 volts, and can
go up to an amp (according to specs), so is that burning the transistor? I
was going to take care of this before plugging in a PIC, but will that
solve this problem too? And is the solution in the form of an LM317
regulator?
2) possibility 2; there's a bug in AN589 that no one has told me about.
Anyone else had this problem?
Andrius Tamulis
1998\06\11@025446
by
Mal Goris
|
Andrius Tamulis writes:
> I am a PIC neophyte, trying to put together the AN589 programmer Microchip
> tells you about. And it seems to not be working. Specifically, transistor
> Q3, the one that is supposed to pull \bar {MCLR} down, keeps burning out.
> Specifically, it's OK while D4/pin 6 is low; \bar {MCLR} is at
> programming voltage. Then I pull D4 high, which is supposed to pull \bar
> MCLR low, but \bar MCLR goes to about 11 volts, and transistor Q3 starts
> to overheat and occasionally smokes. (Well, each _individual_ transistor
> smokes only once, then I replace it, and its replacement smokes too).
You probably have a short somewhere, or one of the resistors that ties
the transistors together is wrongly connected. In the three states of
MCLR you should find that the voltages go to V1, V2 and GND to within
hundredths of a volt.
> I see two possibilities:
>
> 1) It's my as-of-yet unregulated power supply. It's at 15 volts, and can
> go up to an amp (according to specs), so is that burning the transistor? I
> was going to take care of this before plugging in a PIC, but will that
> solve this problem too? And is the solution in the form of an LM317
> regulator?
Adding the regulator at this point won't fix your problem. However,
you do need the regulator. An LM317 is fine. I used an 78L12 with two
series signal diodes between its COMMON and GND and a resistor between
Vout and COMMON.
> 2) possibility 2; there's a bug in AN589 that no one has told me about.
> Anyone else had this problem?
It works.
Mal
--
http://www.nfra.nl/~mgoris/
1998\06\11@073200
by
Caisson
|
> Van: Andrius Tamulis <EraseMEatamulisspam_OUT
TakeThisOuTINDIANA.EDU>
> Aan: PICLIST
spam_OUTMITVMA.MIT.EDU
> Onderwerp: AN589 Programmer
> Datum: woensdag 10 juni 1998 18:25
>
> I am a PIC neophyte, trying to put together the AN589 programmer
Microchip
{Quote hidden}> tells you about. And it seems to not be working. Specifically, transistor
> Q3, the one that is supposed to pull \bar {MCLR} down, keeps burning out.
> Specifically, it's OK while D4/pin 6 is low; \bar {MCLR} is at
> programming voltage. Then I pull D4 high, which is supposed to pull \bar
> MCLR low, but \bar MCLR goes to about 11 volts, and transistor Q3 starts
> to overheat and occasionally smokes. (Well, each _individual_ transistor
> smokes only once, then I replace it, and its replacement smokes too).
>
> I see two possibilities:
>
> 1) It's my as-of-yet unregulated power supply. It's at 15 volts, and can
> go up to an amp (according to specs), so is that burning the transistor?
I
> was going to take care of this before plugging in a PIC, but will that
> solve this problem too? And is the solution in the form of an LM317
> regulator?
>
> 2) possibility 2; there's a bug in AN589 that no one has told me about.
> Anyone else had this problem?
>
> Andrius Tamulis
There is a third possibility though : Line D4 that pulls Q3 low is not
'hard' enough and is pulled up by way of Q1, Q2 and R2. If that's what
happens both Q3 and Q1 are opened thus creating a path from VCC to GND.
That should create enough current to either blow Q1 or Q3.
By the way : You can throw away Q1, Q2, R1 and R2 because you only need to
have the MCLR pin at Zero and +12.5 volts. +5 Volts is only required when
_running_. And you don't want that to happen when programming, do you ?
Pull CLKIN (pin 16) to either GND or VCC. This way the PIC can't generate
clock-pulses, even when the MCLR pin changes too slow.
Greetz,
Rudy Wieser
1998\06\14@215637
by
Andrius Tamulis
Rudy Wieser wrote:
> By the way : You can throw away Q1, Q2, R1 and R2 because you only need
to
> have the MCLR pin at Zero and +12.5 volts. +5 Volts is only required
when
> _running_. And you don't want that to happen when programming, do you ?
I thought that the AN589 had a bit of the "in circuit programming"
philosophy behind it - which is why you can turn off all three transistors
and let /bar MCLR just be pulled to +5V along with the power pin.
Thanks for the replies; I'll get to testing those possibilities soon.
Andrius
1998\06\15@064629
by
Caisson
|
> Van: Andrius Tamulis <@spam@atamulisKILLspam
INDIANA.EDU>
> Aan: KILLspamPICLISTKILLspam
MITVMA.MIT.EDU
> Onderwerp: Re: AN589 Programmer
> Datum: vrijdag 12 juni 1998 18:12
>
> Rudy Wieser wrote:
>
> > By the way : You can throw away Q1, Q2, R1 and R2 because you only
> > need to have the MCLR pin at Zero and +12.5 volts. +5 Volts is only
> > required when _running_. And you don't want that to happen when
> > programming, do you ?
>
> I thought that the AN589 had a bit of the "in circuit programming"
> philosophy behind it - which is why you can turn off all three
transistors
> and let /bar MCLR just be pulled to +5V along with the power pin.
>
> Thanks for the replies; I'll get to testing those possibilities soon.
>
> Andrius
I didn't think of that :-(
But if that's what you want to do, please buffer your ACK (data to PC) line
also.
Better be safe than sorry (and you've got 2 ports left).
Another thing to think of : pull pin 16 of the PIC (OSC1) to GND (only when
using a crystal or RC) so that you won't generate clocks when your reset is
slow ...
Greetz,
Rudy Wieser
1998\06\16@143515
by
Andrius Tamulis
In case anyone was on the edge of their seats wondering what was wrong
with my AN589, it was transistor Q1: it had Vpp on the emmitter, base
_and_ collector, even when D3 was low (an internal short?). Anyway,
that replaced, and (that part of) the programmer now works.
Rudy, thanks for the hints, I'll implement them soon.
Andrius
Rudy Wieser wrote:
> Van: Andrius Tamulis <RemoveMEatamulisTakeThisOuT
INDIANA.EDU>
> Aan: spamBeGonePICLISTspamBeGone
MITVMA.MIT.EDU
> Onderwerp: Re: AN589 Programmer
> Datum: vrijdag 12 juni 1998 18:12
>
>
But if that's what you want to do, please buffer your ACK (data to PC) line
also.
Better be safe than sorry (and you've got 2 ports left).
Another thing to think of : pull pin 16 of the PIC (OSC1) to GND (only when
using a crystal or RC) so that you won't generate clocks when your reset is
slow ...
Greetz,
Rudy Wieser
More... (looser matching)
- Last day of these posts
- In 1998
, 1999 only
- Today
- New search...