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.

Code with no Errors will not link



I have been running with CCS4.2.4 for months with no problem.  Came in this morning and can not link a project that linked yesterday.  The console shows only warnings (no errors) and I get

gmake: Target `all' not remade because of errors.

I believe something was downloaded last night from our IS department, however I have not been able to find out what they did. 

Why would CCS think there are errors when none exist?

Thanks,

    Jerry

  • Hi Jerry,

    can you provide more details?  It would be good to know what changed on the pc/environment. Some intial things to check/try.   Can you provide screen captures/ the console output, which should show the errors.

    - try a fresh workspace

    - try to determine where the changes the last day or so came from/are

    What target do you use?

    Best Regards,
    Lisa

  • Hi Lisa,

      Thank You for the help. I have heard nothing back from our IT department.  Everytime they do an upgrade, they are overloaded with problems.  I Installed CCS5.3.0 and was able to get passed the linking problem.

      I am using the XDS100V2 connected to a C6745.  I also use this setup to develop on a piccolo F28069.  The C6745 is the crisis du jour.  I can get the Test Connection to run on the C6745 with no errors, however I get:

    IcePick_C_0: Error connecting to the target: (Error -1265 @ 0x0) Device ID is not recognized or is not supported by driver. Confirm device and emulator configuration is correct, or update device driver. (Emulation package 5.0.872.0)

    When I attempt to start the debugger.  Looks like I need an emulator upgrade also.  Looking at it now.

    Thank You,

       Jerry

  • Hi Jerry,

    very glad to hear you got past the one issue.  Thanks for the update.  Unfortunately this new issue I suspect comes from a bug.  I do not believe your target (unforutnately despite documentation) is supported with the xds200.  At the very least not yet.   We are both working to update the documents and also looking to see about adding this support going forward.

    I hope this helps clarify and all the best with development.

    Best Regards,
    Lisa

  • Lisa,

      I am more confussed.  CCS 4.2.4 with the XDS100v2 worked on the C6745 until my PC was messed up.  Are you saying this setup with CCS 5.3.0 is not supported?  If so,

      is there a CCS 5 that will work with the XDS100v2 on a C6745 and a F28069 or should I try to reinstall CCS 4.2.4?

    Thank You, Jerry

  • Hi Jerry,

    ah, sorry for some reason I misread and thought you mentioned xds200 instead ov 100v2.  This should certainly work.  Can you provide any further information/diagnostics?   Do you get the error with all projects/workspaces?  Any details would help.

    Best Regards,
    Lisa

  • Hi Jerry,

    is your F28069 a controlSTICK?  Are you using the same configuration to debug the C6745? I wonder if the connection is failing because: a) use of the exact same target configuration file (.ccxml) or b)  trying to connect to the C6745 using a standalone XDS100 but the controlSTICK is still connected to another USB port on your PC (that would confuse CCS)

    I am also available for a webex.

    Best Regards,
    Lisa

  • Hi Lisa,

     The F28069 is a board we developed and is not connected.  I am using a different .ccxml file and different workspace for each target.  As mentioned above, I get this error.

    IcePick_C_0: Error connecting to the target: (Error -1265 @ 0x0) Device ID is not recognized or is not supported by driver. Confirm device and emulator configuration is correct, or update device driver. (Emulation package 5.0.872.0)

    What does Error 1265@0x0  mean?

    Is Emulator package 5.0.872.0 the one I need to install or the one I have?

    How do I check the device ID and figure out why it is not supported or or recognized?

    How/where to I update the device driver?

     

    Thanks, Jerry

  • Hi Jerry,

    the 5.0.872.0 is the one you have.  My v5.3 installtion has the same under TI Emulators version, but let us try reproducing things here. The ICE PICK message comes from before the DSP is connected and the Device ID message means nothing specific, but typically come for configuration or device errors.

    Have you run any update searches from 5.3?

    I will be back as soon as I have had a look at a few further things myself.

    Best Regards,
    Lisa

  • Hi Jerry,

    I have been working with the team here but these connection issues are very hard as it could be hardware, setup, or driver for example.  I have also pulled in some further colleagues on this for you.  I am trying!  We successfully use this setup daily here.

    Running a search on e2e yields an unusual solution from a customer (see below). However, this customer is using a C55x and did something absolutely crazy by soldering the termination resistors in the XDS100 cable - they should be on the board instead according to the wiki page linked at the thread. 

    http://e2e.ti.com/support/dsp/tms320c5000_power-efficient_dsps/f/109/t/114983.aspx


    Can we confirm wether your  C6745 board was running functionally  with CCSv4.2.4?  If not,  it is possible this is a hardware issue (the termination resistors mentioned).  If you started to get this error only after upgrading to v5, then quite honestly almost anything goes. It may still be a hardware issue only uncovered by the updated device driver (shipped with v5) or a misconfiguration specific to the C6745 device (we have literally just verified again with a sister device C6747 and it works fine as I am able to connect it here).

    Can you isolate anything further?   Does the board still work in v4?  Or did whatever change from the last couple days take v4 functionality down as well?  Do you have another pc to try?  Can you share any connection details?

    Best Regards,
    Lisa

  • Hi Jerry,

    another thing I just thought we can double check.  Can you send us the feature details, just to be sure you install did pick up the correct version.  This is Help->About Code Composer Studio->there is an installation details button.   I don't suspect to see anything suspicious but might be worth a double check.

    Best Regards,
    Lisa

  • Hi Lisa,

    The 4.2.4 setup was running fine for months before a download from our IT department.  This tells me the hardware is good. What I installed shows CCS version : 5.3.0.00090, TI Emulator :5.0.872.0,  Spectrum Digital Emulators: 5.2.0.03

    The XDS100v2 I have been using is s/n94Y-D 1052. It has a sticker with X1B_1101155. It also shows a assy 512640 rev -. When I attempt to start the debugger I get:

    IcePick_C_0: Error connecting to the target: (Error -2131 @ 0x0) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.0.872.0)

    I reset and tried again also slowed down the TCLK and got the same result.  The device register is still a question.

    I plugged in another XDS100V2. s/n94Y-D 1225. Sticker X1B_1207208 assy 512640 rev c and get the following:

    IcePick_C_0: Error connecting to the target: (Error -151 @ 0x0) One of the FTDI driver functions used during the connect returned bad status or an error. The cause may one or more of: invalid emulator serial number, blank emulator EEPROM, missing FTDI drivers, faulty USB cable. Use the xds100serial command-line utility in the 'common/uscif' folder to verify the emulator can be located. (Emulation package 5.0.872.0)

    So it looks like when CCS is installed with a XDS100v2 bundle license it only works for the emulator that was connected. There also appears to be a XDS100v2 software version dependancy.  How do the emulator software and CCS connect and what does CCS expect to see?

    Worst case I reinstall 4.2.4 and see what happens.  I was hoping to get the CCS5.

    Thanks, Jerry

  • Hi Jerry,

    there is no license dependency on a specific xds100.   Have you tried installing the ftdi drivers?  Have you double checked the device manager?  The reason I suggested checking v4 again is to try and isolate whether the update or change to your environment in general created some kind of driver/hardware conflict etc  which could be the case if v4 stopped working.  Or whether this is specific to v5 in which case we plough forward debugging v5 setup etc.

    Best Regards,
    Lisa

  • HI Jerry,

    a couple further diagnostic things

    - would you please rung the xds100serial.exe app in the \common\uscif directory and post the results?

    - can you confirm whether the test connection button works?

    Best Regards,
    Lisa

  • The test connection works.  I tried many JTAG speeds and it worked at all the speeds.

    xds100serial:

    VID/PID -> 0403/a6d0    Type -> XDS100v1/v2     Serial# SDU23XB4  Description -> Texas Instruments Inc. XDS100 Ver 2.0

    Hardware configuration is fine.  Where would I get ftdi drivers?

    When trying to connect I get:

    IcePick_C_0: Error connecting to the target: (Error -1265 @ 0x0) Device ID is not recognized or is not supported by driver. Confirm device and emulator configuration is correct, or update device driver. (Emulation package 5.0.872.0)

    Thanks, Jerry

  • Hi Jerry,

    yes everything indicates your emulator is working fine.   This most likely leads to a possible configuration or board issue.  Did you import the project in v5?  If so, would you try regenerating the ccxml file?  Would you verify it used the same settings as the one you previously had running with v4?  Would you be willing to send it offline? (My user name is a link you can use to create a conversation or friend request).  Can you also confirm the the target you are connecting to?  Would you be able to send the Test Connection results?

    Sorry for the questions, but distance debug can be difficult.  If necessary, as mentioned, a webex at some point is also on offer.

    Best Regards,

    LIsa

  • Lisa,

    We found my problem!  The original code was developed on another target board with one C6745 and a CPLD on the JTAG in CCS4.  We then went to our final board with 2 C6745s, 2 CPLDs, and 1 Ethernet Phy.  Without changing the ccxml file it connected and worked with one C6745 which was the first device in the chain.  I have not started working with the other C6745 which clearly would not have worked.  It appears CCS5 is less forgiving of a wrong JTAG chain.

    Thanks for your help,

    Jerry

  • HI Jerry,

    very happy to hear!  Thanks for the update and all the best with development.

    Best Regards,
    Lisa