Skip to content

Latest commit

 

History

History
34 lines (22 loc) · 2.38 KB

README.md

File metadata and controls

34 lines (22 loc) · 2.38 KB
Raw

WSHWTest V0.1.0 (20240404)

Hardware test suite for WonderSwan These descriptions are my interpretation of what is happening, that doesn't mean this is actualy what is happening, I'm open to pull requests for both code and interpretations of how things work.

Start Registers

On all boot roms in all modes: SP is set to 0x2000. PS/CS is set to 0xF000. DS0/DS is set to boot rom base (0xFF00 for ASWAN and 0xFE00 for SPHINX/SPHINX2).

Interrupts

It's important to make distinction between the actual CPU part and the interrupt manager/handler. Even though they are part of the same physical chip in the WonderSwan they are logicaly different parts. The interrupt manager can set the interrupt pin high or low on the CPU and then it can supply an interrupt vector on the low 8 bits of the databus when the cpu request it (when it wants to take an interrupt).

The interrupt manager latches all enabled incoming interrupt requests until they are acknowledged with a write to port 0xB6, the interrupt requests are not cleared by disabling them through 0xB2. The 2 Timer interrupts, VBlank and Line Compare interrupts are just pulsed (don't know for how many cycles) but they are latched (remembered) until they are acknowledged. The serial, key & cartridge interrupts are latched as well but they can't be acknowledged as long as they are enabled and held high by the corresponding device.

All interrupts that are latched and visible in 0xB4 also cause interrupts if/when the cpu is able to accept them.

The interrupt pin on the cpu is enabled as long as there are bits set in 0xB4, the interrupt manager allways sends the vector for the top enabled interrupt.

Timers

The timer logic is a bit backwards, the on/off bit is used to write back the downcounted value, the downcount always happens, this means that if the timer is off and the counter value is 1 an interrupt will happen but zero is not written back to the counter so it's basicly the same as timer on with repeat. Writing to the timer values instantly updates the counter value. Toggling the Timer on/off doesn't reload the counter value, it just pauses / resumes the counter.

So what happens is:

  1. Check if counter is zero, if so stop doing anything more.
  2. Count down counter, if it's now zero tell the interrupt manager.
  3. If counted down value was zero, check repeat bit and fetch timer value.
  4. Is Timer on? Write back downcounted/timer value to counter.