Page 5 of 11

Re: TF CD32 Riser Revision 2 Build Guide.

Posted: 21 Feb 2021 13:09
by arkadiusz.makarenko
I have ordered few problematic devices and I will do my best to answer why they don't work over week or so.
It may be silly bug which stops enumeration some devices. Surpassingly cheaper devices work better for some reason.

Re: TF CD32 Riser Revision 2 Build Guide.

Posted: 21 Feb 2021 19:50
by alenppc
I tried an ancient IBM MO32UO USB mouse and this one has the same issues as the Rapoo (phantom clicks and occasional random jumps). Just to exclude that I messed something up while building it, I built a second riser and I get the same behaviour on both. Unless I screwed up both of them...

All the logitech mice I mentioned above are of the same type, with a little bluetooth dongle so I suspect they probably use the same protocol.

EDIT: it looks like this depends on which accelerator you have plugged into the riser. All of what I reported happens when the TF330 is plugged in. When I tried it with the TF328, the phantom clicks and jumps were gone BUT the mouse will only move vertically and not horizontally.

Re: TF CD32 Riser Revision 2 Build Guide.

Posted: 21 Feb 2021 20:02
by arkadiusz.makarenko
alenppc wrote: 21 Feb 2021 19:50 I tried an ancient IBM MO32UO USB mouse and this one has the same issues as the Rapoo (phantom clicks and occasional random jumps). Just to exclude that I messed something up while building it, I built a second riser and I get the same behaviour on both. Unless I screwed up both of them...

All the logitech mice I mentioned above are of the same type, with a little bluetooth dongle so I suspect they probably use the same protocol.

EDIT: it looks like this depends on which accelerator you have plugged into the riser. All of what I reported happens with the TF330 is plugged in. When I tried it with the TF328, the phantom clicks and jumps were gone BUT the mouse will only move vertically and not horizontally.
I have digged out Logitech Canada210 ,and movements work ok, but clicks are not decoded. I will have a look why this happens.

Re: TF CD32 Riser Revision 2 Build Guide.

Posted: 21 Feb 2021 20:04
by alenppc
The same behaviour that occurs with TF328 occurs also when there is no accelerator plugged in. I am going to try it with the TF360.

Re: TF CD32 Riser Revision 2 Build Guide.

Posted: 21 Feb 2021 20:08
by alenppc
This is so wild. On the TF360 there are no phantom clicks and jumps. Let me know if you need a TF330 for testing, I can send you one. I don't have any more 328s though.

Re: TF CD32 Riser Revision 2 Build Guide.

Posted: 21 Feb 2021 20:28
by terriblefire
Pretty sure Arek has a TF330... if not i'll get him one asap.

Re: TF CD32 Riser Revision 2 Build Guide.

Posted: 21 Feb 2021 20:43
by arkadiusz.makarenko
I have TF330, and all testing was done on it.

EDIT
I think it may be my optimizations. I did optimized each possible cycle. I think I may release CPU tiny little bit too early and some CPUs glitch?

Re: TF CD32 Riser Revision 2 Build Guide.

Posted: 21 Feb 2021 21:10
by alenppc
arkadiusz.makarenko wrote: 21 Feb 2021 20:43 I have TF330, and all testing was done on it.

EDIT
I think it may be my optimizations. I did optimized each possible cycle. I think I may release CPU tiny little bit too early and some CPUs glitch?
If you can send me the fw before optimizations, I can try and report back.

Re: TF CD32 Riser Revision 2 Build Guide.

Posted: 21 Feb 2021 21:17
by arkadiusz.makarenko
alenppc wrote: 21 Feb 2021 21:10
arkadiusz.makarenko wrote: 21 Feb 2021 20:43 I have TF330, and all testing was done on it.

EDIT
I think it may be my optimizations. I did optimized each possible cycle. I think I may release CPU tiny little bit too early and some CPUs glitch?
If you can send me the fw before optimizations, I can try and report back.
You can have a look at history here: (But I wouldn't know exactly what changes were affected)
https://github.com/arkadiuszmakarenko/T ... r_binaries

Re: TF CD32 Riser Revision 2 Build Guide.

Posted: 21 Feb 2021 21:23
by alenppc
Thanks, will test and report back (probably tomorrow).