Searching \ for '[PIC:] YAP-II devel board + windows interface--' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/devices.htm?key=pic
Search entire site for: 'YAP-II devel board + windows interface--'.

Exact match. Not showing close matches.
PICList Thread
'[PIC:] YAP-II devel board + windows interface-- '
2000\07\13@111958 by Stephen B Webb

flavicon
face
I am messing around with a simple program that is supposed to simply echo
characters received on the serial line.  When I run the program (in the
YAP-II devel. board) and start hitting keys, I am not able to successfully
receive a character from the PC.  From my testing so far, it appears that
the program fails to receive a full start bit on the input line.  When I
send ascii char 0, (i.e. binary 00000000) the interrupt routine isn't
invoked at all.  It seeems like the start bit should trigger the interrupt
routine -- so it seems like I'm not getting a start bit.  Hmm.

I'm not really too sure what happens to the signal between the PC and the
pic. Does anyone have any ideas about what could be going on?

-Steve

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]: PIC only [EE]: engineering [OT]: off topic [AD]: advertisements

2000\07\13@214812 by Myke Predko

flavicon
face
Hi Steve,

Could you send me a copy of your interrupt handling routine and how you are
wiring the PICmicro to the "SerOut" Pin (this is the data coming from the
PC).

myke

{Original Message removed}

2000\07\14@133955 by rleggitt

picon face
> I am messing around with a simple program that is supposed to simply echo
> characters received on the serial line.  When I run the program (in the
> YAP-II devel. board) and start hitting keys, I am not able to successfully
> receive a character from the PC.  From my testing so far, it appears that
> the program fails to receive a full start bit on the input line.  When I
> send ascii char 0, (i.e. binary 00000000) the interrupt routine isn't
> invoked at all.  It seeems like the start bit should trigger the interrupt
> routine -- so it seems like I'm not getting a start bit.  Hmm.

Hi, the start bit simply triggers the uart to shift in X bits (whatever
the wordlength is). Upon receipt of bit X+1 (stop bit) the shift register
is moved into the receive buffer, and RXD is set. Since RXD is NOR'd onto
the /INT output (I *think* it's a negated /INT), then THIS is when a
receive interrupt occurs. RXD is cleared when you read the receive buffer.

Note on the PC architecture, the uart's OUT2 output gates the interrupt
output with an (IIRC) NOR gate. So you need to set up the interrupt
controller for IRQ 3/4, set up the IER for RX interrupt, AND set the OUT2
bit.

But first you should hack the uart directly with debug to see if it's
actually receiving (i.e. RXD gets set and the receive buffer contains the
character transmitted). Once that's working, then figure out the
interrupts.

HTH / Rich

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics

2000\07\14@192027 by Stephen B Webb

flavicon
face
>
> Hi, the start bit simply triggers the uart to shift in X bits (whatever
> the wordlength is). Upon receipt of bit X+1 (stop bit) the shift register

Maybe I should have been more clear.  The program I have is written for
the 16F84 which does not have a UART.  The interrupt I was talking about
was the one in the code on the PIC which is supposed to handle the serial
I/O stuff.

-Steve

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics

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