• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 40 subscribers
  • Views 435 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.

Original question:

CCS/CC3235SF: Connecting the CC3235 to the CH340g with the correct SOP's to be toggled by Uniflash

CC3235SF: Creating a slimmed down version of the CC3235SF, general questions

Nicholas Hall1
Prodigy 80 points
Part Number: CC3235SF
Other Parts Discussed in Thread: TM4C1294NCPDT, , SEGGER, UNIFLASH

Hi Everyone, 

     I own a launchpad with the CC3235SF and on it there are two main chips, the CC3235SF itself and the TM4C1294NCPDT. My end goal is to make a slimmed-down version of the CC3235 on a smaller board but I'm wondering what the function of the TM4C1294NCPDT is? Judging from the document it seems this is just additional support for JTAG debugging? If I remove this and put the CC3235 on a custom board whatever software loading/debugging options do I have? Can I load firmware for the CC3235 onto a SPI chip via USB by a FTDI chip like an esp8266? If possible I would like the CC3235 to be on a standalone board with an SPI flash chip talking to an USB-to-COM to load my software from code studios. Thanks for any pointers!!! :)

  • 0
    TI__Mastermind 40965 points

    Hi,

    The TM4C chip on the launchpad is actually the XDS110 debugger that is used to connect the CC3235 to your PC for use with your IDE's JTAG debug mode. It is also used to provide USB to UART functionality, so the UART prints can be displayed on your PC for ease of development.

    The CC3235 does not need that XDS110 for any functionality, it is just there on the launchpad EVM for ease of development. For a custom board, having a set of test pins that connect to the JTAG pins and the UART output pins would be sufficient. From there, you can use another XDS110 (such as the one on a launchpad) or supported JTAG probe such as the Segger JLINK to connect to your custom board for software debug.

    As for loading firmware onto the CC3235, there are a few options:

    1. Load the firmware directly onto the external SPI flash using a SPI flash writer (note that the XDS110 isn't used for this)

    2. Load the firmware indirectly onto the external SPI flash, by using the Uniflash tool on your PC with a USB to UART chip (like an FTDI, or the XDS110) to communicate with the bootloader of the CC3235

    3. Load the firmware indirectly onto the external SPI flash, by using your own custom embedded programming tool to perform the needed bootloader commands to load the firmware using a UART device.

    A more detailed explanation of the possible methods can be found here: http://www.ti.com/lit/swra646

    Let me know if you need more clarification on loading code on your custom board or have any further questions.


    Regards,

    Michael

  • 0 in reply to Michael Reymond
    Prodigy 80 points

    Amazing amount of detail. I will let you know as I am actively developing a board. Thank you!!!