- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
HI All,
iam looking at the document of avalan mm slave interface specification.i am interested in interface level protocol with timings with respect to clock. i have attached the timing diagram of read followed by write using wait_request here that i took from the document. i am seeing once read got deasserted there is one clock cycle delay for the next write to be asserted. i would like to know if read deassertion and write assertion can happen at the same clock edge? in my case i see when read signal deassertion and write signal assertion ,if happens at the same clock edge,the slave code is getting stuck. However the code works fine if i add some delay between two transactions., Regards, Jagadish- Tags:
- avalon
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The diagram is drawn with an extra clock cycle between the read and the write for clarity only.
If the slave design is yours, you will have to correct it. You should at least be able to accept back-to-back writes or reads, going from read to write or vice versa without that extra clock cycle shouldn't pose a problem either.- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
--- Quote Start --- The diagram is drawn with an extra clock cycle between the read and the write for clarity only. If the slave design is yours, you will have to correct it. You should at least be able to accept back-to-back writes or reads, going from read to write or vice versa without that extra clock cycle shouldn't pose a problem either. --- Quote End --- Thanks for the suggestion.Josyb. will change my slave code.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page