• Locked Locked
  • Replies 13 replies
  • Subscribers 55 subscribers
  • Views 7027 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.

CC3200 Lauchpad drivers not working after FT_PROG flashing

Anonymous
Anonymous
Other Parts Discussed in Thread: UNIFLASH, CC3200, ENERGIA

Hello,

I have two CC3200, one Rev 3.2 and the other Rev. 4.1. I had used FT_Prog previously to solve issues related to Uniflash not recognizing the devices, but now the drivers are not working. I tried different methods to force the installation of the drivers, but none seems to work. I attached an image of the devices connected. Windows automatically installs a driver called Dual RS232 when I connected the devices.


I already tried using FTCLean with no luck. I also tried using a different computer. I was going to try Linux Ubuntu but was unable to install Uniflash, I don't have experience with Linux, if anyone can help me with that. The bin file does nothing at all, even running as root. 

I know the Launchpad is working because it's running the "blink" example I uploaded before using FT_Prog, so the problem is the FTDI. I'm able to see the Launchpad as two COM ports if I enable Load VCP. but I'm unable to get any drivers working. I also tried the FTDI D2XX drivers, no luck. I'm using Windows 10 if that helps.


I tried searching for related issues in the forum, but no solution found.

  • TI__Guru**** 171224 points

    Hi,

    When you used the FT_Prog, did you have a template to properly program your FTDI device? The reason of my question is the Device manager shows that your FTDI device is using the standard FTDI VID/PID (and perhaps other settings), therefore chances are it will not work properly with CCS/Uniflash.

    Just for your reference, check attached the template I got from my CC3200 Launchpad.

    Hope this helps,

    Rafael

    (edit: file removed. Check an updated file in a post below)

  • Anonymous
    Anonymous in reply to desouza

    Hi Rafael,


    I followed the instructions from this site. And downloaded the provided FTDI Template (File:CC3200 LP3 DUAL.zip). I do see some differences in the templates content. I would try reflashing it, but FT_PROG is not detecting the devices, even if they show up as COM ports. Can you give any suggestion on how to proceed?

    Regards,

    Pedro

  • Intellectual 485 points
    I have the same issue with you.
    I dont have the solution for using FT Prog again, but you can use Uniflash with Virtual Com port via Load VC of Serial B and set baud rate to 921600
  • in reply to Anonymous
    TI__Guru**** 171224 points
    Pedro,

    Unfortunately I can't tell much about why FT_PROG cannot talk to your device, but I never used this utility in Windows 10. Perhaps you need to run it with admin privileges? I would also try to connect it to a different USB port or even a different PC to see if the device can be recognized. Also, don't forget about the possibility of a faulty USB cable - it is a rare event, but it happens from time to time.

    The page you linked is empty, therefore I can't comment on the procedure itself but it is rather unusual to have to program the FTDI device unless you are creating your own JTAG debugger or a development kit is non-operative.

    All in all, unfortunately I can't help much in this case. Perhaps the experts in the CC3200 forum have seen a similar scenario and could help with this?

    Regards,
    Rafael
  • in reply to desouza
    TI__Guru**** 171224 points

    Pedro,

    Update: a colleague just came with the same problem as you reported: his system couldn't find the FTDI device after he tried to re-program it using FT_PROG. I took his board and plugged on my PC, where it was promptly recognized and I was able to re-program it with the template below (the template previously sent was not properly recognized by the tool).

    Therefore my previous suggestions are still valid: try a different PC and see if you are successful.

    Hope this helps,

    Rafael

    CC3200LP.rar

  • Anonymous
    Anonymous in reply to Giang Hoang Quoc Duong35
    Hello Giang,

    You are right!! I was able to flash the board with Uniflash and upload a new a program. Now I just need to flash the FTDI, I will try with another computer as Rafael suggested.

    Thanks and regards,
    Pedro
  • Anonymous
    Anonymous in reply to desouza
    Hello Rafael,

    Which version of Windows or Linux were you using? Also how was the device identified when you first connected it. Did you enable "Load VCP"?

    Regards,
    Pedro
  • in reply to Anonymous
    Prodigy 10 points

    I also have the same problem. I am using CC3200 launchpad eval board. I have included the same  FTDI chip on the design as well. Hence I tried to follow the procedure given in this link http://processors.wiki.ti.com/index.php/CC31xx_%26_CC32xx_FTDI_Flashing . I have followed the exact procedure as mentioned. I was able to erase the EEPROM but when I wrote into it, and reset the board the board is no more getting detected.

    Can you please suggest so that I can get this working. We have used these parts in our final production version. I tried to contact FTDI support but they say that they would not be able to know what is CC3200 template written for.

    Thanks,

    Bhavya

  • Anonymous
    Anonymous in reply to desouza

    Hi Rafael,

    I tried with a WIndows 7 pc and the SDK drivers with no luck. Can you give more details on the configuration of your pc, is it 32 or 64 bits. I'm able to use Uniflash with the Rev 3.2 launchpad, but with the Rev 4.1 it'a not recognizing when I press the reset button. I did verified verified the cables and pin connection. Any suggestion?

    Regards,
    Pedro

  • in reply to Anonymous
    TI__Guru**** 171224 points

    Pedro,

    Unfortunately my colleague left his Launchpad at home (so I can't tell which Rev is his), but I ran the FT_PROG on a Windows 7/64 and my board was connected to a USB2.0 port (perhaps that may influence something). The FT_PROG version I am using is 3.0.56.245 (not the latest) but, since it works well I won't update it.

    Also, the only difference between the file I sent you and the one present in the page (I can see it now) is the automatic generation of the serial number. All the other settings are identical.

    When I plugged my blank board I saw the same device as you in the Control Panel: two USB to serial converters, both with VCP disabled.

    The screenshot below was taken when I ran FT_Prog on my colleague's board and clicked on Scan and Parse (F5). This was immediately after I connected his board and let Windows figure out the device drivers (I checked the Control Panel for a successful enumeration).

    Then, after programming the device with the template I sent yesterday.

    After that I was able to use the board without problems, even after disconnecting it from the PC.

    One thing I did after applying the template (and before disconnecting the board) was to Scan and Parse (F5) again. It should show the programmed board.

    If that does not work, I suspect there may be a HW issue. I am also forwarding this thread to the device group, so they may be aware if anything else may be happening with the newer boards.

    Hope this helps,

    Rafael

  • Anonymous
    Anonymous in reply to desouza

    Rafael, no luck with my device. Can Ti replace the Rev 4.1 board since I bought it about a month ago. Also I saw a post about flashing the board with another one, will that procedure work in this case?

    Regards,

    Pedro

  • in reply to Anonymous
    TI__Guru**** 171224 points
    Pedro,

    For returns you will have to check with whomever you purchased it from, although I think that an expert from the wireless connectivity MCU group could perhaps bring some additional ideas.

    Similar thing regarding the procedure; I never tried this on this specific Launchpad and unfortunately can't tell with 100% certainty it will work. However, if you properly connect the J8~J11 jumpers to the other board (and be careful to avoid connecting two output pins together), I don't see a reason why it would not work.

    Sorry for not being of much help,
    Rafael
  • in reply to desouza
    Prodigy 10 points

    Hi

    I'm facing also the same issue with my CC3200 LaunchPad xl rev 4.1.

    With several PC W7/64, I've never been able to debug or flash a program with CCS cloud. The VCP is shown, but CCS fails to connect to the board. I can although program it with Energia on OSX. So I dived into the documentation and made the assumption that FTDI may be faulty.

    So I decided to flash it following the instructions with the template provided, then I entered in trouble. Once erased, the EEPROM is shown empty but every time I try to program it with templates, it is not shown anymore by FT_Prog. Sometimes, I can reach it with an error by the command prompt and the scan command. Then I can erase the device which respawn on the FT_prog GUI. It is not systematic, but it works sometimes.

    Now the windows drivers detect the board like Pedro's and the VCP need to be set manually. Energia on OSX is showing an error after each program upload, but the program is working on the board

    So, I think there is an issue when trying to write to the FTDI EEPROM, but it is beyond my knowledge to go further.

    I just asked for a replacement board from TI, we'll see,  but it seems that rev 4.1 has an issue with FTDI.

    Regards,

    Eric