TF Riser Revision 0 Arrives
Moderators: terriblefire, Terriblefire Moderator
-
- Moderator Team
- Posts: 5389
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: TF Riser Revision 0 Arrives
However looks like the composite device is working ... well done.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
-
- Moderator Team
- Posts: 5389
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: TF Riser Revision 0 Arrives
OK if i was a betting man i'd say the CPLD isnt getting the mouse data at this point.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
- arkadiusz.makarenko
- Moderator Team
- Posts: 1208
- Joined: Wed Jun 19, 2019 7:36 am
- Location: Edinburgh
Re: TF Riser Revision 0 Arrives
terriblefire wrote: ↑Sat Mar 14, 2020 2:33 pm Ok no crashes but the mouse delta types are all screwed up from what i originally posted.
Mouse datacomes from the mouse as an unsigned byte which needs to be cast to a signed byte (128-255) -ve, (0-127) +ive...
this needs to be accumulated in the buffer as a signed 16 bit because you can get multiple mouse events per transmission to the amiga.
You accumulate this in a further layer to emulate joy0dat and joy1dat.
You are sending the raw joy0dat and joy1dats to the CPLD. its dumb and doesnt have the gates to do math.
Ok. That was a bug in casting int16_t to uint8_t.
Now it is returning values in ranges -128-127
But code at this point with populating mouse_delta is just looking at only left mouse button.
I will try to investigate if mouse data is leaving chip at all.
Do not trust people. They are capable of greatness.
~ Stanislaw Lem
~ Stanislaw Lem
-
- Moderator Team
- Posts: 5389
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: TF Riser Revision 0 Arrives
The CPLD is definitely not getting data for the mouse
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
- arkadiusz.makarenko
- Moderator Team
- Posts: 1208
- Joined: Wed Jun 19, 2019 7:36 am
- Location: Edinburgh
Re: TF Riser Revision 0 Arrives
I can see that we do use SPI mouse and Keboard data as driven manually by writing directly using GPIO.
Maybe it is messing some registers at some point which are required for SPI?
Do not trust people. They are capable of greatness.
~ Stanislaw Lem
~ Stanislaw Lem
-
- Moderator Team
- Posts: 5389
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: TF Riser Revision 0 Arrives
Erm it’s a bit of a kludge at the moment. I think using the keyboard method to transmit the mouse data is maybe the way forward. I’ll sort this bit out.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
- arkadiusz.makarenko
- Moderator Team
- Posts: 1208
- Joined: Wed Jun 19, 2019 7:36 am
- Location: Edinburgh
Re: TF Riser Revision 0 Arrives
I pushed bugfix re mouse readings to my repository. It is just change to two lines of code.terriblefire wrote: ↑Sun Mar 15, 2020 11:54 am Erm it’s a bit of a kludge at the moment. I think using the keyboard method to transmit the mouse data is maybe the way forward. I’ll sort this bit out.
I will try to extend gamepad support then. At this moment it works only for standard HID PC gamepads. Will try extend it to Xbox360, ps2/3/4 gamepad as well, as they are most common (I think)
I will skip hub support for now, I dont think we have enough ram for this on f105.
Do not trust people. They are capable of greatness.
~ Stanislaw Lem
~ Stanislaw Lem
-
- Moderator Team
- Posts: 5389
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: TF Riser Revision 0 Arrives
Tbh I’m going to swap my ARM for a bigger chip and make some changes to how keyboard works.
I think i have enough info to make a rev1 now
I think i have enough info to make a rev1 now
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
- arkadiusz.makarenko
- Moderator Team
- Posts: 1208
- Joined: Wed Jun 19, 2019 7:36 am
- Location: Edinburgh
Re: TF Riser Revision 0 Arrives
Which chip do you have in mind?terriblefire wrote: ↑Sun Mar 15, 2020 1:38 pm Tbh I’m going to swap my ARM for a bigger chip and make some changes to how keyboard works.
I think i have enough info to make a rev1 now
Do not trust people. They are capable of greatness.
~ Stanislaw Lem
~ Stanislaw Lem
-
- Moderator Team
- Posts: 5389
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: TF Riser Revision 0 Arrives
The 4xx dual USB one you’ve been using
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."