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.

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

python-scripts: step_nv2a.py is buggy #40

Closed
JayFoxRox opened this issue Jul 23, 2017 · 1 comment
Closed

python-scripts: step_nv2a.py is buggy #40

JayFoxRox opened this issue Jul 23, 2017 · 1 comment

Comments

@JayFoxRox
Copy link
Owner

The original concept for this did not work out. This needs further investigation.

The idea was:

  • Pause the puller (= pusher comes to halt as there is no free space)
  • Pause the pusher (= disable CACHE being overwritten)
  • Set pusher address as puller address (= puller has nothing to do)
  • Unpause the puller (= puller still has nothing to do)
  • Set pusher address to new target puller address (= puller runs until pusher address)

Once the fake pusher address reaches the real pusher address (= no more data):

  • Pause the puller (= FIFO is idle now)
  • Assert that pusher address is at real pusher address (= need to continue writing at proper address)
  • Unpause pusher (= let pusher fill CACHE)
  • Pause pusher (= pusher should have advanced / filled CACHE)

Now the initial procedure can be repeated from the second step


The issue, however, is that even with the pusher paused and pusher address = puller address, the entire CACHE seems to be filled with the same method / data pair.
This can also have implications for the general pausing of the NV2A so that should be fixed / cleared up asap!

@JayFoxRox
Copy link
Owner Author

Moved to XboxDev/nv2a-trace

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant