This content has been marked as final. Show 5 replies
What VID/PID is device manager showing for that device???
The latest version of cyconsole can be found in suiteusb 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...
I found this in the device manager:
USB\VID_0852&PID_0081\6&BB9CF62&0&5 ... seems to be OK.
I'm using the latest Version 18.104.22.168 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?
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...
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...?
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????