The AES does not react to mouse events on RPI

[kelihlodversson]

After adding usb mouse support, the mouse pointer can now be moved around on screen.
Even though it looks like the correct mouse movement and button handlers are being invoked, the AES does not seem to update the screen based on the mouse events.

[paulwratt]

does it need the "standard" NetUSB mouse bride as well? Because you are using 192K ROMs as base, is it still looking at the Keyboard chip for mouse messages?

[paulwratt]

have u already confirm mouse output from ur code?

I found this in the Das UBoot repo, u-boot/iclude/configs/rpi.h:

#ifdef CONFIG_CMD_USB
#define CONFIG_USB_DWC2
#ifndef CONFIG_BCM2835
#define CONFIG_USB_DWC2_REG_ADDR 0x3f980000
#else
#define CONFIG_USB_DWC2_REG_ADDR 0x20980000
#endif

does that help?

[kelihlodversson]

Yes I define it like this #define USB_DWC2_REG_ADDR (ARM_IO_BASE+0x980000) And ARM_IO_BASE is 0x3f000000 on PI2+3 and 0x20000000 on PI1

…

On Mon, Aug 13, 2018 at 11:29 AM, Paul Wratt ***@***.***> wrote: have u already confirm mouse output from ur code? I found this in the Das UBoot repo, u-boot/iclude/configs/rpi.h: #ifdef CONFIG_CMD_USB #define CONFIG_USB_DWC2 #ifndef CONFIG_BCM2835 #define CONFIG_USB_DWC2_REG_ADDR 0x3f980000 #else #define CONFIG_USB_DWC2_REG_ADDR 0x20980000 #endif does that help? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADT4sS996SxZ9IhRd0KEAuqZZGYkJsQnks5uQUbugaJpZM4VuPNV> .

-- With kind regards, Hrafnkell "Keli" Hloedversson

[kelihlodversson]

... besides this issue is not about the USB implementation. Even with a working mouse pointer, the events are getting lost somewhere in the AES

[kelihlodversson]

Should be fixed in 5a8c574