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.

the usage of IMG_perimeter

Hi,all

           I am doing some image processing work on evmDM642.When I want to deal with the binary image with the function of IMG_perimeter  of IMGLIB. The application can't run  continue. I list my part of code:

           for ( i = 0; i < numLines; i ++ )
           {               
                     
                    ...

                    ICETEKDM642PCIImagebinary(i);
                   IMG_perimeter(nSegmentTemp+i*capLinePitch,720,binary_out+i*capLinePitch);
             }
          for ( i = 0; i < numLines-2; i ++ )
          {
            yc2rgb16(coeffs, binary_out+i*capLinePitch,
                                    capFrameBuf->frame.iFrm.cb1 + (capLinePitch >> 1) * i,
                                   capFrameBuf->frame.iFrm.cr1 + (capLinePitch >> 1) * i,
                                  disFrameBuf->frame.rpFrm.buf + (disLinePitch << 1) * i,
                                  numPixels); 
           }

         the varible of nSegmentTemp stored with the binary image,I use the IMG_perimeter function to process the image line by line,the output image stored in the varible of binary_out. and then ,I want to display it on the monitor of VGA. BUT, the application run to the Disassembly :

00000508 11409A80            .word         0x11409a80
0000050C 00800414            .word         0x00800414
 AND it halt. The monitor display nothing . Why this happend? Is the error of the function invoke,or something?

Thank you very much!

  • Jun,

     

    You need to implement some basic debug methods in your code and provide a lot more details in order to narrow down your issue.  I am not familiar with what  ICETEKDM642PCIImagebinary() is, as I don't believe that is part of IMGLIB.  I'd suggest compiling the code without optimization on and with symbols enabled and then using breakpoints to stop the code and examine params being passed and return values.  You need to narrow down which function or lines of code are actually causing your issue before anyone can venture a guess as to what may be wrong.