<?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>Kinetis MicrocontrollersのトピックUnable to access UART0 for device MKE04Z64VLH4 using Kinetis SDK and KExx_drv_lib v1.3.0</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Unable-to-access-UART0-for-device-MKE04Z64VLH4-using-Kinetis-SDK/m-p/486916#M30002</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am using KDS v3.0.0 and the KExx_DRV_LIB v1.3.0 to develop an application for the MKE04Z64VLH4.&amp;nbsp; I am using a PEMicro USB Multilink Universal debugger. I have successfully added the additional memory-mapped peripherals and ports for this device.&amp;nbsp; Basic port testing works just fine.&amp;nbsp; However, any attempt to access UART0 (even a memory read of the status register) causes an interrupt and essentially halts the program.&amp;nbsp; As far as I can tell, no interrupts have been defined or enabled, all interrupts point to the "Default Handler".&amp;nbsp; Running the same code on a FRDM-KE04 evaluation board works just fine.&amp;nbsp; Also, running the simple "baremetal" example for the FRMD_KE04 that uses UART0 fails in exactly the same way.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any suggestions on what to try next?&amp;nbsp; Why would a memory read of the UART0 memory location trigger an interrupt?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 17 Mar 2016 20:56:48 GMT</pubDate>
    <dc:creator>zg</dc:creator>
    <dc:date>2016-03-17T20:56:48Z</dc:date>
    <item>
      <title>Unable to access UART0 for device MKE04Z64VLH4 using Kinetis SDK and KExx_drv_lib v1.3.0</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Unable-to-access-UART0-for-device-MKE04Z64VLH4-using-Kinetis-SDK/m-p/486916#M30002</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am using KDS v3.0.0 and the KExx_DRV_LIB v1.3.0 to develop an application for the MKE04Z64VLH4.&amp;nbsp; I am using a PEMicro USB Multilink Universal debugger. I have successfully added the additional memory-mapped peripherals and ports for this device.&amp;nbsp; Basic port testing works just fine.&amp;nbsp; However, any attempt to access UART0 (even a memory read of the status register) causes an interrupt and essentially halts the program.&amp;nbsp; As far as I can tell, no interrupts have been defined or enabled, all interrupts point to the "Default Handler".&amp;nbsp; Running the same code on a FRDM-KE04 evaluation board works just fine.&amp;nbsp; Also, running the simple "baremetal" example for the FRMD_KE04 that uses UART0 fails in exactly the same way.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any suggestions on what to try next?&amp;nbsp; Why would a memory read of the UART0 memory location trigger an interrupt?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Mar 2016 20:56:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Unable-to-access-UART0-for-device-MKE04Z64VLH4-using-Kinetis-SDK/m-p/486916#M30002</guid>
      <dc:creator>zg</dc:creator>
      <dc:date>2016-03-17T20:56:48Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to access UART0 for device MKE04Z64VLH4 using Kinetis SDK and KExx_drv_lib v1.3.0</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Unable-to-access-UART0-for-device-MKE04Z64VLH4-using-Kinetis-SDK/m-p/486917#M30003</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Zachary,&lt;/P&gt;&lt;P&gt;About this "running the simple "baremetal" example for the FRMD_KE04 that uses UART0 fails in exactly the same way",&lt;/P&gt;&lt;P&gt;could you please test one under the KSDK1.3 about the UART0.&lt;/P&gt;&lt;P&gt;And also you can send the project on FRDM-KE04 to me , i will check it on my side .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR&lt;/P&gt;&lt;P&gt;Alice&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Mar 2016 01:49:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Unable-to-access-UART0-for-device-MKE04Z64VLH4-using-Kinetis-SDK/m-p/486917#M30003</guid>
      <dc:creator>Alice_Yang</dc:creator>
      <dc:date>2016-03-18T01:49:12Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to access UART0 for device MKE04Z64VLH4 using Kinetis SDK and KExx_drv_lib v1.3.0</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Unable-to-access-UART0-for-device-MKE04Z64VLH4-using-Kinetis-SDK/m-p/486918#M30004</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Alice - thanks for your suggestions.&amp;nbsp; I downloaded and installed the KSDK1.3 and it does not seem to directly support the &lt;SPAN style="color: #51626f; font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif;"&gt;MKE04Z64VLH4 when using the New Project Wizard.&amp;nbsp; As for the FRMD_KE04 board itself, it never exhibits the problem.&amp;nbsp; The problem only occurs on my client's custom board, so I'm not sure you can reproduce the problem.&amp;nbsp; However I will try and send you the project in case you see something wrong.&amp;nbsp; My next step is to create a PE project (which does appear to support the &lt;SPAN style="color: #51626f; font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif;"&gt;MKE04Z64VLH4).&amp;nbsp; I will post an update when I have some more information.&amp;nbsp; Thanks for your help.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif;"&gt;BR&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif;"&gt;Zack&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Mar 2016 02:47:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Unable-to-access-UART0-for-device-MKE04Z64VLH4-using-Kinetis-SDK/m-p/486918#M30004</guid>
      <dc:creator>zg</dc:creator>
      <dc:date>2016-03-22T02:47:45Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to access UART0 for device MKE04Z64VLH4 using Kinetis SDK and KExx_drv_lib v1.3.0</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Unable-to-access-UART0-for-device-MKE04Z64VLH4-using-Kinetis-SDK/m-p/486919#M30005</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have created a small Processor Expert project which exhibits the problem on my client's board.&amp;nbsp; I have attached a screenshot of the failure.&amp;nbsp; Any suggestions are appreciated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Mar 2016 02:37:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Unable-to-access-UART0-for-device-MKE04Z64VLH4-using-Kinetis-SDK/m-p/486919#M30005</guid>
      <dc:creator>zg</dc:creator>
      <dc:date>2016-03-25T02:37:25Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to access UART0 for device MKE04Z64VLH4 using Kinetis SDK and KExx_drv_lib v1.3.0</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Unable-to-access-UART0-for-device-MKE04Z64VLH4-using-Kinetis-SDK/m-p/486920#M30006</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Zachary,&lt;/P&gt;&lt;P&gt;Does your chip is &lt;SPAN style="color: #51626f; font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif;"&gt;MKE04Z64VLH4 ? If yes , please change the "CPU type":&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_0.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/26104i2534D98F684CD5DB/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_0.png" alt="pastedImage_0.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;then have a try , recommend you first send one char to the terminal , if still can not work,&lt;/P&gt;&lt;P&gt;please use the oscilloscope to check the TX pin whether have signal .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps&lt;/P&gt;&lt;P&gt;Alice&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Mar 2016 03:48:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Unable-to-access-UART0-for-device-MKE04Z64VLH4-using-Kinetis-SDK/m-p/486920#M30006</guid>
      <dc:creator>Alice_Yang</dc:creator>
      <dc:date>2016-03-25T03:48:59Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to access UART0 for device MKE04Z64VLH4 using Kinetis SDK and KExx_drv_lib v1.3.0</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/Unable-to-access-UART0-for-device-MKE04Z64VLH4-using-Kinetis-SDK/m-p/486921#M30007</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The root cause of this problem was found to be in the ConsoleIO component.&amp;nbsp; Changing to the AsynchroSerial component worked fine and has resolved the issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Apr 2016 01:25:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/Unable-to-access-UART0-for-device-MKE04Z64VLH4-using-Kinetis-SDK/m-p/486921#M30007</guid>
      <dc:creator>zg</dc:creator>
      <dc:date>2016-04-06T01:25:23Z</dc:date>
    </item>
  </channel>
</rss>

