Here is a link to a slighly related driver. Typically these types of questions arise when considering board's with out a USB microcontroller. Likely the usb alone is capable of getting you off the ground and anywhere from there. If there is no firmware (if say the chip came with out it or relies on eprom to store it and not flash) then if we knew if the chip supports usb bootloader, you can flash it or load it's firmware through the USB and there is no need for JTAG or other peripherials. We do not know what firmware the USB microcontroller is using, if any. With out getting too far into it, you should learn Microsoft's driver model, the difference between user mode and kernal mode drivers, what driver node's represent, driver hierarchy and how they logically attach themselves, different types of drivers (filter, function, bus), how kernal driver's communicate with user interface, dynamic link libraries, frameworks and API's, WDM framework/API, KMDF and UMDF API's and this is just a short list. Information about the board is necessary. If so there may also be a driver already for it which you can use. It would probably be a custom device but you should look through device types to see if there is an existing type that matches your device. There may already be driver's for that chip if it is an STM or there may be an API to help develop drivers for it.

If you know the type of chip that has the USB i/o on the board, the driver will be for that device. Should you write a driver for the USB device that will attach itself.

Usb generic gamepad driver location