can't open engine

Ofer,

I see numerous queries posted by you in multimidea codecs forum. Looks like you are trying to solve some problem, I suggest you keep only one post alive so that anyone who replies sees the history. Also, this forum is for queries on TI supplied audio/video/speech codecs. Not sure if you query falls in this category.

Look like you are trying to do something on Linux, will move the post in Linux forum.

regards

Yashwant

Ofer Zimmerman said:

while executing my executable (UNIVERSAL application - my own codec) on the target (Linux/OMAP3530) I got:

[1] Failed to open /dev/cmem  

I'm answering your query from (one of) your other thread(s) here...

Yes, you need to run loadmodules.sh to install necessary Linux device drivers (cmemk.ko,dsplinkk.ko).  This is mentioned in a useful document in your CE product:
codec_engine_2_26_02_11\examples\build_instructions.html

Ofer Zimmerman said:

Note1: While I compiled my server I got the following message ""undefined.createMemMapFile(): program = bin/servercom_x64P" - but no error was generated and the executable server was produced.

Feel free to include more detailed error/warning messages.  It's hard for us to determine much from a brief summary or high-level description.  Just include the whole message from the build, which will have file names and line numbers.

Ofer Zimmerman said:

Note2: I deleted SECTIONS{} from packages/gnu/targets/arm/linkcmd.xdt as I was instructed in an earlier psot of mone to bypass CodeSourcery bug that produces ld error 11 (segmentation fault) during the application linking stage

Can you revert back to the CodeSourcery that is recommended with CE?  That is the suggested approach.  If you do so then you will avoid these errors which occur due to a bug in the later CodeSourcery.  I'm under the impression that you upgraded both CodeSourcery and XDC in an attempt to solve your previous problem, but that problem had nothing to do with those components.

It is strongly suggested that you go with the CodeSourcery and XDC with which CE 2.26.02.11 is validated.

Regards,

- Rob

Robert,

I followed carefully the instructions on "Getting started with IUNIVERSAL", I was not aware regarding the build instructions as you mentioned (the document I used did not mention this). So I will follow. 

Please note that I upgraded CodeSourcery since I hit ld 11 (segmentation fault) and I was told here that it is a known CodeSourcery bug and SECTIONS need to be deleted. Anyway can you tell me what are the release  that I need to use for CodeSourcery and XDC that goes with CE ? initially I used CodeSourcery 209q since I wanted to use DVSDK 4.X and this release (209.q) was a must but I did not use the DVSDK since the installation failed (actually finished but there were no docs to explain how to set/configure the environment as was promised by installation). Then I used all the packages as stand alone. Anyway can you tell me what to use (CodeSourcery and XDC?) I do not see any documentation regarding this linkage between releases . What about can't load engine issue?

Thanks Ofer

Hi Robert,

OK (I succcesed compiling the universal_copy example without modifications, the makefile there is using -T .xdl file....maybe this is the problem with the randgen example) anyway where do I get dsplinkk.ko? and cmemk.ko? (they are not under the system files sub-directory) do I need LPM also?

Ofer

You must already have the necessary products installed if your applications are building:

• CMEM is part of the Linux Utils product.
• The DSP Link product can be downloaded here.
  
• LPM is needed for OMAP3 devices, which it looks like you're using.  It's part of the LPM product.

The .ko's you need are listed in the platform-specific codec_engine_<ver>/examples/apps/systemfiles/<platform>/loadmodules.sh

[ Typically, users are recommended to use a DVSDK rather than just Codec Engine standalone.  The documentation included with a DVSDK contains more system-wide documentation, specific to a particular OS/EVM and the components needed to get that particular system up.  Codec Engine supports lots of devices and lots of SW environments, which is why the docs may appear vague at times - we intentionally leverage DVSDK docs to provide system integration instructions for a particular system. ]

Chris

Chris

I started by the DVSDK and followed the instructions/requirements BUT there was no doc launched as was promised by the installation nor on the Internet nor on the DVSDK directory and so I started to use the 2 wizards (codec and server) andI had installed required components. Anyway, I do have linuxutils (under codec engine) and DSP Link (LPM not yet) - my question do I need to build and generate these .ko files or get them from somewhere? 

Thanks Ofer

Yes, the .ko's must be built against your specific Linux kernel.

Chris

Chris,

One more question sorry to bother, while I found and compiled cmem, where is the subdirectory to built the dsplinkk.ko in the dsplink product ? where in the LPM product?

(I do not to harm and destroy by just making, this is the reason I am asking that)

Thanks Ofer

How do I compile dsplinkk.ko and lpm_omap3530.ko ? I have the corresponding directories under codec engine

Ofer

Hi Ofer,

If you are using DVSDK 4.x the Software Developers' Guide is located in <DVSDK_install_dir>/docs/TMS320DM365_Software_Developers_Guide.pdf. That is the main document you should refer to for development using the DVSDK (ie. the one that should have popped up when exiting the installer). Refer to the section on "Rebuilding the DVSDK components" for more information on rebuilding components such as lpm and dsplink. It will guide you on how to rebuild them using the Makefile sitting at the top-level directory in the DVSDK.

Best regards,

Vincent

Vincent,

unfortuantely I am not using the DVSDK since after installation I did not get any doc launched or installed on the disk as was promised. Si I installed components according to requirements of the Coded package Wizard and Server package Wizard.

Can you tell how to do it without the DVSDK?

Ofer