Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1553516
| From | Fabio Estevam <festevam@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: imx: RS-485 problems during TX, maybe DMA related |
| Date | 2017-01-07 01:40 +0100 |
| Message-ID | <sWNd7-1fD-1@gated-at.bofh.it> (permalink) |
| References | <sVWsa-72d-37@gated-at.bofh.it> <sWKff-7Ju-3@gated-at.bofh.it> <sWLEm-9g-35@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi Clemens,
On Fri, Jan 6, 2017 at 8:50 PM, Clemens Gruber
<clemens.gruber@pqgruber.com> wrote:
> But according to the i.MX Pins tool, they can be muxed vice-versa too.
> So if you connected the transceiver-enable to ball L4 (CSI0_DAT16), you
> could mux MX6QDL_PAD_CSI0_DAT16__UART4_CTS_B and
> MX6QDL_PAD_CSI0_DAT17__UART4_RTS_B instead?
Yes, I have tried like this:
&uart4 {
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_uart4>;
uart-has-rtscts;
status = "okay";
};
pinctrl_uart4: uart4grp {
fsl,pins = <
MX6QDL_PAD_CSI0_DAT12__UART4_TX_DATA 0x1b0b1
MX6QDL_PAD_KEY_ROW0__UART4_RX_DATA 0x1b0b1
MX6QDL_PAD_CSI0_DAT16__UART4_CTS_B 0x1b0b1
>;
};
In this case the DE pin of the rs485 transceiver is always at 0 then
RX works and TX does not.
Then I tried to use a gpio for controling the rts line:
&uart4 {
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_uart4>;
rts-gpios = <&gpio6 2 GPIO_ACTIVE_HIGH>;
status = "okay";
};
pinctrl_uart4: uart4grp {
fsl,pins = <
MX6QDL_PAD_CSI0_DAT12__UART4_TX_DATA 0x1b0b1
MX6QDL_PAD_KEY_ROW0__UART4_RX_DATA 0x1b0b1
MX6QDL_PAD_CSI0_DAT16__GPIO6_IO02 0x1b0b1
>;
}
In this case the DE pin of the rs485 transceiver is always at 1, then
TX works and RX does not.
So I was never able to observe the DE pin toggling correctly.
Maybe you could share your userspace application with me offline?
Thanks
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
imx: RS-485 problems during TX, maybe DMA related Clemens Gruber <clemens.gruber@pqgruber.com> - 2017-01-04 17:20 +0100
Re: imx: RS-485 problems during TX, maybe DMA related Fabio Estevam <festevam@gmail.com> - 2017-01-06 22:30 +0100
Re: imx: RS-485 problems during TX, maybe DMA related Clemens Gruber <clemens.gruber@pqgruber.com> - 2017-01-07 00:00 +0100
Re: imx: RS-485 problems during TX, maybe DMA related Fabio Estevam <festevam@gmail.com> - 2017-01-07 01:40 +0100
Re: imx: RS-485 problems during TX, maybe DMA related Clemens Gruber <clemens.gruber@pqgruber.com> - 2017-01-07 14:50 +0100
Re: imx: RS-485 problems during TX, maybe DMA related Fabio Estevam <festevam@gmail.com> - 2017-01-07 16:00 +0100
Re: imx: RS-485 problems during TX, maybe DMA related Clemens Gruber <clemens.gruber@pqgruber.com> - 2017-01-07 16:40 +0100
Re: imx: RS-485 problems during TX, maybe DMA related Fabio Estevam <festevam@gmail.com> - 2017-01-07 17:50 +0100
Re: imx: RS-485 problems during TX, maybe DMA related Clemens Gruber <clemens.gruber@pqgruber.com> - 2017-01-07 22:00 +0100
Re: imx: RS-485 problems during TX, maybe DMA related Fabio Estevam <festevam@gmail.com> - 2017-01-07 22:50 +0100
Re: imx: RS-485 problems during TX, maybe DMA related Clemens Gruber <clemens.gruber@pqgruber.com> - 2017-01-08 00:10 +0100
Re: imx: RS-485 problems during TX, maybe DMA related Fabio Estevam <festevam@gmail.com> - 2017-01-08 03:40 +0100
Re: imx: RS-485 problems during TX, maybe DMA related Clemens Gruber <clemens.gruber@pqgruber.com> - 2017-01-08 19:10 +0100
Re: imx: RS-485 problems during TX, maybe DMA related Fabio Estevam <festevam@gmail.com> - 2017-01-08 22:50 +0100
Re: imx: RS-485 problems during TX, maybe DMA related Clemens Gruber <clemens.gruber@pqgruber.com> - 2017-01-11 01:40 +0100
Re: imx: RS-485 problems during TX, maybe DMA related Fabio Estevam <festevam@gmail.com> - 2017-01-11 13:00 +0100
Re: imx: RS-485 problems during TX, maybe DMA related Fabio Estevam <festevam@gmail.com> - 2017-01-08 16:20 +0100
csiph-web