<?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中的主题 OPENSDA MSD-DEBUG-FRDMK64</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/OPENSDA-MSD-DEBUG-FRDMK64/m-p/321594#M14416</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have tried to install the for the OpenSDA MDS-Debug on the FRDMK64 without success.&amp;nbsp; This SDA file was not in the K64 Quick Start Package, so I downloaded it from the PEMicro.com\opensda website.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, the file is too big to fit on the freedom k64 in bootloader mode.&amp;nbsp; Has anyone else had this issue?&amp;nbsp; It works just fine on the K25.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I am trying to accomplish is run the sensor fusion adapter board on my k64.&amp;nbsp; In order to do this I need to generate a license, which I cannot do until I have the board in MSD mode with a cdc uart.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your assistance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 17 Jul 2014 17:00:10 GMT</pubDate>
    <dc:creator>mlamp</dc:creator>
    <dc:date>2014-07-17T17:00:10Z</dc:date>
    <item>
      <title>OPENSDA MSD-DEBUG-FRDMK64</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/OPENSDA-MSD-DEBUG-FRDMK64/m-p/321594#M14416</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have tried to install the for the OpenSDA MDS-Debug on the FRDMK64 without success.&amp;nbsp; This SDA file was not in the K64 Quick Start Package, so I downloaded it from the PEMicro.com\opensda website.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, the file is too big to fit on the freedom k64 in bootloader mode.&amp;nbsp; Has anyone else had this issue?&amp;nbsp; It works just fine on the K25.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I am trying to accomplish is run the sensor fusion adapter board on my k64.&amp;nbsp; In order to do this I need to generate a license, which I cannot do until I have the board in MSD mode with a cdc uart.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your assistance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jul 2014 17:00:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/OPENSDA-MSD-DEBUG-FRDMK64/m-p/321594#M14416</guid>
      <dc:creator>mlamp</dc:creator>
      <dc:date>2014-07-17T17:00:10Z</dc:date>
    </item>
    <item>
      <title>Re: OPENSDA MSD-DEBUG-FRDMK64</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/OPENSDA-MSD-DEBUG-FRDMK64/m-p/321595#M14417</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Michael,&lt;/P&gt;&lt;P&gt;there was a preproduction board of the FRDM-K64F which used that .SDA files. The production board of the FRDM-K64F have a different OpenSDAv2 bootloader (see &lt;A href="http://mcuoneclipse.com/2014/04/20/using-the-frdm-k64f-with-codewarrior/" title="http://mcuoneclipse.com/2014/04/20/using-the-frdm-k64f-with-codewarrior/"&gt;Using the FRDM-K64F with CodeWarrior | MCU on Eclipse&lt;/A&gt; and more about OpenSDAv2 in &lt;A href="http://mcuoneclipse.com/2014/04/27/segger-j-link-firmware-for-opensdav2/" title="http://mcuoneclipse.com/2014/04/27/segger-j-link-firmware-for-opensdav2/"&gt;Segger J-Link Firmware for OpenSDAv2 | MCU on Eclipse&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;The file you are using is for the OpenSDAv1, not the OpenSDAv1 which uses a different bootloader and application address.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;A matching P&amp;amp;E OpenSDAv2 application can be found in the Kinetis SDK (&lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://www.freescale.com/ksdk):"&gt;http://www.freescale.com/ksdk):&lt;/A&gt;&lt;SPAN&gt; download the beta version of the SDK, and then you fiind the DEBUG_K64F_MBED_PEMICRO_V108.BIN in the root folder of the KDSK_1.0.0-Beta.zip.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Download that .BIN file to the board to have the firmware programmed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jul 2014 17:23:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/OPENSDA-MSD-DEBUG-FRDMK64/m-p/321595#M14417</guid>
      <dc:creator>BlackNight</dc:creator>
      <dc:date>2014-07-17T17:23:47Z</dc:date>
    </item>
    <item>
      <title>Re: OPENSDA MSD-DEBUG-FRDMK64</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/OPENSDA-MSD-DEBUG-FRDMK64/m-p/321596#M14418</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for the quick response.&amp;nbsp; Do you know if there is a MSD-Debug OpenSDA file that will work with the FRDM K64?&amp;nbsp; In order to use the xtrinsic 9-axis board I need to generate a license file by dropping a file (Identify_K64F.s19) on the freedom board and then run a FRS tool (ClGenerateNodeLockedLicense.exe) that will probe the freedom board via the usb cdc serial port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This process was outlined in the FTF course (FTF-CON-F0178.pdf) for the KL&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;25Z, but it also claims to work with the K64.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jul 2014 17:55:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/OPENSDA-MSD-DEBUG-FRDMK64/m-p/321596#M14418</guid>
      <dc:creator>mlamp</dc:creator>
      <dc:date>2014-07-17T17:55:30Z</dc:date>
    </item>
    <item>
      <title>Re: OPENSDA MSD-DEBUG-FRDMK64</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/OPENSDA-MSD-DEBUG-FRDMK64/m-p/321597#M14419</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is a MSD bootloader on the FRDM-K64F board by default (the 'mbed' bootloader). However, it does not accept S19 files and only works with .bin files (see &lt;A href="http://mcuoneclipse.com/2014/04/20/binary-files-for-the-mbed-bootloader-with-eclipse-and-gnu-arm-eclipse-plugins/" title="http://mcuoneclipse.com/2014/04/20/binary-files-for-the-mbed-bootloader-with-eclipse-and-gnu-arm-eclipse-plugins/"&gt;Binary Files for the mbed Bootloader with Eclipse and GNU ARM Eclipse Plugins | MCU on Eclipse&lt;/A&gt;). So you need to convert your S19 file into a binary file first.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jul 2014 18:11:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/OPENSDA-MSD-DEBUG-FRDMK64/m-p/321597#M14419</guid>
      <dc:creator>BlackNight</dc:creator>
      <dc:date>2014-07-17T18:11:55Z</dc:date>
    </item>
    <item>
      <title>Re: OPENSDA MSD-DEBUG-FRDMK64</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/OPENSDA-MSD-DEBUG-FRDMK64/m-p/321598#M14420</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks again.&amp;nbsp; You are getting me half-way there!&amp;nbsp; I am able to use the mbed loader to get the bin file on the k64, and then I switch to the JLink_OpenSDA to verify the board via the com port.&amp;nbsp; However, I cannot verify the program because I cannot correctly convert the S19 to bin with the mot2bin executable.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'll keep you updated on my progress...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jul 2014 21:41:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/OPENSDA-MSD-DEBUG-FRDMK64/m-p/321598#M14420</guid>
      <dc:creator>mlamp</dc:creator>
      <dc:date>2014-07-17T21:41:05Z</dc:date>
    </item>
  </channel>
</rss>

