<?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: Unable to debug TWR-S08PT60 after programming.   in 8-bit Microcontrollers</title>
    <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Unable-to-debug-TWR-S08PT60-after-programming/m-p/463773#M21701</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Eric&lt;/P&gt;&lt;P&gt;yes, when the MCU is in stop is hard to enter to debug or program again the board, are you using the open BDM on the TWR?&lt;/P&gt;&lt;P&gt;If you have a cyclone pro you can use it to reprogram the board using the BDM header instead of the USB OSBDM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you do not have a Cyclone you need to force to reset the MCU to enter to debug mode and reprogram it.&lt;/P&gt;&lt;P&gt;I believe you can do that using the BDM header of the board and put in low the reset and try to make the comunication.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Vicente Gomez&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 27 Apr 2016 20:35:10 GMT</pubDate>
    <dc:creator>vicentegomez</dc:creator>
    <dc:date>2016-04-27T20:35:10Z</dc:date>
    <item>
      <title>Unable to debug TWR-S08PT60 after programming. </title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Unable-to-debug-TWR-S08PT60-after-programming/m-p/463772#M21700</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Code setup the IIC in slave mode and then issued a STOP to wait for an interrupt.&amp;nbsp;&amp;nbsp; After programming with this code the debugger is unable to connect.&amp;nbsp; I suspect that the debugger is unable to interact while the processor is stopped?&amp;nbsp; I guess I could stimulate the IIC and see if the debugger can break in then.&amp;nbsp; Anyone else have this issue and know a solution?&amp;nbsp; I've ordered a spare board just to make sure the project keeps moving for now.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Apr 2016 15:11:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Unable-to-debug-TWR-S08PT60-after-programming/m-p/463772#M21700</guid>
      <dc:creator>ericbryan</dc:creator>
      <dc:date>2016-04-20T15:11:55Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to debug TWR-S08PT60 after programming.</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Unable-to-debug-TWR-S08PT60-after-programming/m-p/463773#M21701</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Eric&lt;/P&gt;&lt;P&gt;yes, when the MCU is in stop is hard to enter to debug or program again the board, are you using the open BDM on the TWR?&lt;/P&gt;&lt;P&gt;If you have a cyclone pro you can use it to reprogram the board using the BDM header instead of the USB OSBDM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you do not have a Cyclone you need to force to reset the MCU to enter to debug mode and reprogram it.&lt;/P&gt;&lt;P&gt;I believe you can do that using the BDM header of the board and put in low the reset and try to make the comunication.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Vicente Gomez&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Apr 2016 20:35:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Unable-to-debug-TWR-S08PT60-after-programming/m-p/463773#M21701</guid>
      <dc:creator>vicentegomez</dc:creator>
      <dc:date>2016-04-27T20:35:10Z</dc:date>
    </item>
  </channel>
</rss>

