Skip to content
GitLab
Explore
Sign in
Register
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
43bc9819
"SAS/TMSS/backend/test/t_tmssapp_scheduling_REST_API.py" did not exist on "24fe76aa76bb328460c2f5ff3e5a5a6f254bb7b4"
Commit
43bc9819
authored
2 years ago
by
Eric Kooistra
Browse files
Options
Downloads
Patches
Plain Diff
Only verify Rx latency for larger block len.
parent
a0954793
Branches
Branches containing commit
No related tags found
1 merge request
!288
Resolve L2SDP-836
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
libraries/io/eth/tb/vhdl/tb_eth_tester.vhd
+26
-16
26 additions, 16 deletions
libraries/io/eth/tb/vhdl/tb_eth_tester.vhd
with
26 additions
and
16 deletions
libraries/io/eth/tb/vhdl/tb_eth_tester.vhd
+
26
−
16
View file @
43bc9819
...
...
@@ -92,9 +92,11 @@ ARCHITECTURE tb OF tb_eth_tester IS
CONSTANT
c_bg_block_len_first
:
NATURAL
:
=
g_bg_ctrl_first
.
samples_per_packet
;
CONSTANT
c_bg_block_len_others
:
NATURAL
:
=
g_bg_ctrl_others
.
samples_per_packet
;
CONSTANT
c_bg_block_len_max
:
NATURAL
:
=
largest
(
c_bg_block_len_first
,
c_bg_block_len_others
);
CONSTANT
c_bg_slot_len_first
:
NATURAL
:
=
c_bg_block_len_first
+
g_bg_ctrl_first
.
gapsize
;
CONSTANT
c_bg_slot_len_others
:
NATURAL
:
=
c_bg_block_len_others
+
g_bg_ctrl_others
.
gapsize
;
CONSTANT
c_bg_slot_len_max
:
NATURAL
:
=
largest
(
c_bg_slot_len_first
,
c_bg_slot_len_others
);
CONSTANT
c_eth_packet_len_first
:
NATURAL
:
=
func_eth_tester_eth_packet_length
(
c_bg_block_len_first
);
CONSTANT
c_eth_packet_len_others
:
NATURAL
:
=
func_eth_tester_eth_packet_length
(
c_bg_block_len_others
);
...
...
@@ -114,6 +116,7 @@ ARCHITECTURE tb OF tb_eth_tester IS
-- Expected Tx --> Rx latency values obtained from a tb run
CONSTANT
c_tx_exp_latency
:
NATURAL
:
=
0
;
CONSTANT
c_rx_exp_latency_en
:
BOOLEAN
:
=
c_bg_block_len_max
>=
50
;
CONSTANT
c_rx_exp_latency_st
:
NATURAL
:
=
27
;
CONSTANT
c_rx_exp_latency_sim_tse
:
NATURAL
:
=
165
;
CONSTANT
c_rx_exp_latency_tech_tse
:
NATURAL
:
=
375
;
...
...
@@ -482,10 +485,16 @@ BEGIN
ASSERT
rx_mon_nof_valid_arr
(
I
)
=
c_mon_nof_valid_others_rx
REPORT
c_tb_str
&
"Wrong rx nof_valid for stream ("
&
NATURAL
'IMAGE
(
I
)
&
")"
SEVERITY
ERROR
;
END
IF
;
ASSERT
tx_mon_latency_arr
(
I
)
=
c_tx_exp_latency
REPORT
c_tb_str
&
"Wrong tx latency for stream ("
&
NATURAL
'IMAGE
(
I
)
&
")"
SEVERITY
ERROR
;
-- For short block lengths the Rx latency appears to become less, the
-- exact Rx latency is therefore hard to predetermine. The actual
-- latency is not critical, therefore it is sufficient to only very
-- the latency when it is more or less fixed.
IF
c_rx_exp_latency_en
THEN
-- The rx_exp_latency is fixed when:
-- . g_loopback_eth = FALSE: the streams operate in parallel.
-- . g_loopback_eth = TRUE and g_nof_streams = 1, because for
-- g_nof_streams > 1 the streams are mul
i
tplexed, so then the Rx
-- g_nof_streams > 1 the streams are mult
i
plexed, so then the Rx
-- latency will vary.
IF
g_loopback_eth
=
TRUE
THEN
IF
g_nof_streams
=
1
THEN
...
...
@@ -502,6 +511,7 @@ BEGIN
c_tb_str
&
"Wrong rx latency using st interface ("
&
NATURAL
'IMAGE
(
I
)
&
")"
SEVERITY
ERROR
;
END
IF
;
END
IF
;
END
IF
;
END
LOOP
;
-------------------------------------------------------------------------
...
...
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