嗨，Maged，
RWI是内部抑制。它不是由我们控制的。在RWI期间，W/PIN或任何其他控制引脚的状态没有相关性。因此，在RWI期间，数据不能以任何方式被破坏。只有在RWI结束时，我们的情况才是重要的。因此，我们建议在W/Win上进行拉拔，以确保在启用RWI之后（控制器仍在启动）不需要写入。
谢谢
拉维
注意：为了说明显而易见的情况，只有当NVSRAM已经完成启动时，控制器IO处于三态，即在结束时结束，而不是处于低状态时，拔出才有帮助。此外，您可以看到，而不是我们/您可以确保CE/IS高，这将有相同的效果，因为任何意外的写作只能发生在CE//和我们/看到在引脚低的条件。
以上来自于百度翻译
以下为原文
Hi Maged,
RWI is an internal inhibit. It is not controlled by WE/. During RWI, condition of WE/ pin or any other control pin has no relevance. And hence, data cannot be corrupted by any means during RWI. Only at the end of the RWI, the WE/ condition will matter. Therefore, we suggest a pull up on WE/ pin to ensure that unwanted writes do not happen
after RWI is enabled (and the controller is still booting up).
Thanks
Ravi
Note: To state the obvious, the pull up helps only if the controller IO is in tristate when nvSRAM has completed boot up - at end of tHRECALL - and not if it is in LOW state. Also, you can see that instead of WE/ you can ensure CE/ is HIGH which would have the same effect since any unintended write can happen only if
both CE/ and WE/ see a LOW condition at the pins.
嗨，Maged，
RWI是内部抑制。它不是由我们控制的。在RWI期间，W/PIN或任何其他控制引脚的状态没有相关性。因此，在RWI期间，数据不能以任何方式被破坏。只有在RWI结束时，我们的情况才是重要的。因此，我们建议在W/Win上进行拉拔，以确保在启用RWI之后（控制器仍在启动）不需要写入。
谢谢
拉维
注意：为了说明显而易见的情况，只有当NVSRAM已经完成启动时，控制器IO处于三态，即在结束时结束，而不是处于低状态时，拔出才有帮助。此外，您可以看到，而不是我们/您可以确保CE/IS高，这将有相同的效果，因为任何意外的写作只能发生在CE//和我们/看到在引脚低的条件。
以上来自于百度翻译
以下为原文
Hi Maged,
RWI is an internal inhibit. It is not controlled by WE/. During RWI, condition of WE/ pin or any other control pin has no relevance. And hence, data cannot be corrupted by any means during RWI. Only at the end of the RWI, the WE/ condition will matter. Therefore, we suggest a pull up on WE/ pin to ensure that unwanted writes do not happen
after RWI is enabled (and the controller is still booting up).
Thanks
Ravi
Note: To state the obvious, the pull up helps only if the controller IO is in tristate when nvSRAM has completed boot up - at end of tHRECALL - and not if it is in LOW state. Also, you can see that instead of WE/ you can ensure CE/ is HIGH which would have the same effect since any unintended write can happen only if
both CE/ and WE/ see a LOW condition at the pins.
举报
