Use ICAP instead of BSCAN for 005-tilegrid/cfg fuzzer because BSCAN parameter depends on location #2537
Conversation
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
hansfbaier
force-pushed
the
005-tilegrid-cfg-fix
branch
from
8bb945b to
e434d2e
Compare
…ANE2 parameter depends on primitive placement Signed-off-by: Hans Baier <[email protected]>
hansfbaier
force-pushed
the
005-tilegrid-cfg-fix
branch
from
e434d2e to
c27c51d
Compare
hansfbaier
force-pushed
the
005-tilegrid-cfg-fix
branch
from
e1db208 to
c27c51d
Compare
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.
BSCAN placement needs to correspond to its JTAG_CHAIN parameter,
so this generates build errors eg for K325T when other chain values than 1 are used.
Fix: Use ICAP instead.