ezsdk 5.02.02.60 make omx failed

Eric Mao

following is the error message copy from the terminial

/usr/local/ezsdk/component-sources/omx_05_02_00_15/packages/../lib/ti/omx/domx/lib/a8host/debug/domx.av5T(DomxProcMgrIf_HLOS.ov5T): In function `DomxCore_procInit':

/usr/local/ezsdk/component-sources/omx_05_02_00_15/packages/ti/omx/domx/DomxProcMgrIf_HLOS.c:155: undefined reference to `ServiceMgr_start'

/usr/local/ezsdk/component-sources/omx_05_02_00_15/packages/../lib/ti/omx/domx/lib/a8host/debug/domx.av5T(DomxProcMgrIf_HLOS.ov5T): In function `DomxCore_procDeInit':

/usr/local/ezsdk/component-sources/omx_05_02_00_15/packages/ti/omx/domx/DomxProcMgrIf_HLOS.c:172: undefined reference to `ServiceMgr_stop'

/usr/local/ezsdk/component-sources/framework_components_3_21_01_26/packages/ti/sdo/fc/memutils/lib/release/memutils.av5T(memutils_cmem.ov5T): In function `MEMUTILS_cacheWbInv':

memutils_cmem.c:(.text.MEMUTILS_cacheWbInv+0x2c): undefined reference to `CMEM_init'

memutils_cmem.c:(.text.MEMUTILS_cacheWbInv+0x38): undefined reference to `CMEM_cacheWbInv'

memutils_cmem.c:(.text.MEMUTILS_cacheWbInv+0x44): undefined reference to `CMEM_exit'

/usr/local/ezsdk/component-sources/framework_components_3_21_01_26/packages/ti/sdo/fc/memutils/lib/release/memutils.av5T(memutils_cmem.ov5T): In function `MEMUTILS_cacheWb':

memutils_cmem.c:(.text.MEMUTILS_cacheWb+0x2c): undefined reference to `CMEM_init'

memutils_cmem.c:(.text.MEMUTILS_cacheWb+0x38): undefined reference to `CMEM_cacheWb'

memutils_cmem.c:(.text.MEMUTILS_cacheWb+0x44): undefined reference to `CMEM_exit'

over 15 years ago

0 Archith John Bency over 15 years ago

TI__Intellectual 2910 points

Eric,

The make command whoch makes sure that all dependencies get built before omx gets built,

either do

#make components

#make omx

OR do the below to build dependencies required only by omx:

# make linux && make syslink_hlos && make osal && make cmem && make omx

Archith

0 Eric Mao over 15 years ago in reply to Archith John Bency

Genius 4330 points

Architch

I try the two methods as you say, and get the same error message as before. Any other suggestions?

0 Archith John Bency over 15 years ago in reply to Eric Mao

TI__Intellectual 2910 points

Can you check the integrity of the installer you downloaded? You can do this by comparing the md5sum of the installer on your machine with what is shared here:

http://software-dl.ti.com/dsps/dsps_public_sw/ezsdk/latest/index_FDS.html

Archith

0 Eric Mao over 15 years ago in reply to Archith John Bency

Genius 4330 points

Architch

I've check the MD5 value of my install file, the value is the same as list in the file md5num.txt

I send a message to you through Conversations,please check it. thank you!

0 Joern over 15 years ago in reply to Eric Mao

Genius 3055 points

Wow, some weeks and the next EZSDK beta release is out there... I downloaded the 5.02.01.59, now we already have the 5.02.02.60.

I welcome each step on this way to an EZSDK release with maybe some day no longer needs the prefix 'beta'.

But what I would actually like to know: Is there a place where the small changes between those sub-releases have been documented? Just to get an idea if a change makes sense concerning our purposes - and to have at least an assumption, which parts might make new problems...

Thanks in advance,
Joern.

0 Archith John Bency over 15 years ago in reply to Joern

TI__Intellectual 2910 points

Joern,

This information is supposed to be in the EZSDK release notes in the form of a Change Log. I think this has been missed for 5.02.02.60. We will have this fixed in further releases.

Archith

0 Joern over 15 years ago in reply to Archith John Bency

Genius 3055 points

I welcome that very much, being hopefully for the future.

For this time I just looked into the release notes from the EZSDK download page - and didn't found a change log for the smaller release steps below 5.02.*.

In each case it was a good idea to publish those notes also independently from the huge EZSDK download and it's installing effort.

Thanks,
Joern.

0 Xianghua Xiao69249 over 15 years ago in reply to Joern

Prodigy 40 points

I built the sdk just fine on LTS 10.04 64-bit.

0 Eric Mao over 15 years ago in reply to Xianghua Xiao69249

Genius 4330 points

I use the LTS 10.04-32bit, Does I must change the Linux system?

0 Eric Mao over 15 years ago in reply to Eric Mao

Genius 4330 points

I delete all installed files, then reinstall the ezsdk, now there is no error message when type make omx

Processors

Processors forum

ezsdk 5.02.02.60 make omx failed