- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
RdFIFO_Emp ty signal of NPI interface is always high
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
09-26-2011 10:00 AM
Hi,
I implement an NPI initiator to read image data from system memory(DRAM).
The DRAM controller is Xilinx MPMC and the buffer type is BRAM.
I ensure and follow the restriction about NPI interface namely
<1>address requests are no more than 4
<2>request data amount without any poping is less than 1024-byte
<3>request address is aligned to the request size
The first 4 requests are read back successfully. After that, RdFIFO_Empty signal of NPI interface is always high, this leads my overall transmission is hanging there.
Are there any possible reasons making that RdFIFO_Empty signal is always high?
Thanks.
Re: RdFIFO_Emp ty signal of NPI interface is always high
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
09-27-2011 08:47 PM
I did a series of experiments and I found that if my first request address is 4-word alignment, entire transmission (640x480 image) can be done without hanging again.
I check .mhs file, the data width is 32-bit. From MPMC data sheet, it has different meaning when transfer size is 0 (word for 32-bit NPI and double-word for 64-bit NPI). Word transfer size is what I want. Why my transmission will hang on if data size is already 32-bit?
If any suggestions, I would be thankful.
Re: RdFIFO_Emp ty signal of NPI interface is always high
[ Edited ]
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
09-28-2011 03:43 AM - edited 09-28-2011 03:44 AM
When you load your address and receive the address ack, a time period later the read FIFO empty signal wil go low. At this point you can read data, but you must stop reading data when you have either exhausted your transfer length or the signal is high.
Once you have exhausted your transfer length you need to issue another address request for the next block of data. Typically the request lengths are 32 dwords.
From your explanation it does not look like you are issuing more than 1 address request.
Cheers,
Re: RdFIFO_Emp ty signal of NPI interface is always high
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
10-08-2011 03:30 AM
Hi,
Thanks for your replying.
Actually I use more aggressive strategy. I use a command FIFO to throttle the outstanding request. The command FIFO is 4 entries.
If I want ROI in 640x480 size image, VFBC interface will let my ROI setting become less flexibility due to its’ 128-byte alignment limitation. That’s the reason why I use NPI.
However, start address of ROI setting may not be 32-word alignment; it could be word-alignment (If the ROI width is limited at multiple of 4) so that word size transfer is needed.
Afterward I decrease my command FIFO entry from 4-entry to 3-entry or 2-entry, the entire transfer will go smoothly.











