<?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: MKL02Z32VFK4 PTB2 alternative(2) Rxd in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/MKL02Z32VFK4-PTB2-alternative-2-Rxd/m-p/1846308#M66288</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/124845"&gt;@claeskjellstrom&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Can you give me more information about how you configured the peripheral? for example:&lt;/P&gt;
&lt;P&gt;- 115200 baud rate&lt;/P&gt;
&lt;P&gt;- 8 data bits&lt;/P&gt;
&lt;P&gt;- No parity&lt;/P&gt;
&lt;P&gt;- One stop bit&lt;/P&gt;
&lt;P&gt;- No flow control.&lt;/P&gt;
&lt;P&gt;For the moment, you can check an example of SDK (version 3.2) called "hello World", in this example, they use UART 0 for communicate at terminal.&lt;BR /&gt;BR&lt;BR /&gt;Habib&lt;/P&gt;</description>
    <pubDate>Fri, 12 Apr 2024 18:53:18 GMT</pubDate>
    <dc:creator>Habib_MS</dc:creator>
    <dc:date>2024-04-12T18:53:18Z</dc:date>
    <item>
      <title>MKL02Z32VFK4 PTB2 alternative(2) Rxd</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/MKL02Z32VFK4-PTB2-alternative-2-Rxd/m-p/1844068#M66276</link>
      <description>&lt;P&gt;Hi, just want to know if anyone came across the same problem as I have with Rx pin PTB2.&lt;/P&gt;&lt;P&gt;The thing is that Txd is sending correctly at 115200b(that's verified) but when receiving it it's completely&lt;/P&gt;&lt;P&gt;crap but defined crap(like when the baudrate is extremely wrong). I have also verified this by connecting&lt;/P&gt;&lt;P&gt;a terminal prog(rxd) to listen to the message, and the message is ok at 115200b but UART is messing it up. If I send 'O','K',cr,lf the message in the rx buffer says 202(dec),106(dec),194(dec). The status flag&lt;/P&gt;&lt;P&gt;indicate overrun and frame error all the time. The rx is interrupted, not the tx.&lt;/P&gt;&lt;P&gt;Any ideas ?&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;Claes&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 10 Apr 2024 16:51:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/MKL02Z32VFK4-PTB2-alternative-2-Rxd/m-p/1844068#M66276</guid>
      <dc:creator>claeskjellstrom</dc:creator>
      <dc:date>2024-04-10T16:51:42Z</dc:date>
    </item>
    <item>
      <title>Re: MKL02Z32VFK4 PTB2 alternative(2) Rxd</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/MKL02Z32VFK4-PTB2-alternative-2-Rxd/m-p/1846308#M66288</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/124845"&gt;@claeskjellstrom&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Can you give me more information about how you configured the peripheral? for example:&lt;/P&gt;
&lt;P&gt;- 115200 baud rate&lt;/P&gt;
&lt;P&gt;- 8 data bits&lt;/P&gt;
&lt;P&gt;- No parity&lt;/P&gt;
&lt;P&gt;- One stop bit&lt;/P&gt;
&lt;P&gt;- No flow control.&lt;/P&gt;
&lt;P&gt;For the moment, you can check an example of SDK (version 3.2) called "hello World", in this example, they use UART 0 for communicate at terminal.&lt;BR /&gt;BR&lt;BR /&gt;Habib&lt;/P&gt;</description>
      <pubDate>Fri, 12 Apr 2024 18:53:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/MKL02Z32VFK4-PTB2-alternative-2-Rxd/m-p/1846308#M66288</guid>
      <dc:creator>Habib_MS</dc:creator>
      <dc:date>2024-04-12T18:53:18Z</dc:date>
    </item>
    <item>
      <title>Re: MKL02Z32VFK4 PTB2 alternative(2) Rxd</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/MKL02Z32VFK4-PTB2-alternative-2-Rxd/m-p/1846447#M66289</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;It turns out that FLL clock was out of tune, so funny thing was that Tx was sending correct but Rx&lt;/P&gt;&lt;P&gt;couldn't receive correct, I had to switch clock to MCGIRCLK instead and now it's working. I would like to know if there is any possibility to trim oscillator through Segger J-link.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;/Claes&lt;/P&gt;</description>
      <pubDate>Sat, 13 Apr 2024 07:19:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/MKL02Z32VFK4-PTB2-alternative-2-Rxd/m-p/1846447#M66289</guid>
      <dc:creator>claeskjellstrom</dc:creator>
      <dc:date>2024-04-13T07:19:09Z</dc:date>
    </item>
    <item>
      <title>Re: MKL02Z32VFK4 PTB2 alternative(2) Rxd</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/MKL02Z32VFK4-PTB2-alternative-2-Rxd/m-p/1847499#M66300</link>
      <description>&lt;P&gt;Hello again &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/124845"&gt;@claeskjellstrom&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regarding your question, I understand that you want to modify the trim register that feeds the module, through the Jlink. However, as the following post says, Jlink doesn't support this feature: &lt;A href="https://community.nxp.com/t5/Kinetis-Design-Studio/trimming-internal-oscillator/td-p/383412" target="_blank"&gt;https://community.nxp.com/t5/Kinetis-Design-Studio/trimming-internal-oscillator/td-p/383412&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;If you need more information about the trim register, you can consult the reference manual for the chapter 21 called "Multipurpose Clock Generator (MCG)" in the register "MCG Control 3 Register (MCG_C3)" as well as "MCG Control 4 Register (MCG_C4)".&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR &lt;BR /&gt;Habib&lt;/P&gt;</description>
      <pubDate>Mon, 15 Apr 2024 22:21:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/MKL02Z32VFK4-PTB2-alternative-2-Rxd/m-p/1847499#M66300</guid>
      <dc:creator>Habib_MS</dc:creator>
      <dc:date>2024-04-15T22:21:59Z</dc:date>
    </item>
  </channel>
</rss>

