The framework crashes when accessing devices that
provide a device descriptor of revision 4.
The stack trace is as follows:
Aug 24, 2006 8:57:06 AM com.ftdichip.ftd2xx.Device open
INFO: Open device 0.
Aug 24, 2006 8:57:06 AM
com.ftdichip.ftd2xx.ui.deviceTree.DevicesTreePanel$1 run
SEVERE: Failed to refresh device list.
java.lang.NoSuchFieldError: inEndPointIsochronous
at
com.ftdichip.ftd2xx.EEPROM.readDeviceDescriptor(Native
Method)
at
com.ftdichip.ftd2xx.EEPROM.readDeviceDescriptor(Unknown
Source)
at
com.ftdichip.ftd2xx.EEPROM.getDeviceDescriptor(Unknown
Source)
at
com.ftdichip.ftd2xx.Device.getDeviceDescriptor(Unknown
Source)
at
com.ftdichip.ftd2xx.Device.<init>(Unknown Source)
at
com.ftdichip.ftd2xx.Service.listDevices(Native Method)
at
com.ftdichip.ftd2xx.ui.deviceTree.DevicesTreeModel.createTree(Unknown
Source)
at
com.ftdichip.ftd2xx.ui.deviceTree.DevicesTreeModel.refresh(Unknown
Source)
at
com.ftdichip.ftd2xx.ui.deviceTree.DevicesTreePanel.refresh(Unknown
Source)
at
com.ftdichip.ftd2xx.ui.deviceTree.DevicesTreePanel$1.run(Unknown
Source)
at
java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Logged In: YES
user_id=1164568
The cause for this problem is, that the native code uses the
wrong field type to quire the device descriptor fields
inEndPointIsochronous and outEndPointIsochronous.
This is fixed in v1.2, which will be released soon.
Logged In: YES
user_id=1164568
!!! This bug is related to the ftd2xxj framework !!!