honest.I'm an IT teacher with a soldering iron. I'm a fast learner but with
no real formal electronics training - but I'm very interested and
appreciative none-the-less. We have nothing like the OOPic here in OZ -
which makes it really attractive since I teach the kids VB and OOPic just
looks like a fantastic platform to me to teach them real world hardware
programming (the only other opportunity is LEGO MindStorms - which doesn't
really cut it). The "VB like" IDE really suits me in the classroom because
there is a direct cognitive connection to the hardware and relates directly
to the VB IDE I teach for other outcomes. Please don't take offence but the
really hi-tech advice is wasted on me right now and not really worth your
time. But thanks for your good info all the same. I'll archive it for future
reference. What do you think about my idea of just buying another new OOPic
and starting afresh?
Mike M.
_____
From: oopic@yahoogroups.com [mailto:oopic@yahoogroups.com] On Behalf Of
rtstofer
Sent: Friday, 11 April 2008 12:05 AM
To: oopic@yahoogroups.com
Subject: [oopic] Re: Dead OOPic?
--- In oopic@yahoogroups. <mailto:oopic%40yahoogroups.com> com, "Mike
Martin" <xaviour2me@...> wrote:
>
> Hi All
> You might recall my laptop parallel port had a problem communicaing
> with the OOPic. I got all the parts and built the active cable from
the
> files section that Dennis suggested (thanks Dennis) and I can now
> detect it. So I tried a very simple flashing led project.
Everything
> looks like it's working and the IDE says it downloads - the
progress
> bar shows it downloading - etc but the project didn't work. When I
read
> the data back up from the eeprom there's nothing there. I know
there's
> power on the board because I can ground an led in the prototyping
area
> and it lights up. I'm going to just buy another OOPic I think but
does
> anyone have any advice before I do? Also I'd like to get Dennis'
book
> but here in Australia it's out of print and the only ones I can see
at
> Amazon don't deliver here for some reason. Any clues?
>
There's one other 'gotcha' to parallel programming: you MAY have to
remove the programming cable to get the program to run. If you want
to do debugging, you need to plug the cable in to the other I2C
connector.
But that doesn't explain why you can't read the EEPROM. The problem
is that it is almost impossible to troubleshoot I2C without a logic
analyzer. You can certainly see part of the operation with an
oscilloscope but to really capture the traffic requires a logic
analyzer.
Sometimes it is possible to get an clue about the signals with a
logic probe like http://www.pololu.
<http://www.pololu.com/catalog/product/314> com/catalog/product/314 At least
you can see/hear if the signals are toggling. There are a number of
logic probes on eBay.
At idle, both the clock and data lines should be high, A transfer
starts when the data line goes low while the clock line is still high.
Richard
[Non-text portions of this message have been removed]
------------------------------------
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