• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 588 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.

Execution programs for DSP C64+ beagle board in CCSv5

Oscar Herranz
Intellectual 770 points
Other Parts Discussed in Thread: SYSBIOS

Hi guys!!

I am working with ARM+DPS architecture and i have doubts about the configuration in order to build programs in DSP with CCSv5.

  • First all, i know that is the ARM who to release the DSP from reset throught a function script but the prodecure is complex...I do not know if when i start to create a new project, this project is for ARM or DSP cause both go to perform operations.
  • In this connection, I don't know if  i have to use gel files for both or only for DSP; I have read in this forum that if I use RTOS for DSP i don't need gel file for DSP..
  • I have understood that when you load a program for DSP, CCSv5 loads the program and the real time operating system but the correct procedure I do not now.
  • Lasty, can i keep on using gdb server in order to debug for ARM and to use other mode for DSP simultaneously? The goal is to work  with ARM and DSP in the same interface, specifically CCSv5

Thanks in advance guys!!

Óscar

 

  • 0
    TI__Guru**** 171349 points

    Óscar,

    Oscar Herranz said:

    First all, i know that is the ARM who to release the DSP from reset throught a function script but the prodecure is complex...I do not know if when i start to create a new project, this project is for ARM or DSP cause both go to perform operations.

    If you are not using embedded Linux, you can create two projects for each core connect to them via an emulator, however you will need a GEL script for that.

    If you are using embedded Linux you can programatically take the DSP out of reset and load code to it through the ARM application. In other words, during the execution your ARM application takes the DSP out of reset, loads code to it and runs.

    To accomplish this one of the two components can be used: DSPLink (if the DSP code has DSP/BIOS) or SysLink (if the DSP uses SYSBIOS).

    These two components are also used in as underlying software by a more sofisticated software framework called Codec Engine (CE for short).

    Oscar Herranz said:

    In this connection, I don't know if  i have to use gel files for both or only for DSP; I have read in this forum that if I use RTOS for DSP i don't need gel file for DSP..

    The GEL files are used to initialize the device and release each core from reset. However, if you are running embedded Linux on the ARM this device initialization is done for you. Therefore no GEL scripts for ARM should be used.

    In the case of DSP, the two components mentioned before can help you with that. Therefore I suggest checking their wiki pages and referring to the embedded software forums for additional questions (it falls off the CCS team expertise...)

    Oscar Herranz said:

    I have understood that when you load a program for DSP, CCSv5 loads the program and the real time operating system but the correct procedure I do not now.

    The DSP executable (a file with extension .out) contains both the RTOS and the program, therefore CCSv5 loads the code to the device via an emulator - independently if the executable has or not an RTOS.

    Oscar Herranz said:

    Lasty, can i keep on using gdb server in order to debug for ARM and to use other mode for DSP simultaneously? The goal is to work  with ARM and DSP in the same interface, specifically CCSv5

    Yes you can. The procedure is similar to the Mixed Mode debug depicted in the Linux Debug in CCSv5 page. The difference is that, instead of attaching the Linux kernel sources to the CortexA8, you can attach the DSP source code to the DSP core. 

    Regards,

    Rafael