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.

TPA6304Q1EVM: EVM's Default Device?

Part Number: TPA6304Q1EVM

PurePath Console, when asked to make a USB connection to the EVM board using the radio button in the lower left corner, concludes that the TPA6304 is configured as device B with no ganging.  

My natural tendency is to conclude that the EVM's designer wanted the board to self-configure as device A, not B.

If I do a USB disconnect using the lower left radio button, select device A, then USB reconnect, PurePath again chooses device B.

The schematic says the pull-up on the /FAULT pin is 5k ohms in series with an LED.  Is this the pull up current that specifies device B?

Can I confirm that the device is B by reading a register?  Which register?

Thanks.

Jim Olson

Indianapolis, IN US

  • Hi Jim,

    As the board designer, I actually didn't want the board to self-configure as device A. Well I did but I got it mixed up in my head so it's now device B. 

    We designed the GUI to autodetect what state the slave address the device is setup as. This is determined during startup when the GUI looks for the ACK (acknowledgement). It first looks at device A, then if it doesn't find it, looks for device B. That way if the customer wants to use this GUI on their own board they can with either slave address. 

    Best Regards,

    Robert Clifton

  • The esteemed Mr. Clifton!  Thanks for the quick response.  And the Box'ed copy of Purepath last Friday night.

    Roger on the default device B.  I can take it either A or B at this stage in my product's development.

    However, your last sentence confused me.  How would any TPA6304 customer use the PurePath GUI on his own board design? 

    I created my TPA6304 "breakout board" because I assumed that the firmware in the dev board's XMOS part (if not the actual XMOS LSI itself) are unavailable to product engineers like me.

  • Hi Jim,

    If they are able to connect the I2C to an external debugger then they can do some debugging using the GUI. Not that anyone would likely use PPC3 that late in development but it's a nice thing to have. 

    If you are needing the firmware we could talk offline and see what how we can support you.

    Best Regards,

    Robert Clifton