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.

TPIC84000-Q1: TPIC84000-Q1 about the code issue

Part Number: TPIC84000-Q1

Hi team,

The customer is using TPIC84000-Q1. First, the customer needs some code routine. Then I provide the code routine that Darren Rollman provided.

Darren Rollman provided the code routine link is :

Please check the attachment for the code routine. Now the customer refers to the code routine to use the  TPIC84000-Q1 device to

communicate with MCU through SPI. The SPI commuincation code is as below. The customer would like to verify if the SPI communication is fine.

Would you support the issue? 

The SPI commuincation: 

// Wake up Message

MCU Send : {0x90, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};

TPIC84000 Send : {0x40, 0x00, 0xC4, 0xC1, 0x15, 0x0D, 0x00, 0xC0};

// Program Configuration

MCU Send : {0x90, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};

TPIC84000 Send : {0x20, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};

// Load Data

MCU Send : {0x30, 0xAA, 0xAA, 0xAB, 0x8B, 0x32, 0x99, 0x5A};

TPIC84000 Send : {0x20, 0x10, 0x00, 0x31, 0x30, 0x45, 0x43, 0x40};

// Program control and status register

MCU Send : {0x20, 0x02, 0x0E, 0x80, 0x00, 0x00, 0x00, 0x00};

TPIC84000 Send : {0x61, 0x55, 0x55, 0x57, 0x16, 0x65, 0x32, 0xB4};

// Start transmission

MCU Send : {0xD0, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};

TPIC84000 Recv : {0x40, 0x04, 0x1D, 0x00, 0x00, 0x00, 0x00, 0x00};

// ReadBack from device to get current measurments

MCU Send : {0xD0, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};

TPIC84000  Send : {0xA0, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};

// Wake up Message

MCU Send : {0x90, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};

TPIC84000 Send : {0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};

Best Wishes,
Mickey Zhang
Asia Customer Support Center
Texas Instruments

3441.TPIC84000 sample code.xlsx

  • Mickey,

    I do have some time to support, so I will try my best to resolve these customer issues. On a quick glance, there is an error with the following chunk of code:



    // Program Configuration

    MCU Send : {0x90, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};

    TPIC84000 Send : {0x20, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};



    This is actually just a duplicate of the wake-up message, and not the proper configuration. It should be:


    // Program Configuration

    MCU Send : {0x10, 0x08, 0x00, 0x18, 0x98, 0x22, 0xA1, 0xA0};

    TPIC84000 Send : {0x20, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00};



    This is actually one of the more important commands to send, as it sets which drivers to enable and for how many bits, the frequency divider, and for what gain. The code above will only turn on OUT1 with a gain of 19vpp. In order to actually get the 19V out, you must supply VS with at least 19+2V (the 2V is for headroom).

    If the customer is still having issues, I would like to see an actual scope plot of the SPI message, as well as the VS voltage and the OUT1 voltage. If they are using the EVM we provide, there are some jumpers that must be connected in order to see the signal. I will also check to make sure the readback from the device is correct. The first frame is a little suspicious...


    Regards,
    Darren
  • Hi Darren,

    Thanks for your help. OK. If the customer has still other question, I will post it on e2e forum.
  • Mickey,

    I think this question was answered, could you please mark as resolved?

    Thanks,
    SiG
  • Hi Sigfredo,

    Thanks for your help.