<?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>i.MX Processorsのトピックimx-uart RX FIFO overrun when not connected</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/imx-uart-RX-FIFO-overrun-when-not-connected/m-p/886654#M134276</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Community,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; We have a custom board based on the sabresd board, with imx6dl processor, using krogoth bsp and kernel 4.1.15&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; I am observing the following strange behaviour:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Sometimes when i boot the board with UART1 disconnected, and after the boot process is complete, i connect the UART to check the logs, i see the following (full log attached):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Feb 5 17:26:21 imx6dl-ctems-alpha kernel: sysrq: SysRq : HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) show-blocked-tasks(w) &lt;BR /&gt;Feb 5 17:26:21 imx6dl-ctems-alpha kernel: imx-uart 2020000.serial: Rx FIFO overrun&lt;BR /&gt;Feb 5 17:26:23 imx6dl-ctems-alpha kernel: sysrq: SysRq : Show Blocked State&lt;BR /&gt;Feb 5 17:26:23 imx6dl-ctems-alpha kernel: task PC stack pid father&lt;BR /&gt;Feb 5 17:26:23 imx6dl-ctems-alpha kernel: sysrq: SysRq : HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) show-blocked-tasks(w) &lt;BR /&gt;Feb 5 17:26:23 imx6dl-ctems-alpha kernel: imx-uart 2020000.serial: Rx FIFO overrun&lt;BR /&gt;Feb 5 17:26:23 imx6dl-ctems-alpha kernel: sysrq: SysRq : HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) show-blocked-tasks(w) &lt;BR /&gt;Feb 5 17:26:23 imx6dl-ctems-alpha kernel: imx-uart 2020000.serial: Rx FIFO overrun&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is some kernel debug stuff i will disable, but i'm not sure if that will help, since this happens intermittently.&lt;/P&gt;&lt;P&gt;The UART configuration is:&lt;/P&gt;&lt;P&gt;115200 8N1, no flow control, connected to imx uart 1. (only TX and RX lines are connected in HW, so HW flow control is not possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Stas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 06 Feb 2019 09:39:55 GMT</pubDate>
    <dc:creator>stasgil</dc:creator>
    <dc:date>2019-02-06T09:39:55Z</dc:date>
    <item>
      <title>imx-uart RX FIFO overrun when not connected</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/imx-uart-RX-FIFO-overrun-when-not-connected/m-p/886654#M134276</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Community,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; We have a custom board based on the sabresd board, with imx6dl processor, using krogoth bsp and kernel 4.1.15&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; I am observing the following strange behaviour:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;Sometimes when i boot the board with UART1 disconnected, and after the boot process is complete, i connect the UART to check the logs, i see the following (full log attached):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Feb 5 17:26:21 imx6dl-ctems-alpha kernel: sysrq: SysRq : HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) show-blocked-tasks(w) &lt;BR /&gt;Feb 5 17:26:21 imx6dl-ctems-alpha kernel: imx-uart 2020000.serial: Rx FIFO overrun&lt;BR /&gt;Feb 5 17:26:23 imx6dl-ctems-alpha kernel: sysrq: SysRq : Show Blocked State&lt;BR /&gt;Feb 5 17:26:23 imx6dl-ctems-alpha kernel: task PC stack pid father&lt;BR /&gt;Feb 5 17:26:23 imx6dl-ctems-alpha kernel: sysrq: SysRq : HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) show-blocked-tasks(w) &lt;BR /&gt;Feb 5 17:26:23 imx6dl-ctems-alpha kernel: imx-uart 2020000.serial: Rx FIFO overrun&lt;BR /&gt;Feb 5 17:26:23 imx6dl-ctems-alpha kernel: sysrq: SysRq : HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) show-blocked-tasks(w) &lt;BR /&gt;Feb 5 17:26:23 imx6dl-ctems-alpha kernel: imx-uart 2020000.serial: Rx FIFO overrun&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is some kernel debug stuff i will disable, but i'm not sure if that will help, since this happens intermittently.&lt;/P&gt;&lt;P&gt;The UART configuration is:&lt;/P&gt;&lt;P&gt;115200 8N1, no flow control, connected to imx uart 1. (only TX and RX lines are connected in HW, so HW flow control is not possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Stas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Feb 2019 09:39:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/imx-uart-RX-FIFO-overrun-when-not-connected/m-p/886654#M134276</guid>
      <dc:creator>stasgil</dc:creator>
      <dc:date>2019-02-06T09:39:55Z</dc:date>
    </item>
    <item>
      <title>Re: imx-uart RX FIFO overrun when not connected</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/imx-uart-RX-FIFO-overrun-when-not-connected/m-p/886655#M134277</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Stas&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;with UART1 disconnected, floating long uart board trace can catch noise and&lt;/P&gt;&lt;P&gt;cause overruns. One can check signal with oscilloscope and set appropriate&lt;/P&gt;&lt;P&gt;pull setting in uart Pad Control Register IOMUXC_SW_PAD_CTL_PAD_x_y register.&lt;/P&gt;&lt;P&gt;Also one can try linux from nxp source.codeaurora.org/external/imx repository&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://source.codeaurora.org/external/imx/linux-imx/tree/?h=imx_4.1.15_1.0.0_ga" title="https://source.codeaurora.org/external/imx/linux-imx/tree/?h=imx_4.1.15_1.0.0_ga"&gt;linux-imx - i.MX Linux kernel&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Feb 2019 11:09:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/imx-uart-RX-FIFO-overrun-when-not-connected/m-p/886655#M134277</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2019-02-06T11:09:32Z</dc:date>
    </item>
  </channel>
</rss>

