You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run SUME simulations ./tools/scripts/nf_test.py sim --major switch --minor default, I get the following error:
Reconciliation of nf_interface_1_log.axi with nf_interface_1_expected.axi
FAIL (1 packets expected, 0 packets received)
Reconciliation of nf_interface_0_log.axi with nf_interface_0_expected.axi
PASS (0 packets expected, 0 packets received)
Reconciliation of nf_interface_2_log.axi with nf_interface_2_expected.axi
PASS (0 packets expected, 0 packets received)
Reconciliation of dma_0_log.axi with dma_0_expected.axi
PASS (0 packets expected, 0 packets received)
Reconciliation of nf_interface_3_log.axi with nf_interface_3_expected.axi
PASS (0 packets expected, 0 packets received)
Makefile:120: recipe for target 'sim' failed
vivado.bash simulation check passes all test cases, but I get an error at the SUME SIMULATION stage.
I noticed that this failure occurs in all my P4 programs when I reach a given number of table entries in commands.txt file.
For example, for a program with the following two match-action tables, I am only able to have 5 entries per table.
If I add a single more entry then the above error comes up.
When I run SUME simulations
./tools/scripts/nf_test.py sim --major switch --minor default
, I get the following error:vivado.bash
simulation check passes all test cases, but I get an error at the SUME SIMULATION stage.I noticed that this failure occurs in all my P4 programs when I reach a given number of table entries in commands.txt file.
For example, for a program with the following two match-action tables, I am only able to have 5 entries per table.
If I add a single more entry then the above error comes up.
Shall I infer from this that NetFPGA SUME won't be able to support more table entries?
Please guide me in this regard.
The text was updated successfully, but these errors were encountered: