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.

AM5728: OpenCV OpenCL offload

Part Number: AM5728
Other Parts Discussed in Thread: SYSBIOS

Hi

I am using ti-processor-sdk-linux-am57xx-evm-04.03.00.05,which include opencl-1.1.14.10-r0.0 and opencv/3.1+gitAUTOINC+9b88e8c746-r3

I have read the TI OpenCV wiki, and I get the similar data:

when opencl off, for 1080P JPEG picture, Canny cost 145ms; when opencl on, Canny cost 17ms.

When I process two same pictures consecutively in the same program, the timing becomes strange

opencl on: Fisrt process:  11ms, Second process: 0.58ms; I try more image process, others always 0.5+ms

Q1:Why is there such a strange phenomenon?

I use OE to create a filesytem, which include dra7-dsp1-fw.xe66.opencl-monitor and dra7-dsp2-fw.xe66.opencl-monitor, which is work fine at openc on status.The above data is based on these two firmware tests

When I use the file system that comes with the SDK package, which dsp monitor firmware is work fine at opencl off, but opencl on, dsp will crash.

root@am57xx-evm:~# cat /sys/kernel/debug/remoteproc/remoteproc2/trace0
[      0.000] 20 Resource entries at 0xfec00000
[      0.000] registering rpmsg-proto:rpmsg-proto service on 61 with HOST
[     74.241] A0=0x1 A1=0xfecc78f4
[     74.241] A2=0x0 A3=0x437f0000
[     74.241] A4=0x0 A5=0x0
[     74.241] A6=0x0 A7=0x0
[     74.241] A8=0x0 A9=0xa2fe4b88
[     74.241] A10=0x1d31bdc0 A11=0x80dbde00
[     74.241] A12=0x808000 A13=0x808124
[     74.241] A14=0x88 A15=0x0
[     74.241] A16=0x77f A17=0x5fc90c0e
[     74.241] A18=0x5fc9100d A19=0x5fc90ffe
[     74.241] A20=0x780 A21=0x440
[     74.241] A22=0x1800144 A23=0x1800140
[     74.241] A24=0x180010c A25=0x20
[     74.241] A26=0xfef26060 A27=0x0
[     74.241] A28=0x88 A29=0x90
[     74.241] A30=0x0 A31=0x808120
[     74.241] B0=0x0 B1=0x1
[     74.241] B2=0xfffffff9 B3=0x808090
[     74.241] B4=0x0 B5=0x437f0000
[     74.241] B6=0x437f0000 B7=0x1d31bdc0
[     74.241] B8=0x1ee95f80 B9=0xffffffff
[     74.241] B10=0x90 B11=0x0
[     74.241] B12=0x808128 B13=0xa25f0000
[     74.241] B14=0x0 B15=0x802668
[     74.241] B16=0x805d36 B17=0x77f
[     74.241] B18=0x437 B19=0x400
[     74.241] B20=0x5fc90ffe B21=0xff
[     74.241] B22=0x5fc9100d B23=0x0
[     74.241] B24=0x1fa3ff B25=0x20
[     74.241] B26=0x400 B27=0x50f
[     74.241] B28=0x400 B29=0x50f
[     74.241] B30=0x510 B31=0xfedfcb60
[     74.241] NTSR=0x1000f
[     74.241] ITSR=0xd
[     74.241] IRP=0xfec21090
[     74.241] SSR=0x0
[     74.241] AMR=0x0
[     74.241] RILC=0x800080
[     74.241] ILC=0x0
[     74.241] Exception at 0x809440
[     74.241] EFR=0x2 NRP=0x809440
[     74.241] Internal exception: IERR=0x2
[     74.241] Fetch packet exception
[     74.241] [t=0x0007da0b] ti.sysbios.family.c64p.Exception: ERROR: line 256:                                                                                                                                                              E_exceptionMax: pc = 0x00809440, sp = 0x00802668.
[     74.241] ti.sysbios.family.c64p.Exception: line 256: E_exceptionMax: pc = 0                                                                                                                                                             x00809440, sp = 0x00802668.
[     74.241] xdc.runtime.Error.raise: terminating execution
root@am57xx-evm:~#

Q2: Why the SDK dsp monitor firmware will crash when opencl on? Can you recurrent it?

If you have any idea, please let me know.

Thanks.