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.

TAS5624ADDVEVM: TAS55XX GUI vs. PurePath v1.16

Part Number: TAS5624ADDVEVM
Other Parts Discussed in Thread: TAS5558, TAS5624A, , TAS5612A, TAS5624

I have a TAS5624ADDVEVM which I would like to use to evaluate TAS5558 and TAS5624A.

I am aware that the documentation recommends to use "TAS55XX GUI" as configuration software. This was already clarified in other forum posts a few years ago.

But when I tried this one, it failed to read from TAS5558 via I²C. Instead of 0x6C it reads just 0x00 from register 0x00. No error message is shown that would point to a problem. Even when I disconnect

InputUsbBoard3  from TAS5624DDVEVM (so TAS5558 is no longer attached) tool reads still 0x00 and no errors are shown. Seems that something is wrong and reading by I²C is not working as expected at all.

I checked device manager and the board is correctly listed HID device. So it seems to be no driver issue.

Then I tried PurePath v1.16 and selected target "TAS5612A".

Here I can succesfully read 0x00 as 0x6C.

As PurePath v1.16 seems to be the more recent software and the diagram seems to match TAS5624ADDVEVM pretty well, I wonder whether TI can officially comment, whether it shall be ok to use it instead of "TAS55XX GUI" for TAS5624ADDVEVM?