To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.handyboardOpen lugnet.robotics.handyboard in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / Handy Board / 6966
6965  |  6967
Subject: 
Re: fried memory
Newsgroups: 
lugnet.robotics.handyboard
Date: 
Tue, 26 Oct 1999 12:08:50 GMT
Viewed: 
993 times
  
it might not be permanently dead, but if it's not, it's not working.

one (or more) of the outputs of these two chips is probably shorted to
ground or shorted to +5v.  the chips get hot when they try to drive
this output to a state other than the one it is shorted to.

with power off, get out your voltmeter and measure continuity from
each of the hc132 and ram pins to +5v and gnd.  find the pin(s) that
stuck in one of these states and shouldn't be.

fred

In your message you said:
I suspect that I fried my memory chip.  The handyboard downloads
Pcode perfectly, but when it tries to synchronize with interactive C,
I get an error.  While the board is off the 62256-12LP and the 74HC132
chips stay hot. is there a good diagnostic that I can perform to see
whether or not the chip is actually dead?

thanks
-Kevin Peterson




Message is in Reply To:
  fried memory
 
I suspect that I fried my memory chip. The handyboard downloads Pcode perfectly, but when it tries to synchronize with interactive C, I get an error. While the board is off the 62256-12LP and the 74HC132 chips stay hot. is there a good diagnostic (...) (25 years ago, 26-Oct-99, to lugnet.robotics.handyboard)

2 Messages in This Thread:

Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR