<?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>8-bit MicrocontrollersのトピックPage boundaries for flash block erase - question</title>
    <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Page-boundaries-for-flash-block-erase-question/m-p/241187#M19580</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I am using an MC9S08QE128. Looking at the memory map:&lt;/P&gt;&lt;P&gt;There is an 8064 byte flash block from 0x2080 to 0x3FFF.&lt;/P&gt;&lt;P&gt;If I want to erase a 512 byte block of flash, (I am using doonstack), must the block start at a page boundary such as 0x2100? The RAM space above this block in the memory map is 0x1880 to 0x207F. Can I erase from 0x2080 since this is not the start of a boundary or would I have to erase from 0x2000 ? (which may cause problems, since the ram extends to 0x207F)&lt;/P&gt;&lt;P&gt;thanks &lt;/P&gt;&lt;P&gt;Russell&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 30 Jan 2013 06:44:01 GMT</pubDate>
    <dc:creator>russellsher</dc:creator>
    <dc:date>2013-01-30T06:44:01Z</dc:date>
    <item>
      <title>Page boundaries for flash block erase - question</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Page-boundaries-for-flash-block-erase-question/m-p/241187#M19580</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I am using an MC9S08QE128. Looking at the memory map:&lt;/P&gt;&lt;P&gt;There is an 8064 byte flash block from 0x2080 to 0x3FFF.&lt;/P&gt;&lt;P&gt;If I want to erase a 512 byte block of flash, (I am using doonstack), must the block start at a page boundary such as 0x2100? The RAM space above this block in the memory map is 0x1880 to 0x207F. Can I erase from 0x2080 since this is not the start of a boundary or would I have to erase from 0x2000 ? (which may cause problems, since the ram extends to 0x207F)&lt;/P&gt;&lt;P&gt;thanks &lt;/P&gt;&lt;P&gt;Russell&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2013 06:44:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Page-boundaries-for-flash-block-erase-question/m-p/241187#M19580</guid>
      <dc:creator>russellsher</dc:creator>
      <dc:date>2013-01-30T06:44:01Z</dc:date>
    </item>
    <item>
      <title>Re: Page boundaries for flash block erase - question</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Page-boundaries-for-flash-block-erase-question/m-p/241188#M19581</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can erase sector at 0x2080. This will erase whole 512bytes sector. You'll get erased nonbanked addresses 0x2080..0x21FF, also banked addresses PPAGE=0:0xA000 to PPAGE=0:0xA1FF. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2013 07:51:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Page-boundaries-for-flash-block-erase-question/m-p/241188#M19581</guid>
      <dc:creator>kef</dc:creator>
      <dc:date>2013-01-30T07:51:42Z</dc:date>
    </item>
    <item>
      <title>Re: Page boundaries for flash block erase - question</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/Page-boundaries-for-flash-block-erase-question/m-p/241189#M19582</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;many thanks for the reply&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2013 09:58:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/Page-boundaries-for-flash-block-erase-question/m-p/241189#M19582</guid>
      <dc:creator>admin</dc:creator>
      <dc:date>2013-01-30T09:58:14Z</dc:date>
    </item>
  </channel>
</rss>

