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.

EK-TM4C123GXL: Usage as USB-Serial(I2C and SPI) Bridge

Part Number: EK-TM4C123GXL
Other Parts Discussed in Thread: TPS65987, TPS65987DDKEVM, TPS55288, TPS65987DDK

Tool/software:

Dear Sirs and Madams,

We purchased EK-TM4C123GXL(TIVA) as a USB-Serial Bridge for the TPS65987.

We connected it according to the TPS65987DDKEVM circuit diagram, but it doesn't work. Is it not possible to use it as a USB-Serial Bridge in the state it is purchased?

By default, the RGB User LED lights up in random colors.

Is the programmed software different between the TIVA mounted in the TPS65987DDKEVM and the EK-TM4C123GXL(TIVA) in the factory-shipped state?

In the initial state immediately after purchase, the TIVA's USB device appears to be not recognized by the computer.

/* EK-TM4C123GXL User's Guide URL */

Tiva C Series TM4C123G LaunchPad Evaluation Kit User's Manual

/* TPS65987DDKEVM User's Guide URL */

TPS65987DDK Evaluation Module User's Guide

Regards,

MM

  • Hi MM,

      Sorry for the late reply as I was out of office and just got back.

    By default, the RGB User LED lights up in random colors.

      The EK-TM4C123GXL LaunchPad is a general evaluation board for TM4C123 device. The board is preprogrammed with a simple example to blink the LED. There is no firmware on the brand new board to act as a bridge to the TPS.

       You will need to install the USB-Serial Bridge firmware on the LaunchPad in order to communicate with the TPS. I'm not familiar with TPS product. I will forward your question to the TPS product experts as to where to get the firmware. 

  • Hi MM,

    As Charles mentioned, a different firmware image is needed to be loaded to the Tiva in order to work with the TPS devices. Unfortunately, we donn't share the firmware with customers.

    In general, end customer applications should not need a TIVA, it is primarily for EVM usability.

    Is there a specific feature you are looking for? I may be able to suggest alternatives.

    Thanks and Regards,

    Chris 

  • Hello Chris,

    We created a board equipped with USB Type-C PD Alternate mode, and we need to configure the registers connected to TPS65987 by I2C and write to the flash connected by SPI.

    Since the USB-Serial (I2C, SPI) bridge function is not necessary for the actual board, we were purchasing a separate EK-TM4C123GXL as a USB-Serial bridge for debugging.

    Is it possible for you to provide us with the TIVA firmware installed in the TPS65987DDKEVM?

    USB-C-PD-DUO-EVM: FTDI functions installed in EVM - Power management forum - Power management - TI E2E support forums

    How does everyone else set the TPS65987 registers and write to the SPI flash?

    Regards,

    MM

  • Hi MM,

    Apologies for the confusion the in previous thread. I'm not sure why the TIVA was recommended previously, but as I mentioned, it does require an separate firmware image to be loaded and we currently do not provide it externally.

    It depends customer to customer, but solutions I've seen and can recommend:

    SPI Flash:

    • Use an EEPROM Programming tool that is compatible with the SPI Flash
      • An example of what we use is the TotalPhase Aardvark. There are cheaper options available, but I have not tried them.

    I2C register:

    • Have an MCU/EC act as I2C controller
    • Use a I2C adapter tool to interface between PC and PD controller.
      • the Aardvark can also do this.

    Thanks and Regards,

    Chris

  • Hello Chris,

    We have to use "TPS65987 Application Customization Tool"  to design the USB Type-C PD controller.

    Based on the method you described, We understood that if using the TPS65987 Application Customization Tool, only the third-party Aardvark is recommended.

    To avoid confusion, We think it should be stated in the EVM manual or data sheet that although FTDI and TIVA are implemented in the EVM, they are not recommended as USB-Serial bridges (adapter) for other than the EVM.

    The customer has to purchase Aardvark, which is more expensive than EVM, just for this.

    Why are you no longer able to provide us with firmware images for TIVA?

    I have to explain this to our customers.

    MM

  • Hi MM,

    Based on the method you described, We understood that if using the TPS65987 Application Customization Tool, only the third-party Aardvark is recommended.

    To avoid confusion, We think it should be stated in the EVM manual or data sheet that although FTDI and TIVA are implemented in the EVM, they are not recommended as USB-Serial bridges (adapter) for other than the EVM.

    The customer has to purchase Aardvark, which is more expensive than EVM, just for this.

    Understood, please also realize that you do not need an Aardvark to flash the SPI flash and to read/write I2C to the part. The only feature I can think of that requires the TIVA/FTDI/Aardvark is the debug mode, which can be replicated by manually implementing I2C reads/writes. The 

    Why are you no longer able to provide us with firmware images for TIVA?

    I am not sure what information came from the previous thread, but when I spoke to the engineers who manage the TIVA image, it's not something we ever have provided for this part. The reason we cannot share it is the firmware image was not developed or cleared to be shared as a customer-shared fw image. It was something meant to be packaged on the EVM as a development tool, but never approved as a separate firmware image that can be shared and used in production.

    Thanks and Regards,

    Chris

  • Hello Chirs,

    I would like to confirm what you mentioned below:

    /*****************************************************************************************************/

    Understood, please also realize that you do not need an Aardvark to flash the SPI flash and to read/write I2C to the part.

    The only feature I can think of that requires the TIVA/FTDI/Aardvark is the debug mode, which can be replicated by manually implementing I2C reads/writes. 

    /*****************************************************************************************************/

    We are trying to operate the TPS65987 according to your documents and manuals.

    We were able to obtain documents for controlling the TUSB1046 and TPS55288 that connect to the TPS65987, but these only describe how to configure the TPS6598x Application Customization Tool.

    The TPS6598x Application Customization Tool only supports FTDI (FT4232), TIVA, and Aardvark.

    And there is also no register manual for the TPS65978.

    I don't think we can set the TPS65987 functions that we actually want to use on the GUI or write them to flash at a stage before debugging, so what do you think?

    The bin file for writing to the flash memory has not been created.

    The TPS65978 is designed to run on the flash memory, so it is not connected to the Ext MCU via I2C.

    How should we design this device?

    TPS6598x Application Customization Tool (Rev. C)

    Regards,

    MM

  • Hi MM,

    The TPS6598x Application Customization Tool only supports FTDI (FT4232), TIVA, and Aardvark.

    And there is also no register manual for the TPS65978.

    I don't think we can set the TPS65987 functions that we actually want to use on the GUI or write them to flash at a stage before debugging, so what do you think?

    You should be able to find the trm here.

    One thing to mention is we recommend new designs move to the TPS65987DDK. It is a P2P feature compatible part that has the latest bug fixes and patches for the TPS65987 family. We do recommend moving to the DK version if early enough in the design phase. It should not require any changes in Hardware, and only requires moving to the "DK" option in the App Config Tool.

    We are working on moving the design resources from the TPS65987DH page to the TPS65987DK page, but are still in the process of moving the documents.

    The primary use for the APP Customization Tool in production is to generate the binary.

    After the APP tool has been configured with the desired settings, you can save the .bin file using "Binary->Save Bin" and choosing the Full flash option. Once you have the full flash binary, you can use any tool at your disposal to program the binary to the EEPROM. We do not require that the tool is a FTDI, TIVA, or Aardvark.

    The only time the FTDI, Tiva, or Aardvark is required is if you are flashing directly from the GUI (Using Binary->Flash from current project).

    I don't think we can set the TPS65987 functions that we actually want to use on the GUI or write them to flash at a stage before debugging, so what do you think?

    I can think of a couple options for programming the SPI flash:

    1. Find a 3rd party SPI EEPROM programmer (something like the Aardvark) to flash the binary file to the SPI EEPROM. Unfortunately, I've only ever used the Aardvark as that is what we have on hand, so do not have any cheaper recommendations.
    2. If you have an EVM, you may be able to use the onboard TIVA/FTDI to program a new SPI flash by swapping it with the populated one.

    Option 1 is the easier of the two.

    Thanks and Regards,

    Chris

  • Hello Chris,

    As advised, we are using the "DDK" version of the TPS65987 device.

    I already understood that the TPS65987EVM is equipped with FTDI and TIVA (the latest vetrsion also has Aardvark) and allows access to the TPS65987 device and SPI flash.

    However, I also understood that if I would like to do something similar with the board we created, only Aardvark can support it too.

    The problem could be solved if I could obtain the TIVA firmware mounted on the TPS65987DDKEVM, but since this is not possible, I will consider purchasing Aardvark.

    I mistakenly thought that TIVA had USB-Serial functionality already written in it, like STLINK(STMicro) and KitProg(Infineon).

    Regards,

    MM

  • Hi MM,

    Understood, apologies for any confusion on the tooling. I agree that the Aardvark is a good path forwards.

    Thanks and Regards,

    Chris

  • Hello Chris,

    I understood this issue.

    I will close this thred.

    However, it is a pity that we users cannot obtain the sample code of TIVA mounted in TPS65987DDKVM.

    Is it no good even if we sign an NDA?

    Regards,

    MM