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.

[AHB] What signal of AHB-Lite might be connected to FIFO's EMPTY output?

Status
Not open for further replies.

ivlsi

Advanced Member level 3
Advanced Member level 3
Joined
Feb 17, 2012
Messages
883
Helped
17
Reputation
32
Reaction score
16
Trophy points
1,298
Activity points
6,868
[AHB] What signal of AHB-Lite should be connected to FIFO's EMPTY output?

Hi All,

I need to connect a regular Sync FIFO as a Slave on AHB-Lite bus.

Where should I connect FIFO's EMPTY signal? It seems connecting it to ~HREADY signal is a bad idea...

Thank you!
 
Last edited:

Yep, it's a bad idea, because you can lock the bus up for an arbitrary time. Probably should have a status register that can be read to see if the FIFO contains data.
 
  • Like
Reactions: ivlsi

    ivlsi

    Points: 2
    Helpful Answer Positive Rating
What about connection the FIFO EMPTY signal to HRESP or HSPLIT? Probably connecting to HSPLIT is better...
 

There's no hsplit in AHB-lite.
 
  • Like
Reactions: ivlsi

    ivlsi

    Points: 2
    Helpful Answer Positive Rating
Okay, in case it's a Full AHB bus, could then the FIFO EMPTY be connected to HSPLIT? Is there a better connection for this signal?
 

You can create another AHB address for empty signal polling. So FIFO data write uses one AHB address(Or maybe a serial of addresses), polling EMPTY signal uses another AHB address.
 
  • Like
Reactions: ivlsi

    ivlsi

    Points: 2
    Helpful Answer Positive Rating
I see, but "polling" is not a part of AHB protocol...
So, should status of the EMPTY signal be read each time before reading a value from FIFO? It seems it would reduce by twice the bandwidth of FIFO in term of Reads... I mean, in order to read 4 values from FIFO, should 8 Read Accesses be performed (ReadEmptyStatus->ReadFIFOValue->ReadEmptyStatus->ReadFIFOValue->...)?
 

Possibly. You need to consider what is important given your application. Is the FIFO slow relative to whatever is reading it (i.e. slow UART FIFO + fast CPU)? If so, it probably doesn't matter. If the data rate is high, then perhaps it does matter. Perhaps a count register would be better than an single empty flag. If the rate is very fast, i.e. only likely to be a cycle or two delay, then you could just drive hready. Alternatively, depending upon the width of the FIFO data and bus, you could combine the empty flag and fifo data.
 
  • Like
Reactions: ivlsi

    ivlsi

    Points: 2
    Helpful Answer Positive Rating
Connection of FIFO FULL signal to HREADY would be okay? Will it not stuck the bus? The HREADY is equal to WAIT, so the bus will be stuck until at least one value from FIFO be read...
 

Yes, it would lock up the bus. If you know that the FIFO is likely to have data in a cycle or two, maybe that is OK. If you don't, then it's probably not a good idea.
 

    V

    Points: 2
    Helpful Answer Positive Rating
So, how to handle FIFO FULL signal from a Slave on AHB bus?
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top