• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 461 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.

TLV320AIC3106EVM GUI, how tuse it in SPI mode?

gilbert vellet
Prodigy 175 points

Hi,

First I must say that the Software installation for TLV320AIC3106EVM is really outdatted and flaky. To think that each average Joe like me buying the EVM has to know that GUI rev 1.0.1 must be used instead of 1.0.0. Then that the NI-VISA runtime included is not compatible in Windows 7 64bit, so a new NI-VISA must be downloaded. And that the USB-MODEVM driver is never installed correctly on the first trial, and must be installed manually. So much time lost just to get the GUI to open correctly...

Now for my current problem. How to make SPI configuration working? All example script are in I2C mode. I read the appendix G of the user guide. I tried to write and read the register 00. In the command line interface I tried the following:

i spi8

w 00 FF

r 00 00.

I look into the Read data section, I see parameter commands. Where is the data read? Can you detail more how to use SPI mode ?

Another thing, the "INDICATOR UPDATES" does not work most of the time, in fact no readback stuff on the gui works. Like the DAC overflow, or the headset detection.

If i switch back to i2c mode and I run the script for stereo headphone. I can verify the audio path is OK with a headset. But all the nice knobs of the DAC and high power output do not reflect the actual state of the device. I find this very useless when trying to fine tune settings.

I guess it is futile to hope for a gui apdate any time soon.

  • 0
    TI__Guru* 84915 points

    Hi, Gilbert,

    The TLV320AIC3106EVM GUI has many functions that don't work properly, such the "INDICATOR UPDATES" function. So, we suggest do not use this function.

    Regarding the read data section, the SPI uses a different format to read data:

    r 00 xx yy : (r - read; 00 - only used for I2C address or MSB of 16-bit address for SPI; xx register; yy data bytes that will be read)

    Note: Remember that the xx register must be written in format ADDR(Bits 7:1) - R/W' (Bit 0). So, if you read the register 0x04, the xx value must be 0x09 (last bit must be '1' for read).

    For example, if you want to read 5 bytes from register 15, the line code would be:

    r 00 1F 05

    Please take a look of the following picture for details. The first 3 bytes (marked in red) refer to the read command and the number of bytes that will be read. Then the bytes marked in blue contains all the data values of the registers 15, 16, 17, 18, 19. They coincide with the default values of datasheet.

    Additionally, you must remember to configure the jumpers JMP10, JMP11 and JMP12 to use the SPI mode. Please take a look of the 2.2.2 TLV320AIC3106 Jumper Locations section for details.

    I hope this helps you. If you still have questions, please let me know.

    Best regards,
    Luis Fernando Rodríguez S.

  • 0 in reply to Luis Fernando Rodriguez S.
    Prodigy 175 points

    Mr Rodriguez,

    Thanks to your help, I can now read and write bytes in SPI mode with my TLV320AIC3106EVM.

    Based on what you said, a lot of the GUI is not working. Any GUI software update coming soon? Do you have a list of what is working? About all the knobs and switch, is it safe to assume they should work. And that only the visual feedback is defective? Is there a way to preload the position of the knobs and switches based on a configuration script? This way I could finetune a configuration and see the effect on the gui at the same time as observing the audio signal. And then save the knobs positions into a new script.

    Finally transmit to your boss a message to say that I am very disappointed by the EVM software package. For me the software should never have been released in that state. It is not even at the level of a beta release. There is no errata, or warning about all the bugs. You waste your customers time on easily avoidable problems. It is not what I expect from a prestigious company like as TI. ( Even if I am not happy, I still think that TI make great ICs)

    Best regards,

    Gilbert Vellet

  • 0 in reply to gilbert vellet
    TI__Guru* 84915 points
    Hi, Gilbert,

    I apologize for the problems caused by the GUI functionality. The indicators don't work correctly the most part of time. So, we suggest to read the flags by the command-line interface. It is the best tool to know the correct value that the indicator should show. The rest of the functions work properly and the EVM can be used correctly with the other windows and buttons.

    Thank you for the suggestions that you provided. I will notify about this issue to avoid any problems in the future.

    Best regards,
    Luis Fernando Rodríguez S.