6 Replies Latest reply on Jul 3, 2013 12:55 PM by userc_43390

    flash protection

      I am about to complete a Creator project for PSoC3 (my first major project) and would like to add some flash protection before I release it for use.  I read in a TRM or somewhere that the flash protection can't be used for bytes that hold SPC data such as EEPROM memory.  My question is:  how do I find which addresses are being used for my EEPROM memory so I can exclude flash protection on those bytes? 

        • 1. Re: flash protection

          The eeprom is not flash (as emulated eeprom) so no need to exclude it from protection, it lies outside of the normal address space.





          • 2. Re: flash protection

            From the datasheet -




            There is no need of APIs to read from the EEPROM. The entire content of the EEPROM is
            mapped into memory space and can be read directly. EEPROM allows read access at the byte
            level. The following defines are used for reading EEPROM:


             CYDEV_EE_BASE                                  The base pointer of the EEPROM memory
             CYDEV_EE_SIZE                                    The size of the EEPROM memory space in bytes
             CYDEV_EEPROM_ROW_SIZE             The size of a row of the EEPROM in bytes


            Using the base pointer, individual bytes of the EEPROM memory can be read.




            There is a project available on start page of Creator so you can look at how R/W to EEPROM


            is done.




            Basically you have a set of data that you want stored in EEPROM. As the definer of the data


            typically you write a rows worth at a time to the EE. And as definer you know its size and how


            its packed into the row format. That in turn gives you the # rows you will be writing, 16 bytes at


            a time. In Creator, double clicking *.cydwr will lead you to a group of tabs, and one of them


            is flash protection. So you would un protect those rows that you intend to write.




            Note .map file will show you whats mapped into all memory regions.








            Regards, Dana.

            • 3. Re: flash protection

              Memory map for PSOC 3





              • 4. Re: flash protection


                • 6. Re: flash protection

                  Thanks.  I think the memory map was exactly what I was looking for.  Between that and CYDEV_EE_BASE, the addressing makes sense now.