如何识别哪些地址用于我的EEPROM存储器？

从数据表-
不需要API从EEPROM读取。EEPROM的整个内容映射到存储器空间，并且可以直接读取。EEPROM允许字节级别的读访问。以下定义用于读取EEPROM：
^ EEDPRM存储器的基本指针：CyDeVIEWEEL大小，EEPROM内存空间的大小为字节。
使用基本指针，可以读取EEPROM存储器的各个字节。
在创建者的起始页上有一个项目，因此您可以查看R/W如何进行EEPROM。
完成了。
基本上，您有一组希望存储在EEPROM中的数据。作为数据的定义者
通常，你写一行值一次给EE。作为定义，你知道它的大小和如何
它被打包成行格式。这反过来又给你写的行，16字节。
一段时间。在创建者中，双击*.CydWR将引导你到一组选项卡，其中一个
是闪光保护。所以你不会保护你打算写的那些行。
请注意，MAP文件将显示您映射到所有内存区域的内容。
CyPress公司
问候，Dana。



     以下为原文
  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.
     
    www.cypress.com/
     
    Regards, Dana.

PSoC 3内存映射



     以下为原文
  Memory map for PSOC 3
     
     

附属的。
PSoC 3内存映射
141.3 K



     以下为原文
  Attached.

•   PSOC 3 Memory Map.jpg 141.3 K
  
  

附属的。
PSoC 3存储器MAP1.JPG
141.3 K



     以下为原文
  Attached.

•   PSOC 3 Memory Map1.jpg 141.3 K
  
  

谢谢。我认为记忆地图正是我要找的。在这和CyDeVeleYBASE之间，寻址现在变得有意义了。



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