report an APEX kernel bug

cancel
Showing results for 
Search instead for 
Did you mean: 

report an APEX kernel bug

Jump to solution
489 Views
1054072686
Contributor I

report an APEX bug, it doesn't happen in EMU environment.
Create a very simple project with one input and one output
matNumberInlet0(512, 512, VSDK_CV_8UC1);
matNumberOutlet0(512, 512, VSDK_CV_8UC1)
write only one code in kernel like-->
static int staticint = 0;
vec32u* pDst = (vec32u*)dst0;
pDst[staticint] = staticint++;
return;
//expect result, every iteration, only one line's value is set.
//wrong result, at the first iteration, not only 0, but also 64, 128, ... lines's value is set.
// then you can see different values(1,3,5,7....) is set is the last rows, although i just expect to see one line is set at the bottom.

Labels (1)
0 Kudos
1 Solution
331 Views
1054072686
Contributor I

I think I already got the answer for this issue.
It's due to APEX will copy CMEM buffer to output matrix repeatedly by default even if you did nothing during some of the iterations.
that means if you change a value in the first iteration, but you did nothing in all other following iterations.
because the CMEM buffer may include several iteration contents, so the first iteration result will be copied to some other iterations.
thus you will get a wrong impression, you assign value once, but many lines are assinged.

you can say it is an apex bug, also you can say it's not.

--Smith Ou

View solution in original post

2 Replies
332 Views
1054072686
Contributor I

I think I already got the answer for this issue.
It's due to APEX will copy CMEM buffer to output matrix repeatedly by default even if you did nothing during some of the iterations.
that means if you change a value in the first iteration, but you did nothing in all other following iterations.
because the CMEM buffer may include several iteration contents, so the first iteration result will be copied to some other iterations.
thus you will get a wrong impression, you assign value once, but many lines are assinged.

you can say it is an apex bug, also you can say it's not.

--Smith Ou

View solution in original post

331 Views
dumitru-daniel_
NXP Employee
NXP Employee

Hi christinaxu,

In case of bug reports for the Vision SDK via NXP Community, what is the preferred way to handle these subjects?

Do you know is there is a dedicated person for support VSDK issues on the community?


In general, this community space was created to handle MATLAB Vision Toolbox related issues but if we can help users in generic Vision SDK topics we will be happy to do it.

Thank you!

Daniel

0 Kudos