• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 246 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.

TAS5806MDEVM: Eval doesn't show up on I2C, no sound output

Kevin Jordan35
Prodigy 90 points
Part Number: TAS5806MDEVM
Other Parts Discussed in Thread: PUREPATH-CMBEVM, TAS5806M

I have an eval kit I cannot get working. I have 12v to J9/J10, and inject an external 3.3v line into the DVDD jumpers. I connect the SDA/SCL to a Raspberry Pi 4. With i2cdetect, I do not see either of the chips.

With the SCL/SDA jumpers disconnected to the TAS5806 devkit, I see this:

pi@raspberrypi:~ $ i2cdetect -y 1
    0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: 20 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --

With the SCL/SDA wires connected I see this:

pi@raspberrypi:~ $ i2cdetect -y 1
    0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: 20 -- -- -- -- -- -- -- -- -- -- -- 2c 2d -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- 54 -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

I assume 2c and 2d are the EEPROM. When I dump 2c and 2d I see this:

pi@raspberrypi:~ $ i2cdump -y 1 0x2c
No size specified (using byte-data access)
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 00 00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 ...?............
10: 01 00 00 00 11 00 00 00 00 00 00 00 00 00 00 00 ?...?...........
20: 01 07 09 01 00 40 02 00 00 00 00 00 00 00 00 00 ????.@?.........
30: 00 00 00 02 00 11 00 00 40 00 f9 04 00 20 80 00 ...?.?..@.??. ?.
40: 01 00 00 00 00 00 01 00 00 00 00 00 30 30 33 30 ?.....?.....0030
50: 07 00 00 00 00 00 00 00 00 00 00 00 00 f8 00 00 ?............?..
60: 00 00 00 00 00 00 00 a3 00 00 00 00 00 50 11 24 .......?.....P?$
70: 00 00 00 00 00 38 00 00 00 00 09 03 00 00 00 00 .....8....??....
80: 00 00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 ...?............
90: 01 00 00 00 11 00 00 00 00 00 00 00 00 00 00 00 ?...?...........
a0: 01 07 09 01 00 40 02 00 00 00 00 00 00 00 00 00 ????.@?.........
b0: 00 00 00 02 00 11 00 00 40 00 f9 04 00 20 80 00 ...?.?..@.??. ?.
c0: 01 00 00 00 00 00 01 00 00 00 00 00 30 30 33 30 ?.....?.....0030
d0: 07 00 00 00 00 00 00 00 00 00 00 00 00 f8 00 00 ?............?..
e0: 00 00 00 00 00 00 00 a3 00 00 00 00 00 50 11 24 .......?.....P?$
f0: 00 00 00 00 00 38 00 00 00 00 09 03 00 00 00 00 .....8....??....

Address 0x54 only returns FF for all addresses.

I do not see 0x58 or 0x5A (the addresses specified on the EVAL document). I'm also playing I2S data out of the Raspberry Pi, into the jumpers on the eval board and no audio is coming out the speakers.

Is something broken with both of the chips on the Eval board? What can I do to test to see if the 2 ICs on the eval board are working? Is the PUREPATH-CMBEVM board required to make the TAS5806 chips on this eval kit work?

Thanks,

--Kevin

  • 0
    Prodigy 90 points

    I figured out the 2c and 2d listed on the i2cdetect are the TAS5806 chips, the addresses are inverted.

    I still can't figure out how to get sound to play out of the TAS5806. Need help with sending the correct commands to have the audio come out of the speakers. I'm playing I2S data from the raspberry Pi, but nothing I do will allow the 4 Ohm speakers to play.

  • 0 in reply to Kevin Jordan35
    TI__Genius 14420 points

    Hello Kevin,

    We typically recommend the PUREPATH-CMBEVM when using the TAS5806MxEVM as it was not intended for standalone use and our PPC3 software configure the device using the PUREPATH-CMBEVM.

    In the TAS5806M datasheet we provide the Startup Procedure in section 9.5.3.1, if you are not using the PUREPATH-CMBEVM you need to make sure you are following the startup sequence in your configuration. Our startup sequence you need to bring up PDN to high once your power supplies are stable. From what you are describing PDN is floating on your HW setup so you need to make sure you have a connection for PDN and that it is following our startup sequence, otherwise the device is going to be in shutdown.

    Best Regards,

    Luis

  • 0 in reply to Luis Fernandes de Pina
    Prodigy 90 points

    I've tried following the section in 9.5.3.1 and I'm getting "Clock Faults" and "FS Error"s now.

    write: 0x1: 0x11 - Reset Chip
    write: 0x78: 0x80 - Clear Faults
    FS_MON: FS Error (reg: 0x37)
    Run Status: Deep sleep (reg: 0x68)
    write: 0x1: 0x0 - Remove Reset
    write: 0x78: 0x0 - Remove Clear Fault
    FS_MON: FS Error (reg: 0x37)
    Run Status: Deep sleep (reg: 0x68)
    write: 0x33: 0x3 - 32-bit
    FS_MON: FS Error (reg: 0x37)
    Run Status: Deep sleep (reg: 0x68)
    write: 0x3: 0x0 - Deep Sleep
    FS_MON: FS Error (reg: 0x37)
    Run Status: Deep sleep (reg: 0x68)
    write: 0x3: 0x2 - HiZ
    FS_MON: FS Error (reg: 0x37)
    Clock fault (reg: 0x71)
    Run Status: HIZ (reg: 0x68)
    write: 0x5c: 0x1 - coefficient
    FS_MON: FS Error (reg: 0x37)
    Clock fault (reg: 0x71)
    Run Status: HIZ (reg: 0x68)
    write: 0x3: 0x3 - Play
    FS_MON: FS Error (reg: 0x37)
    Clock fault (reg: 0x71)
    Run Status: HIZ (reg: 0x68)

    Is there something else I should be doing to start this chip? From what I can tell from my Oscilloscope, the Raspberry Pi is sending out I2S data. I tried changing the 32bit input to all the different settings and nothing worked.  

  • 0 in reply to Kevin Jordan35
    Prodigy 90 points

    Nevermind, I was using a buffering chip provided by XMOS and that ended up lowering the voltage of the BCK line. I removed that backpack and went direct to the Raspberry Pi, and the script above started working.