Cart New Account Login

HomeAbout usProductsSupportForumsBlogCustomer Service

Please accept the use of cookies on our site

At PEmicro we use web browser cookies in order to provide you with an enhanced experience and in order to be able to do things like shopping cart processing and identify you when you login to our website.

Click here to accept

search inside this forum
search inside all forums
Preserve internat E2prom on KE02
Josep M. Sep 15, 2017 at 09:13 AM (09:13 hours)
Staff: Takao Y.

  • I am working with a Kinetis KE02 with internal memory E2prom and I need to update the program of some boards that were already working while retaining the data that are in the E2prom, but when I record the new program with the Cyclone MAX, I overwrite the data that I have in the E2prom.

    How can I do to preserve the data in E2prom that had initially?


  • Greetings,

    This is a question asked often. You should have found the answer by doing a search in our forums.

    Look into Preserve Range:

    Takao Yamada

  • Thank you for your response,

    I tried to include line "PRESERVE_RANGUE" betwen "NO_BASE_ADDRESS" and "ADDR_RANGUE" in file "freescale_ke02z64m4_pflash_eeprom.arp" but data in eepom is still erased.

    ADDR_RANGE=00000000/0000FFFF/00/FFFFFFF8/FFFFFE00/ ; $00000000-$0000FFFF P-Flash
    ADDR_RANGE=10000000/100000FF/00/FFFFFFF8/FFFFFF00/ ; $10000000-$100000FF D-Flash

    what am i doing wrong?

  • Greetings,

    Within the cyclone max there is a software called PROGACMP. Try using your modified algorithm there and see if you can program the device while preserving the data. If it works there, then we can look into why the image you are creating is not working. If it also does not work there, then we can look into the algorithm why it is not working.

    Takao Yamada

  • Greetings,

    With PROGACMP I can program the device and data is preserved with both algorithms, the original one and the modified.

    With Cyclone both algorithms erase the eeprom.

  • Greetings,

    THe original algorithm is suppose to erase both the PFLASH and DFLASH. You are suppose to see your EEPROM data not preserved. So I am confused as to why you see the same results with both algorithms. Please redo the test and make sure you see a difference. After running the EM command, use the Show module command to confirm that the memory has been completely erased. Only the modified algorithm should re-program your preserved data back after erasing.

    Takao Yamada

  • Greetings,

    Sorry, in my previous test I forgot to execute the command BM.

    Executing first the BM command PROGACMP works well. With the original algorithm erases the data and with the modified it preserves them.

    But with Cyclone the eeprom isn't preserved.

  • Where I said BM wanted to say EM.

  • Greetings,

    Are you sure you are using the modified algorithm when creating a new image using image creation utility?

    What commands in order are you using in your image? Make sure to remove old images on your cyclone and confirm you have a new image with the modified algorithm. I have tested this before so I have confidence this is supposed to work. Especially if you were able to get it working with PROGACMP.

    Takao Yamada

  • Greetings,

    I have verified it and I am completely sure that the algorithm file is modified, the same as when I use PROGACMP. In the cyclone I have a single image file and it is the correct one and always erases the data of the eeprom.

    Commands for the image file are:

    CM C:\.....\Freeacale_ke02z64m4_modified.asp
    SS C:\.....\"hex file"

    "Cyclone Image Creation Utility" Version
    Cyclone MAX V7.94-6.2 (firmware)

    I tried to do the same with a Cyclone FX (with "Image Creation Utility" version and the result was the same.

    Thanks for your help.

    Josep Mestre

  • Greetings,

    Could you create a support ticket by going to Support page -> Support requests and post the algorithm you are using? I want to look at it and also discuss with the cyclone experts to find out why this is not working in standalone. Now is a good time to bring this up because they are in the works to release a new firmware.

    Takao Yamada

    • Hi

      I have a similar issue of preservinge a part of the FLASH during programming a Kinetis K10 processor.

      I have modified the algorithm file and it works if I use PROGACMP but when running it in standalone mode on the Cyclone the data is erased and reads as 0xFF

      Was this problem resolved?

      Best Regards
      Joakim Arnsby

      • Hi

        No, I have not managed to keep the E2Prom when programming with the Cyclone. I had to do a program to read the existing values, update the program with the Cyclone and then retrieve the athering values.

        None of the solutions that gave me PEmicro worked.

        Best regards.
        Josep Mestre

  • Greetings,

    From the support ticket, the user never answered back to our questions. Most likely the issue is the user was using the SD command in their list of commands. If you secure the chip and attempt to preserve data, that will not work. To be able to enter debug on a secured chip the entire flash must be completely erased and no data will be preserved.

    Takao Yamada

  • Hi

    I'm not using the SD command, these are the commands I'm using


    I used the exact same commands and the same algorithm file with PROGACMP and that worked. I have also upgraded Cyclone Image creation utililty to the latest version but still with the same issue.

    Is there a way to get more loggin info from the Cyclone during standalone mode?
    It's hard to se exactly what it does from the on screen status bar.


  • Hi Joakim,

    Not sure if you still have the issue.

    I just tried our Cyclone Max and Cyclone Universal (and FX) with KE02Z64M2 and K701M0M15 with Preserve Range. I didn't see any issue both in interactive mode (PROGACMP_Cyclone.exe) and stand alone mode.

    Below are the modifications of the algorithms:
    For KE02, I added the following two lines since I want to test both DFlash and PFlash.

    For K70, I added only one line:

    Would you please try our latest software and firmware and see if you still have the issue although I don't recall any code improvements regarding preserving range?

    If the issue still exists, would you please send me a copy of the algorithm file, your S19 file, (if you want to preserve certain data, you shouldn't have them in your S19 file), and a screen shot of your createImage? My email address is

    Best Regards

Add comment

   Want to comment? Please login or create a new PEMicro account.

© 2019 P&E Microcomputer Systems Inc.
Website Terms of Use and Sales Agreement