Dear osoraku,
Please see comments below:
I notice that there are targets for building usbdm.4.dll for libusb V1, and targets for building usbdm.4.dll with the previous version of libusb. I understand libusb v1 is required for 64 bit windows, but does it also work for win32? Is that why you included the capability to build usbdm.4.dll with previous libusb, so you could still support win32?
The previous V0 targets were just for testing. I discovered, after changing to libusb V1, that there was a signed version of libusb v0 that can be used with windows 7 but it still seems a sensible change - especially under linux.
How hard would it be to modify the flash programmer projects to produce DLL's instead of GUI or command line? I looked into it, but trying to strip out the interactions with wxWidgets seemed like it might be rather messy.
Most of the target specific programming code is in the various FlashProgramming.cpp and DeviceData.cpp files. The only use of wxWidgets is for wxString I think. It should be reasonable painless to change these to C++ strings and remove the dependence. The rest of the code is mostly gui stuff.
I have BDM pods built about a year ago from your v1 designs. It is the JM60 version, with no support for RS08 and no support for providing target Vdd. It has been working great for programming HCS08 and CFV1 targets. Do you believe this vintage of pod should still work with the new v4 f/w and DLLs? I have been having some problems trying to use v4 f/w and dll's either with the pre-built HCS08 flash programmer included in your v4 distro, or with CodeWarrior 6.3. I've seen both these scenarios work, but there seems to be serious slugishness in recognizing the pod, and even after it is found communicating with the target is rather hit-or-miss. But, I have been successful in programming HCS08 targets at least once with both of these methods. It feels like there is something funky with the new USB driver (which I managed to install following your instructions), but I really don't know. Is it possible to use usbdm.4.dll with v4 f/w but use the previous libusb and windows driver, just as a point of comparison?
The dialogue and such for the BDM will be significantly slower because they have to enumerate the devices and open each one to obtain the serial number. I have had some problems with getting this process correct but I thought all the issues should be sorted by now.
Your earlier hardware should work with the newer firmware - check your design against the schematic provided with the firmware.
You should be able to use the libusbV0 drivers by just swapping the usbdm.4.dll files but I won't guarantee this because it hasn't been tested in a while and I may have made some changes to the V1 code that is not reflected in V0.
You could also try using the debug version of the usbdm.4.dll and check the log file for any clues for the delays or unreliability.
OK - found the problem I think - in some cases the usbdm.4.dll was treating JMxx BDMs as JB16 BDMs. This was due to a late fix for JB16s and me not thorougly testing what I thought was a minor change. Sorry! Download the updated file from sourceforge under errata and see if that fixes the problem.
bye
