• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 677 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.

general question about dsplink

Kevin Nellen
Prodigy 120 points

Other Parts Discussed in Thread: OMAPL138

Hi,

I'm currently using the eXperimenter kit with the OMAPL138 processor.
I built a WinCE with DSPLink as instructed in the InstallGuide_WinCE_OMAPL138.pdf using Platform Builder IDE.
DSPLink  seems to be built in since the EBOOT writes "DSPLINK Module (1.65.00.03) created on Date: Nov  1 2011 Time: 08:31:06" to the console at startup.

In section 10, I copied the messagegpp files (messagegpp.exe message.out dsplinkk.dll) to the SD-Card, connected with Telnet to the device and startet the app "messagegpp.exe MESSAGE.OUT 10" and the following error is displayed:

========== Sample Application : MESSAGE ==========
Entered MESSAGE_Create ()
Error opening file MESSAGE.OUT, error: 2
PROC_load () failed. Status = [0x80008009]
Leaving MESSAGE_Create ()
Entered MESSAGE_Delete ()
MSGQ_release () failed. Status = [0x8000800b]
Leaving MESSAGE_Delete ()
====================================================

anyway, my question is:
Do I need to build an DSPBIOS with DSPLink for the DSP core and load it before starting windows CE on the GPP core?

Thanks

  • 0
    TI__Mastermind 22760 points

    Kevin,

    The error code [0x80008009] indicates that the DSP executable could not be found.  Could you try specifying the full path to the message.out executable when running messageapp.exe?  The messageapp.exe is probably looking for message.out at the root of the file system, and not finding it.  Alternatively, if you are using Platform Builder, you could try importing the message.out to the WinCE filesystem, using the remote file viewer.

    Best regards,

        Janet

     

  • 0 in reply to janet
    Prodigy 120 points

    Janet,

    I did specify the full path and it worked, thank you very much.
    which get's us to my next question:
    How does the GPP load the Programm to the DSP? It it loaded via JTAG, or has the GPP access to the DSP RAM?

    Thanks,
    Kevin 

  • 0 in reply to Kevin Nellen
    TI__Mastermind 22760 points

    Kevin,

    The GPP is loading the code by writing it to the DSP's memory (although PROC_load() is agnostic to the type of loader being used, as it makes calls to load the executable through a function interface. So theoretically, a different type of loader could be used).

    Best regards,

        Janet