Difference between revisions of "RS-485"
From ArmadeusWiki
(New page: = RS485 = Informations and mini HOWTOs for the APF28/iMX28 mxs-auart and busybox stty patches. Author: JanosA == Linux stty == * Setup APF28 serial port for RS485 communication: <pre cl...) |
(Add supported platforms) |
||
Line 1: | Line 1: | ||
− | + | Informations and HOWTOs for ArmadeuS RS-485 support. | |
− | Informations and | + | |
Author: JanosA | Author: JanosA | ||
+ | |||
+ | |||
+ | == Supported Board and Software versions == | ||
+ | * Currently only the APF28 (iMX28) board with Linux kernel v2.6.35.3 supported. (mxs-auart patch) | ||
+ | * Linux stty patch included only in busybox v1.19.4 (Patch already submitted to the busybox mailing list) | ||
+ | |||
== Linux stty == | == Linux stty == | ||
− | * Setup APF28 serial port for | + | * Setup APF28 serial port for RS-485 communication: |
<pre class=apf> | <pre class=apf> | ||
# stty -F /dev/ttySP0 raw | # stty -F /dev/ttySP0 raw | ||
Line 12: | Line 17: | ||
</pre> | </pre> | ||
− | * Set extra delays for TXEN/RTS signaling before and after the transmitted packet (in microseconds): | + | * Set extra delays (if needed) for TXEN/RTS signaling before and after the transmitted packet (in microseconds): |
<pre class=apf> | <pre class=apf> | ||
# stty -F /dev/ttySP0 rs485delaybefore 100 | # stty -F /dev/ttySP0 rs485delaybefore 100 | ||
Line 18: | Line 23: | ||
</pre> | </pre> | ||
− | * To get current | + | * To get current RS-485 parameters. (If the port device supports the RS-485 options you will see the last two lines) |
<pre class=apf> | <pre class=apf> | ||
# stty -F /dev/ttySP0 | # stty -F /dev/ttySP0 | ||
Line 35: | Line 40: | ||
* The "rs485delaylastchartx" parameter is not used in DMA mode. | * The "rs485delaylastchartx" parameter is not used in DMA mode. | ||
* The parameters: "rs485rtsonsend" "rs485rtsaftersend" "rs485rxduringtx" are not used. (Only used by atmel_serial.c and crisv10.c drivers) | * The parameters: "rs485rtsonsend" "rs485rtsaftersend" "rs485rxduringtx" are not used. (Only used by atmel_serial.c and crisv10.c drivers) | ||
− | * If the | + | * If the RS-485 mode is turned on, it will override (turn off) the RTS/CTS hardware flow settings of the uart, don't care what is configured. |
== C code == | == C code == | ||
− | * The | + | * The RS-485 mode can be turned on with ioctl calls from C code, here is the example: |
<source lang="C"> | <source lang="C"> | ||
#include <stdio.h> | #include <stdio.h> | ||
Line 56: | Line 61: | ||
− | /* Don't forget to read first the current state of the | + | /* Don't forget to read first the current state of the RS-485 options with ioctl. |
If You don't do this, You will destroy the rs485conf.delay_rts_last_char_tx | If You don't do this, You will destroy the rs485conf.delay_rts_last_char_tx | ||
parameter which is automatically calculated by the driver when You opens the | parameter which is automatically calculated by the driver when You opens the | ||
Line 64: | Line 69: | ||
} | } | ||
− | /* Enable | + | /* Enable RS-485 mode: */ |
rs485conf.flags |= SER_RS485_ENABLED; | rs485conf.flags |= SER_RS485_ENABLED; | ||
Line 91: | Line 96: | ||
== Hardware Notes == | == Hardware Notes == | ||
− | * The | + | * The RS-485 Transmit Enable (TXEN) output will be the RTS pin of the uart. |
− | * The TXEN/RTS output is _active low_, it must be inverted to use it with the popular | + | * The TXEN/RTS output is _active low_, it must be inverted to use it with the popular RS-485 transceiver ICs. |
− | * When the u-boot runs and the board start to boot, the RTS pin works as input, please add a pullup resistor to this pin before the inverter, to prevent | + | * When the u-boot runs and the board start to boot, the RTS pin works as input, please add a pullup resistor to this pin before the inverter, to prevent RS-485 bus lockups. |
Revision as of 20:07, 15 May 2013
Informations and HOWTOs for ArmadeuS RS-485 support.
Author: JanosA
Supported Board and Software versions
- Currently only the APF28 (iMX28) board with Linux kernel v2.6.35.3 supported. (mxs-auart patch)
- Linux stty patch included only in busybox v1.19.4 (Patch already submitted to the busybox mailing list)
Linux stty
- Setup APF28 serial port for RS-485 communication:
# stty -F /dev/ttySP0 raw # stty -F /dev/ttySP0 -echo -echoe -echok # stty -F /dev/ttySP0 rs485
- Set extra delays (if needed) for TXEN/RTS signaling before and after the transmitted packet (in microseconds):
# stty -F /dev/ttySP0 rs485delaybefore 100 # stty -F /dev/ttySP0 rs485delayafter 100
- To get current RS-485 parameters. (If the port device supports the RS-485 options you will see the last two lines)
# stty -F /dev/ttySP0 speed 9600 baud; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0; -brkint -imaxbel rs485 -rs485rtsonsend -rs485rtsaftersend -rs485rxduringtx rs485delaybefore = 100; rs485delayafter = 100; rs485delaylastchartx = 1250;
Please note:
- You can't set the "rs485delaylastchartx" parameter, it's calculated automatically from the baudrate.
Special notes for the APF28/iMX28 mxs-auart driver:
- All delays are in microseconds.
- The "rs485delaylastchartx" parameter is not used in DMA mode.
- The parameters: "rs485rtsonsend" "rs485rtsaftersend" "rs485rxduringtx" are not used. (Only used by atmel_serial.c and crisv10.c drivers)
- If the RS-485 mode is turned on, it will override (turn off) the RTS/CTS hardware flow settings of the uart, don't care what is configured.
C code
- The RS-485 mode can be turned on with ioctl calls from C code, here is the example:
#include <stdio.h>
#include <fcntl.h>
#include <linux/ioctl.h>
#include <linux/serial.h>
#include <asm-generic/ioctls.h> /* TIOCGRS485 + TIOCSRS485 ioctl definitions */
int main(void) {
struct serial_rs485 rs485conf;
int fd = open ("/dev/ttySP0", O_RDWR);
if (fd < 0) {
printf("Error: Can't open: /dev/ttySP0\n");
}
/* Don't forget to read first the current state of the RS-485 options with ioctl.
If You don't do this, You will destroy the rs485conf.delay_rts_last_char_tx
parameter which is automatically calculated by the driver when You opens the
port device. */
if (ioctl (fd, TIOCGRS485, &rs485conf) < 0) {
printf("Error: TIOCGRS485 ioctl not supported.\n");
}
/* Enable RS-485 mode: */
rs485conf.flags |= SER_RS485_ENABLED;
/* Set rts/txen delay before send, if needed: (in microseconds) */
rs485conf.delay_rts_before_send = 0;
/* Set rts/txen delay after send, if needed: (in microseconds) */
rs485conf.delay_rts_after_send = 0;
if (ioctl (fd, TIOCSRS485, &rs485conf) < 0) {
printf("Error: TIOCSRS485 ioctl not supported.\n");
}
fcntl(fd, F_SETFL, 0);
int n = write(fd, "ABC\r\n", 5);
if (n < 0) {
/* Error handling */
}
if (close (fd) < 0) {
printf("Error: Can't close: /dev/ttySP0\n");
}
}
Hardware Notes
- The RS-485 Transmit Enable (TXEN) output will be the RTS pin of the uart.
- The TXEN/RTS output is _active low_, it must be inverted to use it with the popular RS-485 transceiver ICs.
- When the u-boot runs and the board start to boot, the RTS pin works as input, please add a pullup resistor to this pin before the inverter, to prevent RS-485 bus lockups.