<?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 USB BDM Unable to connect to Hardware interface in CodeWarrior for MCU</title>
    <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/USB-BDM-Unable-to-connect-to-Hardware-interface/m-p/257989#M9852</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;i am using Code warrior 10.5 with MCF54415, windows x64 Environment.&lt;/P&gt;&lt;P&gt;currently i am facing one issue, whenever i connect the PEBDM(USB Multilink Rev.D) to my Board it always shows one error :&lt;/P&gt;&lt;P&gt;An error occured while connecting to interface hardware or target specified.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="9893_9893.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/119725iFE1A1766D4B44960/image-size/large?v=v2&amp;amp;px=999" role="button" title="9893_9893.jpg" alt="9893_9893.jpg" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="PE_Download.JPG.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/42837i548BFD8E396FC8A3/image-size/large?v=v2&amp;amp;px=999" role="button" title="PE_Download.JPG.jpg" alt="PE_Download.JPG.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="9894_9894.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/119726i6812FA15283C3FA4/image-size/large?v=v2&amp;amp;px=999" role="button" title="9894_9894.jpg" alt="9894_9894.jpg" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Error_P&amp;amp;E.JPG.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/42838i81A877DF5270F0FD/image-size/large?v=v2&amp;amp;px=999" role="button" title="Error_P&amp;amp;E.JPG.jpg" alt="Error_P&amp;amp;E.JPG.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Attached the Snapshot of Error.&lt;/P&gt;&lt;P&gt;Please help me out of this error.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Kunal gaur&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 24 Feb 2014 23:10:00 GMT</pubDate>
    <dc:creator>kunalgaur</dc:creator>
    <dc:date>2014-02-24T23:10:00Z</dc:date>
    <item>
      <title>USB BDM Unable to connect to Hardware interface</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/USB-BDM-Unable-to-connect-to-Hardware-interface/m-p/257989#M9852</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;i am using Code warrior 10.5 with MCF54415, windows x64 Environment.&lt;/P&gt;&lt;P&gt;currently i am facing one issue, whenever i connect the PEBDM(USB Multilink Rev.D) to my Board it always shows one error :&lt;/P&gt;&lt;P&gt;An error occured while connecting to interface hardware or target specified.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="9893_9893.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/119725iFE1A1766D4B44960/image-size/large?v=v2&amp;amp;px=999" role="button" title="9893_9893.jpg" alt="9893_9893.jpg" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="PE_Download.JPG.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/42837i548BFD8E396FC8A3/image-size/large?v=v2&amp;amp;px=999" role="button" title="PE_Download.JPG.jpg" alt="PE_Download.JPG.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="9894_9894.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/119726i6812FA15283C3FA4/image-size/large?v=v2&amp;amp;px=999" role="button" title="9894_9894.jpg" alt="9894_9894.jpg" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Error_P&amp;amp;E.JPG.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/42838i81A877DF5270F0FD/image-size/large?v=v2&amp;amp;px=999" role="button" title="Error_P&amp;amp;E.JPG.jpg" alt="Error_P&amp;amp;E.JPG.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Attached the Snapshot of Error.&lt;/P&gt;&lt;P&gt;Please help me out of this error.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Kunal gaur&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Feb 2014 23:10:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/USB-BDM-Unable-to-connect-to-Hardware-interface/m-p/257989#M9852</guid>
      <dc:creator>kunalgaur</dc:creator>
      <dc:date>2014-02-24T23:10:00Z</dc:date>
    </item>
    <item>
      <title>Re: USB BDM Unable to connect to Hardware interface</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/USB-BDM-Unable-to-connect-to-Hardware-interface/m-p/257990#M9853</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Kunal,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are many reasons why you can get this error. Please see below the most common problems and how to solve them:&lt;/P&gt;&lt;P style="text-indent: -0.25in;"&gt;&lt;STRONG&gt;&lt;SPAN class="pasted-list-info"&gt;1)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;/STRONG&gt;First restart CW and unplug the MCU to be sure that CW is not causing the debugger lines to keep some values that are not allowing the MCU to be programmed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="text-indent: -0.25in;"&gt;&lt;STRONG&gt;&lt;SPAN class="pasted-list-info"&gt;2)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;The MCU is not being flashed correctly&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Please find attached a video showing 4 different ways to flash a Freescale Kinetis device (the process for ColdFire processors is the same).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="text-indent: -0.25in;"&gt;&lt;STRONG&gt;&lt;SPAN class="pasted-list-info"&gt;3)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;Your connection is corrupted&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;You can either create a new connection or create a new project which will create automatically a new connection, and then you can use the new connection to flash your original project.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="text-indent: -0.25in;"&gt;&lt;STRONG&gt;&lt;SPAN class="pasted-list-info"&gt;4)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;USB Multilink is defective or firmware is no up to date&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;You can download latest firmware from P&amp;amp;E Micro website: &lt;A href="http://www.pemicro.com/products/product_viewDetails.cfm?product_id=163"&gt;http://www.pemicro.com/products/product_viewDetails.cfm?product_id=163&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="text-indent: -0.25in;"&gt;&lt;STRONG&gt;&lt;SPAN class="pasted-list-info"&gt;5)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;USB Multilink Drivers were not installed correctly &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;One solution is to do a re-install of CW, but because this is very time consuming, you might try another approach; installing the drivers manually. The good thing is: you can install the drivers from &amp;lt;CW installation path&amp;gt;\drivers\P&amp;amp;E.&lt;/P&gt;&lt;P&gt;But the WinDriver one is a little bit tricky (as Windows does not recognize it with ‘scan for new hardware’).&lt;/P&gt;&lt;P&gt;The needed steps are shown in the attached document (Installing PnE Jungo Drivers Manually.pdf) so you know how you can install the driver manually.&lt;/P&gt;&lt;P&gt;You can also find an FAQ on the web about driver re-installation: &lt;SPAN style="text-decoration: underline;"&gt;&lt;A href="http://www.pemicro.com/faqs/faq_view.cfm?id=29&amp;amp;menu_id=faqs"&gt;http://www.pemicro.com/faqs/faq_view.cfm?id=29&amp;amp;menu_id=faqs&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="text-indent: -0.25in;"&gt;&lt;STRONG&gt;&lt;SPAN class="pasted-list-info"&gt;6)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;Hardware problem or hardware design problem&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I recommend to double check that your hardware is not damaged, after this you can compare the TWR-5441x schematic with yours and verify that there is no problem with the debugger lines.&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=TWR-MCF5441X"&gt;http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=TWR-MCF5441X&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://cache.freescale.com/files/32bit/hardware_tools/schematics/SCH-26131.pdf?fr=g"&gt;http://www.freescale.com/files/32bit/hardware_tools/schematics/SCH-26131.pdf?fr=g&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="text-indent: -0.25in;"&gt;&lt;STRONG&gt;&lt;SPAN class="pasted-list-info"&gt;7)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;The Flash device you are using is not supported my CodeWarrior&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;If you decide to use a Flash device that is not supported by CodeWarrior you must make two things to have it usable.&lt;/P&gt;&lt;P style="text-indent: -0.25in;"&gt;&lt;SPAN class="pasted-list-info"&gt;A.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;Create a Flash Algorithm&lt;/P&gt;&lt;P&gt;CodeWarrior uses .elf files which describe Flash algorithms. Although some flash memories have the same physical characteristics, the program and erase time cycles may change from one memory to other (even if they are from the same manufacturer). This is why you must create a flash algorithm for the device you have selected. In your CodeWarrior installation path you can find a document which explains how to create an algorithm for a flash device.&lt;/P&gt;&lt;P&gt;C:\Program Files\Freescale\CW MCU v10.5\MCU\Help\PDF\AN3859.pdf&lt;/P&gt;&lt;P style="text-indent: -0.25in;"&gt;&lt;SPAN class="pasted-list-info"&gt;B.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;Create the flash device description and add it to CodeWarrior&lt;/P&gt;&lt;P&gt;Once you have the appropriate algorithm for your flash memory you must create a device description. The device description is a bunch of parameters that you must add to a .xml file with the appropriate Syntax. This file contains all supported flash devices. You can generate this information by yourself or you can use a script to generate the info and just paste it in the .xml file. Look to the same document for this purpose&lt;/P&gt;&lt;P&gt;C:\Program Files\Freescale\CW MCU v10.5\MCU\Help\PDF\AN3859.pdf&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps!&lt;/P&gt;&lt;P&gt;Carlos&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Feb 2014 22:24:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/USB-BDM-Unable-to-connect-to-Hardware-interface/m-p/257990#M9853</guid>
      <dc:creator>Carlos_Musich</dc:creator>
      <dc:date>2014-02-25T22:24:23Z</dc:date>
    </item>
    <item>
      <title>Re: USB BDM Unable to connect to Hardware interface</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/USB-BDM-Unable-to-connect-to-Hardware-interface/m-p/257991#M9854</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Carlos,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks for the Useful information.&lt;/P&gt;&lt;P&gt;it was very helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just one query i have , this video it shows flashing into internal flash, does the same procedure follows for external flash as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your support.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Kunal Gaur&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Feb 2014 03:01:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/USB-BDM-Unable-to-connect-to-Hardware-interface/m-p/257991#M9854</guid>
      <dc:creator>kunalgaur</dc:creator>
      <dc:date>2014-02-26T03:01:17Z</dc:date>
    </item>
    <item>
      <title>Re: USB BDM Unable to connect to Hardware interface</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/USB-BDM-Unable-to-connect-to-Hardware-interface/m-p/257992#M9855</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Kunal,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;If the external flash is supported by CodeWarrior and you have the correct settings in the linker file and initialization files the process is the same.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="text-align: left;"&gt;&lt;SPAN style="font-family: Calibri; color: black; font-size: 11pt;"&gt;Initialization files are .&lt;/SPAN&gt;&lt;SPAN style="font-family: Calibri; color: black; font-size: 11pt;"&gt;mem&lt;/SPAN&gt; &lt;SPAN style="font-family: Calibri; color: black; font-size: 11pt;"&gt;and &lt;/SPAN&gt;&lt;SPAN style="font-family: Calibri; color: black; font-size: 11pt;"&gt;.cfg&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="text-align: left;"&gt;&lt;SPAN style="font-family: Calibri; color: black; font-size: 11pt;"&gt;.mem file tells the debugger all information about the memory space in the MCU and memory addresses. &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="text-align: left;"&gt;&lt;SPAN style="font-family: Calibri; color: black; font-size: 11pt;"&gt;.cfg contains all the initialization instructions that the debugger uses to configure the MCU with the minimum settings required to start the communication between MCU and debugger. &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="text-align: left;"&gt; &lt;/P&gt;&lt;P style="text-align: left;"&gt;&lt;SPAN style="font-family: Calibri; color: black; font-size: 11pt;"&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="text-align: left;"&gt;&lt;SPAN style="font-family: Calibri; color: black; font-size: 11pt;"&gt;Carlos&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2014 17:32:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/USB-BDM-Unable-to-connect-to-Hardware-interface/m-p/257992#M9855</guid>
      <dc:creator>Carlos_Musich</dc:creator>
      <dc:date>2014-03-19T17:32:16Z</dc:date>
    </item>
  </channel>
</rss>

