<?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>OSBDM and TBDMLのトピックProblem accessing MKL27Z256M4 using USBDM</title>
    <link>https://community.nxp.com/t5/OSBDM-and-TBDML/Problem-accessing-MKL27Z256M4-using-USBDM/m-p/401749#M3062</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi pgo,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a board populated with either a MKL25Z128M4 or MKL27Z256M4 (they are pin compatible, the later basically with twice the flash and ram memory). I have no problem flashing and debugging the MKL25Z128M4 based board, but when I try to access the MKL27Z256M4, the debugger fails with error that the "Target device does not agree with selected". Using the stand alone ARM programmer, when I press the "Detect Chip" button, it will say it is unidentified, with Chip ID 23161d82. It will allow me to erase the chip, but not program it, reporting the same error about the Chip ID not being correct. According to the Reference Manual of this chip, document KL27P64M48SF6RM, the value 23161d82 for the SIM_SDID is indeed correct (the second 1 is the revision number and may change in the future, but all other fields are correct). It seems as if the software assumes an incorrect Chip ID? Is there a way around that?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Uri&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 16 Oct 2015 01:07:56 GMT</pubDate>
    <dc:creator>uribendelac</dc:creator>
    <dc:date>2015-10-16T01:07:56Z</dc:date>
    <item>
      <title>Problem accessing MKL27Z256M4 using USBDM</title>
      <link>https://community.nxp.com/t5/OSBDM-and-TBDML/Problem-accessing-MKL27Z256M4-using-USBDM/m-p/401749#M3062</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi pgo,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a board populated with either a MKL25Z128M4 or MKL27Z256M4 (they are pin compatible, the later basically with twice the flash and ram memory). I have no problem flashing and debugging the MKL25Z128M4 based board, but when I try to access the MKL27Z256M4, the debugger fails with error that the "Target device does not agree with selected". Using the stand alone ARM programmer, when I press the "Detect Chip" button, it will say it is unidentified, with Chip ID 23161d82. It will allow me to erase the chip, but not program it, reporting the same error about the Chip ID not being correct. According to the Reference Manual of this chip, document KL27P64M48SF6RM, the value 23161d82 for the SIM_SDID is indeed correct (the second 1 is the revision number and may change in the future, but all other fields are correct). It seems as if the software assumes an incorrect Chip ID? Is there a way around that?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Uri&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Oct 2015 01:07:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/OSBDM-and-TBDML/Problem-accessing-MKL27Z256M4-using-USBDM/m-p/401749#M3062</guid>
      <dc:creator>uribendelac</dc:creator>
      <dc:date>2015-10-16T01:07:56Z</dc:date>
    </item>
    <item>
      <title>Re: Problem accessing MKL27Z256M4 using USBDM</title>
      <link>https://community.nxp.com/t5/OSBDM-and-TBDML/Problem-accessing-MKL27Z256M4-using-USBDM/m-p/401750#M3063</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OK, I have found the XML file where those SDID values are defined (arm_devices.xml), and indeed it had an incorrect value: 27160d80, which should be fixed to 23160d80.&lt;/P&gt;&lt;P&gt;I can now use the flash programmer and the debugger normally.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Uri&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Oct 2015 15:52:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/OSBDM-and-TBDML/Problem-accessing-MKL27Z256M4-using-USBDM/m-p/401750#M3063</guid>
      <dc:creator>uribendelac</dc:creator>
      <dc:date>2015-10-16T15:52:28Z</dc:date>
    </item>
    <item>
      <title>Re: Problem accessing MKL27Z256M4 using USBDM</title>
      <link>https://community.nxp.com/t5/OSBDM-and-TBDML/Problem-accessing-MKL27Z256M4-using-USBDM/m-p/401751#M3064</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Uri,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will correct this in the next version.&lt;/P&gt;&lt;P&gt;It would appear that the KL27 in that size is actually a KL23 family?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;bye&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 17 Oct 2015 07:36:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/OSBDM-and-TBDML/Problem-accessing-MKL27Z256M4-using-USBDM/m-p/401751#M3064</guid>
      <dc:creator>pgo</dc:creator>
      <dc:date>2015-10-17T07:36:27Z</dc:date>
    </item>
    <item>
      <title>Re: Problem accessing MKL27Z256M4 using USBDM</title>
      <link>https://community.nxp.com/t5/OSBDM-and-TBDML/Problem-accessing-MKL27Z256M4-using-USBDM/m-p/401752#M3065</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi pgo,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe the MKL27Z128 and MKL27Z256 are identical to the corresponding MKL43Z components, except their LCD related functionality has been disabled. I also seem to recall reading somewhere that the MKL27Z64 and MKL27Z32 are a slightly different core, which would explain why they have a separate Reference Manual.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Uri&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 17 Oct 2015 11:24:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/OSBDM-and-TBDML/Problem-accessing-MKL27Z256M4-using-USBDM/m-p/401752#M3065</guid>
      <dc:creator>uribendelac</dc:creator>
      <dc:date>2015-10-17T11:24:17Z</dc:date>
    </item>
  </channel>
</rss>

