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.

XDAIS on C672x

Other Parts Discussed in Thread: TMDXDAISXDM, OMAP-L137

Hi,

I am a beginner to XDAIS and need some help in running an XDAIS example projects on C672x platform.

For XDAIS Developer's Kit, I downloaded v5.21 from location mentioned on "http://focus.ti.com/docs/toolsw/folders/print/tmdxdaisxdm.html". For testing, I opened one of the example projects, "auddec1_copy.pjt" under "..\xdais_5_21\examples\ti\xdais\dm\examples\auddec1_copy\pjt" in CCS. When i try to build this project, it gives me below error:

"auddec1_copy.c", line 17: fatal error: could not open source file "xdc/std.h"

But when I download XDAIS v5.21, I dont see any XDC folder. Please let me know if I need to install something additional for XDC. One of the documents mention to follow sprued6.pdf for XDC insatllation. I did go through that document and it talks about altering the mak file. But I dont see any mak file inside the downloaded example proejct. Please let me know what am I missing here.

Thanks,

Megha

 

 

  • I think you need to add a couple -D options to your compiler options to look like this:

    cl6x -Dxdc_target_types__=ti/targets/std.h -Dxdc_target_name__=C64

    FYI, I got that info from here.
  • Hi Brad,

    Thanks for the reply. I did try to add that to command line, but it gave me below command line error:

    Command-line error: invalid macro definition: c16x -Dxdc_target_types__=ti/targets/std.h

    Also as I am using C672x should i define

    -Dxdc_target_name__=C64
    as
    -Dxdc_target_name__=C67

    I think the issue is that there is no std.h file in the installed v5.21 of xdais.
    Please let me know if I am missing anything.

    Thanks
    Megha

     

  • Perhaps you should update to the latest version of XDAIS.  The version you're using is almost 2.5 years old.  I believe you need to download the XDC tools as well to get the std.h file.

  • Thanks Brad,

    Finally after installing the latest versions of XDAIS and XDC tools, I was able to compile the examples provided in XDAIS.

    I have another question regarding development platform to be used for XDAIS. I need to develope my algorithm to meet XDAIS requirements and on a C672x platform. For that do I need to use PADK? Is it possible to use SDK on a DA710/708 EVM?

    Thanks,

    Megha Daga

     

  • I'm not sure I fully understand what you're asking.  Since a XDAIS algorithm is a "pure" algorithm (i.e. doesn't touch peripherals) then it shouldn't matter what you use to develop it.  It could be PADK, DA710 EVM, simulator, etc.  The core is the main thing you need to have correct.

    Brad

  • Hi Brad,

    If I understand right, XDAIS algorithms are generally library projects and I will be getting a library as output. For real time testing of that library is it fine to test it with any platform: PADK or SDK? Is there any document which talks about real time testing of XDAIS algorithms?

    Thanks

    Megha Daga

     

  • Hi Brad,

    Is there any document which talks about how to integrate a XDAIS algorithm into PADK? I trying to design a XDAIS compliant algorithm and want to run the real time test on PADK. I have been looking for documents on this, but have been unable to find any yet.

    Thanks

    Megha

     

  • Megha,

    To be honest, I think there is a bit of a gap in terms of XDAIS support with c672x.  Back when we had the c6713 we used something called "the Reference Frameworks" as the run-time environment into which you plug your XDAIS algorithm.  That software has been superseded by "Framework Components" and "Codec Engine" which still support your XDAIS algorithms from the past, but in a revised run-time environment.  As I look at the release notes for Framework Components and Codec Engine it looks like they have been tested on newer devices like OMAP-L137 (which is same as c6747 + ARM9), but they were not tested on c672x.  So I think you would either need to get the older "Reference Frameworks" and forward port to 672x or else you can get the newer Framework Components and backport to 672x.

    Perhaps the best option (if it's possible for you) would be to move your development to c674x.  That way you can use the newer software and it will be easier to get supported.

    Brad

  • Hi Brad,

    XDAIS documents suggest to use a tool "Component Wizard" to create a XDAIS compliant algorithm. This tool should be present in CCS but I dont see it either in CCS v3.1 or v3.3. Is it suppose to be bought seperately?

    Also can you please point me to the Reference Frameworks and the newer Framework Components you talked about in your previous e-mail.

    Thanks

    Megha

     

  • The latest version of the eXpress DSP Component Wizard is bundled with version 4 of xDAIS.

    You can find it at: https://www-a.ti.com/downloads/sds_support/targetcontent/XDAIS/xdais_4_0/index.html

    Having a solid reference/example is often sufficient. In this case you can see http://tiexpressdsp.com/wiki/index.php?title=XDAIS_sample_algorithm 

    Sample code is attached to that article.

    Reference Frameworks can be found here: https://www-a.ti.com/downloads/sds_support/applications_packages/index.htm

    The "xDAIS Framework Components "can be found here: http://software-dl.ti.com/dsps/dsps_registered_sw/sdo_sb/targetcontent/index.html

  • Hi Brad,

    I am now able to create XDAIS compliant algorithm using Component Wizard. Now I am trying to test the code using QualiTI.

    QualiTI is suppose to be present in the xdais_4_0 link you provided. I am going through qualiti_ug.doc present in the qualtiti folder inside this xdais release. As per the XDAIS link this QualiTI release works outside CCS and uses Perl Scripting. For that I downlaoded the latest versionof ActivePerl. The qualiti_ug.doc talks about some qualiti.ini file and systest (under the section Configuring QualiTI on Windows), whichI am unable to find inside the xdais released folder.

    Is there something else I need to download for QualiTI? I believe there is a version of QualiTI which I can use with CCS. Can you please let me know where can I find that and if thsts copatible with xdais 4.0.

    Thanks

    Megha

  • Megha,

    The only thing you should use from 4.0 is the utility to generate your XDAIS algorithm.  Once you've gotten that far I would switch everything to the latest XDAIS version.  The latest XDAIS will have a much better version of the QualiTI tool.  Many enhancements/fixes have been made.

    Brad

  • Hi Brad,

    I did download latest version of XDAIS from "http://software-dl.ti.com/dsps/dsps_registered_sw/sdo_sb/targetcontent/XDAIS/xdais_6_00/index.html", but again this folder is quite different from the one in XDAIS 4.0 release and I still dont see QualiTI listed on CCS tool.

    Please let me know if I am missing anything here.

    Thanks

    Megha

     

     

  • You must have missed the startqti.bat file in the root directory of the xdais installation.  Open that file for editing and it describes where more info can be found.  I think it only depends on having a XDC_INSTALL_DIR variable defined.

  • Thanks Brad, it works with the batch file.

    Megha

     

  • Hi,

    No I am not building with -g

    Megha

     

     

     

  • Hi Brad,

    I have converted one of my algorithms to XDAIS compliant and am running it on PADK platform. There are a couple of issues I found:

    1. I have a c file inside my code which has all the global variables/arrays declared. As per XDAIS requirements, all the variables/arrays should be in .far section. Hence I placed all the variables/arrays in ".far:module". When I test this library on QualiTI tool, it gives me an error to XDAIS Rule 26 saying founda '.bss' section in this file. I am not sure why is the section going in .bss when I define it to be in .far? Also when I build this library on PADK it gives me below warning:

    warning: Detected a near (.bss section relative) data reference to the symbol _T_Attack_Coeff defined in section .far.  The reference occurs in xxx.obj (algLib\abc.lib), section .text:filter, SPC offset 00000890.  Either make the symbol near data by placing it in the .bss section, or make the references to the symbol far.  For C/C++ code use 'far' or 'near' modifiers on the type definition of the symbol or compile with the  --mem_model:data switch.

    and to avoid this warning I have to put the variable (giving the warning) in bss section. Once I put it in bss section, the warning goes off, but the problem with the QualiTI tool remains. I also notice that I ges this warning only with variables and not with arrays. I am not sure I understand this behaviour.

    2. When I test the librray on QualiTI tool I also get error with Rule 20. I have tested XDAIS examples on QualiTI tool and all of them give this error. I tried to build and test the release mode library too, but the error is same.

    Please let me know if you have any ideas on the baove issues.

    Thanks

    Megha

     

  • Please start a new thread with a more specific subject for any follow on questions.

    MeghaDaga said:

    Hi Brad,

    I have converted one of my algorithms to XDAIS compliant and am running it on PADK platform. There are a couple of issues I found:

    1. I have a c file inside my code which has all the global variables/arrays declared. As per XDAIS requirements, all the variables/arrays should be in .far section. Hence I placed all the variables/arrays in ".far:module". When I test this library on QualiTI tool, it gives me an error to XDAIS Rule 26 saying founda '.bss' section in this file. I am not sure why is the section going in .bss when I define it to be in .far?

    Look in your map file to see which files have allocations in bss.  The offending variable might be somewhere else that you overlooked.

    MeghaDaga said:

    Also when I build this library on PADK it gives me below warning:

    warning: Detected a near (.bss section relative) data reference to the symbol _T_Attack_Coeff defined in section .far.  The reference occurs in xxx.obj (algLib\abc.lib), section .text:filter, SPC offset 00000890.  Either make the symbol near data by placing it in the .bss section, or make the references to the symbol far.  For C/C++ code use 'far' or 'near' modifiers on the type definition of the symbol or compile with the  --mem_model:data switch.

    and to avoid this warning I have to put the variable (giving the warning) in bss section. Once I put it in bss section, the warning goes off, but the problem with the QualiTI tool remains. I also notice that I ges this warning only with variables and not with arrays. I am not sure I understand this behaviour.

    You could set memory model as far or you could define that specific variable as far.

    MeghaDaga said:

    2. When I test the librray on QualiTI tool I also get error with Rule 20. I have tested XDAIS examples on QualiTI tool and all of them give this error. I tried to build and test the release mode library too, but the error is same.

    Please let me know if you have any ideas on the baove issues.

    Thanks

    Megha

    http://tiexpressdsp.com/index.php/QualiTI#Rule_20:_must_declare_worst-case_stack_requirements