We use a (paid) s/w company who is an expert on device driver development for our custom design on Windows.ġ) You are using an USB device which is based on custom VID and / PID IDs. XMOS or someone else can probably expand on these topics. Here are some comments we believe to be accurate for your request. 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. 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. I have installed the driver on a Win10 PC and the behaviour is strange:ġ) Wasapi works 2) direct sound works 3) ASIO KO #define VENDOR_ID (0x1CBA) // Xmos VID so as to use the drivers installed with the Xmos tools #define SERIAL_STR "" // default to empty serial number - a value can be loaded into the str table from the OTP at runtime I introduced the PID received in the following way: I received my PID and the related driver a few days ago. I prefer to hide the information about his third party. #define VENDOR_ID (0x1CBA) // Xmos VID so as to use the drivers installed with the Xmos tools #define SERIAL_STR "" // default to empty serial number - a value can be loaded into the str table from the OTP at runtime I started from a Dev Kit suppplied by a third party and with the kit I received also the Driver for Windows. I have designed a board around the XU216-512-TQ128 chip.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |