[Adi-linux-docs] page changed: mcapi_bmp2jpg_demo: [Test method]

[aaronwu1 <no...@do...>]

New Revision: http://docs.blackfin.uclinux.org/doku.php?id=mcapi_bmp2jpg
_demo

Old Revision: http://docs.blackfin.uclinux.org/doku.php?id=mcapi_bmp2jpg
_demo&rev=1385610113

Edit Summary: [Test method] 



@@ -3,11 +3,10 @@

  This is a MCAPI dual core communication demo case for bf609. With the he
lp of MCAPI, we can run general task on coreA with Linux, and run other CP
U consuming tasks on coreB bear_metal environment. In this demo, coreA ope
n a bmp file, which is captured from the USB camera, pass it to coreB to d
ecode into jpeg. Once the encoding work is done, coreA get notified and co
ntinue to save it as a jpeg file. This feature is available since 2013 rel
ease.

  

  ===== Test method=====

  

- First configure the kernel and buildroot distribution as other general M
CAPI test case, as described in https://docs.blackfin.uclinux.org/doku.php
?id=test_icc

+ First configure the kernel and buildroot distribution as other general M
CAPI test case, as described in https://docs.blackfin.uclinux.org/doku.php
?id=test_icc, configure to enable the USB camera following http://docs.b
lackfin.uclinux.org/doku.php?id=linux-kernel:drivers:usb_video_device_cl
ass, and select to enable the ffmpeg.

  

- Then put a BMP file of 24bpp(or use this one directly: {{:test.zip|}})un
der /bin of your target board, run following:

  

  load icc server to slave core

  <code>

  root:/> cd bin

@@ -23,5 +22,5 @@

  <code>

  root:/bin> bmp2jpg

  </code>  

  

- When the above is done, you should have a test.jpg file created in root 
directory of your target board.

+ When the above is done, you should have a test.jpg file created in /bin 
of your target board.