• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 297 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.

OMAPL138 problem with .out files larger than 1MB

TIguru
Expert 1430 points
Other Parts Discussed in Thread: OMAPL138, OMAP-L138

Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4

Friends:

Has anyone come across the following problem:

On a OMAPL138 processor, DSPLink does not execute when loading  DSPApp.out coeff files greater than 1 Megabyte. This occurs when using a DSPApp.out file which includes DSP/BIOS pspdrivers_01_30_01 UART driver libraries and additional custom DSP algorithms.  The problem has been narrowed down to a file size issue.  Whenever a large (>900kB) .out file is created, DSPLink fails to execute.  If the file is less than 900kB everything runs as expected.

We have expanded DSP_Link Memory Space to include 16 Megabytes of DDR allocated to the DSP and have no problem running DSPApp.out files that are in the 400 Kbytes to 800 Kbyte range, but as our DSPApp.out file approaches 900kB we are unable to get DSPLink to run.

 

Any and all help will be greatly appreciated.

  • 0
    TI__Expert 4930 points

    Enrique,

    What do you mean by fails to execute? Does it give a specific failure code?

    The default memory map supports load of DSP executable with size ~ 1MB.

    There are some troubleshooting FAQ's at

    http://processors.wiki.ti.com/index.php/Troubleshooting_DSPLink_configuration_issues#Problem:_PROC_load_failed_with_DSP_ERANGE_error

    The solution to the problem is to change the memory map to give a bigger DDR size. Since you have already done that, I would like more details on the failure you are seeing.

    Which DSPLink version are you on? One of our releases had a bug in which PROC_load would hang if args section size in DSP executable was insufficiently configured instead of failing with an appropriate error.

    Deepali

     

     

  • 0 in reply to Deepali Uppal
    Expert 1430 points

    Deepali

       Thank you for your reply.  Here is a screen snapshot of the startup debug messages:

    "INIT: Entering runlevel: 5
    Starting telnet daemon.
    DSPLINK Module (1.65.00.02) created on Date: Aug  7 2010 Time: 03:32:47
    Starting syslogd/klogd: done

     _____                    _____           _         _
    |  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_
    |     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
    |__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|
                  |___|                    |___|

    Arago Project http://arago-project.org arago ttyS2

    Arago 2009.11 arago ttyS2

    arago login: root
    root@arago:~# ./leaps leaps-dsp.out
    Little Endian System Detected!
    Starting
    Failed to connect to socket.: Operation now in progress
    DSPLink Configuration Complete. Status = 8000
    Received from DSP: MsgId=0; SOW=0
    Failed to connect to socket.: Operation already in progress
    Failed to connect to socket.: Operation already in progress
    Failed to connect to socket.: Operation already in progress
    Failed to connect to socket.: Operation already in progress
    Failed to connect to socket.: Operation already in progress
    Failed to connect to socket.: Operation already in progress
    Failed to connect to socket.: Operation already in progress
    Failed to connect to socket.: Operation already in progress
    Failed to connect to socket.: Operation already in progress
    Failed to connect to socket.: Operation already in progress
    Failed to connect to socket.: Operation already in progress
    Failed to connect to socket.: Operation already in progress
    Failed to connect to socket.: Operation already in progress
    Failed to connect to socket.: Operation already in progress
    Failed to connect to socket.: Operation already in progress
    Failed to connect to socket.: Operation already in progress
    Failed to connect to socket.: Operation already in progress
    Connected to host.

    "

    Normal 0 false false false EN-US X-NONE X-NONE

    Version number for DSPLink is  dsplink_linux_1_65_00_02 and the OMAP-L138_dsp_1_00_00_11 SDK.  Currently, the application dsp_app.out being worked on is right at 1MB  It loads and runs.  If debugging information is turned on the  dsp_app.out file goes to 1.2 MB  and the dsp_app.out appears to load and initialize but does not run and produces the DSP_Halt debug message displayed above.

    Please let me know if the message above may be indicative of what could be wrong.  Once again, thank you for taking the time to respond.


  • 0 in reply to TIguru
    TI__Expert 4930 points

    Enrique,

    Can you find out which driver/code the prints are coming from? They are not coming from DSPLink.

    Are you using Codec Engine as well?

    This kind of odd behavior might be due to memory map inconsistencies.  For starters, what are the bootargs used in u-boot when starting the Linux kernel?

    Are you using the default memory map? If not have you followd all steps ar http://processors.wiki.ti.com/index.php/Changing_DSPLink_Memory_Map to update the memory map?

    Deepali

  • 0 in reply to Deepali Uppal
    Expert 1430 points

    Deepali

     

     Thank you for your suggestion to check the memory map.  Upon close review, there were a couple mappings which needed corrections.  We are now able to run larger than 1.2MB applications.  Once again, thank you for your time and help.

     

    Regards,

    Enrique