• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 98 subscribers
  • Views 541 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.

DSP Link OMAPL138

Joe Tijerina
Intellectual 680 points
Other Parts Discussed in Thread: OMAPL138, OMAP-L138, OMAP-L137

Im having trouble getting printf statements to work.  I'm building a DSP Link sample application with printf statements on the DSP side and running it on target (OMAPL138) but the printfs statments do not seem to work.  printf's work just fine on the ARM side but not on the DSP.  I'm building the DSP Link app in Linux through the command line using gcc and TI cl6x compilers for the ARM and DSP, respectively.    

Can you sggest alternative methods for printing out stuff on the DSP side with my setup?

    

  • 0
    TI__Mastermind 24340 points

    Hi Joe,

    Do you mean you want to see the printf statements that you put in the DSP code printed in the Linux console?

    The DSP side is not Linux aware. The printf in the DSP side is to be used with CCS and it prints to the CCS stdout window. 

    You would need to send messages between the DSP and the ARM (using DSPLink or codec engine) and print those messages in the ARM side.

  • 0 in reply to Mariana
    Intellectual 680 points

    Thanks for suggestion. 

    Is it possible to probe the DSP with CCS via JTAG and be able to see the DSP side printf's through a CCS stdout window in real time?  CCS running on a separate windows machine and would be used strictly as a probing tool.  I'm trying to figure out a way to use printf's on both sides and see both of them in real time while executing on target.   

  • 0 in reply to Joe Tijerina
    TI__Mastermind 24340 points

    Hi Joe,

    The best way would be to send a message using DSPLink from the DSP to the ARM and have the ARM print it, but is you want to use CCS for the DSP app, you could use a similar procedure to this procedure described at:

    http://tiexpressdsp.com/index.php/Debugging_the_DSP_side_of_a_DSPLink_application_on_OMAP-L137_using_CCS

    This procedure was made for OMAP-L137 and it was not adapted yet for OMAP-L138 - it is in the to-do list.

     

  • 0 in reply to Mariana
    Intellectual 680 points

    Ok, thanks for link. 

    I was looking at the 'Notify' component for sending my DSP messages to the ARM for printing and I noticed that the current implementation only allows for 32bit integer info transfers.  Could this be easily modified to send more data (i.e. arrays)?  

    Also, do you guys have a time table for adapting the debugging procedure from the link to the L138?

     

  • 0 in reply to Joe Tijerina
    TI__Mastermind 24340 points

    Hi Joe,

    Joe Tijerina said:
    I was looking at the 'Notify' component for sending my DSP messages to the ARM for printing and I noticed that the current implementation only allows for 32bit integer info transfers.  Could this be easily modified to send more data (i.e. arrays)?  

    The best one would be the MSGQ, this is used to in the helloDSP example (needs to be adapted for OMAP-L138). You can see that the message that is passed between the DSP and the ARM has a string. The DSP messages are there.

     

    Joe Tijerina said:
    Also, do you guys have a time table for adapting the debugging procedure from the link to the L138?

    It is in the to-do list, but it is not ready yet.

  • 0 in reply to Mariana
    Intellectual 680 points

    Changing the subject a bit..

    When building a DSPLink sample application, I noticed that a linker cmd like file (messagecfg.cmd) file gets generated by a Configuration Tool (e.g. dsplink/dsp/BUILD/OMAPL138GEM_o/MESSAGE/BIOS_REL/messagecfg.cmd), what is this Configuration Tool and what does it consist of, where does it reside?  Is that where you would configure your memory map?   

    Does this configuration tool also configure the ARM's memory map?  I'd like to know what ext SDRAM memory is allocated for the ARM.   

    Please advice.

  • 0 in reply to Joe Tijerina
    Intellectual 680 points

    I'm using the OMAP-L138 eXperimente Kit from Logic.

    I'm trying to add parameters to the MSGQ component of DSP Link. 

    On the GPP side, I figured out that one could update the MSGQ_MsgHeader structure in file .../dsplink/gpp/inc/usr/msgqdefs.h for additional parmeters, for instance. 

    However, I can't seem to figure it out how to do a similar thing or the DSP side.   Can you point me to the master file where the MSGQ_MsgHeader structure is defined?  For now, I simply want to add a header parameter to MSGQ header struct and be able to pass it between the GPP and DSP.   

  • 0 in reply to Joe Tijerina
    TI__Mastermind 24340 points

    Hi Joe,

    I would not encourage you to change the structure in the directory you did at all.

    Instead, please edit:

    1) in the GPP side: struct ControlMsg in the helloDSP.c file.

    2) In the DSP side: struct ControlMsg in the helloDSP_config.h file.

    Of course the structures have to match in both files.