<?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: MC9S08 &amp;quot;dead&amp;quot; flash? in 8-bit Microcontrollers</title>
    <link>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08-quot-dead-quot-flash/m-p/1512698#M23553</link>
    <description>&lt;P&gt;Based on the S19 file, CodeWarrior and the P&amp;amp;E Multlilink Universal FX are supposed to set those locations to 0xA1 and 0x08. &amp;nbsp;They are always 0xFF.&lt;/P&gt;</description>
    <pubDate>Sat, 27 Aug 2022 14:38:09 GMT</pubDate>
    <dc:creator>GaryOlmstead</dc:creator>
    <dc:date>2022-08-27T14:38:09Z</dc:date>
    <item>
      <title>MC9S08 "dead" flash?</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08-quot-dead-quot-flash/m-p/1511891#M23551</link>
      <description>&lt;P&gt;Just when I thought I'd seen everything, something new comes along.&amp;nbsp; Today I have two flash memory locations, 0x402E and 0x402F that always read 0xFF.&amp;nbsp; They should be 0xa1 and 0x08 (CMP #08).&lt;/P&gt;&lt;P&gt;The processor is an MC9S08QE128.&amp;nbsp; I'm using CW for MCUs, 11.1.&amp;nbsp; Questions:&lt;/P&gt;&lt;P&gt;&amp;nbsp;- Can I use CW to attempt to manually reprogram these locations to verify the problem?&lt;/P&gt;&lt;P&gt;&amp;nbsp;- Is there a test to see what other locations might be affected?&lt;/P&gt;&lt;P&gt;&amp;nbsp;- Is there a way to tell CW to avoid these locations?&lt;/P&gt;</description>
      <pubDate>Thu, 25 Aug 2022 17:06:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08-quot-dead-quot-flash/m-p/1511891#M23551</guid>
      <dc:creator>GaryOlmstead</dc:creator>
      <dc:date>2022-08-25T17:06:36Z</dc:date>
    </item>
    <item>
      <title>Re: MC9S08 "dead" flash?</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08-quot-dead-quot-flash/m-p/1512641#M23552</link>
      <description>&lt;P&gt;sorry would be possible that you to explain a little bit&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You have a program and you can not write to those addresses?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;how are you writing to those?&lt;/P&gt;
&lt;P&gt;you can write to all the other memory areas&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;are you using flash routines?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;regards&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Aug 2022 23:26:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08-quot-dead-quot-flash/m-p/1512641#M23552</guid>
      <dc:creator>vicentegomez</dc:creator>
      <dc:date>2022-08-26T23:26:26Z</dc:date>
    </item>
    <item>
      <title>Re: MC9S08 "dead" flash?</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08-quot-dead-quot-flash/m-p/1512698#M23553</link>
      <description>&lt;P&gt;Based on the S19 file, CodeWarrior and the P&amp;amp;E Multlilink Universal FX are supposed to set those locations to 0xA1 and 0x08. &amp;nbsp;They are always 0xFF.&lt;/P&gt;</description>
      <pubDate>Sat, 27 Aug 2022 14:38:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08-quot-dead-quot-flash/m-p/1512698#M23553</guid>
      <dc:creator>GaryOlmstead</dc:creator>
      <dc:date>2022-08-27T14:38:09Z</dc:date>
    </item>
    <item>
      <title>Re: MC9S08 "dead" flash?</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08-quot-dead-quot-flash/m-p/1513468#M23554</link>
      <description>&lt;P&gt;So when you load the S19 using the multilink FX and CodeWarrior, the file is loaded properly, without error but two locations are not written, it is correct?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can you please check that you are setting the correct device?&lt;/P&gt;
&lt;P&gt;if you run the loaded program on the device, the device runs?&lt;/P&gt;
&lt;P&gt;regards&lt;/P&gt;</description>
      <pubDate>Tue, 30 Aug 2022 01:04:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08-quot-dead-quot-flash/m-p/1513468#M23554</guid>
      <dc:creator>vicentegomez</dc:creator>
      <dc:date>2022-08-30T01:04:52Z</dc:date>
    </item>
    <item>
      <title>Re: MC9S08 "dead" flash?</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08-quot-dead-quot-flash/m-p/1514781#M23555</link>
      <description>&lt;P&gt;&amp;nbsp;Vincent --&lt;/P&gt;&lt;P&gt;The program is for the QE128, which is on the board.&lt;/P&gt;&lt;P&gt;The program runs, but obviously doesn't load Port A.&lt;/P&gt;&lt;P&gt;I wrote a tiny program just to test those memory locations.&amp;nbsp; Here is the main part of the program:&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;XDEF _Startup&lt;BR /&gt;ABSENTRY _Startup&lt;/P&gt;&lt;P&gt;ORG RAMStart ; Insert your data definition here&lt;BR /&gt;ExampleVar: DS.B 1&lt;/P&gt;&lt;P&gt;ORG $4028 ; was ROMStart&lt;BR /&gt;&lt;BR /&gt;_Startup:&lt;BR /&gt;LDHX #RAMEnd+1 ; initialize the stack pointer&lt;BR /&gt;TXS&lt;BR /&gt;CLI ; enable interrupts&lt;/P&gt;&lt;P&gt;mainLoop:&lt;BR /&gt;NOP&lt;BR /&gt;lda PTAD&lt;BR /&gt;feed_watchdog&lt;BR /&gt;BRA mainLoop&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It puts the "LDA PTAD" right at 0x402E and 0x402F.&amp;nbsp; No difference, they are 0xFF.&lt;/P&gt;&lt;P&gt;I then added some NOPs to shove the code over a bit:&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;ORG $4028 ; was ROMStart&lt;BR /&gt;&lt;BR /&gt;_Startup:&lt;BR /&gt;LDHX #RAMEnd+1 ; initialize the stack pointer&lt;BR /&gt;TXS&lt;BR /&gt;CLI ; enable interrupts&lt;/P&gt;&lt;P&gt;mainLoop:&lt;BR /&gt;NOP&lt;BR /&gt;NOP&lt;BR /&gt;NOP&lt;BR /&gt;NOP&lt;BR /&gt;NOP&lt;BR /&gt;lda PTAD&lt;BR /&gt;feed_watchdog&lt;BR /&gt;BRA mainLoop&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;0x402E and 0x402F are still 0xff.&amp;nbsp; The LDA PTAD has moved to 0x4032.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So, I guess the chip is bad.&lt;/P&gt;&lt;P&gt;Is there a way to test the next chip to see if it has a similar problem?&amp;nbsp; I know the factory has ways, but is there anything I can use?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Gary&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Aug 2022 16:34:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08-quot-dead-quot-flash/m-p/1514781#M23555</guid>
      <dc:creator>GaryOlmstead</dc:creator>
      <dc:date>2022-08-31T16:34:18Z</dc:date>
    </item>
    <item>
      <title>Re: MC9S08 "dead" flash?</title>
      <link>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08-quot-dead-quot-flash/m-p/1514896#M23556</link>
      <description>&lt;P&gt;Sorry, I do not know how you can test all the flash in an easy way and fast way.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;but you can try to load data in all the flash and then perform a mass erase, but this will be slow&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I do not remember if PÊ has any option for that using the ciclone&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Aug 2022 19:50:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/8-bit-Microcontrollers/MC9S08-quot-dead-quot-flash/m-p/1514896#M23556</guid>
      <dc:creator>vicentegomez</dc:creator>
      <dc:date>2022-08-31T19:50:15Z</dc:date>
    </item>
  </channel>
</rss>

