Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
H
HDL
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Jira
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
RTSD
HDL
Commits
7ef939a8
Commit
7ef939a8
authored
8 years ago
by
Eric Kooistra
Browse files
Options
Downloads
Patches
Plain Diff
Clarified description about that the DSP component has to pass on sop and eop.
parent
2ffb9cb9
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
libraries/base/dp/src/vhdl/dp_fifo_info.vhd
+14
-2
14 additions, 2 deletions
libraries/base/dp/src/vhdl/dp_fifo_info.vhd
with
14 additions
and
2 deletions
libraries/base/dp/src/vhdl/dp_fifo_info.vhd
+
14
−
2
View file @
7ef939a8
...
@@ -32,6 +32,13 @@
...
@@ -32,6 +32,13 @@
-- the data. To save logic and RAM and to not burden the data function with
-- the data. To save logic and RAM and to not burden the data function with
-- the handling of the info this dp_fifo_info can realign the original
-- the handling of the info this dp_fifo_info can realign the original
-- snk_in info with the delayed snk_in data.
-- snk_in info with the delayed snk_in data.
-- The dp_fifo_info uses the info_snk_in.sop and info_snk_in.eop to write
-- the info_snk_in info to the FIFO and it uses the data_snk_in.sop and
-- data_snk_in.eop to read the info from the FIFO. Therefore the DSP
-- component must pass on the snk_in.sop and snk_in.eop, to be able to
-- attach the info_snk_in sop info and eop info again at the output. The
-- g_fifo_size must be sufficient to fit the maximum latency in number of
-- blocks (sop's) that the DSP component can introduce.
--
--
-- Usage:
-- Usage:
-- data_snk_out
-- data_snk_out
...
@@ -39,8 +46,8 @@
...
@@ -39,8 +46,8 @@
-- .
-- .
-- |-----| . |------|
-- |-----| . |------|
-- snk_out <------ | | <------------ | | <---- src_in
-- snk_out <------ | | <------------ | | <---- src_in
-- snk_in ---*--> | DP
| ------------> | dp | ----> src_out
-- snk_in ---*--> | DP
/
| ------------> | dp | ----> src_out
-- | |
| | fifo |
-- | |
DSP
| | fifo |
-- | |-----| | info |
-- | |-----| | info |
-- | info_snk_in | |
-- | info_snk_in | |
-- \------------------------> |------|
-- \------------------------> |------|
...
@@ -51,6 +58,11 @@
...
@@ -51,6 +58,11 @@
-- . The data is passed on unchanged by dp_fifo_info.
-- . The data is passed on unchanged by dp_fifo_info.
-- . The dp_fifo_info preserves the RL=1 but is does delay the data by one
-- . The dp_fifo_info preserves the RL=1 but is does delay the data by one
-- cycle.
-- cycle.
-- . If the DSP component does not pass on the sop and eop, then it can be
-- possible to recreate these at the output based on the valid using e.g.
-- dp_block_gen. This assumes that the DSP does pass on the valid, that the
-- block size is known and that the first valid at the output corresponds
-- to a sop.
LIBRARY
IEEE
,
common_lib
,
technology_lib
;
LIBRARY
IEEE
,
common_lib
,
technology_lib
;
USE
IEEE
.
STD_LOGIC_1164
.
ALL
;
USE
IEEE
.
STD_LOGIC_1164
.
ALL
;
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment