使用CyConsole访问冲突

VID/PID是设备管理器显示的设备吗？？？？cyconsole的最新版本可以在suiteu*** 3.4发现…你可能想下载…你点击哪个字段来获得这个访问违规？即复制你的问题的步骤…



     以下为原文
          What VID/PID is device manager showing for that device???   
The latest version of cyconsole can be found in suiteu*** 3.4... you might want to download that... Which field did u click to get this access violation... i.e. steps to replicate your issue...   

我在设备管理器中发现了这一点：USB  VIDY0852和PIDY088A 6和BB9CF62和0和5…似乎没问题。我现在使用最新版本1.7.0.2。这里我一步一步地做着：1。我插入了我们的设备（设备管理器加载适当的驱动程序）2。启动CySale- & Gt；获得错误消息：模块“CalStudio.exe”中地址00418059处的访问冲突。读地址0000000，3。打开EZ-USB接口（我不能在DeCIELIST中看到我们的设备）。它是空的……）4。点击lgEePROM按钮-gt；得到错误消息：在模块'CalStudio.exe中的地址040FFA8中访问访问失败。读取地址00000 978。5。点击BultRANT按钮-Gt；获得错误消息：模块“CalStudio.exe”中地址4040E55 E中的访问违规。读取地址00000 978。6。点击GeDeVIY按钮-gt；获得错误消息：模块“CalStudio.exe”中地址4040D8C1中的访问违规。读取地址00000 978。有什么想法吗？固件为什么会阻塞CySalk？谢谢，安德烈亚斯



     以下为原文
          I found this in the device manager:   
USBVID_0852&PID_00816&BB9CF62&0&5 ... seems to be OK.   
   
I'm using the latest Version 1.7.0.2 now.   
   
Here step by step what I am doing:   
1. I pluged in our device (device manager loaded the proper driver)   
2. started the CyConsole --> got the Error message: Access violation at address 00418059 in module 'CyConsole.exe'. Read of address 0000000A.   
3. Open EZ-USB Interface (I can not see our device in the devicelist. It's empty...)   
4. clicked LgEEPROM button --> got the Error message: Access violation at address 0040FFA8 in module 'CyConsole.exe'. Read of address 00000978.   
5. clicked Bulk Trans button --> got the Error message: Access violation at address 0040E55E in module 'CyConsole.exe'. Read of address 00000978.   
6. click GetDevie button --> got the Error message: Access violation at address 0040D8C1 in module 'CyConsole.exe'. Read of address 00000978.   
   
Any idea? why does the firmware totaly block the cyConsole?   
   
Thanks,   
Andreas   
   

以下是可能发生的事情…该设备被枚举，因此主机知道设备配置和东西…当驱动程序枚举设备时，它将再次执行相同的描述符请求集。如果该设备在这个阶段没有正确响应，那么驱动程序将通信该设备到CySalk，但不能正确地给设备提供能力。这将导致CyStAccess访问没有正确访问的地方。这是你能做的…如果你有一个CATC示踪剂…把它挂起来，观察枚举序列…如果可能上传你的IIC文件在这里…我来看看我是否能找出确切的原因…



     以下为原文
          Here is what might be happening... the device is enumerated and so the host knows the device config and stuff... when the driver enumerates the device it will do the same set of descriptor requests again... if the device doesn't respond properly at this stage then the driver will communicate that device is there to cyconsole but won't be able to give the capabilities to the device properly.... this will cause the cyconsole to access places which it doesn't have proper access to....   
Here is what you can do... if you have a CATC tracer... hook it up and observe the enumeration sequence... if possible upload your iic file here... i'll see if i'm able to figure out the exact cause...   

是的，这样的事情可能会发生。不幸的是，我们没有CATC示踪剂。上传任何东西都是不可能的。我得到了这样的信息：“最大附件目录大小已经达到，没有进一步的附件可以上载。”我稍后再试试。如果你能想出办法的话，那就太好了。但是，擦除EEPROM是没有可能的吗？或者像急救工具之类的……？



     以下为原文
          Yes something like this might happen. Unfortunatly we don't have a CATC tracer.   
   
It's impossible to upload anything. I get this message: "The maximum attachment directory size has been reached, no further attachments can be uploaded." I will try it again later...   
   
It would be nice if u could figure out something. But is there no possibility to erase the eeprom? Or something like an emergency-tool or so...?   
   
   
   
   

在DVK有一个开关，你可以使用它禁用EEPROM…启动后，您可以启用它，然后用一个工作IIC文件覆盖它…你使用DVK还是自定义板？？？？？



     以下为原文
          In the DVK there is a switch using which you can disable the EEPROM... after booting up you can enable it and then overwrite it with a working iic file... are you using the DVK or a custom board????