Hi, I'm working on a project using TAS1020B. The product is designed to support 96kHz, 24bit USB audio. I downloaded the development kit from TI website and found only the TSC2100_FW8 software can work with 44.1kHz while the volume control function is disabled. All other sample code including V1.8 cann't work. When I download the BIN file of V1.8 to the EEPROM, the windows can recognize it as tas1020a eva..... but it cann't out put the IIS streaming, it seems the driver is not correct.
I'm wondering if there is a set of sample code which can support 96kHz, 24bit ? And Can you send it to my email: jyhong@139.com?
Thank you very much.
David,
There is no example code for 96kHz, 24bit audio in the FDK, and there won't be any - that's one of the reasons the device is currently in 'NRND' status - there is no intent to support OEMs developing new functionality.
However, OEMs have been successful in the past using the TAS1020B to transfer 96kHz 24bit audio (in a single direction - not both directions simultaneously). You can _start_ from the v1.8 code, but have to modify it. Some of the modifications would be:
- switch from AC97 codec interface to I2S codec interface (i.e., 'mode')
- switch from passing codec commands via the AC97 interface to using I2C or GPIO for codec commands
- eliminate the number of channels moving in the opposite direction, including associated buffers
- increase buffer size for audio data due to 16->24 bit and 48kHz -> 96kHz
- add ACG support for new sample rates
- modify USB descriptors appropriately
- support sample rate command from the host
Regards,
Frank
Dear Frank,
Thank you very much for your prompt reply.
I have a problem when using the V1.8 firmware. Either I burn the original APP116.bin or APP124.bin or compile the project and create a new bin file, the device couldn't work as a usb audio device. I attach a picture of the device manager as below:
What problem it would be?
And I have another question, there are 2 folders in the V1.8 named Application and Rom. What's the usage of the folder named Rom?
According to your experience, how long it will take if we want to change the firmware to support 96kHz, 24bit?
Thank you very much for your help.
As to the TAS1020B not showing-up in Device Manager, I think it's because v1.8 expects to initialize the AC97 codec - which it doesn't find when running on your hardware - hence the code never gets to the program loop wherein it handles control transfers.
The 'Rom' folder has the code that is actually resident in the internal ROM on the TAS1020B. The 'Application' folder has code for an application that runs on a 'TAS1020EVM'; that code makes use of the ROM code 'framework'. The amount of program RAM on the TAS1020B is not large, so a typical application should attempt to make as much use of the ROM as possible.
Unfortunately, the TAS1020EVM is no longer available.
In order to build your application, you will need the compiler and linker from Keil for the 8051/8052. At least one OEM has used sdcc instead of Keil for this, but linking to the in-ROM code is more-difficult when using sdcc (i.e., you're on your own), since the ROM image was built using the Keil toolset. Also, sdcc produces different endian code than Keil produces.
I'd estimate two man-months of effort to convert from v1.8 to a version that has the capabilities you desire.
Thank you very much for your information. I'll start to study the code and will need your help if I encounter some problems. Thanks in advance for your help.