Error: No driver found for Bus Pirate CDC (new BP5 connected to Windows 7)

General
1

Hi, I would like to know if the new Bus Pirate 5 is supported on Windows 7.
My PC has Win7 (64bit) with SP1.

When I connect the BP5 to this desktop PC, I get the error message:
“Bus Pirate CDC, no driver found”. A screenshot of the error is shown below.

Bus Pirate5_no driver_error
Bus Pirate5_no driver_error1400×788 39.9 KB

With no CDC driver, there is no emulated COM port and no connectivity to Tera-Terminal. Hopefully a BP5 Windows 7 driver exists. Any help will be greatly appreciated.

1 Like
2

Windows 7 is quite old(+), and did not ship with generic CDC support.

You can check here for an example solution, although you’d need to update it to match the BusPirate’s VID and PID.

x https://forum.microchip.com/s/topic/a5C3l000000MGHIEA4/t292632?comment=P-2314212 x

To be more specific, you don’t need to write a driver, you just need to modify an .INF file to tell Windows to load the CDC driver against the VID:PID (Vendor ID and Product ID), which for BP5 is (I believe) 1209:7332.

x Another resource: https://wiki.segger.com/Windows_CDC_Driver_Installation x

The above are likely not enough … because BP5 exposes multiple interfaces. I no longer have a Windows 7 machine, but the basic concept is still the same: You need an .INF file that tells Windows 7 what driver to load. Since CDC is a standard, you can re-use an existing Windows 7 COM port driver (see above), but you have to adjust the INF file to install the driver for the specified interfaces. How to specify the specific interfaces (not just the VID:PID) in the INF … that’s something I no longer remember.

Good luck, and do share if you get it working, as it will help others too!

 

(+) Windows 7 support ended on January 14, 2020.

2 Likes
3

Thank you for your help. It is a good starting point for me to investigate further. Yes, I will share if I do get it working.

1 Like
4

Example USB CDC ACM .inf by LUFA (AVR):


;************************************************************
; Windows USB CDC ACM Setup File
; Copyright (c) 2000 Microsoft Corporation
;************************************************************

[DefaultInstall]
CopyINF="LUFA CDC Bootloader.inf"

[Version]
Signature="$Windows NT$"
Class=Ports
ClassGuid={4D36E978-E325-11CE-BFC1-08002BE10318}
Provider=%MFGNAME%
DriverVer=7/1/2012,10.0.0.0

[Manufacturer]
%MFGNAME%=DeviceList, NTx86, NTamd64, NTia64

[SourceDisksNames]

[SourceDisksFiles]

[DestinationDirs]
DefaultDestDir=12

[DriverInstall]
Include=mdmcpq.inf
CopyFiles=FakeModemCopyFileSection
AddReg=DriverInstall.AddReg

[DriverInstall.Services]
Include=mdmcpq.inf
AddService=usbser, 0x00000002, LowerFilter_Service_Inst

[DriverInstall.AddReg]
HKR,,EnumPropPages32,,"msports.dll,SerialPortPropPageProvider"

;------------------------------------------------------------------------------
;  Vendor and Product ID Definitions
;------------------------------------------------------------------------------
; When developing your USB device, the VID and PID used in the PC side
; application program and the firmware on the microcontroller must match.
; Modify the below line to use your VID and PID.  Use the format as shown below.
; Note: One INF file can be used for multiple devices with different VID and PIDs.
; For each supported device, append ",USB\VID_xxxx&PID_yyyy" to the end of the line.
;------------------------------------------------------------------------------
[DeviceList]
%DESCRIPTION%=DriverInstall, USB\VID_03EB&PID_204A

[DeviceList.NTx86]
%DESCRIPTION%=DriverInstall, USB\VID_03EB&PID_204A

[DeviceList.NTamd64]
%DESCRIPTION%=DriverInstall, USB\VID_03EB&PID_204A

[DeviceList.NTia64]
%DESCRIPTION%=DriverInstall, USB\VID_03EB&PID_204A

;------------------------------------------------------------------------------
;  String Definitions
;------------------------------------------------------------------------------
;Modify these strings to customize your device
;------------------------------------------------------------------------------
[Strings]
MFGNAME="http://www.lufa-lib.org"
DESCRIPTION="LUFA CDC Class Bootloader"
3 Likes
5

That’s useful … Does anyone know if that works for multi-interface devices (single USB device with two exposed CDC-based COM ports), such as the BP5/BP5XL/BP6?

Anyone have an INF that configures a multi-COM-port USB device (any vendor)?

IIRC, Windows 7 and MAC had troubles...

I’ve only seen it used where a single COM port was exposed, and recall there being difficulties getting a single device with two COM ports to work properly on both Windows and Mac with a single configuration.

1 Like
6
Here are more helpful links

collapsed by default to save vertical thread space.
1 Like
7

From this link, the following very relevant information comes forth:

The device ID for an interface PDO has the following form:
USB\VID_v(4)&PID_p(4)&MI_z(2)

Thus, if the COM ports are at interfaces #0 and #2, then the matching string would be:

USB\VID_1209&PID_7332&MI_0
USB\VID_1209&PID_7332&MI_2

Adjusting the INF file to match on the above (which is the interface that my device appears as) instead of just matching against USB\VID_1209&PID_7332 may be enough to get you started?

For Win7, I think you may need the INF to match three IDs:

USB\VID_1209&PID_7332 → usbccgp.sys installation section
USB\VID_1209&PID_7332&MI_0 → usbser.sys installation section
USB\VID_1209&PID_7332&MI_2 → usbser.sys installation section

1 Like
8

Thank you everyone, this was my situation as well. “Somewhere” I have an .inf for the old bus pirate 5 that does 2 CDCs, but not the MSC. I have tried to hunt it down in my repos, but suspect it is in an archived drive somewhere.

This is an example for CDC/MSC that is supposed to work on WIN XP+.

1 Like