• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 41 subscribers
  • Views 541 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.

CC3235MODSF: uniflash com port selection

user6378938
Expert 1200 points

Part Number: CC3235MODSF
Other Parts Discussed in Thread: UNIFLASH,

Please enlighten me how we can chose the COM port in the UniFlash GUI for flashing the boards on our PCBs.

So far went through all the menus but only found "connect" button that responds with "Auto detection failure".

Thus auto detection does not work, neither the can I manually select the com port:

a) by default

b) when auto detection fails

How we suppose to use this tool with boards that have no JTAG?

  • 0
    Guru 80815 points

    Hi,

    Please read this.

    Jan

  • 0 in reply to Jan D
    Expert 1200 points

    Thanks, this helped.

    I found this thread and saw it is an old one.
    The referenced wiki page still describes the UniFlash 4.x.x and there is nothing in the uniflash 6.1 manual about this web based GUI that works together with a command line batchfile.

    Really strange that one needs to browse through forum and deprecated/"end of support" wiki pages to get an answer for TI tool that has a manual and lists this batchfile as a CLI tool while actually it opens the same browser interface that UniFlash GUI.

    Anyway, it worked. Now I only need to figure out why the JTAG/SWD interface is disabled till we flash the first time a service pack and/or an app with uniflash no matter what SOP pins we select...so i guess back to forum browsing for someone having the same issue.

  • 0 in reply to user6378938
    Guru 80815 points

    Hi,

    I don't know where you see issue with documentation. At product page for CC3235MODSF you find swru469 where at chapter 7.5 is command gui_cfg described.

    Your issue with JTAG/SWD is likely that you not have switched device into development mode at Uniflash.

    Jan

  • 0 in reply to Jan D
    Expert 1200 points

    Chapter 3-4-5-6 Use of graphical interface

    Chapter 7 - Command line.

    Chapter 7.5 gui_cfg (without explanation)

    If that isn't confusing I do not know what is.

    Devices are in development mode when UniFlash connected the first time.

  • 0 in reply to user6378938
    Guru 80815 points

    Hi,

    If you have confident that device is still in development mode (you should check this by Uniflash - you can upload here screenshot of Uniflash when you are connected to device) it is likely a hardware issue (e.g. wrong design of your board).

    Jan

  • 0 in reply to Jan D
    Expert 1200 points

    I used the CC3235MODSF module only the JTAG the power pins and SOP pins are connected, no circuit or board is involved.

    Just tried to erase the external flash (using FlashCenter - totaphase spi tool) and it seems if it is empty the JTAG/SWD connection is locked out.

    When I connect to the device with the UniFlash it shows that the device is in debug mode. Once I download a service pack (then restart the device) the JTAG gets reenabled. 

  • 0 in reply to user6378938
    Guru 80815 points

    Hi,

    This is expected behaviour. JTAG/SWD is unlocked only when at sFlash is uploaded image in development mode. If sFlash is blank or there is a image in production mode, JTAG is not enabled.

    Jan