Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Expose sending commands to noc1 and noc0 #526

Open
tt-vjovanovic opened this issue Feb 18, 2025 · 3 comments
Open

Expose sending commands to noc1 and noc0 #526

tt-vjovanovic opened this issue Feb 18, 2025 · 3 comments

Comments

@tt-vjovanovic
Copy link
Member

When noc0 hangs, we would like to use noc1 to access chip.
@ihamer-tt
Copy link

ihamer-tt commented Feb 18, 2025 •
edited
Loading

@tt-vjovanovic, This will also require tt-lens support to select noc 1. Is this ready?

@broskoTT, as this feature is used for debugging a P0 (possibly HW-based) issue, and we need to look at it asap.

@pgkeller
Copy link

We've decided that this is the best way forward on the P0 HW bug, if a hacked solution will work in the short term we'd use that ASAP. Thanks.

@tt-vjovanovic
Copy link
Member Author

Hacked solution with this PR: #534

tt-vjovanovic added a commit that referenced this issue Feb 24, 2025
@tt-vjovanovic
Simple hack for #526 until it is properly fixed (#534)
c59c9d0 
Exposing global variable for using noc1 in tlb.
Disabling coordinate translation when setting up tlb for noc1.

Note: this is bad implementation since required coordinates for
communication with UMD are virtual which get converted into physical,
but in tt-lens we are converting noc1 into virtual as if it is noc0, UMD
reverses this so on device ends up noc1 coordinate...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pgkeller @ihamer-tt @tt-vjovanovic