Debug ezusb and cyusb drivers on the same computer

The Development Environment Supporting fx2lp 68014a used in the project is suite 3.4.7, And the built-in debugging tool is the control console. You can burn the built-in Ram or external EEPROM, but it only supports binding cyusb. SYS driver device, does not support older ezusb. SYS driver.

??

In the project, the host computer interface program is compiled based on the old drive ezusb. sys and does not use cyusb. Lib, which causes debugging trouble.

??

There are two methods to achieve a convenient debugging process (burning, testing, burning, and then testing ):

??

1. Use the old debugging software ezusb control panel in the fx2 era to burn the firmware, so that 68013a can always be bound to the ezusb. SYS driver, and the vid and PID of the device can be fixed to a value.

??

Rating: I may not use the ezusb Control Panel too much. I am too lazy to try again because I have failed to write the eeprom several times.

??

2. After the firmware is compiled, bind the device to cyusb. sys, use the control console to download the firmware, bind the device to ezusb. sys, and open the interface program for debugging. For convenience, I have defined vid_0547 & pid_1002 in the installation information files of cyusb. sys and ezusb. SYS. The dscr. A51 In the firmware also specifies that the device is vid_0547 & pid_1002. The driver of the device is bound to cyusb. sys (manually selected to create one of Multiple matching drivers. XP lists all driver installation information that matches the vid and PID of the device. the device name declared in the INF file), then use the control console to burn the firmware (the vid and PID remain unchanged during the process), and then update the device driver to ezusb. sys (still manually selected), and then you can use the interface program to test. When you need to modify the firmware, you can update the device driver to cyusb. sys (benefits of the same vid and PID are highlighted, and the driver can be converted without modifying any inf file), and then the control console is used for writing. This completes the cycle of "Burning write-debugging-burning write-debugging.

??

Comment: during this period, XP prompts that the device needs to be restarted. If the device cannot be found during debugging, replugging the device to successfully enumerate the device and bind it to the new driver. This is also a temporary method, compared to repeatedly modifying the vid & pid in INF, just a few clicks, more convenient.

??

Conclusion: The best method is to use the ezusb control panel, which is based on the ezusb. SYS driver in the fx2 era. This saves the trouble of switching the driver. I just haven't figured out how to use it, or whether the ezusb Control Panel supports the burning of fx2lp series devices. I should spend some time reading the instructions on ezusb control panel, which may simplify the workload.

Debug ezusb and cyusb drivers on the same computer