• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 82 subscribers
  • Views 892 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.

Product DC/DC LED Lighting. USB won't connect through GUI or Code Composer. DUPLICATE POST

Drew V
Prodigy 150 points
Other Parts Discussed in Thread: CONTROLSUITE

Product DC/DC LED Lighting. USB won't connect through GUI or Code Composer.

With test GUI I get " Could Not Connect. Please Check Connections. Have confirmed Baud setup, (8bit and 1 stop) have even played with even and odd.

With Code Composer I get no connection, and error C28xx: Error: (Error -1135 @ 0x3F6000) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Release 5.0.333.0) ""

Tried multiple USB ports, enable disable, all jumpers are correct per Quick start guide and

  • 0
    TI__Guru** 119500 points

    Drew,

    Do you still need help with this? Title says duplicate post but I don't see anything else from you.

    This sounds to me like the FTDI USB-JTAG/UART chip on your controlCARD is not programmed. It's very frustrating when this happens (just happened to me two weeks ago).

     

    You need to download the FTDI tools from their website. We have been using MProg but they just moved over to a new tool - it should work as well.

    You then have to connect to the board, scan, and program with the attached file. Sometimes you have to erase first.

     

    XDS100_wUART.ept
  • 0 in reply to ChrisClearman
    Prodigy 150 points

    Hi Chris,

    Yes, still need help,

    Haven't been coding in years, so some extra guidance is always appreciated.

    I am going to try your suggestion shortly, will let you know the results.

    Thanks

  • 0 in reply to Drew V
    TI__Guru** 119500 points

    here is the MProg 3.5 download

    http://www.ftdichip.com/Support/Utilities.htm

    you should be able to verify re-programming of the FTDI chip

  • 0 in reply to ChrisClearman
    Prodigy 150 points

    Hi Chris,

    Have hit a roadblock (after a day of trying), and hope you can help. (Know we have a time gap, so not expecting a reply tonight)

    Quick note, Opened up firewall for CCS, I had found some blocking. Have been playing with MSP430's (for a few months) and had no port or blocking problems. Am running Vista Ultimate (the computer had been collecting dust,, pulled of the shelf and dedicated it to just development) could Vista be a problem for CCS, and if so, bug fix or back to XP or up to 7?

    Current state.

    Have no program bugs on build or rebuild, but on debug I keep getting the same errors.

    Current RUN with another erase and reload of USB using FT_PROG (MProg replacement).

    STACK copy

    Lighting_DCDC [F2803x_RAM] - Texas Instruments XDS100v1 USB Emulator_0/C28xx [Project Debug Session]   
        Device   
            Thread [main] (Suspended)   
                0 main() at Lighting_DCDC-Main.c:253 0x008600   
                1 _args_main() at args_main.c:43 0x00954c   
        Texas Instruments XDS100v1 USB Emulator_0/C28xx (5:43:11 PM)   
        Texas Instruments XDS100v1 USB Emulator_0/C28xx: CIO (5:43:11 PM)   


    Texas Instruments XDS100v1 USB Emulator_0/CLA_0 [Non-Project Debug Session]   
        Disconnected Device   
            Thread [main] (Disconnected(Unknown))   
                0 <symbol is not available> 0x00000000   
        Texas Instruments XDS100v1 USB Emulator_0/CLA_0 (5:43:21 PM)   
        Texas Instruments XDS100v1 USB Emulator_0/CLA_0: CIO (5:43:21 PM)   






    OLDER RUNS

    Run in F2803x_FLASH


    Lighting_DCDC [F2803x_FLASH] - Texas Instruments XDS100v1 USB Emulator_0/C28xx [Project Debug Session]   
        Device   
            Thread [main] (Suspended)   
                0 main() at Lighting_DCDC-Main.c:253 0x3f6000   
                1 _args_main() at args_main.c:43 0x3f6f57   
        Texas Instruments XDS100v1 USB Emulator_0/C28xx (4:51:03 PM)   
        Texas Instruments XDS100v1 USB Emulator_0/C28xx: CIO (4:51:03 PM)   


    Texas Instruments XDS100v1 USB Emulator_0/CLA_0 [Non-Project Debug Session]   
        Disconnected Device   
            Thread [main] (Disconnected(Unknown))   
                0 <symbol is not available> 0x00000000   
        Texas Instruments XDS100v1 USB Emulator_0/CLA_0 (4:51:38 PM)   
        Texas Instruments XDS100v1 USB Emulator_0/CLA_0: CIO (4:51:38 PM)   

     

    RUN in F280x_RAM


    Texas Instruments XDS100v1 USB Emulator_0/CLA_0 [Non-Project Debug Session]   
        Disconnected Device   
            Thread [main] (Disconnected(Unknown))   
                0 <symbol is not available> 0x00000000   
        Texas Instruments XDS100v1 USB Emulator_0/CLA_0 (4:51:38 PM)   
        Texas Instruments XDS100v1 USB Emulator_0/CLA_0: CIO (4:51:38 PM)   


    Lighting_DCDC [F2803x_RAM] - Texas Instruments XDS100v1 USB Emulator_0/C28xx [Project Debug Session]   
        Device   
            Thread [main] (Suspended)   
                0 main() at Lighting_DCDC-Main.c:253 0x008600   
                1 _args_main() at args_main.c:43 0x00954c   
        Texas Instruments XDS100v1 USB Emulator_0/C28xx (5:06:48 PM)   
        Texas Instruments XDS100v1 USB Emulator_0/C28xx: CIO (5:06:48 PM)   

    Thanks for your efforts.

    Drew

  • 0 in reply to Drew V
    Prodigy 150 points

    Hi Chris,

    1. The application for the product will not be USB but TCP-IP, so I am not looking for a long term hard fix.

    2. As I mentioned, I haven't been coding for a while, but want to personally do proof of product (TI), and concept (ours) prior to development staff build (<30day time frame).

    Thanks again,

     

    Drew

  • 0 in reply to Drew V
    TI__Guru 57255 points

    Drew,

    Firstly, Vista should not be an issue with CCS.  I know we have several customers that are using CCS with Vista.  From a similar post I see that the MSP430 version of CCS may not install the xds100 drivers that this board requires.
    http://e2e.ti.com/support/microcontrollers/tms320c2000_32-bit_real-time_mcus/f/171/t/129991.aspx

    However, from the build notes that you posted in your message, it looks like there is no problem.  CCS seems to be connecting to the MCU alright.  If you follow the instructions found in the DCDCLighting how to run guide, you should get your CCS project to work correctly.
    C:\TI\controlSUITE\development_kits\Lighting_DCDC_vX.X\Lighting_DCDC\~Docs\Lighting_DCDC.pdf

    Finally, the DCDCLighting project is made to work out of FLASH.  I would recommend starting with the FLASH build.  I cannot remember if the RAM build compiles or works correctly.  I'll take a look tomorrow once I get back to my work computer if you're interested.


    Thank you,
    Brett

  • 0 in reply to Brett Larimore
    Prodigy 150 points

    Hi Brett,

    Thanks for some new directions. I need some more help.

    Background info, I originally loaded CCS (MSP430 limited version) with no changes, then I loaded the c2000 version of CCS without the board attached, and with separate workspace settings. Have 2 CCS's loaded, I use the each for their respected processors. ? Do you think I should just wipe clean and start fresh with just the c2000 version, and if so should I have separate workspace for each processor, or does it matter.

    Things seems to have gotten worse.

    Have lost TI USB drivers, they now show as USB Serial Converter A and B, and under ports when the board powers up it had shown 1 COM port and now it loads 2 (qty) COM ports.Noot loading the TI xds100 drivers, although they to be installed. (same ? as above, clean new install of CCS, sometimes it's easier to start fresh than keep chasing issues, I am up for your opinion)

    Here is the latest runs.

    Build 1

    Texas Instruments XDS100v1 USB Emulator_0/CLA_0 [Non-Project Debug Session]   
        Disconnected Device   
            Thread [main] (Disconnected(Unknown))   
                0 <symbol is not available> 0x00000000   
        Texas Instruments XDS100v1 USB Emulator_0/CLA_0 (3:55:09 PM)   
        Texas Instruments XDS100v1 USB Emulator_0/CLA_0: CIO (3:55:09 PM)   

    Lighting_DCDC [F2803x_FLASH] - Texas Instruments XDS100v1 USB Emulator_0/C28xx [Project Debug Session]   
        Disconnected Device   
            Thread [main] (Disconnected(Unknown))   
                0 <symbol is not available> 0x000000   
        Texas Instruments XDS100v1 USB Emulator_0/C28xx (3:57:46 PM)   
        Texas Instruments XDS100v1 USB Emulator_0/C28xx: CIO (3:57:46 PM)   

       
    Error connecting to the target: --XDS100v1 USB Emulator_0/C28xx-
    (Error -151 @ 0x0)
    This utility failed to open the adapter for a custom emulator.
    The adapter returned an error.
    (Release 5.0.429.0)

    On the Lighting_DCDC.pdf  I have some ?'s.


    INSPECT THE PROJECT Instructions (I think I'm missing something)

    Page 20 item 2.
    Confirm that the ADC and PWM1-8 peripheral clocks are enabled (lines 107-123)
    -----Code as supplied:   Lines 107-126------

    SysCtrlRegs.PCLKCR0.bit.ADCENCLK = 1;    // ADC
       //------------------------------------------------
       SysCtrlRegs.PCLKCR3.bit.COMP1ENCLK = 1;    // COMP1
       SysCtrlRegs.PCLKCR3.bit.COMP2ENCLK = 1;    // COMP2
       SysCtrlRegs.PCLKCR3.bit.COMP3ENCLK = 1;  // COMP3
       //------------------------------------------------
       SysCtrlRegs.PCLKCR1.bit.ECAP1ENCLK = 0;    //eCAP1
       //------------------------------------------------
       SysCtrlRegs.PCLKCR0.bit.ECANAENCLK=0;   // eCAN-A
       //------------------------------------------------
       SysCtrlRegs.PCLKCR1.bit.EQEP1ENCLK = 0;  // eQEP1
       //------------------------------------------------
       SysCtrlRegs.PCLKCR1.bit.EPWM1ENCLK = 1;  // ePWM1
       SysCtrlRegs.PCLKCR1.bit.EPWM2ENCLK = 1;  // ePWM2
       SysCtrlRegs.PCLKCR1.bit.EPWM3ENCLK = 1;  // ePWM3
       SysCtrlRegs.PCLKCR1.bit.EPWM4ENCLK = 1;  // ePWM4
       SysCtrlRegs.PCLKCR1.bit.EPWM5ENCLK = 1; // ePWM5 -(line 123)-
       SysCtrlRegs.PCLKCR1.bit.EPWM6ENCLK = 0;    // ePWM6
       SysCtrlRegs.PCLKCR1.bit.EPWM7ENCLK = 0;    // ePWM7
       SysCtrlRegs.PCLKCR0.bit.HRPWMENCLK = 0;    // HRPWM

    Am I to stop at line 123 ? Should I enable to EPWM7ENCLK.

    And the GPIO0 & 2-9 should be set as below (example)?

    //  GPIO-03 - PIN FUNCTION = LED String 2 PWM
        GpioCtrlRegs.GPAMUX1.bit.GPIO3 = 1;        // 0=GPIO,  1=EPWM2B,  2=SPISOMI-A,  3=COMP2OUT
    //    GpioCtrlRegs.GPADIR.bit.GPIO3 = 1;        // 1=OUTput,  0=INput
    //    GpioDataRegs.GPACLEAR.bit.GPIO3 = 1;    // uncomment if --> Set Low initially
    //    GpioDataRegs.GPASET.bit.GPIO3 = 1;        // uncomment if --> Set High initially
    //--------------------------------------------------------------

    Thanks,

    Drew

  • 0 in reply to Drew V
    TI__Guru 57255 points

    Drew,

    Yes, if you are continuing to have issues with CCS, I would recommend reinstalling it.  You can download it directly from here the link below.  If you're using MSP430 and C2000, the code size limited version may be good enough.  You'll need to see what type of code size you would need expect from your product.
    http://processors.wiki.ti.com/index.php/Download_CCS

    As for your question about the Lighting_DCDC.pdf document, the text is supposed to read "Confirm that the ADC and PWM1-5 peripheral clocks are enabled (lines 107-123).  I'll have the document fixed in a future release of controlSUITE.

    For each pin, the GPADIR bit only needs to be set if the GPAMUX register configure the pin as a GPIO.  If the pin is configured as PWM, the DIR bit is ignored.


    Thank you,
    Brett