• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 30 subscribers
  • Views 393 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TAS3204 won't boot from EEProm

Christopher K.
Intellectual 450 points
Other Parts Discussed in Thread: TAS3204

Dear ladies and gentleman,

I'm trying for quiet a time now to get a TAS3204 DSP working and after some discarded pcb layouts I finally produced a layout with low noise and a working TAS3204. Or at least I believe that the TAS is working since the I/O test configuration streams audio through the DSP. The problem is that I can't persuade the TAS to follow an EEProm programming.  My biggest problem is to figure out, where the failure is located. On a oszillioscope I can see a datatransfer between the EEProm and the TAS, but that's about it. I have attached my test configuration from the pure path studio hoping, that you could check it and maybe try to program it into a TAS3204 to see if this part is correctly done so far.

Greeting from Germany

Christopher

  • 0
    TI__Expert 3215 points

    Christopher,

    My understanding is that you're using your own board but somehow you couldn't make TAS working properly. 

    I took a look at your .pfw file, looks pretty stright forward. But I don't have access to an EVM now, so can't try it.

    I have couple of suggestions:

    1) If you haven't tried it on a TAS3204 EVM, try it to see if it works there.

    2) simplify the .pfw, make it a stereo, pass through to see whether that makes any difference.

    3) check whether you've run the I2C command to configure the audio channels properly.

    If nothing helped, I'll try this on my EVM when I get back to my office, hopefully next week.

    Susan

  • 0 in reply to susan xu
    Intellectual 450 points

    Dear Susan,

     

    thank you for your reply. You where right, when you assume that I'am using a self developed board. As I wrote before is my most rescent problem the fact that the TAS won't execute the EEProm program. It allways starts with the default configuration and streams audio unaltered from the inputs to the outputs. So from this side, I would say that the TAS is working and only the programming is at fault. What I did so far is to write the hex generated with Pure Path Studio sequential into the EEProm and nothing more. You're suggesting that I should check any I2C commands to configure the audio channels. Well I'am not sure on what you are refering with this. I couldn't find any informations regarding this topic in the datasheet of the TAS3204. Another problem of mine is, that I don't have a EVM Board for this project. So it would appreciate if you could check my attached files with one of your eval-boards. This would eleminate the hex file as a failure source.


    best regards,

    Christopher

  • 0 in reply to Christopher K.
    TI__Expert 3215 points

    Christopher,

    I just built the .pfw you uploaded and downloaded to my EVM and it runs fine and I also tried to configure the parameters for the components at run-time, also no problem.

    I understand why you don't have those I2C configuration examples since you don't have an EVM.

    The one I am using is the default that comes with board, as I uploaded. on PPS manu-> tools->I2C command tools and put that file there and let it execute when resetting.

    Hope you could resolve your issue soon.

    Susan

     

  • 0 in reply to susan xu
    Intellectual 450 points

    Hello Susan,

    thank you for you efforts. It's good to know, that the configuration isn't the problem, now I would assume that the eeprom content itself is the problem. What I have done so far is to write the hex file generated with pps sequential into the eeprom starting at adress 0, maybe something goes wrong in this process. The next thing I will do is to use a system controller to take a look at the failure registers of the tas via i2c. Maybe I can find a clue on the problem through this.

    I also would like to thank you for adding the configuration file. My problem with that is, that I'am not sure if it is helping me in any way cause I don't have a direct interface to my tas. Will these commands be embedded in the hex file because if I click exectue now in the I2C command tools windows it tells me, that no hardware is connected? So it seems that I'am missing an interface that the EVM has.

    Greetings from Germany,

    Christopher