Fix: Improved null test to run your c script simulation#792
Open
M-shahid-saeed wants to merge 1 commit into
Open
Fix: Improved null test to run your c script simulation#792M-shahid-saeed wants to merge 1 commit into
M-shahid-saeed wants to merge 1 commit into
Conversation
Contributor
|
Hi @M-shahid-saeed, We're happy to accept this PR once the following changes are made:
Best, |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
While performing C-script simulations for the cl_dram_hbm_dma example, I encountered an issue where the simulation environment was not correctly synchronizing with the software-side execution in test_null.sv.
Since FPGA resources are costly, verifying the C-runtime logic through simulation before hardware deployment is critical. This PR adds specific helper functions/logic to test_null.sv to:
Ensure the C-script triggers the hardware simulation correctly.
Provide better visibility into software-to-hardware handshakes during null tests.
Prevent simulation hangs when running the specific HBM/DRAM DMA software stack.
Verified on the HDK simulation environment.