• State TI Thinks Resolved
  • Locked Locked
  • Replies 18 replies
  • Answers 1 answer
  • Subscribers 102 subscribers
  • Views 1770 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.

C5535 eZdsp for usb missing project files so debugger does not track source code

Jeff Sylvester
Prodigy 80 points

we have bought several C5535 EZDSP and we are trying to run C55_Connected_Audio_Framework_EZDSP However when trying to build the project in CCS4 using the included CD, the project is missing the file CSL_USB_IsoFullSpeedExample_Out.pjt and the compiler gives the message "This project contains unresolved buildable linked resources. It might not build as expected.  CSL_USB_IsoFullSpeedExample_ezdsp_Out.pjt" 

when I run the code in debug mode, some of the sources are missing, so I can only see dissassembly window, and I have no idea where the code is operating from.  Is this due to the missing .pjt file or is this a setting inside of CCS4.x

The readme file in the project install directory is this:

Product info:
   Name     c55-connected-audio-framework
   Platform C55XX_EZDSP
   Version  01.51.00.03
   Hash     d0adb146f543ca050cb2c852e41ff0ad49f31c8c
 
To build c55-connected-audio-framework project automatically, please follow the steps below:

1. Make sure CCS4 4.2.4 or later is insatlled in C:\Program Files\Texas Instruments\ccsv4
2. Make sure DSP/BIOS 5.41.10.36 is installed in C:\Program Files\Texas Instruments\bios_5_41_10_36
3. Make sure Codegn tool 4.3.6 or 4.3.9 for CCS4 is insatlled in C:\Program Files\Texas Instruments\....
4. Run C55_Connected_Audio_Framework-xx.xx.xx.xx-Setup.exe installer and select the install directory
5. cd to the install directory and run click2build.bat
6. The project will be created and the CCS4 workspace is at <install directory>\c55-connected-audio-framework

 

If the automatic build fails, please follow the steps below to build the project using CCS4:
 
1. Delete the .metadata directory mentioned above from the install if it exists
2. Open CCS4
3. Enter <install directory>\c55-connected-audio-framework as the workspace. Click OK
4. Window->Preferences. Expand CCS. Click RTSC.
5. In ISA family, select C5500.
6. In Code Generation Tool, select TI 4.3.6 or 4.3.9. If you do not see this option, you need to download the codegen tool from
 
 https://www-a.ti.com/downloads/sds_support/TICodegenerationTools/download.htm

7. Check DSP/BIOS and check 5.41.10.6 from the menu if you see it. If the selection of DSP/BIOS is successful,  click OK and go to step 11
8. Click Add. Check Select product version. Check if you see 5.41.10.36 in the menu. If yes. Select it.  Click OK.
9. If not, Check Select product from the file-system.  Browse the file system and search for the directory where DSP/BIOS 5.41.10.36 is installed (bios_5_41_10_36). Click OK.
10. If you do not have 5.41.10.36 installed. You need to download it from the link below
 
 http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dspbios/index.html
 
11. CCS4 will create a skeleton .metadata\ directory under <install directory>\c55-connected-audio-framework at this point
12. Use CCS4 to import from import and rebuild the project
13. Project->Import existing CCS/CCE Eclipse Project. Select <install directory>\c55-connected-audio-framework  as the search directory.
14. View->C/C++ Projects
15. Project->Rebuild All

 

  • 0
    TI__Mastermind 30140 points

    Hi Jeff,

    Lets try to get you up and running! It sounds like you did not import all of the projects.

    I am referring to build 01.52.01.00 for reference.

    When you open CCS, do you set your workspace to C:\c55\C55_Connected_Audio_Framework_ALL\c55-connected-audio-framework (or to equivalent path)?

    Next import all required projects by navigating to  File -> Import Project -> CCS -> Existing CCS...

    Next to the "Select search-directory" field, browse to the same c55-connected-audio-framework directory and click on OK.

    Several projects should be discovered and checked (like below).

    Click on Finish to exit from the Import Wizard.

    Next, right click on CSL_USB_IsoFullSpeedExample_ezdsp , and set it as the active project.

    Right click it and Build Project.

    For me, there are no errors.

     

    You can try the latest release (Click on Get Software): http://www.ti.com/tool/c55x-audioframework

    You can also refer to the Wiki page http://processors.wiki.ti.com/index.php/C5000_Connected_Audio_Framework

     

    Hope this helps,
    Mark

  • 0 in reply to Mark M
    Prodigy 80 points

    I still get the same error: I downloaded and installed the newer audioframework with this version: Product Info:

    Name C55_Connected_Audio_Framework

    Platform ALL

    Version 01.52.01.00

    Date Fri 10/28/2011

    Hash b2705c04b634227c0dcf25bbbf556ed8bda5b0e8

    I imported the project and it found the 8 listed ccs projects, I did a build all: and for every project it tells me *.pjt is still missing and for each project I get warning, this project contains unresolved buildable an linked resources. It may not build as expected.

    So I uninstalled CCS4.2.4 and reinstalled it and imported the projects again and it still gives me the same warning. I also installed on an entirely differnt machine that has windows XP and still get the same results.

  • 0 in reply to Jeff Sylvester
    TI__Mastermind 30140 points

    Hi Jeff,

    This warning should be ignored.

    CSL_USB_IsoFullSpeedExample_Out.pjt is a project file used by CCS3.3.

    Since you are using CCS4.x, this file has no effect - the equivalent project information is contained in the .project, .ccsproject, .ctdproject, and .ctdbuild files.

    These are located under ...\c55-connected-audio-framework\build\CSL_USB_IsoFullSpeedExample_ezdsp_Out\

    To get rid of the warning, right click on the .pjt file (highlighted in your screenshot) and delete it from the project.

    OR

    Edit the .project file and remove these lines:

            <link>
                <name>CSL_USB_IsoFullSpeedExample_Out.pjt</name>
                <type>1</type>
                <locationURI>COMMON_ROOT/build/CSL_USB_IsoFullSpeedExample_Out.pjt</locationURI>
            </link>

    I will file a bug against this warning and post this information to the FAQ of the Connected Audio Framework FAQ:

    http://processors.wiki.ti.com/index.php/C5000_Connected_Audio_Framework#Frequently_Asked_Questions

    Best Regards,
    Mark

  • 0 in reply to Jeff Sylvester
    Prodigy 80 points

    deleted project file and now no warring, however initial problem still there, can not see C source code in debugger, because symbol table or source files for BIOS are not linked?  not sure, all I get is dissassembly window.  I need to see OS source to be able to patch in a new task etc..

  • 0 in reply to Jeff Sylvester
    TI__Mastermind 30140 points

    When you load the program, CCS should open csl_usb_iso_fullspeed_example.c and the blue arrow shows that the Program Counter is at the beginning of void main(void).

    You can view the C/C++ project files tab by clicking on View --> C/C++ Projects.

    Make sure that you are loading the .out file that was built with the Debug configuration and not the Release configuration or you will lose debugging ability. (your screen shot looks like it is Debug). You can right click on the .out file and view its properties to be certain.

    After loading the program, you can open a file and set a break point. When you run the program, execution should stop at your breakpoint. From there you may single step, watch variables, etc.

    In the screen shot below, I am showing how to set a breakpoint inside of the BIOS task TSK_PbAudioAlg inside of app_audio_alg.c. The breakpoint stops execution after DSP/BIOS executes this task. Breakpoint must be inside of the while loop.

    Hope this helps,
    Mark

  • 0 in reply to Mark M
    Prodigy 80 points

    am I understanding this correctly?  I am supposed to manually open a C source file after Guessing what portion of the code is supposed to be running, then set a breakpoint, etc..   sounds pretty 2nd rate to me, all other tool set I have used. if you hit the run button, and then stop/pause execution, it (the tool) automatically loads the C source file so you can see where the code stopped,  currently CCS is not doing this for me.  as soon as I step out of main.c     I loose all ability to see anything.   Is my workspace or tool configuration missing something or set up wrong?   I would expect eclipse to operate the same as it does for other tools.  for example I use eclipse for designing C code inside of FPGA's and when I enter debug, it automatically finds the source code "C" file and opens it for me when I stop or pause the debugger from running.  and I can see exactly what function or subroutine I am currently in.  so it looks at the program counter, and goes and finds the C source file that matches where the program counter is currently pointing, I have verified that I am using the debug, output file, so there should be a symbol table and other "Un-Optimized" data there to link C source file to currently operating assembly instructions.  Are my debug settings incorrect??  In the attached picture, I just stepped through the main c file, and the program then jumps to DSP BIOS or RTOS and then I loose track of where code goes.  

  • 0 in reply to Jeff Sylvester
    TI__Mastermind 30140 points

    Hi Jeff,

    This project uses the DSP/BIOS operating system to switch between the various tasks that are run. DSP/BIOS is currently not open-source, so whenever you halt the program in an unknown state, it is very likely that the program counter is inside of these DSP/BIOS object-code routines.

    At 100MHz system clock, the utilization of the DSP is ~40% during audio playback and ~15% without audio. So there is a high probability that a halt during execution will stop inside of TSK_idle - no source code for this task.

    Also the Asynchronous Sample Rate Converter (ASRC) is provided as an object code library, so if you step through these instructions there will be no corresponding C-code displayed.

    You can step through the execution of the program by setting a breakpoint inside of the task that your are interested in - like TSK_PbAudioAlg.

    Alternately, you can view the state of DSP/BIOS after an execution halt by opening the ROV (Runtime Object Viewer). Open ROV by clicking on View -> Other -> Analysis Views -> ROV

    The screen shot below shows the ROV window indicating that the DSP/BIOS execution is inside of the TSK_idle (after randomly halting execution)...

    DSP/BIOS Resources:

    DSP/BIOS Users Guide: http://www.ti.com/lit/ug/spru423h/spru423h.pdf

    DSP/BIOS Wiki: http://processors.wiki.ti.com/index.php/Category:DSPBIOS

    DSP BIOS Debugging Tips: http://processors.wiki.ti.com/index.php/DSP_BIOS_Debugging_Tips

     

    How would you like to customize this project? We may be able to offer some tips to speed up your development.

    Most people insert their own application code inside of app_audio_alg.c where there are comments:

            /*                                    */
            /* Insert Record audio algorithm here */
            /*                                    */

    OR

            /*                                      */
            /* Insert Playback audio algorithm here */
            /*                                      */

    Hope this helps,
    Mark

     

  • 0 in reply to Mark M
    Prodigy 80 points

    we want to physically attach other hardware to the board that requires probably writing a new task or write several new task, and or also modify current tasks.    we need access to com ports, UART and I2C and I2S to attach to new hardware and write new functions and application code to run.  we were hoping not to have to read hundreds or thousands of pages of documentation.  such is life, there's no such thing as a free lunch. 

  • 0 in reply to Mark M
    Prodigy 140 points

    Hello


    I whant to customize the  CSL_USB_IsoFullSpeedExample_Out.pjt project from C500 Connected Audio Framework by adding some effects like echo, reverberation, alien etc. and I'm not sure where to insert the code. Can you give me a pice of advice?

    Thank you 

    Alexa

  • 0 in reply to Mark M
    Expert 1035 points

    Hello,

    I'm trying to compile the project with memory model "huge"
    The problem is that the ASRC lib seem to be compiled with different memory model so it can't link.
    Can we get source file of ASRC or the ".lib" for huge memory model?

    Thank you very much,

    Max 

  • 0 in reply to Maxime GUYON
    TI__Mastermind 23785 points

    Have you complied everything with "huge" model?

    regards.

  • 0 in reply to Maxime GUYON
    TI__Mastermind 30140 points

    Hi Maxime,

    See if the following wiki helps you to rebuild the library with a huge memory model:

    http://processors.wiki.ti.com/index.php/C55x_Common_Errors_and_Fixes

    Hope this helps,
    Mark

    [EDIT - fixed broken link]

  • 0 in reply to Mark M
    Expert 1035 points

    Hello,

    Yes i compiled all the project with huge memory model.
    I also modified the Bios config file (".tcf") to use huge memory model.
    It generate all the library file "dma", "pal_os" and other... with huge model but
    NOT the ASRC lib because it is already a ".lib" and source are no available so i cannot
    rebuild this lib with huge memory model... That's why when the linker take the ASRC lib, memory model of ASRC is bad...


    PS: Mark Mckeown: I already did all things suggered buy your link...
    PS2: Your link is bad when we click on it. (Need to copy the text to address bar)

    Thank you for your help,

    Max

  • 0 in reply to Maxime GUYON
    TI__Mastermind 30140 points

    Hi Max,

    I understand now - the ASRC .lib file is prebuild with large memory model, and without the source you cannot rebuild to the huge memory model.

    I will try to post the ASRC library that is built and tested with the huge memory model.

    Regards,
    Mark

  • 0 in reply to Mark M
    Expert 1035 points

    Hello,

    Yes that's exactly my problem!

    Thank you for your help!

    Regards,

    Max

  • 0 in reply to Mark M
    TI__Mastermind 30140 points

    Hi Max,

    Please try this ASRC library built for the huge memory model:

    7065.asrc_dly_fix_lib.lib

    This is a preliminary release with no guarantees of version compatibility, documentation, etc.

    I requested the ASRC built with the huge memory model for the next release of the Connected Audio Framework.

    Let us know how it goes.

    Regards,
    Mark

    multiply by

  • 0 in reply to Mark M
    Expert 1035 points

    Hello Mark,

    Thank you for your reply,

    Since i found another solution for my project, finally i don't use ASRC...
    But in case, i tested to include your ".lib" file of the huge version of ASRC and it seem that two function or symbols are undefined in this version:

    "unresolved symbol _ASRC_getNumOutSamps, first referenced in ./app_usbac.obj"
    "unresolved symbol _coefs16b, first referenced in ./app_asrc.obj"

    Thank you Mark.