<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: iMX6 UART RS485 mode? in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/iMX6-UART-RS485-mode/m-p/242534#M20483</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;A customer is in need of the exact same feature, I wonder if someone has an update on this topic?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Bruno&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 26 Aug 2013 14:10:14 GMT</pubDate>
    <dc:creator>bfac</dc:creator>
    <dc:date>2013-08-26T14:10:14Z</dc:date>
    <item>
      <title>iMX6 UART RS485 mode?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6-UART-RS485-mode/m-p/242533#M20482</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Has anyone had any experience using the RS485 capabilities of the iMX6 in Linux?&amp;nbsp; Just had a quick look through the Kernel sources and arrived at drivers/tty/serial/imx.c which seems to be doing the right things with regard to standard 232 and IRDA functionality, but I can't find anywhere the 485 functionality is implemented.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In fact RS485 mode is allegedly enabled by setting the MDEN field of the UARTx_UMCR register to&amp;nbsp; 0x02 but this register definition is suspiciously missing from the defines in imx.c, which I guess means that IRDA compatibility with slow data rate isn't implemented either.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TIA&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Aug 2013 11:59:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6-UART-RS485-mode/m-p/242533#M20482</guid>
      <dc:creator>simondunn</dc:creator>
      <dc:date>2013-08-06T11:59:33Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6 UART RS485 mode?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6-UART-RS485-mode/m-p/242534#M20483</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;A customer is in need of the exact same feature, I wonder if someone has an update on this topic?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Bruno&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Aug 2013 14:10:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6-UART-RS485-mode/m-p/242534#M20483</guid>
      <dc:creator>bfac</dc:creator>
      <dc:date>2013-08-26T14:10:14Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6 UART RS485 mode?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6-UART-RS485-mode/m-p/242535#M20484</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry I should have posted my findings.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyway there is no RS485 driver support in the BSP so the existing serial driver will need to be modified.&amp;nbsp; A 485 transceiver will need to be added to your board and brought out on one of the UARTs.&amp;nbsp; UART5 is brought out to a connector designed for blue tooth (J13) or UART2 is brought out on pads EIM_D27 -&amp;gt; 29 (amongst others) via J508&amp;nbsp; which you might be able to connect to quite easily for development purposes.&amp;nbsp; I can't see that the sabre SD board exposes any other UARTs that might be suitable; uart1 is attached to a usb to serial converter and uart3 to a GPS receiver for example. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Incidentally my initial post included reference to the MDEN field, well ignore that.&amp;nbsp; The MDEN field only enables rs485 9 bit address mode and standard 485 multi drop will work quite happily without this particular feature.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Aug 2013 12:21:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6-UART-RS485-mode/m-p/242535#M20484</guid>
      <dc:creator>simondunn</dc:creator>
      <dc:date>2013-08-27T12:21:56Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6 UART RS485 mode?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6-UART-RS485-mode/m-p/242536#M20485</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you found anything new concerning this topic? Has Freescale weighed in or provided any development assistance?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a custom I.MX6Q board and I am attempting to transfer files using the minicom program. I am getting traffic on the ports but my transmit side gets a 'Retry 0: Timeout on pathname' error message.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Following is my COM port status before and after the file transmission attempt:&lt;/P&gt;&lt;P&gt;&lt;A href="mailto:root@winsys-ubuntu-desktop:/etc/init"&gt;root@winsys-ubuntu-desktop:/etc/init&lt;/A&gt;# cat /proc/tty/driver/IMX-uart&lt;/P&gt;&lt;P&gt;serinfo:1.0 driver revision:&lt;/P&gt;&lt;P&gt;0: uart:IMX mmio:0x02020000 irq:58 tx:10579 rx:260 RTS|CTS|DTR|DSR|CD&lt;/P&gt;&lt;P&gt;1: uart:IMX mmio:0x021E8000 irq:59 tx:0 rx:0 DSR|CD&lt;/P&gt;&lt;P&gt;2: uart:IMX mmio:0x021EC000 irq:60 tx:0 rx:0 DSR|CD&lt;/P&gt;&lt;P&gt;3: uart:IMX mmio:0x021F0000 irq:61 tx:0 rx:0 DSR|CD&lt;/P&gt;&lt;P&gt;4: uart:IMX mmio:0x021F4000 irq:62 tx:0 rx:0 DSR|CD&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="mailto:root@winsys-ubuntu-desktop:/etc/init"&gt;root@winsys-ubuntu-desktop:/etc/init&lt;/A&gt;# cat /proc/tty/driver/IMX-uart&lt;/P&gt;&lt;P&gt;serinfo:1.0 driver revision:&lt;/P&gt;&lt;P&gt;0: uart:IMX mmio:0x02020000 irq:58 tx:10962 rx:264 RTS|CTS|DTR|DSR|CD&lt;/P&gt;&lt;P&gt;1: uart:IMX mmio:0x021E8000 irq:59 tx:0 rx:0 DSR|CD&lt;/P&gt;&lt;P&gt;2: uart:IMX mmio:0x021EC000 irq:60 tx:99 rx:0 RTS|DSR|CD&lt;/P&gt;&lt;P&gt;3: uart:IMX mmio:0x021F0000 irq:61 tx:140 rx:0 DSR|CD&lt;/P&gt;&lt;P&gt;4: uart:IMX mmio:0x021F4000 irq:62 tx:0 rx:0 DSR|CD&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Sep 2013 18:28:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6-UART-RS485-mode/m-p/242536#M20485</guid>
      <dc:creator>PaulDeMetrotion</dc:creator>
      <dc:date>2013-09-16T18:28:52Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6 UART RS485 mode?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6-UART-RS485-mode/m-p/242537#M20486</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;SPAN class="hps"&gt;Can you&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;describe&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;in detail&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;under the&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;485&lt;/SPAN&gt; &lt;SPAN class="hps"&gt;model?&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Sep 2013 04:00:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6-UART-RS485-mode/m-p/242537#M20486</guid>
      <dc:creator>方圆张</dc:creator>
      <dc:date>2013-09-24T04:00:02Z</dc:date>
    </item>
    <item>
      <title>Re: iMX6 UART RS485 mode?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX6-UART-RS485-mode/m-p/242538#M20487</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I modified the imx.c driver and device tree&lt;span class="lia-inline-image-display-wrapper" image-alt="rs485_direction.jpeg.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/46000iB1098A584551D71C/image-size/large?v=v2&amp;amp;px=999" role="button" title="rs485_direction.jpeg.jpg" alt="rs485_direction.jpeg.jpg" /&gt;&lt;/span&gt;, and it look like it working fine. The problem is that I could not use the DTE mode, as this swap the RX/TX and CTS/RTS pin direction, thus I left it in the normal DCE mode, and toggle DTR, as this is now an output!!&amp;nbsp; The reason for this was that I already have a PCB and did not want to do 'cut and past'.&amp;nbsp; I had to change the device tree as follows&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;amp;uart5 {&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; pinctrl-names = "default";&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; pinctrl-0 = &amp;lt;&amp;amp;pinctrl_uart5&amp;gt;;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; fsl,uart-has-rtscts;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; status = "okay";&lt;/P&gt;&lt;P&gt;};&lt;/P&gt;&lt;P&gt;pinctrl_uart5: uart5grp {&lt;/P&gt;&lt;P&gt;&amp;nbsp; fsl,pins = &amp;lt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MX6QDL_PAD_KEY_COL1__UART5_TX_DATA&amp;nbsp;&amp;nbsp;&amp;nbsp; 0x1b0b1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MX6QDL_PAD_KEY_ROW1__UART5_RX_DATA&amp;nbsp;&amp;nbsp;&amp;nbsp; 0x1b0b1&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MX6QDL_PAD_CSI0_DAT18__UART5_RTS_B&amp;nbsp;&amp;nbsp;&amp;nbsp; 0x1b0b1&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MX6QDL_PAD_CSI0_DAT19__UART5_CTS_B&amp;nbsp;&amp;nbsp;&amp;nbsp; 0x1b0b1 &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;gt;;&lt;/P&gt;&lt;P&gt;};&lt;/P&gt;&lt;P&gt;The scope trace show the direction change before the first byte and ends when the last byte is transmitted.&lt;/P&gt;&lt;P&gt;This is most obviously not the perfect solution but it worked for me, please feel free to comment and correct my short comings.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This was tested on a RiOTboard.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Sep 2014 20:28:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX6-UART-RS485-mode/m-p/242538#M20487</guid>
      <dc:creator>creatron</dc:creator>
      <dc:date>2014-09-17T20:28:12Z</dc:date>
    </item>
  </channel>
</rss>

