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
Ex: Output of uname -a + lsb_release -a + printenv + conda list
Linux chipyard-server 5.15.0-136-generic #147~20.04.1-Ubuntu SMP Wed Mar 19 16:13:14 UTC 2025 x86_64 GNU/Linux
Other Setup
Current Behavior
I leveraged the blackbox feature on Chipyard to customize an ROCC accelerator and crafted a C program for emulation testing. This C program includes a 2 - D array sized at [6][4096].
I used 6 ROCC instructions to transfer the elements in this array, moving one row at a time (meaning one ROCC instruction could transfer 4096 elements). But when I performed the run - binary - debug operation on the compiled program, Chipyard reported the following error.(By the way,the The array type is long long.)
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Error: "/home/worker/code/chipyard-1.13.0/sims/vcs/generated-src/chipyard.harness.TestHarness.RoccExamRocketConfig/gen-collateral/TestHarness.sv", 99: TestDriver.testHarness: at time 767415000 ps
Assertion failed: *** FAILED *** (exit code = 5)
Fatal: "/home/worker/code/chipyard-1.13.0/sims/vcs/generated-src/chipyard.harness.TestHarness.RoccExamRocketConfig/gen-collateral/TestHarness.sv", 101: TestDriver.testHarness: at time 767415000 ps
$finish called from file "/home/worker/code/chipyard-1.13.0/sims/vcs/generated-src/chipyard.harness.TestHarness.RoccExamRocketConfig/gen-collateral/TestHarness.sv", line 101.
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Strangely, the error disappears and data transfer works normally when I reduce the array size to [5][4096] (removing one row of elements) and use 5 ROCC instructions.
I wonder if the issue is due to my .riscv file being too large, as it has reached 233KB. If not, what could be causing this? I hope to get your help.
Expected Behavior
Data transfer with ROCC instructions can function normally even when the array size is [6][4096].
Other Information
No response
The text was updated successfully, but these errors were encountered:
Background Work
Chipyard Version and Hash
Release: 1.13.0
OS Setup
Ex: Output of
uname -a
+lsb_release -a
+printenv
+conda list
Linux chipyard-server 5.15.0-136-generic #147~20.04.1-Ubuntu SMP Wed Mar 19 16:13:14 UTC 2025 x86_64 GNU/Linux
Other Setup
Current Behavior
I leveraged the blackbox feature on Chipyard to customize an ROCC accelerator and crafted a C program for emulation testing. This C program includes a 2 - D array sized at [6][4096].
I used 6 ROCC instructions to transfer the elements in this array, moving one row at a time (meaning one ROCC instruction could transfer 4096 elements). But when I performed the run - binary - debug operation on the compiled program, Chipyard reported the following error.(By the way,the The array type is long long.)
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Error: "/home/worker/code/chipyard-1.13.0/sims/vcs/generated-src/chipyard.harness.TestHarness.RoccExamRocketConfig/gen-collateral/TestHarness.sv", 99: TestDriver.testHarness: at time 767415000 ps
Assertion failed: *** FAILED *** (exit code = 5)
Fatal: "/home/worker/code/chipyard-1.13.0/sims/vcs/generated-src/chipyard.harness.TestHarness.RoccExamRocketConfig/gen-collateral/TestHarness.sv", 101: TestDriver.testHarness: at time 767415000 ps
$finish called from file "/home/worker/code/chipyard-1.13.0/sims/vcs/generated-src/chipyard.harness.TestHarness.RoccExamRocketConfig/gen-collateral/TestHarness.sv", line 101.
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Strangely, the error disappears and data transfer works normally when I reduce the array size to [5][4096] (removing one row of elements) and use 5 ROCC instructions.
I wonder if the issue is due to my .riscv file being too large, as it has reached 233KB. If not, what could be causing this? I hope to get your help.
Expected Behavior
Data transfer with ROCC instructions can function normally even when the array size is [6][4096].
Other Information
No response
The text was updated successfully, but these errors were encountered: