在平台构建器中将触摸屏驱动程序添加到 CE 6 后无触摸

发布于 2024-08-21 17:49:09 字数 108 浏览 5 评论 0原文

我已将 TSHARC 触摸屏驱动程序添加到我的 Windows CE 项目中,但触摸不起作用。 dll 就在那里,触摸屏校准可执行文件也在那里。我不知道加载哪些驱动程序以及何时加载。任何指导将不胜感激。

I have added a TSHARC touchscreen driver to my Windows CE project, but the touch does not work. The dll is there, as is the touchscreen calibration executable. I have no visibility into which drivers are loaded and when. Any guidance would be appreciated.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

随风而去 2024-08-28 17:49:09

您必须进行一些调试,并且触摸屏驱动程序往往具有挑战性,因为它们会加载到 GWES 中,并且触摸屏的电气特性会根据尺寸和制造商的不同而发生巨大变化。驱动器很少能开箱即用 - 您几乎总是必须根据面板特性调整采样时序等,最好使用示波器来完成。

要检查的事情:

  1. 驱动程序是否已加载? RETAILMSG/DEBUGMSG 会告诉您“
  2. 您遇到触摸中断了吗?”
  3. 在向下中断之后,您的代码是否返回到接收向上中断的状态?
  4. 如果您查看面板信号本身的时序,您是否在信号稳定时进行采样(即,您在中断后没有采样太快)?

You're going to have to do some debugging, and touchscreen drivers tend to be challenging because they get loaded into GWES and because the electrical characteristics of touchpanels change dramatically based on size and manufacturer. It's very rare for a driver to just work right out of the box - you almost always have to adjust sample timings and the like based on panel characteristics, and that's best done using an oscilloscope.

Things to check:

  1. Is the driver getting loaded at all? A RETAILMSG/DEBUGMSG would tell you that
  2. Are you getting touch interrupts?
  3. After a down interrupt, is your code getting back to state to receive an up?
  4. If you look at the timings from panel signals themselves, are you sampling when the signals are stable (i.e. you're not sampling too soon after the interrupt)?
无畏 2024-08-28 17:49:09

事实证明,这是 OHCI 驱动程序与已安装的另一个 USB 驱动程序之间的冲突。

Turns out it was a conflict between the OHCI driver and another USB driver already installed.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文