<?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>S12 / MagniV Microcontrollers中的主题 Re: S12XS - interrupt controlled hardware finite state machine</title>
    <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/S12XS-interrupt-controlled-hardware-finite-state-machine/m-p/189958#M7352</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;If you compare S12/S12X flash program/erase procedure to say MC912D60A flash prograam/erase, then you will note that S12/S12X do have program/erase finite state machine and D60A doesn't have such machine. Programming D60A user software has to set PGM bit, write aligned word to&amp;nbsp;flash to select row of flash to be programmed, wait for 10us, set flash programming&amp;nbsp;voltage enable bit, wait 5us, write data, wait for word program time, 30-40us, repeat write-wait until whole row is programmed, finally clear PGM bit, wait 5us and clear HVEN bit. In contrast, S12/S12X have flash programming state machine so that we just write a flash command and flash data and just wait until CCIF is set, or until CBEIF is set and we can write another command to flash controller. In D60A we had to follow specific timing precisely, interrupts had to be disabled, else we could overexposure high voltage applied to flash and damage the flash. S12/S12X flash state machine easied it a lot.&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 15 Feb 2008 14:33:38 GMT</pubDate>
    <dc:creator>kef</dc:creator>
    <dc:date>2008-02-15T14:33:38Z</dc:date>
    <item>
      <title>S12XS - interrupt controlled hardware finite state machine</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/S12XS-interrupt-controlled-hardware-finite-state-machine/m-p/189957#M7351</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;P align="left"&gt;&lt;SPAN style=": ; font-size: 2; font-family: Courier;"&gt;Hi,&lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left"&gt;&lt;SPAN style=": ; font-size: 2; font-family: Courier;"&gt;I read following statement in some forum,&lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left"&gt;&lt;SPAN style=": ; font-size: 2; font-family: Courier;"&gt;"current controllers and flash devices have an internal interrupt&lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left"&gt;&lt;SPAN style=": ; font-size: 2; font-family: Courier;"&gt;controlled hardware finite state machine to control the timing of the erase /&lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left"&gt;&lt;SPAN style=": ; font-size: 2; font-family: Courier;"&gt;write operations."&lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left"&gt;&lt;SPAN style=": ; font-size: 2; font-family: Courier;"&gt;I am writing flash driver for S12XS controller, I did not find any reference in datasheet where above statement can be proven.&lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left"&gt;&lt;SPAN style=": ; font-size: 2; font-family: Courier;"&gt;Any pointers for same?&lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left"&gt;&lt;SPAN style=": ; font-size: 2; font-family: Courier;"&gt;Thanks.&lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left"&gt;&lt;SPAN style=": ; font-size: 2; font-family: Courier;"&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left"&gt;&lt;SPAN style=": ; font-size: 2; font-family: Courier;"&gt;&amp;nbsp;Ajay&lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left"&gt;&lt;SPAN style=": ; font-size: 2; font-family: Courier;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left"&gt;&lt;SPAN style=": ; font-size: 2; font-family: Courier;"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Feb 2008 13:16:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/S12XS-interrupt-controlled-hardware-finite-state-machine/m-p/189957#M7351</guid>
      <dc:creator>JadhavAj</dc:creator>
      <dc:date>2008-02-15T13:16:00Z</dc:date>
    </item>
    <item>
      <title>Re: S12XS - interrupt controlled hardware finite state machine</title>
      <link>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/S12XS-interrupt-controlled-hardware-finite-state-machine/m-p/189958#M7352</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;If you compare S12/S12X flash program/erase procedure to say MC912D60A flash prograam/erase, then you will note that S12/S12X do have program/erase finite state machine and D60A doesn't have such machine. Programming D60A user software has to set PGM bit, write aligned word to&amp;nbsp;flash to select row of flash to be programmed, wait for 10us, set flash programming&amp;nbsp;voltage enable bit, wait 5us, write data, wait for word program time, 30-40us, repeat write-wait until whole row is programmed, finally clear PGM bit, wait 5us and clear HVEN bit. In contrast, S12/S12X have flash programming state machine so that we just write a flash command and flash data and just wait until CCIF is set, or until CBEIF is set and we can write another command to flash controller. In D60A we had to follow specific timing precisely, interrupts had to be disabled, else we could overexposure high voltage applied to flash and damage the flash. S12/S12X flash state machine easied it a lot.&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Feb 2008 14:33:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S12-MagniV-Microcontrollers/S12XS-interrupt-controlled-hardware-finite-state-machine/m-p/189958#M7352</guid>
      <dc:creator>kef</dc:creator>
      <dc:date>2008-02-15T14:33:38Z</dc:date>
    </item>
  </channel>
</rss>

