You are correct about pretty much everything. There is actually quite a lot
of documentation at
https://github.com/m-labs/misoc/blob/master/misoc/interconnect/csr_eventmanager.py

The CSR_CAS_BUTTONS_EV_ENABLE is for which events will trigger the IRQ. To
test you are going to need to register an IRQ handler and then enable
interrupts.

I don't know if anyone has tested interrupts in MicroPython on FPGAs yet.

Tim 'mithro' Ansell

On 9 Aug. 2017 5:35 pm, "Karl Malakoff" <karltheawes...@gmail.com> wrote:

Hi Tim,

Let me know if you find the event manager docs lying around anywhere. I
think I was able to work out a bit of it.

CSR_CAS_BUTTONS_EV_STATUS register is 1 when the button is being pressed
and goes back to 0 on release.

CSR_CAS_BUTTONS_EV_PENDING register starts off at 1 when the board is
started. Writing 1 to any bit sets it back to 0. If the button is pressed
it goes back to 1 and stays at one till it's written to again. I'm not sure
if it should be 1 on boot, I would expect it to be 0 till the button is
pressed for the first time.

I can't work out what CSR_CAS_BUTTONS_EV_ENABLE is for. I can read and
write to it and just keeps whatever value I give it. But the other
registers function the same no matter what value is in this one. I'm
thinking maybe it's for enabling interrupts? Not sure how I could test that
though.

Cheers,
Karl

-- 
You received this message because you are subscribed to the Google Groups
"hdmi2usb - A HDMI capture solution" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to hdmi2usb+unsubscr...@googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"hdmi2usb - A HDMI capture solution" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hdmi2usb+unsubscr...@googlegroups.com.

Reply via email to