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

dsplink sample application message.out didn't work.

JOOYEON LEE
Prodigy 120 points
Other Parts Discussed in Thread: OMAP3530

I used the subproject %DSPLINK%\etc\host\projects\WinCE\CATALOG\dsplink.PbcXml supported in TI, and it should run the message sample application as default.

I got the file 'message.out ' after building the project, and I copied it to the FLATRELEASEDIR directory. 

But, when I run it in Target Control as the command "s messagegpp /Release/message.out 10000, I can't get any results from that.

My debugger output is like below:

 

352250 PID:400002 TID:45400b6 RELFSD: Opening file messagegpp.exe from desktop

PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\EVM_3530_NEW\EVM_3530\RELDIR\EVM_OMAP3530_ARMV4I_RELEASE\MESSAGEGPP.EXE'

 354658 PID:2e6000e TID:45400b6 ========== Sample Application : MESSAGE ==========

 354659 PID:2e6000e TID:45400b6 Entered MESSAGE_Create ()

 354660 PID:400002 TID:45400b6 DSP Clk Rate 430000

 354667 PID:2e6000e TID:45400b6 PROC_attach () failed. Status = [0x80008012]

 354667 PID:2e6000e TID:45400b6 PROC_setup () failed. Status = [0x80008012]

 354668 PID:2e6000e TID:45400b6 Leaving MESSAGE_Create ()

 354668 PID:2e6000e TID:45400b6 Entered MESSAGE_Delete ()

 354668 PID:2e6000e TID:45400b6 MSGQ_release () failed. Status = [0x8000800b]

 354684 PID:2e6000e TID:45400b6 Leaving MESSAGE_Delete ()

PB Debugger Unloaded symbols for 'C:\WINCE600\OSDESIGNS\EVM_3530_NEW\EVM_3530\RELDIR\EVM_OMAP3530_ARMV4I_RELEASE\MESSAGEGPP.EXE'

 

I don't know why PROC_attach() and PROC_setup() failed.

I followed the document 'InstallGuide_WinCE_OMAP3530.pdf' 

  • 0
    TI__Expert 4930 points

    Lee

    it looks to me that the recently built dsplinkk.dll is not loaded at boot time. Can you check if the dll is present in $(_FLATRELEASEDIR) ana available for use.

    Deepali

  • 0 in reply to Deepali Uppal
    Prodigy 120 points

    There was dsplinkk.dll in $(_FLATRELEASEDIR) but it was not an updated file, generated at 2010.12.02. The recently updated dsplinkk.dll is in %DSPLINK%\gpp\BUILD\EXPORT\RELEASE, %DSPLINK%\gpp\BUILD\PMGR\BIN\RELEASE, and %DSPLINK%\gpp\export\BIN\WinCE\OMAP3530\RELEASE.

    So I manually copied it to the $(_FLATRELEASEDIR), but when I boot the system, the debugger shows the warning such as "Symbols cannot be loaded. Timestamp of module on device does not match timestamp of local module: DSPLINKK.DLL. To ignore this warning and load symbols, please change settings in debugger options."

    I don't know why dsplinkk.dll wasn't copied to $(_FLATRELEASEDIR) automatically, and why it doesn't still work.

    PS. Could you tell me where the %_TARGETPLATROOT%\ is? 

    InstallGuide says the DLLs and EXEs in %_TARGETPLATROOT%\target\%_TGTCPU%\%WINCEDEBUG% would be copied to the %_FLATRELEASEDIR% automatically. However I don't know where the above path is, and why it didn't copy the files.

  • 0 in reply to JOOYEON LEE
    TI__Expert 4930 points

    Lee

    Can you open

    • Go to Build Menu -> Open Release Directory in build window. This will start the DOS command window with WINCE environment set.

    All the environment variables for that project will be available in that command window.

    Deepali

  • 0 in reply to Deepali Uppal
    Prodigy 120 points

    Thank you, but I don't know still why the dlls and exes in %_TARGETPLATROOT%\target\%_TGTCPU%\%WINCEDEBUG% are not copied to %_FLATRELEASEDIR%.

    At boot-up time, the debugger message is like below:

    PB Debugger Loaded 'C:\WINCE600\OSDESIGNS\EVM_3530_NEW\EVM_3530\RELDIR\EVM_OMAP3530_ARMV4I_RELEASE\DSPLINKK.DLL', no matching symbolic information found.

      66250 PID:400002 TID:c00002 DSPLINK Module (1.65.00.03) created on Date: Nov  9 2010 Time: 12:17:23

     

    Can it be related the operating system distribution files?

    I'm sure the path of env.vars in my DSP distribution file are correct, but I'm not sure that in my GPP distribution file are correct. 

    My distribution files is like that:

    <omap3530_wince6.0.mk>

    USE_DISTRIBUTION := 1

    #   ============================================================================

    #   Set the values of necessary variables to be used for the OS.

    #   ============================================================================

    #   ----------------------------------------------------------------------------

    #   Base directory for the GPP OS

    #   ----------------------------------------------------------------------------

    BASE_BUILDOS    := $(_WINCEROOT)

    #   ----------------------------------------------------------------------------

    #   Base for toolchain

    #   ----------------------------------------------------------------------------

    BASE_TOOLCHAIN  := $(_WINCEROOT)\SDK\BIN

    #   ----------------------------------------------------------------------------

    #   Base for code generation tools - compiler, linker, archiver etc.

    #   ----------------------------------------------------------------------------

    BASE_CGTOOLS    := $(_WINCEROOT)\SDK\BIN

     

    <c64xxp_5.xx_windows.mk>

    #   ----------------------------------------------------------------------------

    #   Base directory for the DSP OS

    #   ----------------------------------------------------------------------------

    BASE_INSTALL    := "$(TI_TOOLS_BASE_DIR)"

    ifeq ($(BASE_INSTALL), "")

    BASE_INSTALL    := C:\TITOOLS

    endif

    BASE_SABIOS     := "$(BIOS_INSTALL_DIR)"

    ifeq ($(BASE_SABIOS), "")

    BASE_SABIOS     := $(BASE_INSTALL)\bios

    endif

    BASE_BUILDOS    := $(BASE_SABIOS)\packages\ti\bios

    #   ----------------------------------------------------------------------------

    #   Base directory for the XDC tools

    #   ----------------------------------------------------------------------------

    XDCTOOLS_DIR    := "$(XDC_INSTALL_DIR)"

    ifeq ($(XDCTOOLS_DIR), "")

    XDCTOOLS_DIR    := $(BASE_SABIOS)\xdctools

    endif

    #   ----------------------------------------------------------------------------

    #   Base for code generation tools - compiler, linker, archiver etc.

    #   ----------------------------------------------------------------------------

    BASE_CGTOOLS    := "$(CODEGEN_INSTALL_DIR)"

    ifeq ($(BASE_CGTOOLS), "")

    BASE_CGTOOLS    := $(BASE_INSTALL)\C6000\cgtools

    endif

    BASE_CGTOOLSBIN := $(BASE_CGTOOLS)\bin

     

    Does it have any wrong path? 

  • 0 in reply to JOOYEON LEE
    Prodigy 120 points

    oh,,, I got the solution of the problem.

    That was because I had not deleted or renamed the files in %_WINCEROOT%\PLATFORM\<BSP>\Files, so I renamed the dsplinkk.dll in that directory, and then it worked.

    But I wonder if I have to rename all the files in that directory, and what does that mean??

  • 0 in reply to JOOYEON LEE
    TI__Expert 5320 points

    For the problem in hand, you need to rename/remove only the dsplink related files from the %_WINCEROOT%\PLATFORM\<BSP>\Files folder (ex: dsplinkk.dll, message*) if they are present. The reason being that the binaries in this folder could be old and is not updated by the dsplink build procedure. However, when you do the BSP build, the "copy files to release directory" phase of the buillds copies files from the %_TARGETPLATROOT%\target\%_TGTCPU%\%WINCEDEBUG% folder to FLATRELEASEDIR first and then from %_WINCEROOT%\PLATFORM\<BSP>\Files to FLATRELEASEDIR. Hence the dsplinkk.dll in your FLATRELEASEDIR was older version. Hence you end up with wrong versions of the files.

    -Madhvi