Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
01/27/01 18:11
Read: times


 
#8691 - RE: shift reg glitch revisited :)
I'd take a look and the assembly listings machine code and confirm that the equates for the port.bit is correct.

The assembly listings reveal all. You may find that a STRING you are using for the port.bit is actually used as a register name.

It should be something obvious but overlooked like that since you've confirmed the pin input with the oscilloscope. When reality appears violated, it almost always means one of your assumptions is wrong. Challenge your assumptions; make sure the code is inputing the pin you expect and that it is initializing the input pin high. Check the machine code in the assembly listing and look it up to make sure.

Post some code.

If you have a spare I/O pin you can use as an input, wirewrap to that pin (don't cut the trace). If it works there, you'll at least confirm a peice of reality. :)

aka j

List of 13 messages in thread
TopicAuthorDate
shift reg glitch revisited :)            01/01/70 00:00      
RE: shift reg glitch revisited :)            01/01/70 00:00      
RE: shift reg glitch revisited :)            01/01/70 00:00      
RE: shift reg glitch revisited :)            01/01/70 00:00      
RE: shift reg glitch revisited :)            01/01/70 00:00      
RE: shift reg glitch revisited :)            01/01/70 00:00      
RE: shift reg glitch revisited :)            01/01/70 00:00      
RE: shift reg glitch revisited :)            01/01/70 00:00      
RE: shift reg glitch revisited :)            01/01/70 00:00      
RE: shift reg glitch revisited :)            01/01/70 00:00      
RE: shift reg glitch revisited :)            01/01/70 00:00      
to C or not            01/01/70 00:00      
RE: shift reg glitch revisited :)            01/01/70 00:00      

Back to Subject List