没有EEPROM_Start的PSoC3 EEPROM产生CYRET_UNKNOWN

红杉，
感谢您与我们分享您的经验！
鲍勃



     以下为原文
  sequoiacpe,
    thank you for sharing your experience with us!
     
    Bob

你好，
在创建者2（EEPROM V1.60）中的EEPROM数据表提到了API支持。例如：对于API EEPROMYSTATE（），它提到“此API仅适用于PSoC 3生产或以后使用”。PSOC 3 ES3是生产硅。
同时，当使用EEPROM和Flash API时，请不要忘记阅读系统参考指南——“Flash和EEPROM”一节。它告诉我们CyStTebug（）API需要在执行一系列FLAS/EEPROM写入功能时被调用。
问候，Aniruddha



     以下为原文
   Hi,
          The EEPROM datasheet in Creator 2.0 (EEPROM v1.60) mentions about the APIs support. e.g.: For API EEPROM_Start(), it mentions that "This API is available only for PSoC 3 Production or later". PSoC 3 ES3 is production silicon.
    Also while using EEPROM and Flash APIs please don't forget to read System Reference Guide - section "Flash and EEPROM". It tells us that CySetTemp() API needs to be called once before executing a series of Flash / EEPROM writing functions.
    Regards, Aniruddha

如果没有启用ECC（我怀疑它是典型的规范），则需要CyStFraseHeBuffER（）。
但我的观点是，在ES2上工作的EEPROM代码在ES3上可能不起作用。我最新的查看EEPROM示例项目（只有1个可用）不包括启动。CyPress在改变它们所需要的操作时，应该做出更明确的改变，并扩大CyStAcess，以更有效地告诉什么是真正的问题，当任何改变都放弃了旧的可操作代码和新的要求。测试和更新当更改影响示例项目时所需的更新。
红杉属



     以下为原文
   AND CySetFlashEEBuffer() is needed if not ECC enabled (which I suspect is the typical norm).
    But my point was that EEPROM code that worked on ES2 probably will not work on ES3. And my latest look at EEPROM example projects (only 1 available) does not include the Start. Cypress should be more explicit when changing what is needed for operation when they make a significant change; and expand the cystatus to be more helpful to tell what is the true problem when any change obsoletes old workable code with new requirements. And test and update where required when a change effects an example project. 
    sequoiacpe

你好，
在PSoC创建者2组件包3中，我看到示例项目清楚地提到EEPROM启动是针对PSoC3 ES3或更高版本，并且EEPROMYSTATE（）API被称为“CythPoS3O.ES3”定义。你是指其他PSoC Creator版本/构建？请注意，PSOC3 ES2设备支持已从PSoC Creator 2.1移除，因为PSoC3 ES3是生产质量的硅。我建议你移动到PSoC3 ES3硅。
我同意大多数API的地位并没有明确指出失败的原因。我会尽力把你的关心传达给合适的团队。谢谢你的建议。
问候，Aniruddha



     以下为原文
  Hi,
         In PSoC Creator  2.0 Component Pack 3, I see that the example project clearly mentions that EEPROM start is for PSOC3 ES3 or later and also EEPROM_Start() API is called guarded by 'CY_PSOC3_ES3' define. Are you referring to some other PSoC Creator version/ build? Please note that PSoC3 ES2 device support has been removed from PSoC Creator 2.1 as PSoC3 ES3 is the production quality silicon. I suggest you to move to PSoC3 ES3 silicon.
         I agree that the status for most of the APIs does not clearly mention the reason for failure. I will try to convey your concern to the appropriate team. Thanks for your suggestion.
     
    Regards, Aniruddha