AW: [En-Nut-Discussion] RS485 TX/RX control pin

[Damian Slee]

>>Damian: Can you please confirm this?

Sounds correct. 

-----Original Message-----
From: en-nut-discussion-bounces at egnite.de [mailto:en-nut-discussion-bounces at egnite.de] On Behalf Of Oliver Schulz
Sent: Wednesday, May 26, 2004 4:31 PM
To: Ethernut User Chat (English)
Subject: AW: AW: [En-Nut-Discussion] RS485 TX/RX control pin

Hi Przemek,

Yes, your're right. I had the focus of the changed sbi to UART_HDX_TX, but didn't compare the parameters. Sorry.

Obviously it is a mistake to use (UART_RTS_PORT, UART_RTS_BIT) in AvrUsartTxStart. Like you pointed out, it must be (UART_HDX_PORT, UART_HDX_BIT) to work correctly.

Damian: Can you please confirm this?

Meanwhile I will change the files in CVS.

Regards,
Oliver.

> -----Ursprüngliche Nachricht-----
> Von: en-nut-discussion-bounces at egnite.de
> [mailto:en-nut-discussion-bounces at egnite.de]Im Auftrag von Przemyslaw 
> Rudy
> Gesendet: Mittwoch, 26. Mai 2004 10:09
> An: Ethernut User Chat (English)
> Betreff: Re: AW: [En-Nut-Discussion] RS485 TX/RX control pin
> 
> 
> Sorry, it's still there :)
> Versions 1.1.4.2 and 1.3 of the usartavr.c CVS.
> Maybe I'm wrong but it looks like switching the mode to transmit 
> operates on the RTS pin instead of HDX pin.
> It's easy to detect that as if you undefine the usage of RTS in 
> module.h you won't be able to compile.
> 
> Regards,
> Przemek
> 
> Oliver Schulz wrote:
> > ...
> > If you finally have version 1.1.4.2, you will see, that
> this bug is fixed in
> > line 1117.
> > ...
> 
> _______________________________________________
> En-Nut-Discussion mailing list
> En-Nut-Discussion at egnite.de
> http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion
> 
_______________________________________________
En-Nut-Discussion mailing list
En-Nut-Discussion at egnite.de
http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion