TI E2E Community
Audio Converters Forum
DFU issues on TAS1020B
I'm trying to do some USB development on the TAS1020. All the documentation in the Firmware Development Kit/Datasheet/UG indicate that the process ought to be the following:
1. Remove EEPROM chip (or short SDA or something) to initiate a host boot
2. Plug in the device, which will enumerate with a dummy VID/PID (0xFFFF and 0xFFFE).
3. Use the TI DFU software to download a properly formatted file to the device/EEPROM.
Well, my problem lies in between steps 2 and 3. After shorting out the EEPROM, I plug in the device and am unable to locate acceptable drivers. The device describes itself as "Unknown" manufacturer and product, and the DFUUSB.inf and DFUUSB.sys files packaged in the DFU_Software portion of the downloadable Firmware dev kit don't seem to cut the mustard. I can point the driver install directly to them or even select the inf file, but the installation never works. What's more, I've watched the data come across a bus analyzer, and the correct VID/PID come across, it's just that there is nothing on the other side waiting for it.
The 1020EVM guide (a guide for an old eval board for the product) indicates that there was once a 3.5" driver floppy or something that contained drivers and a file called "DFU.EXE" which does not make an appearance in the FDK.
Ther eis a DFUTEST.EXE, but it always fails to recognize a DFU device.
I'm stuck. Any thoughts?
Embedded Systems Engineer
I need this too.
I have an M-Audio Ozone, that's a midi keyboard controller with audio interface. And I think that is Bricked... (now... previously I replaced the tas1020a on it) windows detect it as Unknown. I guess that is in dfu mode waiting for a firmware but i can find a way to install a dfu driver. There are no support for this in M-Audio, no firmware updates.
I have an M-Audio Ozone, that's a midi keyboard controller with audio interface. And I think that is Bricked... (now... previously I replaced the tas1020a on it :S) windows detect it as Unknown. I guess that is in dfu mode waiting for a firmware but i can find a way to install a dfu driver, I tried the firmware developer kit's driver . There are no support for this in M-Audio, no firmware updates.
David, I just wrote a long reply to this but the forum ate it.
Have a look at this link for debugging driver installation: http://www.microsoft.com/whdc/driver/install/setupapi.mspx
Try editing the following lines in the INF:
and changing them to:
According to all the doco I've read on INF's so far there shouldn't be a space on the RHS. This needs to match the models-section-name in the INF so that the installer knows which drivers to install. My theory is that it isn't finding any relevant driver to install. However, this would mean that the driver has been broken for 9 years and not been fixed which I can't believe.
Could you update the thread with any progress you make as I'm going to be following this path soon.
OK, I've spoken to 3 colleagues about the syntax now and they all agree that this looks like a typo in the INF file. If possible could a TI representative step in and confirm.
It would also be good to know if there is a more recent pdf for the Firmware DK which has all the placeholders filled and would give me a little more confidence that the contents are correct. It looks like the first draft from the engineer rather than the finished document.
Actually, after I posted this question, I contacted TI support. They quickly provided me with a new set of drivers- which worked. I noted that after I made the inquiry, the FDK download was taken down for some period, so it's possible that they've updated the installer. I'd suggest sending them an email requesting it, or if you don't mind using a file some guy on the internet gives you, I'd be happy to send you the driver they gave me. I'm pretty sure I have the original zip file somewhere around here..
ok, brilliant. I'd actually appreciate hearing how you've got on with the part as well as getting hold of the drivers. Drop me a line on sjalloq_at_hotmail_dot_com.
Sorry, just now saw the question on DFU. Please see attached for the correct .inf The one on FDK will be fixed shortly.
Texas Instruments, Inc.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.