best regards
cihan
--- In oopic@yahoogroups.com, ooPIC Tech Support <dennis.clark@...> wrote:
>
> Remove the Big chip (ooPIC) from the board and try to download. If
that
> works then the CPU is accessing the EEPROM when the computer is trying
> to program it. This can be because the reset line is not pulling low,
> which means that your connection to the computer is bad, the CPU is
> damaged or the cable is bad. If it still doesn't work with the CPU
> pulled out then either the EEPROM is damaged or has a bent pin or
again,
> the cable is bad. Check to see if the /reset line pulls low, to do
this
> you'll need a DVM and to use the troubleshooting screen (the one
used to
> choose a cable) to set various lines to see if they go low/high. If
all
> the pins toggle as they should and the programmer works when the big
> chip is removed then the CPU is bad. If all of the lines toggle and
the
> EEPROM DOES program when the big chip is removed then the EEPROM is
> either bad or has a bent pin.
>
> DLC
>
> chngedik wrote:
> > no, it was giving around 8~9 volts
> > it was nothing about connections.
> > --- In oopic@yahoogroups.com, <dennis.clark@> wrote:
> >
> >> Battery? An oft overlooked culprit.
> >>
> >> DLC
> >>
> >> ooPIC Tech Support
> >>
> >> -----Original Message-----
> >>
> >> From: "chngedik" <mcgedik@>
> >> Subj: [oopic] need technical support, anyone can help?
> >> Date: Fri Jan 4, 2008 1:57 pm
> >> Size: 1K
> >> To: oopic@yahoogroups.com
> >>
> >> hi guys, ladies;
> >>
> >> i have been working on a graduating project and i decided to use
> >> oopic. few tries later, there was an error occured;
> >> -------------
> >> the fallowing was detected while establishing I2C communications
> >>
> >> the I2C bus clock status reported a logic state 1, when a logic state
> >> of 0 expected this could be caused any of the fallowing;
> >>
> >> A. the programming port is not configured correctly
> >> B. the programming cable was not attached to the PC (it was)
> >> C. the programming cable's I2C clock line is not properly connected
> >> D. the programming cable's I2C clock status line is not properly
> >>
> > connected
> >
> >> E. the I2C clock line is shorted to +5 volts on the oopic or in the
> >>
> > cable.
> >
> >> F. the I2C clock status line is shorted to +5 volts in the cable.
> >> -------------------
> >>
> >> i tried the cable, it was ok. i controlled it's connections. also
> >> remade a new one still the same error.
> >>
> >> i tried the troubleshooting page on the manuel. the oopic passed all
> >> the tests also.
> >>
> >> i tried the 10k on the resistance near to eeprom for capacitances.
> >>
> >> i don't know what to do next. i need some advices.
> >> thanks for your helps.
> >>
> >> cihan.
> >>
> >>
> >>
> >>
> >>
> >>
> >> Yahoo! Groups Links
> >>
> >>
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>
> --
> ------------------------------------------------------
> Dennis Clark ooPIC Tech Support
> www.oopic.com
> ------------------------------------------------------
>
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/oopic/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/oopic/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:oopic-digest@yahoogroups.com
mailto:oopic-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
oopic-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
No comments:
Post a Comment