• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 55 subscribers
  • Views 2123 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.

Trouble Connecting to CLA

Graham Henderson
Prodigy 200 points
Other Parts Discussed in Thread: CCSTUDIO

I am having trouble connecting to the cla of the 28035   We I try to connect I get the following error:

 

Warning:
Error 0x40000202/-1
Warning during: Memory, OCS,
This error was generated by TI's USCIF driver.

SC_ERR_TRIVIAL_NEG <-1>
This '-1' value should be returned only during code development.
It is a temporary value used when a more appropriate error value
has not yet been assigned. This is the most negative of the three trivial
error numbers that are used by USCIF adapters, drivers and utilities.


I/O Port = 0

Board Name: Blackhawk USB2000 - F28035 CLA Controller
Cpu Name: cla_0

Abort:        Close Code Composer Studio.
Retry:        Try to connect to the target again.
Cancel:        Remain disconnected from the target
Diagnostic:    Run diagnostic utility.

 

I am using

CCS 3.3.83.16

Blackhawk UBS2000  with the following drivers:

Driver Release v3.3.300.2, 23 JUN 2009

CCStudio v3.3 Driver files with USCIF v35.34.0.2 support

 

This driver will install Blackhawk emulator files for CCStudio v3.3 with  SR12 applied.  This update replaces all other CCS v3.3 driver releases.  No other patches are needed.

 

Also included in this update are:

  • Updated imports to support the new C2000 Piccolo B F2803x devices.

  • Added C6457 Imports.

 

 

SR12 Patches:

 

  1. C2000 CLA Support v3.3.0.0, 24 JUN 2009

    Installs only Blackhawk emulation files for CLA support and requires base SR12 driver release above to already be installed on your system.

 

 

  • 0
    TI__Guru* 92130 points

    Graham,

    Looks like you have installed service release 12 on the limited linker evaluation tools?  You shouldn't need service release 12 with this install. 

    One thing to check is that you have connected the debug window to the main CPU before you connect to the CLA debug window. 

    I'm going to move this post to the code composer forum so the experts there can help

    -Lori

  • 0 in reply to Lori Heustess
    Prodigy 200 points

    Lori:

    Note:  I am using a 035 ControlCard with the Experimenter Kit

    Yes...I installed 3.3-16 and then applied the Blackhawk service release followed by the driver update.  I tried a clean install of CCS and then applied the Blackhawk driver update only.  The Blackhawk driver update would not install due to missing files.  I applied the 12 service release and then reinstalled 3.3 16 and then applied the driver update.  The drivers installed, but I still get the following error:

    Open CCS - parallel debug manager opens

    Select TMS320C2800_0    and open CCS

    Select and open the example project     Example_2803xClaAdc.pjt

    Connect to TMS320C2800_0 - Successful

    Slect cla_0 and open

    Warning:
    Error 0x40000200/-1170
    Warning during: OCS,
    The driver is unable to communicate with the DAP. 0x00000000


    I/O Port = 0

    Board Name: Blackhawk USB2000 - F28035 CLA Controller
    Cpu Name: cla_0

    Attempt to connect to the CLA

    Abort:        Close Code Composer Studio.
    Retry:        Try to connect to the target again.
    Cancel:        Remain disconnected from the target
    Diagnostic:    Run diagnostic utility.

     

     

     

  • 0 in reply to Graham Henderson
    TI__Guru* 92130 points

    Graham,

    Unfortunately I don't have a blackhawk emulator here to try it out on.   Someone here more familiar with the error message may have some input, but I also suggest contacting blackhawk support.

    -Lori

  • 0 in reply to Lori Heustess
    TI__Guru* 92130 points

    Graham,

    I was copied on an email internally - it seems you are able to connect with the XDS100 but not able to run.  When you say you can not run please let me know if it is it the main CPU or the CLA?  

    If it is with regards to the CLA - make sure a task has been started.  If no tasks are running (ie the CLA is idle) then the run button will issue an error.  This is because there is nothing to "run".   To get a task started you can do the following:

    Insert an MDEBUGSTOP instruction as the first instruction of the task.  This is a CLA breakpoint.  Then rebuild the code and load it.

    Next you can start a task by writing to the force register MIFRC in the debugger window.  Bit 0 corresponds to task 1, bit 1 to task 2 and so forth.  The CLA should start execution and halt on the MDEBUGSTOP.  You can examine the MPC and the MIRUN registers to see that the CLA is executing and halted on the MDEBUGSTOP.

    Now you can single step the CLA or run to the next MDEBUGSTOP or to the end of the task.

    In the video section of the community area I posted a short video that introduces debugging the CLA in CCS 3.3.  This might help.

    http://e2e.ti.com/media/p/28209.aspx

    If it is the main CPU that you can not run, then I'm not sure what the issue is at the moment.   Please let us know.

     

  • 0 in reply to Lori Heustess
    Prodigy 200 points

    Lori:

    With help from Charlie and David I have been able to get the XDS100USB to connect to the Docking Station with our 28035 controlCard.  I have been able to open the CLA debugging window and stepped  through the CLA code.  I uninstalled CCS and the Blackhawk drivers and reinstalled just CCS 3.3.83.16.  Part of my problem was missundestanding the errors generated when you ask the CLA to run when it is already running.  Your video tutorial was very helpful and has answered some of my remaining questions.  One thing to note...if the image changes one must reload the symbols in the CLA window.

    I am working directly with Blackhawk to get the USB2000 working with release 3.383.16.  I will post the results for the benifit of others.

    Best,

    Graham...

     

     

     

     

  • 0 in reply to Graham Henderson
    TI__Guru* 92130 points

    Graham,

    Great news on being able to get up and running.  Also good point about reloading the symbols.

    I was able to get a BH USB2000 controller from Charlie.  I have run into trouble getting the BH driver patch for the CLA to install in the proper directory.  It is insisting on using the default CCS directory which is not where I have my CCS installed that supports the CLA.  So at this point I am faced with uninstalling my regular CCS and reinstalling the CLA version.  I can empathize with your frustration. 

    They may already be aware of this issue with your interaction with them.  I will see if our emulation group or marketing has a BH contact as well.

    Regards

    Lori

     

  • 0 in reply to Lori Heustess
    Prodigy 200 points

    Lori:

    Again....thanks to all for their support.  I have a clean install of CCS on a separate computer and will be verifying XDS100USB connection shortly.  After that I will apply the Blackhawk drivers per BH's instructions and give it a go. I will report my results to BH and have offered them any help they require to help verify the installation of the drievers with 3.3.83.16.  As stated, I will post my resuts to this thread.

    Graham...

  • 0 in reply to Graham Henderson
    TI__Guru**** 162315 points

    As a follow-up blackhawk recently posted an update to their driver package that adds improved support for CLA debug for their XDS510 class emulators.  You can get the updated drivers via the Update Manager in CCSv4, it should automatically check for it but you can always manually search for updates.  For 3.3 the drivers are on the blackhawk website.

     

    John

  • 0 in reply to Lori Heustess
    Prodigy 230 points

    Hi Lori!

     

    Lori Heustess said:

    n the video section of the community area I posted a short video that introduces debugging the CLA in CCS 3.3.  This might help.

    http://e2e.ti.com/media/p/28209.aspx

    If it is the main CPU that you can not run, then I'm not sure what the issue is at the moment.   Please let us know.

    When the version with CCS 4 ?

     

    Thanks, L.

  • 0 in reply to Loriano Galeotti
    TI__Guru* 92130 points

    Loriano Galeotti said:
    When the version with CCS 4 ?

    Loriano,

    CLA debug is available as of CCS 4.02. If you have an earlier version, then please download the latest or check for software updates.

    Refer to the following Wiki pages for generic Code Composer Studio v4 information:

    CCS 4 Information: http://tiexpressdsp.com/index.php/CCSv4

    CCS 4 downloads: http://tiexpressdsp.com/index.php/Download_CCS

     

    Debug for the CLA in CCS 4 is much like that in CCS 3.3.  The biggest difference is you no longer have to use the parallel debug manager.   Instead you click on the processor you want to control in the debug window.  I've placed a screenshot of this on the debugging CLA wiki page

    Cheers

    Lori

     

  • 0 in reply to Lori Heustess
    Prodigy 230 points

    Hi Lori!

    Lori Heustess said:

    Debug for the CLA in CCS 4 is much like that in CCS 3.3.  The biggest difference is you no longer have to use the parallel debug manager.   Instead you click on the processor you want to control in the debug window.  I've placed a screenshot of this on the debugging CLA wiki page

    I'm currently using CCS 4.1.0.02003 . I succeeded in connecting board.

    I found some troubles in understanding how to act for debugging a flash project (in particular, I discovered that I must disable "halt at program termination" and "enable CIO" to use breakpoints, and the concept that CLA and main CPU are to be run separately is not very immediate when using debugger and requires a lot of research in forum). 

    I see that CCS4 and 3 are very similar under this aspect, but when something is not working properly, you never know if maybe there is something that you haven't setup properly or a bug or whatever else.

    Having a tutorial for 4 would allow you to be confident almost on the debugger setup.

    I found a very strange bahaviour in debugger. Register view don't show correct values for floating data (I'm placing another thread for this issue).
    Another thing, would be nice to have symbols automatically loaded also in CLA device in debugger. I know that I can do it from "load symbol" menu, but it required me a while for realizing it and looking for a solution in the forum.

    Bye, Loriano.