• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 30 subscribers
  • Views 639 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TUSB3210 clarifications?

Cristian Dolha
Prodigy 80 points

Greetings,


My name is Cristian Dolha (or just Chris), and i'm currently studying in Finland. I've been an audio DIY-ist for quite a few years now, and i've recently discovered / become interested in TI DSP chips. They, in combination with some class D amplifiers, would make for quite a potent and compact small-scale PA system for my band (among other things).

Now, on most (if not all) of the TI DSP EVM's, the TUSB3210 is used as a USB-I2C interface, and i'm guessing it has some sort of firmware in the adjacent EEPROM.

Is the firmware contained in the TUSB3210's EEPROM secret / confidential? It would be far more hassle-free to just hook up a small interface board to the DSP board, if/when i need to update some DSP settings, than to unsocket the DSP's EEPROM, put it in my programmer, write the new program and put it back.

I apologize in advance if the Audio forum was the wrong place to post this, but it seemed the closest match for my inquiry.

  • 0
    TI__Genius 14545 points

    Chris,

    Cristian Dolha said:
    Is the firmware contained in the TUSB3210's EEPROM secret / confidential?

     

        Are you looking for just the binary or the full source code? We have no issues with providing the binary.

     

    Drew

     

  • 0 in reply to dabuan
    Prodigy 80 points

    First of all, thanks for the swift reply.

    No, i'm not looking for the source code, since my knowledge of programming is almost zilch, so thanks for the binary file.

     

    Are there any issues i should be aware of? I mean, as far as i can figure, the TUSB3210 on the "TI input USB" board communicates with the DSP on the EVM, and the DSP's EEPROM is on the same I2C bus (... right?). So then, if i power-down after i send the DSP firmware to its EEPROM, disconnect the TUSB, and power up the DSP, it should work (as in get initialised, and so on), shouldn't it?

     

    Let me know if i'm missing something from "the big picture"...

     

    Chris

  • 0 in reply to Cristian Dolha
    TI__Genius 14545 points

    Chris,

    Cristian Dolha said:
    So then, if i power-down after i send the DSP firmware to its EEPROM, disconnect the TUSB, and power up the DSP, it should work (as in get initialised, and so on), shouldn't it?

     

    It theory it should work, however you may find that in practice you may run into other problems. Bus contention, Signal Integrity, etc... It's no guarantee that it will work, but the DSP should be smart enough to self load if you configure it correctly according to your application needs.

  • 0 in reply to dabuan
    Prodigy 80 points

    One last question:

     

    Is this the firmware for the USB-I2C, as it's implemented on the TI Input USB board? Or some "generic" implementation?

  • 0 in reply to Cristian Dolha
    TI__Genius 14545 points

    Cristian Dolha said:
    Is this the firmware for the USB-I2C, as it's implemented on the TI Input USB board?

     

        This is the firmware as it is implemented on the single boardTAS3x EVMs. I'm not sure about the Input USB board as I wasn't involved in this design, but I suspect it is the same this board is shipped with the TAS3108EVM2.

  • 0 in reply to dabuan
    Prodigy 80 points

    Thanks for the clearing up, once more. Now all that's left is hoping that perhaps someone involved with the separate input board will chime in sometime (soon?) :D

  • 0 in reply to Cristian Dolha
    TI__Genius 14545 points

    Chris,

    Cristian Dolha said:
    Now all that's left is hoping that perhaps someone involved with the separate input board will chime in sometime (soon?)

     

     I would personally choose a more proactive approach and try to program the EEPROM with the attached binary and test to see if it works or not.

    If it doesn't work, then your project will be gated by someone else, if it does work, you are free to carry on and finish your project.

  • 0 in reply to dabuan
    Prodigy 80 points

    I *was* gonna try that out anyway, but i have to finish a pcb design for it, etch it, put it together, etc.

     

    But thanks for all the support so far, anyway :)

  • 0 in reply to Cristian Dolha
    TI__Genius 14545 points

    Chris,

      Understood. I didn't mean to step on your toes, I don't like being dependent on others, so I was just sharing my personal preference.

  • 0 in reply to dabuan
    Prodigy 80 points

    No worries :) I appreciate the... encouraging and proactive advice ;)