Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

the problem of Axi4 Lite BReady does not asserted in the xilinx Vivado.

Status
Not open for further replies.

u24c02

Advanced Member level 1
Joined
May 8, 2012
Messages
404
Helped
2
Reputation
4
Reaction score
2
Trophy points
1,298
Activity points
4,101
Hi.

I'm trying to implement the fifo in the vivado.
the fifo which is based on axi4 lite prtocal.

I just made one maser and interconnect and fifo_generator.

The problem is that I issue the awaddr and wdata and checked awready and wready but Bready does not asserted in the progress.

Does anyone give to me any hint what should I check to do ?

- - - Updated - - -

Sorry BVALID not bready
 

You really ought to read Xilinx document PG057, which describes the AXI4, AXI4-Lite and AXI4-Stream interfaces to the Xilinx FIFOS.

Table 1-8 explains that the BVALID signals are used as EMPTY flags. So if it is not asserting, then you are attempting to read from an empty FIFO.

r.b.
 

You really ought to read Xilinx document PG057, which describes the AXI4, AXI4-Lite and AXI4-Stream interfaces to the Xilinx FIFOS.

Table 1-8 explains that the BVALID signals are used as EMPTY flags. So if it is not asserting, then you are attempting to read from an empty FIFO.

r.b.
Thanks, I'm confused after read the document, then the fifo does not follow axi interface?
 

In AXI4 , VALID and READY signals are used as flow control on each channel, with the provider of data on the channel asserting VALID to let the consumer of data know it has data to send. On a Xilinx FIFO, the EMPTY flag serves the same purpose. It lets the consumer of the data know whether or not there is data to consume.

The document says that the AXI4 interface is a wrapper around the native-interface FIFO. Thus, using the VALID signal as an EMPTY signal makes perfect sense, and follows the spirit, if not the letter, of the AXI4 spec.

Does it follow the AXI4 spec exactly? I don't know. It has been a few years since I used AXI4. But as a designer, as long as I understand what Xilinx is doing, it doesn't really matter. I will design the interfacing circuitry to work with Xilinx's interpretation of the AXI4 spec. If I am using legacy AXI4 IP, i will design glue logic to make it work.

Why do you think it does not follow the spec?

r.b.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top