Searching \ for '[PIC] Solved? (sorta) Pin sharing between clock an' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page:
Search entire site for: 'Solved? (sorta) Pin sharing between clock an'.

Exact match. Not showing close matches.
PICList Thread
'[PIC] Solved? (sorta) Pin sharing between clock an'
2010\02\15@231623 by MCH

I tracked it down to the clock that is the issue, as the I/O works fine
on the shared port/bit (PortD-5). If anything, you would think that's
the one that would have problems being that it's a switching I/O port.

So, that just leaves the clock that works on PortB-0, but not on shared
port D-6.

Well, I tried changing the timing (adding NOPs) before and after reading
the bit, and that made no difference. I am right at the 200 nS minimum
bit available time spec, but that same code worked fine with the
dedicated bit (PortB-0). I also made sure I cleared port D at the
beginning of the clock subroutine just so I start with a known state.

Then, I tried port D-0 (also shared), and it worked! That's odd because
D-0 is also shared with the LCD display data. So, I tried D-5, and that

So, I moved the clock to D-7 and moved the I/O to D-6 since I wanted
them to use consecutive port bits. And that works. FYI, the RST line is
dedicated since it controls when the clock is accepting data input.

So, the question is: Why does the clock signal not work on D-6, but it
works on (seemingly) any other bit on the same port, and why does the
I/O work on D-6?

Yes, I made sure there was nothing other than the LCD and this clock
chip using ports D5, 6, and 7.

While this will work, I would like to understand what was wrong.
Any ideas?

Joe M.

Spehro Pefhany wrote:
{Quote hidden}

2010\02\15@235806 by MCH

I should note that when I say "clock", I'm talking about the CLK signal,
not the clock chip itself.

Joe M.

MCH wrote:
{Quote hidden}

More... (looser matching)
- Last day of these posts
- In 2010 , 2011 only
- Today
- New search...