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

Mutli-Component Test Fail #334

Open
alyosha-tas opened this issue Oct 28, 2023 · 1 comment
Open

Mutli-Component Test Fail #334

alyosha-tas opened this issue Oct 28, 2023 · 1 comment
Assignees

Comments

@alyosha-tas
Copy link

alyosha-tas commented Oct 28, 2023

I have a new test here that currently doesn't work on NanoboyAdvacnce:

https://github.com/alyosha-tas/gba-tests/blob/master/timer/timer_reset.gba

It's named timer_reset because it is supposed to read from timer one cycle after writing to timer enable. It does this by using DMA 1 to start the timer, then DMA 0 to read the timer. DMA's are started with consecutive writes, so DMA 0 should take over exactly when DMA 1 has finished writing to the timer reg.

NanoboyAdvance currently fails one of the tests, but I can't tell why. Works on GBP though.

@fleroviux fleroviux self-assigned this Nov 2, 2023
@fleroviux
Copy link
Member

Oh, I think this relates to that after enabling the timer it can tick right away but it takes a cycle to load the reload value into the counter. So far I accounted for the case specifically where this would cause a timer overflow, but I didn't handle the case where a counter read would happen right after enabling the timer correctly yet.

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

No branches or pull requests

2 participants