• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 32 subscribers
  • Views 677 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.

Using LDRAunit with Code Composer

Mike Ashman
Intellectual 430 points
Other Parts Discussed in Thread: CODECOMPOSER, HALCOGEN

We purchased LDRAUnit from Texas Instruments and are using it to analyze our code that will run on the Hercules. I am running Code Composer V6.0 but it looks like LDRAUnit only allows me to select Code Composer V5.0.

Is there a guide on configuring LDRAUnit to use the correct version of Code Composer? According to some LDRAUnit doc I have read I should be able to use a CodeComposer project file to setup the analysis, include file paths, etc...but this option doesn't seem to be available to me.

I was told by LDRA that since we purchased from TI I need to work with TI on configuration.

  • 0
    TI__Intellectual 1835 points

    Mike,

    How did you purchase LDRAunit?  Was that part of a Compliance Support Package?  The LDRAunit included with that package is only intended to be called and used by the TAU (Test Automation Unit) in the CSP - and only to be used for the software (HALCoGen or Diagnostic Library) from TI.  In this case it should be working and don't think it needs to use CCS at all.  This is the only way I can think of that you could have purchased LDRAunit from TI, so what you are trying to do really isn't supported by this LDRAunit.  Again, it was only intended to be invoked by the TAU in the CSP.  Hope that makes sense.  If you need more capability from LDRA, then you would need to discuss with them about getting a full license of their tools.

    Let me know if I have any misunderstanding of what you are trying to do.

    Regards,
    Roy

  • 0 in reply to Roy Haley
    Intellectual 430 points
    Hello Roy,
    Thank you for your response. I think I understand now, we did purchase as part of a CSP and thus I guess can only test the Halcogen code. I will discuss with LDRA.
    I do have a question on the use of TAU however, or I can open a new thread. In our Halcogen code we add USER_CODE sections and these can contain global variables defined outside of the Halcogen code. For example when we receive new SPI data we will put some data in an operating system queue which will wake up a thread that lives outside of the Halcogen code. When I try to run TAU on this code it complains that the queue is undefined, which of course it is because the queue is defined in another C file. Is there a way to work around issues like these?
  • 0 in reply to Mike Ashman
    TI__Genius 14205 points

    Hi Mike,

    As Roy mentioned that intention of TAU is to test HALCoGen generated file. If you have additional file needed for testing, this has to be placed inside the "source" folder that HALCoGen generates or it has to be placed in the same folder as test case xls ( take Test\ADC1\FuncTest as reference.). 

    The reason is we auto generate the make file, which will pick all files in the above mentioned 2 folders.

    You can have few more controls using the Build option.txt file, where you can provide the include paths or include libraries etc.