• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 97 subscribers
  • Views 301 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.

Adding A New Kernel to c6accel

Shawn Gao
Prodigy 70 points
Other Parts Discussed in Thread: OMAP3530

Hi,

I added a VLIB function to c6accel following TI's instruction http://processors.wiki.ti.com/index.phptitle=C6Accel_Advanced_Users_Guide#Adding_a_new_kernel.2Flibrary_to_C6Accel

However, when I ran the test app this function failed with status code -7 while other c6accel functions worked well. Since -7 is for IUNIVERSAL_EFXNIDFAIL, I switched its ID with a c6accel function IMG_histogram_8's ID. for example:

#define IMG_HISTOGRAM_8_FXN_ID 0X01020009

#define MY_FXN_ID 0X01020100

and switched them.

Now the IMG_histogram_8 returns "pixel mismatch at offset 7, c6accel=0 Native = 1 c6accel_IMG_histogram_8 failed" and my vlib function fails with status -6.

1. As far as I'm concern, the ID is the only way the DSP can identify which function is called from ARM-side. As long as I change a function ID in C6Accel.h and iC6Accel.h in both DSP side and ARM side, the function should still work. Why the IMG_histogram_8 is not working?

2. Does the status -6 of UNIVERSAL_process return by DSP function C6accel_ti_imglibFunctionCall? If so why I changed the return(IUNIVERSAL_EPARAMFAIL) to other values but it still returned -6?

Can anyone help me with these issues?

Thanks,

Shawn 

  • 0
    Prodigy 70 points

    You might ignore my post. Just found out in the latest dvsdk 4.03 contains c6accel_1_01_00_07 which has vlib added. I'll work on this package instead. 

  • 0 in reply to Shawn Gao
    Prodigy 70 points

    I've figure out what happened on my first post. The reason is simple. You need to copy c6accel_omap3530.x64P, cmemk.ko,dsplinkk.ko,lpm_omap3530.ko,sdmak.ko to your target file system after you modify the c6accel package. In my case I failed to update these files in the target system and I used the old ones. So no changes on DSP side have been made at runtime. 

    FYI.