You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
But I just saw that I didn't read the full spec, so indeed (seems I missed the tiny (*) paragraph beneath the table ^^"), I must fix the firmware to send a report with the last sent coordinates and TIP = 0.
Do you know if there's some sort of maximal time-frame I have to send that report in?
The firmware is fixed, I'm still waiting for 24h to pass to see if I didn't introduce some bug (device will be powered continuously during that time and I will check on random basis if it is still responding as expected), but for now it's working okay.
In fact the touch response got better than with the original firmware, so I'm pretty pleased with the result.
Regarding my question, I re-read the spec. and it states that the touch up is expected on the report frame following the last "touch down" state, so I assumed that sending the information in the same time-frame than any other report would fit (that's about a 20ms time frame in my firmware)
I'm glad that someone makes its working with Windows10!
Unfortunatelly i'm not as smart to get rid with compiling whole firmware... i'm just beginner with stm32.
I'm using eclipse on windows and have StLink for programming/debugging.
Can you make and publish /send me already compiled file please (.elf file)?
In the time i'll try to make it compiles in linux cause it's too messy for beginner to edit compiler scripts ;)