USB Audio 2.0 Stereo Driver for Windows 10 Update
Posted: Wed Aug 30, 2017 9:12 am
Hello,
I have designed a board around the XU216-512-TQ128 chip.
I started from a Dev Kit suppplied by a third party and with the kit I received also the Driver for Windows.
The firmware with the Dev Kit reports:
#define VENDOR_STR "xxx"
#define PRODUCT_STR_A1 "yyyyyyyyy"
#define PRODUCT_STR_A2 "yyyyyyyyy"
#define SERIAL_STR "" // default to empty serial number - a value can be loaded into the str table from the OTP at runtime
#define VENDOR_ID (0x1CBA) // Xmos VID so as to use the drivers installed with the Xmos tools
#define PID_AUDIO_2 (0x----)
#define PID_AUDIO_1 (0x----)
I prefer to hide the information about his third party.
I received my PID and the related driver a few days ago.
I introduced the PID received in the following way:
// #define VENDOR_STR "xxx"
// #define PRODUCT_STR_A1 "yyyyyyyyy"
// #define PRODUCT_STR_A2 "yyyyyyyyy"
// #define SERIAL_STR "" // default to empty serial number - a value can be loaded into the str table from the OTP at runtime
// #define VENDOR_ID (0x1CBA) // Xmos VID so as to use the drivers installed with the Xmos tools
#define PID_AUDIO_2 (0x30B3)
#define PID_AUDIO_1 (0x30B3)
I have installed the driver on a Win10 PC and the behaviour is strange:
1) Wasapi works 2) direct sound works 3) ASIO KO
I have installed the same driver on a Win7pro PC and the driver is signalled with a question mark and a yellow triangle in the device manager of the control panel of Win7pro and, of course, the board doesn't start.
If I flash the exactly the same board with the firmware used when the board was designed and I use the driver received with the Dev Kit of the third party everything is perfect.
Any suggestion?
I have designed a board around the XU216-512-TQ128 chip.
I started from a Dev Kit suppplied by a third party and with the kit I received also the Driver for Windows.
The firmware with the Dev Kit reports:
#define VENDOR_STR "xxx"
#define PRODUCT_STR_A1 "yyyyyyyyy"
#define PRODUCT_STR_A2 "yyyyyyyyy"
#define SERIAL_STR "" // default to empty serial number - a value can be loaded into the str table from the OTP at runtime
#define VENDOR_ID (0x1CBA) // Xmos VID so as to use the drivers installed with the Xmos tools
#define PID_AUDIO_2 (0x----)
#define PID_AUDIO_1 (0x----)
I prefer to hide the information about his third party.
I received my PID and the related driver a few days ago.
I introduced the PID received in the following way:
// #define VENDOR_STR "xxx"
// #define PRODUCT_STR_A1 "yyyyyyyyy"
// #define PRODUCT_STR_A2 "yyyyyyyyy"
// #define SERIAL_STR "" // default to empty serial number - a value can be loaded into the str table from the OTP at runtime
// #define VENDOR_ID (0x1CBA) // Xmos VID so as to use the drivers installed with the Xmos tools
#define PID_AUDIO_2 (0x30B3)
#define PID_AUDIO_1 (0x30B3)
I have installed the driver on a Win10 PC and the behaviour is strange:
1) Wasapi works 2) direct sound works 3) ASIO KO
I have installed the same driver on a Win7pro PC and the driver is signalled with a question mark and a yellow triangle in the device manager of the control panel of Win7pro and, of course, the board doesn't start.
If I flash the exactly the same board with the firmware used when the board was designed and I use the driver received with the Dev Kit of the third party everything is perfect.
Any suggestion?