<?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 KEAZ128 write flash issue in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KEAZ128-write-flash-issue/m-p/461534#M27658</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am using the PE function below to write flash for bootloader . &lt;/P&gt;&lt;P&gt;LDD_TError FLASH1_Write(LDD_TDeviceData *DeviceDataPtr, LDD_TData *FromPtr, LDD_FLASH_TAddress ToAddress, LDD_FLASH_TDataSize Size)&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It works well until the start address is 0x5860. But it can't work well when write the data to start address which is 0x586C.&lt;/P&gt;&lt;P&gt;It can work well if I changed start address from 0x586C to 0x5870 (the data also be rearranged).&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;lt;part of s19 file&amp;gt;&lt;/P&gt;&lt;P&gt;S11358400000000000000000000000000000000054&lt;/P&gt;&lt;P&gt;S11358500000000000000000000000000000000044&lt;/P&gt;&lt;P&gt;S10F586000000000000000000000000038&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #e23d39;"&gt;S113586C586C6C58000000F0FF1F000000000000000056&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My question:&lt;/P&gt;&lt;P&gt;1. Can function FLASH1_Write work in the CAN Interrupt event?&lt;/P&gt;&lt;P&gt;2. Is there any limit&amp;nbsp; for FLASH1_Write's param&amp;nbsp; LDD_FLASH_TAddress ToAddress ？&lt;/P&gt;&lt;P&gt;3. Any advice...&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Jason&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-337543"&gt;KEA128_APP_3.s19.zip&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 09 Mar 2016 06:58:33 GMT</pubDate>
    <dc:creator>jason_zhang</dc:creator>
    <dc:date>2016-03-09T06:58:33Z</dc:date>
    <item>
      <title>KEAZ128 write flash issue</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KEAZ128-write-flash-issue/m-p/461534#M27658</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am using the PE function below to write flash for bootloader . &lt;/P&gt;&lt;P&gt;LDD_TError FLASH1_Write(LDD_TDeviceData *DeviceDataPtr, LDD_TData *FromPtr, LDD_FLASH_TAddress ToAddress, LDD_FLASH_TDataSize Size)&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It works well until the start address is 0x5860. But it can't work well when write the data to start address which is 0x586C.&lt;/P&gt;&lt;P&gt;It can work well if I changed start address from 0x586C to 0x5870 (the data also be rearranged).&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;lt;part of s19 file&amp;gt;&lt;/P&gt;&lt;P&gt;S11358400000000000000000000000000000000054&lt;/P&gt;&lt;P&gt;S11358500000000000000000000000000000000044&lt;/P&gt;&lt;P&gt;S10F586000000000000000000000000038&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #e23d39;"&gt;S113586C586C6C58000000F0FF1F000000000000000056&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My question:&lt;/P&gt;&lt;P&gt;1. Can function FLASH1_Write work in the CAN Interrupt event?&lt;/P&gt;&lt;P&gt;2. Is there any limit&amp;nbsp; for FLASH1_Write's param&amp;nbsp; LDD_FLASH_TAddress ToAddress ？&lt;/P&gt;&lt;P&gt;3. Any advice...&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Jason&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-337543"&gt;KEA128_APP_3.s19.zip&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Mar 2016 06:58:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/KEAZ128-write-flash-issue/m-p/461534#M27658</guid>
      <dc:creator>jason_zhang</dc:creator>
      <dc:date>2016-03-09T06:58:33Z</dc:date>
    </item>
    <item>
      <title>Re: KEAZ128 write flash issue</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KEAZ128-write-flash-issue/m-p/461535#M27659</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The issue has been solved.&lt;/P&gt;&lt;P&gt;All user state is erased when the bootloader start.&lt;/P&gt;&lt;P&gt;PC GUI sends the&amp;nbsp; CAN Data with consistent 8 bytes longth,&lt;/P&gt;&lt;P&gt;even though the S19 is not long enough,full with 0x00.&lt;/P&gt;&lt;P&gt;That is the reason why I can't write flash 0x586C,&lt;/P&gt;&lt;P&gt;0x586C - 0x586F flash has been written with 0x00.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From the datasheet below,is not allowed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Datasheet&lt;/P&gt;&lt;P&gt;---------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;CAUTION&lt;/P&gt;&lt;P&gt;A flash byte or longword must be in the erased state before&lt;/P&gt;&lt;P&gt;being programmed. Cumulative programming of bits within a&lt;/P&gt;&lt;P&gt;flash byte or longword is not allowed.&lt;/P&gt;&lt;P&gt;---------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;P&gt;Jason&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Mar 2016 03:34:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/KEAZ128-write-flash-issue/m-p/461535#M27659</guid>
      <dc:creator>jason_zhang</dc:creator>
      <dc:date>2016-03-10T03:34:41Z</dc:date>
    </item>
    <item>
      <title>Re: KEAZ128 write flash issue</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KEAZ128-write-flash-issue/m-p/461536#M27660</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Janson,&lt;/P&gt;&lt;P&gt;Thanks for your sharing.&lt;/P&gt;&lt;P&gt;I think the other bootloader developers also may encounter this kind of mistake.&lt;BR /&gt;Have a great day,&lt;BR /&gt;Ping&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Mar 2016 08:39:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/KEAZ128-write-flash-issue/m-p/461536#M27660</guid>
      <dc:creator>jeremyzhou</dc:creator>
      <dc:date>2016-03-10T08:39:11Z</dc:date>
    </item>
  </channel>
</rss>

