Skip to content

rd_enable latching (or lack of it) #3

@feldi12

Description

@feldi12

Hi!
I was going through your code and I noticed, that if the controller is in any of the "REF" states, the busy signal is low. However, when rd_enable signal goes high, the address of read operation will be read and latched, but the rd_enable itself will not start read, as this can only start if the controller is in "IDLE" state. This forces user to leave the address and rd_enable signals high until busy signal goes high, which makes code further on much more complicated.

  1. Am I reading it right, or have I missed something?
  2. How about latching the rd/wr commands, and supplementing busy signal logic? I think that would solve the problem...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions