完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
扫一扫,分享给好友
我们使用CyPress USB控制器为我们自己的产品,应该在Windows Vista/7 64位下工作。正如我在这个论坛中发现的,我们需要一个来自Vista的X64操作系统的签名驱动程序。现在我想知道我需要给司机签名的步骤。我想给司机签字,因为(如果我没有错的话)费用不算太高(根据我在这里发现的,证件费99美元)。
我从微软指南中了解内核模式代码签名演练:如何:1)从商业CA(证书AutoMy)中获取软件发布者证书(SPC);2)从驱动文件(.sys)和驱动程序设置信息文件(.INF)创建.CAT文件;3)使用SPC到签署CAT文件,以便能够在Windows Vista/7 64位下使用驱动程序。 安装CyPress USB通用驱动程序(3.4.6),我得到了CySUBSIS和CySUB.IF文件(在C:程序文件 CyPress CyPress套件USB 3.4.6驱动程序 WLH)。这些工作对我们的产品(目前只禁用司机签名执法)。 现在,我觉得错过了一些信息,我需要有自己的签名驱动程序,将与我们的XXX产品,以便一旦我们的产品插入到一台计算机上安装了驱动程序,产品被自动识别为XXX产品。 首先,我想我必须改变USB控制器和CysB.IF的VID和PID,不是吗?我想这些值必须由微软提供,我不能使用任何值,不是吗?在这种情况下,我如何从微软获得它们?那么,如果我不修改CysB.SIS驱动程序,我是否需要遵循赛普拉斯指出的具有WHQL证书的程序?如果我不需要这个WHQL签名过程,我是否应该简单地遵循内核模式代码的签名,提供我的微软? 请尽可能详细地描述不同场景所需的步骤。 以上来自于百度翻译 以下为原文 We use Cypress USB controllers for an our own product that should work under Windows Vista/7 64-bit. As I discovered in this forum we need a signed driver for x64 OS from Vista on. Now I would like to know the step I need to sign the driver. I would like to sign the driver because (if I'm not wrong) the cost is not too high (according to what I found here the certificate costs 99$). I learned from the Microsoft guide on kernel-mode code signing walkthrough how to: 1) obtain a Software Publisher Certificate (SPC) from a commercial CA (Certificate Autorithy); 2) create a .CAT file starting from the driver file (.SYS) and the driver setup information file (.INF); 3) use the SPC to sign the CAT file in order to be able to use the driver under Windows Vista/7 64-bit. Installing Cypress USB Generic Driver (3.4.6) I got the cyu***.sys and cyu***.inf files (under C:Program FilesCypressCypress Suite USB 3.4.6Driverwlh). These work fine for our product (for the moment only disabling the driver signature enforcement). Now I feel to miss some information on the steps I need to have our own signed driver that will work with our XXX product so that once plugged in our product to a computer that has the driver installed, the product is automatically recognized as the XXX product. First of all I guess I have to change on the USB controller and on the cyu***.inf the VID and the PID, isn't it? I guess these values have to be provided by Microsoft and I cannot use any values, isn't it? In this case how do I get them from Microsoft? Then if I do not modify the cyu***.sys driver do I need to follow the procedure that Cypress indicates for having the WHQL certificate? If I do not need this WHQL signing procedure, should I simply follow the instructions on the kernel-mode code signing walkthrough provided my Microsoft? Please details as much as possible the steps needed for different scenarios. |
|
相关推荐
22个回答
|
|
WiQuALL有所有的步骤,只要跟着它,你就会得到签名的司机。
1,购买VrISIGN,并签署您的驱动程序。 2,使用WHQL测试工具(不容易)在64位系统上测试已签名的驱动程序,并将已成功的测试结果订阅给Winqual。 3,等待签署的CAT文件。 找到一个WHQL支持者会更容易。. 以上来自于百度翻译 以下为原文 Winqual have all the steps, just follow it, you will get signed drivers. 1, Buy verisign, and sign your driver. 2, Test The signed driver on 64bit system using WHQL test tools(Not easy), and subscribe the succeded test result to Winqual. 3, wait for signed cat files. Find a WHQL suppotor will be easier. . |
|
|
|
通过WiNUSB下载固件是没有问题的。所有的源代码都是由CyPress提供的,可以适用于WiUSB。查看供应商命令的AppNoT: HTTP://www. CyPress?RID=34485,在此查找所有加载第二阶段加载器的信息。此外,您可以查看FX2Load的源代码。您必须在控制端点上写入一些供应商请求,停止CPU,加载RAMOFE新固件(从AppNoT)并运行CPU,在此之后您可以编写小的或大的EEPROM。它工作很好,不需要CysB.SyS,而且还可以读取EEPROM内容。
以上来自于百度翻译 以下为原文 Firmware download via WinUSB is no problem. All the source code is provided by Cypress and can be adapted to WinUSB. Take a look at the AppNote for vendor commands: http://www.cypress.com/?rID=34485 in this you find all information for loading the second stage loader. Further you can look into the source code of fx2load. You have to write some vendor requests over the Control Endpoint, stop the CPU, load the RAM with new firmware (from the appnote) and run the CPU, after this you can write the small or large eeprom. It works great and with no need of CyUSB.sys and addionally you can read back the eeprom content. |
|
|
|
VID由UB-IF提供(请看AthTP://www.USB/org/home),一旦拥有了VID,您就可以自行分配和维护PID。
您可以通过WHQL签署司机或使用第三方证书来签署司机(SPC)。WHQL签名涉及测试,因此需要注意硬件与软件的交互是正确的。这就是我们推荐的那个。 我正在研究使用第三方证书签署的步骤。一旦我准备好就会更新这里。 当做, 阿南德 以上来自于百度翻译 以下为原文 VID is provided by USB-IF (please look at http://www.u***.org/home), Once you own a VID you can assign and maintain PID by yourself. You can WHQL sign the driver or use a 3rd party certificate to sign the driver (SPC). WHQL signing involves testing so it takes care that the hardware software interaction is right. So this is the one we've been recommending. I'm working on documenting the steps involved in signing using 3rd party certificate. Will update here once I have it ready. Regards, Anand |
|
|
|
谢谢克里斯。请问WiUSB上有固件加载器的发布版本吗?我不想听起来懒惰,但重写相同的典型的东西一次又一次…制造同样的错误…这听起来很低效。
也是一阶问题。假设我有所有的WiUSB实现为我的柏树设备-它如何帮助在64位签署斗争?换句话说,它是在F8冗余或仅仅简化认证过程的时候开始定制的吗?我可以使用红色对话框,但我不想禁用驱动程序签名,而不是调整窗口(与BCDEDIT.EXE或别名)。 对不起,可能有新问题,但我刚进入64位。我觉得自己还不舒服。 当做, 德米特里 以上来自于百度翻译 以下为原文 Thanks Chris. May I ask is there a published version of the firmware loader on winu***? I don't want to sound lazy but rewriting the same typical stuff again and again... making the same bugs... this sounds inefficient. And also first order question. Assuming that I have all-winu*** implementation for my cypress device - how does it help in the 64-bit signing struggle? In other words, does it make custom start on F8 redundant or just simplifies the certification process? I can live with red colored dialogs but I would like not to disable driver signing and not to tune windows (with the bcdedit.exe or alikes). Sorry for the possibly newbie questions but I've just got into 64-bit. Not feeling myself comfortable yet. Regards, Dmitry |
|
|
|
使用WHQL测试工具测试驱动程序,首先建立一个网络(服务器,工作站,测试PC),不是吗?既然我们是一家创业公司,我们不想花那么多时间,我们该怎么办?
AASI,你说不是WHQL签名,我可以使用SPC,但是在CyPress AN597文档中写有“……”驱动程序质量签名允许驱动程序在Windows中加载微软定义的兼容性和可靠性要求。在正常模式(……)中,驱动程序不能加载Windows 7和Vista 64位操作系统(OS)而不需要驱动程序质量签名。那么,WHQL与SPC符号的真正区别是什么呢?在实践中会发生什么,当司机将上演(DIFX)或安装在另一台电脑? 你能给我更多关于Windows 7 64位的CysBSIS签名驱动程序的详细信息吗?我想这是WHQL签署的,不是吗?我可以使用这个.sys签名的驱动程序和我自己用SPC签名吗?我将从.INF文件(我将放VID/PID)和您签名的.sys开始构建.CAT文件。这样就够了吗? 我们USZZ的FX2 CY7C68013的目的是安装在其他机器上的驱动程序编程和尽可能少的用户交互。 以上来自于百度翻译 以下为原文 Test the driver using WHQL test tools means to setup firstly a network (server, workstation, test PC), isn't it? Since we are a startup company and we do not want to spend all that time, how should we do? aasi, you say that instead of WHQL sign I can use a SPC, but in the Cypress AN5297 document there is written "[...] Driver quality signature allows the driver to load in Windows with compatibility and reliability requirements defined by Microsoft. The driver cannot be loaded in Windows 7 and Vista 64-bit operating systems (OS) without driver quality signature in normal mode [...]". So which is the real difference between WHQL and SPC sign? What will happen in practice when the driver will be staged (DIFx) or installed on another PC? And please can you give me more details on this cyu***.sys signed driver for Windows 7 64-bit? I guess it is WHQL signed, isn't it? May I use this .sys signed driver and by myself sign with SPC only the .cat file that I will construct starting from the .inf file (where I'll put our VID/PID) and the .sys signed by you? Would this be enough? We use EZ-USB FX2 CY7C68013 and the goal is to install on other machines the driver programmatically and with as less as possible user interaction. |
|
|
|
抱歉,我不能提供源代码,因为我在工作中写的。但我可以给你提示。是不是真的很难。
使用WINUSB驱动程序,您可以在没有对Windows X64进行任何修改的情况下运行您的设备,没有F8按压。如果你没有任何签名,你在安装时得到红色警告,这就是全部。你可以用99美元买一个VrISIGN代码签名签名,然后用这个文件签名CAT文件,所以你只得到一条信息“你想信任……?”你也可以选择“永远信任”。 以上来自于百度翻译 以下为原文 Sorry, I cannot provide the source code, as I wrote this on work. But I can give you hints. Is is not really difficult. With the WinUSB driver you can run your device without any modifications on Windows x64, no F8 pressing. If you dont have any signature, you get a red warning while install, that´s all. You can buy a verisign code signing signature for USD 99 and signe the cat file with this, so you get only a message "Do you want to trust...?" where you can also choose "Ever trust.". |
|
|
|
我看到公司把这个作为一个服务,你也可以看看这个方法。
SPC和WHQL的区别在于SPC不涉及测试。因此,WHQL签署将给予更多的质量方面的信心。 我还没有机会与SPC签署的驱动程序一起来查看操作系统的行为,但是基于MS文档,我的理解是SPC签名的驱动程序将以相同的方式运行并且可以被分发。 Win 7和Vista X64将不允许将文件写入系统文件夹,除非它们被签名。 签名类型与哈希代码和内容有关。当更改INF文件时,哈希代码将被破坏,因此无法使用.CAT文件。在对INF文件进行必要的修改之后,您可以使用INF2CAT生成它。 如果您在驱动程序中签名并将其放置在适当的系统文件夹中,则在使用该驱动程序时不需要用户干预。 当做, 阿南德 以上来自于百度翻译 以下为原文 I've seen companies provide this as a service you might wanna look at that approach as well. The difference between SPC and WHQL is that SPC does not involve testing. So WHQL signed would give more confidence in terms of quality. I've not got a chance to play around with SPC signed drivers to see the behavior of the OS but based on MS documents my understanding is that SPC signed driver will behave the same way and can be distributed. Win 7 and Vista x64 will not allow writing files to system folder unless they are signed. Signing kind of has to do with hash code and stuff. When you change the inf file the hash code will be broken so you'll not be able to use the .cat file. You can generate it using inf2cat after making the necessary modifications to the inf file. If you sign the driver and place it in the appropriate system folder, no user intervention will be needed while using the driver. Regards, Anand |
|
|
|
嗨,德米特里,
我发布了一个基于CyAPI.LIB的主机应用程序,我已经开发了固件下载测试版。您可以使用此作为开发代码的参考。 当做, 阿南德 固件下载 56.7 K 以上来自于百度翻译 以下为原文 Hi Dmitry, I'm posting a beta version of CyAPI.lib based host application I had developed for firmware download. You can use this as reference to develop your code. Regards, Anand
|
|
|
|
抱歉,我仍然缺少关于Windows 7 64位的Cy***.系统签名的驱动程序的信息。我在某处读到,可以签署.sys,猫,或两者。这个链接都是签名的吗?他们都是和WHQL签的吗?因为如果是的话,有可能保持您的系统与WHQL签署,并使用我们的CAT与SPC签署吗?这样,我们就可以选择快速SPC签名方法,并保持WHQL签名的好处。提前感谢
以上来自于百度翻译 以下为原文 Sorry I'm still missing information on this cyu***.sys signed driver for Windows 7 64-bit. I read somewhere that it is possible to sign either the .sys, the .cat or both of them. In this link are both signed? And are they both signed with WHQL? Because if yes, is it possible to keep your.sys signed with WHQL and use our .cat signed with SPC? In this way we might just opt for the fast SPC signing method and keep mantaining the benefit of the WHQL signing. thanks in advance |
|
|
|
它与CyUSB.sys接口,用于处理和发送供应商请求。用WiUSB等值替换这2个部分应该让你更快地运行。
当做, 阿南德 以上来自于百度翻译 以下为原文 It interfaces with CyUSB.sys for getting handle and sending vendor requests. Replacing those 2 parts with WinUSB equivalents should get you up and running quicker. Regards, Anand |
|
|
|
它是WHQL签名的,它已经签署了.sys和.INF作为一个完整的包。猫包含签名。所以我认为你不能用你提出的方式来使用它。
当做, 阿南德 以上来自于百度翻译 以下为原文 It is WHQL signed and it has signed the .sys and .inf as a whole package. The .cat contains the signature. So I don't think you would be able to use it in the fashion that you're proposing. Regards, Anand |
|
|
|
应用笔记(HTTP://wwwyCysP.COM/?)RID=34253)我上传的代码是上传到我们站点的一部分。你应该能够从那里得到必要的解释。
当做, 阿南德 以上来自于百度翻译 以下为原文 The app note (http://www.cypress.com/?rID=34253) of which the code I posted is a part of has been uploaded to our site. You should be able to get the needed explanation from there. Regards, Anand |
|
|
|
谢谢AASI的回复。最后一件事(希望),如果它与WHQL签署,当我试图在Windows 7 64位安装它时,为什么要得到下面的警告:“不安装这个设备是不推荐的,因为Windows不能验证它与您的硬件兼容……”
以上来自于百度翻译 以下为原文 Thanks aasi for your reply. Just last thing (hopefully), if it is signed with WHQL why do I get the following warning when trying to install it in windows 7 64-bit: "Installing this device is not recommended because Windows cannot verify that it is compatible with your hardware...." |
|
|
|
德米特里:如果您只想在未编程的FX2设备上首次编程固件,可以使用来自CyPress的签名X64驱动程序:HTTP://www. CyPress?ID=4和;RID=53338,与CySalk一起使用。
以上来自于百度翻译 以下为原文 Dmitry: If you only want to program the firmware the first time on unprogrammed FX2 devices, you can use the signed x64 driver from cypress: http://www.cypress.com/?id=4&rID=53338 together with CyConsole. |
|
|
|
1。你是在使用文件吗?
2。你的设备是否有固件在运行,或者连接一个未编程的FX2LP? 当做, 阿南德 以上来自于百度翻译 以下为原文 1. Are you using the files as is? 2. Does your device have a firmware running in it or are you connecting a unprogrammed FX2LP? Regards, Anand |
|
|
|
你好,AASI,
你确定CYUSB不支持等时性传输吗?我需要转换我们的32位应用程序上运行的AN2131,使用ISO通道。 我有一张比较EZUSBto CyUSB的IOCTLS表,现在看来,EZUBSyIOLRead和.x写现在包含在IOCTLYAppToStEnthNo.Endol转移或… 黑斑狗尾草 841.5 K 以上来自于百度翻译 以下为原文 Hi aasi, Are you sure that the CyUSB does not support Isochrounous transfer? I need to convert our 32bit app running on an AN2131 which uses ISO channels. I have a sheet of IOCTLS comparing EZUSB to CyUSB and it seems that EZUSB_IO_READ and .._WRITE are now contained in IOCTL_ADAPT_SEND_NON_EPO_TRANSFER or .._DIRECT
|
|
|
|
如果你不想花太多的时间和金钱来签署CYSUBSIS驱动程序,考虑切换到WinUSB oder LibUSB驱动程序。我们使用WiUSB驱动程序和努力改变应用软件战争一天的工作。这比WHQL的努力要少得多。如果你想从UAC获得一个蓝色的消息(你想信任供应商……),那么你需要安装的是VISISIN ID(99美元)。通用驱动程序从XP SP2开始运行在所有Windows系统上,并且作为一块石头是稳定的。AFIKB现在也被签署,并且即使在64位系统上也可以使用WHQL。
以上来自于百度翻译 以下为原文 If you don´t want to spend so much time and money on signing the CyUSB.sys driver, consider switching to WinUSB oder LibUSB driver. We use WinUSB driver and the effort to change the application software war about one day of work. This is much less then the effort for WHQL. WinUSB is signed by MS and if you want to get only a blue message (Do you want to trust the vendor...) from UAC while install all you need is the Verisign ID (99US$). The universal driver works on all Windows Systems beginning with XP SP2 and is stable as a rock. AFAIK the LibUSB is now signed, too and can also be used without WHQL even on 64 bit systems. |
|
|
|
你好,
关于SPC和WHQL签名驱动程序之间的差异——如果您打算悄悄安装您的驱动程序(没有用户干预/对话框等,以大多数硬件提供商的方式做),您必须有WHQL签名驱动程序。这一点没有得到很好的记录,当我们从GualAlgSub购买SPC证书时,签署了我们的驱动程序,然后尝试通过DpSIN.EX-Windows安装我们正确签署的驱动程序包,弹出一个对话框,询问您是否信任发行商,您真的想要安装驱动程序吗?但是,如果用户允许这个驱动程序在所有窗口上运行正常,但是对话框的安装过程不太好… 后来我们试图搬到WHQL,但重点是它只接受VISISIN证书,我们拥有的GualSal签署不能在那里使用。所以我们现在必须再购买一个证书: 最好的问候,Arturas 以上来自于百度翻译 以下为原文 Hi, Regarding difference between SPC and WHQL signed drivers - if you plan to install your driver silently (without user intervention/dialog boxes etc, in the way most hardware providers does) you MUST have WHQL signed driver. This point is not documented very well, we came to this when we bought SPC certificate from GlobalSign, signed our driver, then tried to install our properly signed driver package via dpinst.exe - Windows pops up a dialog asking do you trust the publisher and do you really want to install the driver. However, if user will allow this - driver works ok on all Windows, but that dialog make installation process not so nice... Later we tried to move to WHQL but the point is that it accepts certificate only from Verisign, our owned from GlobalSign cant be used there. So we have to buy one more certificate now :) Best regards, Arturas |
|
|
|
谢谢你们所有人!现在我有了一些更清楚的想法(但还不完全)。
我们有一个SPC暂时,因为去WHQL签署太长和复杂。因此,目前我们通过请求用户接受安装驱动程序(弹出窗口,请求信任或不发布)来解决非完整的无声驱动器安装。目前我们正在使用CyPress通用驱动程序。 现在,WiUSB驱动程序的优点是什么?此外,WiUSB应该签署(创建猫,然后签署它),所以我想,如果我们通过SPC签署,我们仍然有弹出窗口,不是吗? 以上来自于百度翻译 以下为原文 thanks to all of you guys! Now I've ideas a bit more clear (but still not completely). We have got a SPC for the moment, since going for the WHQL signing is too long and complicated. Hence for the moment we settle for a non complete silent driver installation by requiring the user to accept to install the driver (a pop-up window asking to either trust or not the publisher). And for the moment we are using the Cypress general driver. Now, what is the advantage of the WinUSB driver? Also the WinUSB should be signed (creating the CAT and then sign it), hence I guess that if we sign through SPC we still have the pop-up window, isn't it? |
|
|
|
只有小组成员才能发言,加入小组>>
752个成员聚集在这个小组
加入小组2069 浏览 1 评论
1824 浏览 1 评论
3633 浏览 1 评论
请问可以直接使用来自FX2LP固件的端点向主机FIFO写入数据吗?
1760 浏览 6 评论
1509 浏览 1 评论
CY8C4025LQI在程序中调用函数,通过示波器观察SCL引脚波形,无法将pin0.4(SCL)下拉是什么原因导致?
507浏览 2评论
CYUSB3065焊接到USB3.0 TYPE-B口的焊接触点就无法使用是什么原因导致的?
357浏览 2评论
CX3连接Camera修改分辨率之后,播放器无法播出camera的画面怎么解决?
410浏览 2评论
357浏览 2评论
使用stm32+cyw43438 wifi驱动whd,WHD驱动固件加载失败的原因?
854浏览 2评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-11-22 00:24 , Processed in 1.432421 second(s), Total 112, Slave 96 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号