• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 81 subscribers
  • Views 741 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.

F28335 with experimenter's kit not recognized at all in Windows Devices and Printers

Arthur Jones


I have a TMS320 F28335 control card that I have been programming with a TI experimenter's kit using Matlab/Simulink and Code Composer Studio v3.3. I also have an F28027 launchpad that I have also been working with.

For some reason the 28335 control card is not consistently recognized by Windows consistently. The launchpad always is recognized immediately when plugged in. The 28335 control card is not always consistent about being recognized by Windows, sometimes when it is plugged in, it works well, other times it does not appear as an icon in Windows Devices and Printers. Sometimes it will work, randomly after being plugged in for an hour or more, without doing anything to it.

The problem is that there never seems to be a consistent reason why it is not being recognized. I have attempted to flash this device, unsuccessfully, so I am not sure if that could be related to the problem also.

It may sound like a beginner's mistake, but if anyone has had anything similar I would appreciate the help.

  • 0
    TI__Guru 57255 points

    Arthur,

    The issue sounds like some kind of weird driver conflict issue, the FTDI chip not working well/Windows is not playing well, or a power issue.

    1) Can you try closing CCS, restarting the computer and trying to use a new CCS workspace
    2) It may be worthwhile to reprogram the FTDI chip.  I've seen this get rid of Windows+FTDI issues in the past.  See the following post:
    http://e2e.ti.com/support/microcontrollers/c2000/f/171/t/21086.aspx
    3) Have you added any extra components to the Docking Station baseboard for experimentation?  If so, might you be running into an issue with power budget?

    Has your device ever been able to connect after the flash programming failure?


    Thank you,
    Brett

  • 0 in reply to Brett Larimore

    I have been able to program the board RAM a few times after the flash programming failure. I have been trying to reprogram the FTDI chip as described in the link, except the device is not being recognized at all anymore. Previously Windows would recognize the device after waiting for a while (sometimes about 15 minutes or so, sometimes over an hour). Now it seems that Windows is not viewing the device at all. There are no external devices attached to the experimenter's kit (except the f28335 control card).

    I also have a launchpad F28027 device and a Piccolo controlSTICK device, and both of those devices are detected immediately when plugged in to any USB drive on the computer. I also have another computer that I have set up the same, and the same thing happens.

    I believe it may be a windows problem, but I am lost as to why the other devices work fine, on both computers, but this device doesn't even appear in the Windows Devices and Printers list as an unknown device. I also don't understand why it was working previously, at least after being plugged in a while, but no longer works at all.

    Thanks again for the help, anything you can think of would help.

  • 0 in reply to Arthur Jones
    TI__Guru 57255 points

    Arthur,

    Thanks.

    Does the FTDI programming utility detect the FTDI chip each time you hit 'Scan for Available Devices'? 
    -If so, then I'd think that the issue is likely some very weird thing with Windows.  Based on what you've said, I cannot think of a reason why this case in particular would be happening.
    -If not, then I'd lean toward it being Windows or potentially hardware.  In particular I'd recommend desoldering JP2 to look for any potential scraping/wear underneath, etc.  Then I'd resolder JP2 on once done and try again.

    When you do the FTDI programming I would recommend Scanning, Erasing, Programming, and then Scanning again.  You'd maybe then need to unplug the USB cable and replug it in for Windows to detect and install the proper driver.  If this isn't what you're doing, this may help.



    Thank you,
    Brett

  • 0 in reply to Brett Larimore

    I started looking into whether this is a hardware problem, and I believe it is.

    When I touch my finger on or around the FTDI chip on the experimenter's board, Windows acknowledges the device. After retrying this many time, I have found that sometimes I can get the device to show up as an unknown device, sometimes XDS100 working with errors, and sometimes XDS100 working correctly. I probably will have to just buy a new Experimenter's Kit, unless you know some common point of failure that I could try to fix this.

    I am not sure what caused the device to malfunction, as I only had it sitting on my desk, and didn't have any device attached to it that could provide power. Any testing I did involved using the 3.3 V reference on the board, so I don't think overvoltage on the device is the problem.

    Anyways, thanks for the help, I think I'm just going to buy another board.

    Arthur

  • 0 in reply to Arthur Jones
    TI__Guru 57255 points

    Arthur,

    A final thought: is J8 on the 'Docking Station' populated?  If it is, take off the jumper.

    Other than that, hardware may in fact be your issue.  JP2 would be my first place to look.  After that I'd suspect a dry solder joint (potentially on DA1, U1, U3, or U4).

    Based on the intermittent nature of the problem I'd think the board is probably somewhat easily fixable if you can find the issue. 

    If you find the cause let me know.


    Thank you,
    Brett