Re: [Libusb-win32-devel] Invalid Parameter in usb_set_configuration call on Win7

[Mirco S. g. <mir...@gm...>]

Xiaofan Chen,

Hi,
>
> Ref: I said the following at that time (more than five year ago).
> "There is a hack to get libusb-win32 to work with such device
> (to replace bulk with interrupt transfer in the driver level)
> but it is much better that you change the firmware to		<---------------------------------
> be compliant with the USB specifications.
I'm neither a device driver developer nor a hardware expert, however, changing the firmware is a very interesting thing: 
in many USBDM/BDM support docs it is stated that it is possible to upgrade JB16 devices (inside my Axiom BDM-CF pod 
there is a WC9JB16FAE chip, probably a 28 pin MC68HC908JB16 presenting himself to windows 7 usb interface as 
USB\VID_0425&PID_1001&REV_0001) with a freshen firmware using USBICP program. The details on the entire procedure sound 
to me as "mystical", I mean something like this (just an example, with a different PID):

...
You must use 32-bit Windows XP to perform this
2. You must have Office 2010 installed - evaluation version is enough as it's only required for some unresolved 
dependency of USBICP.EXE
3. You can't use latest USBDM as support for JB16 has been broken for quite a while
4. USBDM developer has nuked all old versions from Sourceforge. I've proved links to working versions below.
You can't use latest USBDM as support for JB16 has been broken for quite a while
4. USBDM developer has nuked all old versions from Sourceforge. I've proved links to working versions below.

  * Download and install USBDM 4.9.5 with default settings
    http://files.mpoli.fi/sekalaiset/usbdm/ ... 5b_Win.msi <http://files.mpoli.fi/sekalaiset/usbdm/USBDM_4_9_5b_Win.msi>
  * Download USBDM_Win32_4_6a.zip from
    http://files.mpoli.fi/sekalaiset/usbdm/ ... 2_4_6a.zip <http://files.mpoli.fi/sekalaiset/usbdm/USBDM_Win32_4_6a.zip>
  * Extract USBDM_Win32_4_6a.zip
  * Plugin Wayengineer TBDM while pulling pin 10 of MON08 connector GND to initiate ICP mode
    Pin 10 is also known as MON_DATA, see "C:\Program Files\pgo\USBDM 4.9.5\FlashImages\JB16\OSBDMe.pdf" included in
    USBDM 4.9.5 package for pinout if necessary.
  * Install USBICP driver from USBDM_Win32_4_6a.zip "Win32\Freescale ICP Files"
  * TBDM should be detected as USB\VID_0425&PID_ff02 "Motorola JB16/JG16 ICP Device"
  * If it comes up as USB\VID_0425&PID_1000 then you failed to initiate ICP mode
  * Launch USBDM_Win32_4_6a\Win32\Freescale ICP Files\USBICP.EXE
  * Select "Initial_Programming_MassErase.imp" when asked to open file
  * Next browse to "C:\Program Files\pgo\USBDM 4.9.5\FlashImages\JB16" and select USBDM_JB16.s19
  * Go thru Erase, Program, Verify and close USBICP
  * Unplug TBDM
  * Uninstall USBDM 4.9.5
  * Download and install 4.9.4 as it's last version with working JB16 support
    http://files.mpoli.fi/sekalaiset/usbdm/ ... 4b_Win.msi <http://files.mpoli.fi/sekalaiset/usbdm/USBDM_4_9_4b_Win.msi>
  * Plug TBDM back without grounding pin 10
  * New device will be detected, point driver install wizard to
    "C:\Program Files\pgo\USBDM 4.9.4\USBDM_Drivers\Drivers"
  * New USB ID should be VID_16D0&PID_0567 and name "USBDM BDM Interface"
  * You can now follow regular USBDM docs. Programmer will also work with 32-bit and 64-bit Win7 now.

...

So I wonder if someone could explain to me exactly how to "upgrade" my Turbo BDM Light Coldfire" in order to have it 
working as a "new" BDM device.
I'll be glad forever.

Thank you very much for your suggestions.

Mirco