VLIB example build error issue

hi, jd

have you solved this problem ?

i got this error too, when i try to porting VLIB2.0 to DM642 platform.

could anyones help us?

Best regards,

                         yqhen

yqhen,

Not exactly.

But I also have DM6437 EVM. With the same software setup, I had success.  So, I believe that the issue may be the build of library itself. For ver. 2.0 TI might have used an old BIOS version.

Will keep you posted. Let me know if you get it working.

jd

HI jd,

I believe VLIB is made for the C64x+ core. So it will not work for DM642 that has a C64x core...

Mariana,

I dont thinks so. If you look at the documentation of VLIB - SPRUG00A, Section 1 (About VLIB 2.0 release), it is clearly mentioned that it is designed for C64x or c64x+ devices. Also, if you look inside its  library folder, there is a subfolder named C64 and it contains vlib.c64. Plus there is an example provided by TI for DM642 EVM.

jd,

I have an older version that just mentions C64x+ and does not have DM642, but do not worry - I will investigate it and get back to you.

Hi jd,

The test project as provided in VLIB for DM642 builds. If you had uncommented or modified the project, it may not work because of the following reason.

 64x versions of VLIB_updateEWRMeanS32, VLIB_updateEWRVarianceS32, VLIB_subtractBackgroundS32,
VLIB_mixtureOfGaussiansS32 and VLIB_testCannyEdgeDetector functions are not available currently. This was mentioned in the release notes.

So if you were trying to use any of these functions, it wont work.

Please let me know which function are you using on DM642.

Regards

Senthil

Thanks Senthil.

jd, what version of code generation tools are you using?

v6.0.8

jd,

I made sure this issue wont come up in the new VLIB 2.1 release.

It is better if you can update to the newer VLIB which would come on the web positively next week.

Regards

Senthil

Please update to the latest CGT:

http://tiexpressdsp.com/index.php/Updating_Code_Generation_Tools_in_CCS_3.3

This way you make sure it is not a bug in CGT.

Unfortunately, I need to use all of those functions. The thing I do not understand is if it is supported on C64 core, how come the example does not work out of thebox. I did not modify it at all. Interestingly, I found in SPRAA84A that _smpy32 is a new instruction to C64+ that was not available in C64. Could that be the reason, or it is a BIOS or cgtool issue? Also, shouldn't vlib.c64 be built with that consideration?

Thanks  Senthil and Mairana for your efforts. I really like to have it working with DM642 as lots of development work i am doing is on that processor.

 jd

jd,

Actually the functions VLIB_updateEWRMeanS32, VLIB_updateEWRVarianceS32, VLIB_subtractBackgroundS32, VLIB_mixtureOfGaussiansS32 were not supposed to be present in the vlib.l64 library. But it was included in the build because newer code generation tools automatically map the smpy32 intrinsic (which is not present in 64x as you mentioned) to function calls. As it is a function call, performance of the kernels degrade. So it actually works in 64x if you have newer cgtools but it is not optimal.

There are 16 bit versions of the above said kernels. Do you need 32 bit versions ?
If its ok with unoptimal 32 bit versions, it should work with the present library.

I will try to raise a request for optimal development of 32 bit versions if it is required for you.

Feel free to ask for more clarification.

Regards
Senthil

Your are right Mariana. I have got it working finally. It seems v.6.1.11 is the answer. So, to summerize,

A toolset that works with DM642 is

CCS 3.3.82.13

BIOS 5.31.02

CGTOOLS v6.1.11

Thanks. Btw yqhen you may want to follow the same instructions.

jd

Yes, I have tight real-time constraints for my application that needs optimal usuage of the DSP. The vlib is definately helping to improve the efficiency. And 32-bit kernals will be extremely useful to me and others.

Thanks.

jd

Hey Senthil,

I was looking around for vlib 2.1 version, is it out now? How would we know about it?

Thanks.

Jwalant

Should be out in a bit more than a week.

It should show up in myregisteredsoftware if you already requested and can access 2.0. I think it send you an e-mail when a new version of software is posted, but not sure..