完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
我有一个使用PIC18F2550的USB CDC设备,它已经在XP、Win7和Win8.x上工作,但是在我的Win10笔记本电脑上,它枚举和安装OK,但是当它开始作为COMx端口通信时,软件失败。当Win8平板电脑升级到Win10时,同样的问题也出现了。有时当它被连接时,它会随机断开并重新连接。使用设备管理器,我看到它安装在端口0001和集线器0003上。事件日志显示:“设备USBVID04D8&PID_FDCFEti20090414需要进一步安装”,但是,事件查看器显示:“驱动程序管理结束了安装驱动程序eti-bsa.inf_inf_amd64_d223b509628e08feti-btsa3.inf for Device Instance ID USBVID_04D8&PID_FDCFETI20090414;ETI200414wi的过程。”根据我的搜索,我发现了其他关于这个问题的参考资料,结论是没有问题的。我怀疑当通信开始时,问题可能是对过电流的敏感性,但是设备描述符请求完整的500mA,而设备实际上只画出350妈妈。我可能会尝试使用动力集线器,看看它是否工作得更好。实际上,我检查了软件的调试文件,它显示它从COM端口发送了字符,但是在大约1秒的超时时间内没有收到回复。该设备由一个USB CDC部分组成,它连接到同一板上一个单独的数据采集部分,用Si8241数字隔离器隔离,系统工作在57600波特。谢谢!
以上来自于百度翻译 以下为原文 I have a USB CDC device using a PIC18F2550 that has been working on XP, Win7, and Win8.x, but on my Win10 laptop, it enumerates and installs OK, but when it begins communication as a COMx port, the software fails. The same problem occurred on a Win8 tablet when it was upgraded to Win10. Sometimes while it is attached it will disconnect and reconnect at random. Using the Device Manager, I see that it is installed on Port#0001 and Hub#0003. The events log reads: "Device USBVID04D8&PID_FDCFETI20090414 requires further installation" However, the event viewer shows: "Driver Management concluded the process to install driver eti-bsa.inf_amd64_6d223b509628e08feti-btsa3.inf for Device Instance ID USBVID_04D8&PID_FDCFETI20090414 with the following stateu: 0x0" From my searches I found other references to this that concluded it was not a problem. I suspect that the problem could be sensitivity to overcurrent when the communication starts, but the device descriptors request the full 500 mA and the device actually draws only 350 mA. I may try a powered hub to see if that works better. Actually, I checked my software's debug file and it shows that it sent characters out of the COM port but did not receive a reply within a timeout period of about 1 second. The device consists of a USB CDC section which connects to a separate data acquisition section on the same board, isolated with an Si8241 digital isolator, and the system operates at 57600 baud. Any ideas would be much appreciated. Thanks! |
|
相关推荐
1个回答
|
|
要了解更多信息,我发现我的驱动程序文件(ETI-BTSA3.inf)是基于DriverVer=11/15/2007,5.1.2600.0中提供的早期版本的。我安装了最新的框架从2016年4月和示例驱动程序是非常不同的。我根据需要修改了它,但现在在抱怨:“文件的散列不存在于指定的目录文件中。文件可能已损坏或被篡改“我在Win8机器上重新安装驱动程序也有一些问题,所以我可能需要通过严格的角色来允许无签名的驱动程序安装。
以上来自于百度翻译 以下为原文 For a bit more information, I found that my driver file (ETI-BTSA3.inf) was based on an earlier version supplied in DriverVer=11/15/2007,5.1.2600.0. I installed the latest framework from April 2016 and the example driver is much different. I modified it as needed, but it is now complaining that: "The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering" I'm also having some problems re-installing the driver on my Win8 machine, so I may need to go through the rigamarole to allow unsigned driver installation. |
|
|
|
只有小组成员才能发言,加入小组>>
5163 浏览 9 评论
2000 浏览 8 评论
1928 浏览 10 评论
请问是否能把一个ADC值转换成两个字节用来设置PWM占空比?
3174 浏览 3 评论
请问电源和晶体值之间有什么关系吗?PIC在正常条件下运行4MHz需要多少电压?
2226 浏览 5 评论
733浏览 1评论
615浏览 1评论
有偿咨询,关于MPLAB X IPE烧录PIC32MX所遇到的问题
505浏览 1评论
PIC Kit3出现目标设备ID(00000000)与预期的设备ID(02c20000)不匹配。是什么原因
631浏览 0评论
528浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-11-23 21:04 , Processed in 0.996144 second(s), Total 46, Slave 40 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号