<?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>8-bit MicrocontrollersのトピックRe: Modbus RTU communication error</title>
    <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Modbus-RTU-communication-error/m-p/2402129#M24371</link>
    <description>&lt;P&gt;I have changed my implementation to bare metal code still i am receiving only 1 byte.&lt;BR /&gt;Please share any input.&lt;/P&gt;</description>
    <pubDate>Wed, 05 Aug 2026 11:20:33 GMT</pubDate>
    <dc:creator>An95</dc:creator>
    <dc:date>2026-08-05T11:20:33Z</dc:date>
    <item>
      <title>Modbus RTU communication error</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Modbus-RTU-communication-error/m-p/2400511#M24361</link>
      <description>&lt;P&gt;I am writing code for MC9S08JM60 to read MODBUS RTU holding registers. I am reading 15 holding registers which gives me a 35 byte frame. So i am expected to get 1 interrupt for each byte but i am getting 1 interrupt for the first byte of the frame and next interrupt is for the first byte of the next frame. So I am losing the rest 34 bytes. Please provide any input for this.&lt;BR /&gt;&lt;BR /&gt;I am attaching my code snippets.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jul 2026 10:52:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Modbus-RTU-communication-error/m-p/2400511#M24361</guid>
      <dc:creator>An95</dc:creator>
      <dc:date>2026-07-30T10:52:13Z</dc:date>
    </item>
    <item>
      <title>Re: Modbus RTU communication error</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Modbus-RTU-communication-error/m-p/2400630#M24362</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/209102"&gt;@An95&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you for your post!&lt;BR /&gt;&lt;BR /&gt;There is any documentation of Modbus RTU with the S08.&lt;BR /&gt;&lt;BR /&gt;But the issue you are facing could be related to not clear the RDRF.&lt;/P&gt;
&lt;P&gt;The RDRF (Receive Data Register Full) flag is cleared only by reading SCI1D after reading SCI1S1. If SCI1D is not read in the ISR, the interrupt fires once and then the receiver stalls.&lt;/P&gt;
&lt;P&gt;Refer to&amp;nbsp;14.2.4 SCI Status Register 1 (SCIxS1) of the&amp;nbsp;MC9S08JM60 Series Data Sheet.&lt;/P&gt;
&lt;P&gt;Make sure your code is clearing the flag correctly.&lt;BR /&gt;&lt;BR /&gt;BR&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jul 2026 19:33:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Modbus-RTU-communication-error/m-p/2400630#M24362</guid>
      <dc:creator>carlos_o</dc:creator>
      <dc:date>2026-07-30T19:33:57Z</dc:date>
    </item>
    <item>
      <title>Re: Modbus RTU communication error</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Modbus-RTU-communication-error/m-p/2401158#M24364</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/241501"&gt;@carlos_o&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;&lt;BR /&gt;Thank you for your response.&lt;BR /&gt;The RDRF flag is cleared when it enters the callback function of the interrupt service routine. The 35 byte frame is coming in a single interrupt. If I take a buffer of 35 bytes even then i am not able to read the whole frame.&lt;BR /&gt;Please share your input regarding this.&lt;BR /&gt;BR&lt;/P&gt;</description>
      <pubDate>Sat, 01 Aug 2026 12:44:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Modbus-RTU-communication-error/m-p/2401158#M24364</guid>
      <dc:creator>An95</dc:creator>
      <dc:date>2026-08-01T12:44:47Z</dc:date>
    </item>
    <item>
      <title>Re: Modbus RTU communication error</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Modbus-RTU-communication-error/m-p/2402129#M24371</link>
      <description>&lt;P&gt;I have changed my implementation to bare metal code still i am receiving only 1 byte.&lt;BR /&gt;Please share any input.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Aug 2026 11:20:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Modbus-RTU-communication-error/m-p/2402129#M24371</guid>
      <dc:creator>An95</dc:creator>
      <dc:date>2026-08-05T11:20:33Z</dc:date>
    </item>
    <item>
      <title>Re: Modbus RTU communication error</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Modbus-RTU-communication-error/m-p/2402131#M24372</link>
      <description />
      <pubDate>Wed, 05 Aug 2026 11:23:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Modbus-RTU-communication-error/m-p/2402131#M24372</guid>
      <dc:creator>An95</dc:creator>
      <dc:date>2026-08-05T11:23:33Z</dc:date>
    </item>
    <item>
      <title>Re: Modbus RTU communication error</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Modbus-RTU-communication-error/m-p/2402280#M24375</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/209102"&gt;@An95&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The SCI only could receive 1 byte each time&amp;nbsp;RDRF is trigger. So, you will need to trigger 35 interrupts to read the 35 bytes you are sending.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You could refer to the chapter&lt;STRONG&gt; 14.3.3 Receiver Functional Description&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;The SCI module only has one&amp;nbsp;SCI Data Register (SCIxD) that could save 8 bits each time.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Aug 2026 22:42:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Modbus-RTU-communication-error/m-p/2402280#M24375</guid>
      <dc:creator>carlos_o</dc:creator>
      <dc:date>2026-08-05T22:42:33Z</dc:date>
    </item>
  </channel>
</rss>

