I am too the point that I have to write code for the TAS1020B and would like to make sense of what I am reading. In the firmware package there are 2 directories, ROM and Application.
What use is the ROM code? When do I need to modify it and how do I load it?
What is the purpose of the Application code? How do I load it without wiping out the ROM code or vise versa?
I am using the tlv320aic3254evm-k board. I can remove the address select jumper from the eeprom and cause the device to come up in DFU mode. Next I put the jumper back on and using the DFU utility I can upload a file and reset the board. I am uploading the compiled ROM code. I compiled the ROM code, converted the hex to bin, ran this through the header utility with the VID=451 PID=1020 marked the eeprom type as application (won't take input file otherwise), uploaded result through DFU utility.
Now what?
If I re-plug the device it comes up as nothing, so I must be doing something wrong even though the utility doesn't complain. I examine the output of the header utility and see that a header was added but who knows if the parameters are correct, the explanation of what is necessary is non-existent.
Can you provide the necessary header.exe input parameters to get a device file to load and run?
Next I guess that I need some type of application? I can compile and hex2bin the application. I also need to run the binary through the header program, is the header.txt file provided in the application directory correct? If so, I run app116 binary through header and get another output file with the header prepended.
How am I supposed to upload this application to the device if the device is running the previously uploaded ROM code, it isn't in DFU mode anymore?
Ultimately I will have an application running with VID=415 and PID=1020, what driver will recognize this and allow it to be used as a sound input/output device?