AWR1243BOOST: Query related to the vcop processing from Application layer

Hi Varsha,

You should be able to do this to just call the APIs. However, there are other considerations for efficiency regarding the performance of getting the data into EVE Internal memory.

I will request our EVE experts to look at this question.

Thanks and Regards,
Piyali

Hi Piyali, 

Thank you for your reply. I have tried using them by including the header file paths and kernel file paths in a makefile. (I don't know if this is the correct way). But, I come across with the following errors while I do :

gmake -s -j 

Following is the terminal log: 

Build of libraries done.
# Configuro done!
# Making tda2px-evm:ipu1_1:debug:vision_sdk_lib...
# Compiling tda2px-evm:ipu1_1:debug:vision_sdk: /home/arifchandmulani/Desktop/PROCESSOR_SDK_RADAR_03_03_00_00/vision_sdk/apps/src/common/app_init/app_init_ipu1_1.c
# Compiling generated MAIN_APP_ipu1_1_pem4.oem4
# Linking into /home/arifchandmulani/Desktop/PROCESSOR_SDK_RADAR_03_03_00_00/vision_sdk/binaries/apps/tda2px_evm_bios_radar/vision_sdk/bin/tda2px-evm/vision_sdk_arp32_1_debug.xearp32F...
#
"/home/arifchandmulani/Desktop/PROCESSOR_SDK_RADAR_03_03_00_00/vision_sdk/links_fw/src/rtos/bios_app_common/tda2px/eve1/linker_cmd_eve1_debug.cmd", line 7: warning: 
   no matching section
"/home/arifchandmulani/Desktop/PROCESSOR_SDK_RADAR_03_03_00_00/vision_sdk/links_fw/src/rtos/bios_app_common/tda2px/eve1/linker_cmd_eve1_debug.cmd", line 8: warning: 
   no matching section
"/home/arifchandmulani/Desktop/PROCESSOR_SDK_RADAR_03_03_00_00/vision_sdk/links_fw/src/rtos/bios_app_common/tda2px/eve1/linker_cmd_eve1_debug.cmd", line 13: warning: 
   no matching section
#
# /home/arifchandmulani/Desktop/PROCESSOR_SDK_RADAR_03_03_00_00/vision_sdk/binaries/apps/tda2px_evm_bios_radar/vision_sdk/bin/tda2px-evm/vision_sdk_arp32_1_debug.xearp32F created.
#
# Linking into /home/arifchandmulani/Desktop/PROCESSOR_SDK_RADAR_03_03_00_00/vision_sdk/binaries/apps/tda2px_evm_bios_radar/vision_sdk/bin/tda2px-evm/vision_sdk_ipu1_1_debug.xem4...
#
# Linking into /home/arifchandmulani/Desktop/PROCESSOR_SDK_RADAR_03_03_00_00/vision_sdk/binaries/apps/tda2px_evm_bios_radar/vision_sdk/bin/tda2px-evm/vision_sdk_c66xdsp_1_debug.xe66...

 undefined                                    first referenced                                                                                                                                                             
  symbol                                          in file                                                                                                                                                                  
 ---------                                    ----------------                                                                                                                                                             
 vcop_peak_detection_binlog_energy_scaling_cn /home/arifchandmulani/Desktop/PROCESSOR_SDK_RADAR_03_03_00_00/vision_sdk/binaries/apps/tda2px_evm_bios_radar/lib/tda2px-evm/66/debug/app_alg_plugins.ae66<radarPkDetect.oe66>
 vcop_peak_detection_energy_across_antenna_cn /home/arifchandmulani/Desktop/PROCESSOR_SDK_RADAR_03_03_00_00/vision_sdk/binaries/apps/tda2px_evm_bios_radar/lib/tda2px-evm/66/debug/app_alg_plugins.ae66<radarPkDetect.oe66>
 vcop_tx_decoding_cn                          /home/arifchandmulani/Desktop/PROCESSOR_SDK_RADAR_03_03_00_00/vision_sdk/binaries/apps/tda2px_evm_bios_radar/lib/tda2px-evm/66/debug/app_alg_plugins.ae66<radarPkDetect.oe66>

error: unresolved symbols remain
error: errors encountered during linking;
   "/home/arifchandmulani/Desktop/PROCESSOR_SDK_RADAR_03_03_00_00/vision_sdk/bi
   naries/apps/tda2px_evm_bios_radar/vision_sdk/bin/tda2px-evm/vision_sdk_c66xd
   sp_1_debug.xe66" not built
make[7]: *** [/home/arifchandmulani/Desktop/PROCESSOR_SDK_RADAR_03_03_00_00/vision_sdk/binaries/apps/tda2px_evm_bios_radar/vision_sdk/bin/tda2px-evm/vision_sdk_c66xdsp_1_debug.xe66] Error 1
make[6]: *** [c66xdsp_1] Error 2
make[5]: *** [apps_dsp1] Error 2
make[5]: *** Waiting for unfinished jobs....
#
# /home/arifchandmulani/Desktop/PROCESSOR_SDK_RADAR_03_03_00_00/vision_sdk/binaries/apps/tda2px_evm_bios_radar/vision_sdk/bin/tda2px-evm/vision_sdk_ipu1_1_debug.xem4 created.
#
make[4]: *** [apps] Error 2
make[3]: *** [apps] Error 2
make[2]: *** [apps_exe] Error 2
make[1]: *** [apps] Error 2
gmake: *** [vision_sdk] Error 2
arifchandmulani@punelpt152:~/Desktop/PROCESSOR_SDK_RADAR_03_03_00_00/vision_sdk/build$ 


Regards,
Varsha

Hi Varsha,

   The files you are mentioning are natural C code and are not optimized code on EVE. These are the functions against which we compare the output of our optimized implementation to confirm the functionality. The optimized code are present in src_kernelC folder of the corresponding kernel. You can call these kernels from SDK but you will need to link with the libraries present in <evesw>/kernels/lib/release/libevekernels.eve.lib.

Regards,

Anshu

Hi Anshu, 

Thank you for the reply. I have understood the difference of natural C and optimized code. I have some silly queries, When I call those functions the call is from .k file directly or the kernel's .c and .h file created? Can you please help me understand How to specifically link the libraries present in <evesw>/kernels/lib/release/libevekernels.eve.lib.  

Regards,

Varsha

Hi,

And I want to simply use the natural c functions as they are used in the apps testbench code? How could I do this?

Regards,
Varsha

Hi Varsha,
You can just call the natural C function from your test bench and link your final application with libevekernels. This library has all natural C symbols.

Regards,

Anshu

Hi Varsha,

   Were  you able to make progress on this? If yes please close this thread. If not then let  us know

Regards,

Anshu

Hi Anshu,

Sorry for late response. But I was not able to solve this issue. As I was shifted to some other task, I could not get back to u. I was not able to understand what you meant by linking your final application with libevekernels. It should be already linked I guess.?

Regards,
Varsha

Varsha,
As mentioned libevekernels contains symbols for natural C code. If you are using eve sw applet test bench then it should already be linking with the correct library and you should not get any errors. But if you are trying to use these functions in some of your code base then you should link to the above library mentioned.

Regards,
Anshu

Ok Anshu,

I will check that .

Regards,
Varsha

Hi Varsha,
Are you able to make progress on this thread?

Regards,
anshu