<?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 MC9S08JM16 USB Interrupt Status Is Lost in 8-bit Microcontrollers</title>
    <link>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08JM16-USB-Interrupt-Status-Is-Lost/m-p/205135#M17103</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sometimes USB TOKDNE interrupt seems to be lost in my application.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;--- after week with technical support ---&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've got some new information about the problem and a short way to reproduce it from scratch.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please see attached files:&lt;BR /&gt;&amp;nbsp;* mc9s08jm16usb.pdf - detailed bug report;&lt;BR /&gt;&amp;nbsp;* s08jm16usb.mp4 - video clip;&lt;BR /&gt;&amp;nbsp;* usblost.zip - CodeWarrior project and source code for mc9s08jm16.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I insist the problem stems from the datasheet or MCU hardware; anyway, MCU hardware's behavior doesn't conform with the datasheet. As we are developing a highly-reliable application, I guess I can't afford the risk of using just 'some proven to work solution' such as medicalusb software; I should have a reasonable explanation why it works before I can include it in my project. There is also another reason why I can't use medicalusb: its code footprint is too large and won't fit in our&lt;BR /&gt;project "as is", so I'll have to redesign the medicalusb stack (and I cannot do that without full understanding of the problem in question). Hope this helps to solve my problem. At least MCU datasheet will be corrected.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any idea?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;WBR,&lt;BR /&gt;Nick Postnikov.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 04 Jun 2010 12:18:23 GMT</pubDate>
    <dc:creator>Leptinotarsadec</dc:creator>
    <dc:date>2010-06-04T12:18:23Z</dc:date>
    <item>
      <title>MC9S08JM16 USB Interrupt Status Is Lost</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08JM16-USB-Interrupt-Status-Is-Lost/m-p/205135#M17103</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sometimes USB TOKDNE interrupt seems to be lost in my application.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;--- after week with technical support ---&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've got some new information about the problem and a short way to reproduce it from scratch.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please see attached files:&lt;BR /&gt;&amp;nbsp;* mc9s08jm16usb.pdf - detailed bug report;&lt;BR /&gt;&amp;nbsp;* s08jm16usb.mp4 - video clip;&lt;BR /&gt;&amp;nbsp;* usblost.zip - CodeWarrior project and source code for mc9s08jm16.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I insist the problem stems from the datasheet or MCU hardware; anyway, MCU hardware's behavior doesn't conform with the datasheet. As we are developing a highly-reliable application, I guess I can't afford the risk of using just 'some proven to work solution' such as medicalusb software; I should have a reasonable explanation why it works before I can include it in my project. There is also another reason why I can't use medicalusb: its code footprint is too large and won't fit in our&lt;BR /&gt;project "as is", so I'll have to redesign the medicalusb stack (and I cannot do that without full understanding of the problem in question). Hope this helps to solve my problem. At least MCU datasheet will be corrected.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any idea?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;WBR,&lt;BR /&gt;Nick Postnikov.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Jun 2010 12:18:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08JM16-USB-Interrupt-Status-Is-Lost/m-p/205135#M17103</guid>
      <dc:creator>Leptinotarsadec</dc:creator>
      <dc:date>2010-06-04T12:18:23Z</dc:date>
    </item>
    <item>
      <title>Re: MC9S08JM16 USB Interrupt Status Is Lost</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08JM16-USB-Interrupt-Status-Is-Lost/m-p/205136#M17104</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In the first place, I never use MC9S08JM16/60 for reliable USB applications, because of degraded USB engine (SIE) on these chips. Just for toys. When I've seen the datasheeet of these MCUs, I was surprised that the SIE architecture resembles to PIC's so much. PIC USB SIE is notorious as trouble maker.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;These discussions for PIC SIE are directly applied to these Freescale chips, too.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- Tight timing requirement of firmware on OUT-SETUP sequence (around 100 us dead-line response for USB interrupt)&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.microchip.com/forums/fb.aspx?m=403160" rel="nofollow" target="_blank"&gt;http://www.microchip.com/forums/fb.aspx?m=403160&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- Data toggle synchronization error for double buffer (ping-pong) on Set_Configuration(), Set_Interface() and Clear_Feature(ENDPOINT_HALT).&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.microchip.com/forums/tm.aspx?m=503200" rel="nofollow" target="_blank"&gt;http://www.microchip.com/forums/tm.aspx?m=503200&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've seen this degraded SIE architecture for low-speed devices. It's in permissible range for low-speed applications, but not for full-speed devices. As one engaged in medical instruments development so long, I recommend Freescale to withdraw these chips from medical USB applications.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Tsuneo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Jun 2010 17:48:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08JM16-USB-Interrupt-Status-Is-Lost/m-p/205136#M17104</guid>
      <dc:creator>Tsuneo</dc:creator>
      <dc:date>2010-06-04T17:48:16Z</dc:date>
    </item>
    <item>
      <title>Re: MC9S08JM16 USB Interrupt Status Is Lost</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08JM16-USB-Interrupt-Status-Is-Lost/m-p/205137#M17105</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Nick,&lt;/P&gt;&lt;P&gt;Would you please attach the bug report/mp4/zip which you mentioned in your post?&lt;/P&gt;&lt;P&gt;I am suspecting a similar problem in my project.&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 01 Nov 2014 03:24:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08JM16-USB-Interrupt-Status-Is-Lost/m-p/205137#M17105</guid>
      <dc:creator>leesp</dc:creator>
      <dc:date>2014-11-01T03:24:15Z</dc:date>
    </item>
  </channel>
</rss>

