exxos's Atari, Amiga & retro forum

terriblefire wrote: 26 Apr 2020 22:27

arkadiusz.makarenko wrote: 26 Apr 2020 20:31 @terriblefire

I need to rewrite USB library, differences are quite substantial between devices, just copying bits didn't work.

I don't want to slow you down, if you can work on stock library then great, just create project with FS and HS HID USB, and I will replace library when it is ready. It may take me a little more time as expected.

Ok i'll get the basic amiga.c / amiga.h setup with a stock library and you can hack away after you're done rewriting.

One thing I did notice is that one of the USB ports turned on my usual mouse and one didnt. I presume this is part of the issue.

If it was HS Then you need to comment one line related to ULPI clock enable. I will send yout exact line of code tomorrow.

arkadiusz.makarenko wrote: 26 Apr 2020 23:16

terriblefire wrote: 26 Apr 2020 22:27

Ok i'll get the basic amiga.c / amiga.h setup with a stock library and you can hack away after you're done rewriting.

One thing I did notice is that one of the USB ports turned on my usual mouse and one didnt. I presume this is part of the issue.

If it was HS Then you need to comment one line related to ULPI clock enable. I will send yout exact line of code tomorrow.

Honestly for right here and now i'll just use one USB port and let you extend it later.

Progress at last!
I love Meld, it saved be days.

I managed to get two devices with multiple interfaces registered. And I tested receiving data from one device from multiple interfaces.

Need to test if data is correctly received from devices, and complete middleware bit to get one point of access to different types of devices

Great work.

Arek, one question,
is RTC already working?

8 Bit Dreams wrote: 28 Apr 2020 10:28 Arek, one question,
is RTC already working?

No nothing is working yet.. It doesnt talk to the amiga yet.

EDIT: Arek is focussing on the USB stack and middleware.

8 Bit Dreams wrote: 28 Apr 2020 10:28 Arek, one question,
is RTC already working?

It is not on my to do list yet. I need to learn anything about power modes for this chip first

At this point I am battling with report parser for mouse on interface 1. Build in mouse report parser doesn't work (I assume it does only for mouse in boot mode), and my own parser doesn't read report size correctly.
It may be issue with one step before - reading hid descriptors for interface different than interface 0.
Build in functions can read them only for default interface -0, maybe I missed something when I was porting code to f722. This would cause that hid report descriptor for keyboard would be parsed as mouse report descriptor.

arkadiusz.makarenko wrote: 29 Apr 2020 00:42 It is not on my to do list yet. I need to learn anything about power modes for this chip first

At this point I am battling with report parser for mouse on interface 1. Build in mouse report parser doesn't work (I assume it does only for mouse in boot mode), and my own parser doesn't read report size correctly.
It may be issue with one step before - reading hid descriptors for interface different than interface 0.
Build in functions can read them only for default interface -0, maybe I missed something when I was porting code to f722. This would cause that hid report descriptor for keyboard would be parsed as mouse report descriptor.

You'll get there :) or else ;)

Mwahahahahaha :) ok lockdown is starting to affect me...

terriblefire wrote: 29 Apr 2020 00:49

arkadiusz.makarenko wrote: 29 Apr 2020 00:42 It is not on my to do list yet. I need to learn anything about power modes for this chip first

At this point I am battling with report parser for mouse on interface 1. Build in mouse report parser doesn't work (I assume it does only for mouse in boot mode), and my own parser doesn't read report size correctly.
It may be issue with one step before - reading hid descriptors for interface different than interface 0.
Build in functions can read them only for default interface -0, maybe I missed something when I was porting code to f722. This would cause that hid report descriptor for keyboard would be parsed as mouse report descriptor.

You'll get there :) or else ;)

Mwahahahahaha :) ok lockdown is starting to affect me...

Got it.
It was messed new ST HID Parser, I reverted to old library version, updated few bits and now it works.
https://github.com/arkadiuszmakarenko/TFRiserRev1F722

arkadiusz.makarenko wrote: 29 Apr 2020 09:22 Got it.
It was messed new ST HID Parser, I reverted to old library version, updated few bits and now it works.
https://github.com/arkadiuszmakarenko/TFRiserRev1F722

Excellent work.