Reply
Regular Visitor
Posts: 7
Registered: ‎11-11-2011

Camera Frame Buffer Demo migrate to ML 605 board

Hello,

I have   purchased the following hardware separately:
  AES-FMC-IMAGEOV-V1       Dual Image Sensor FMC Module
  AES-ACC-OV9517-G         OmniVision 1 MP Camera Kit with Ribbon Cable

I want to migrate these into an ML 605 board (EDK 13.1). I have many difficulties doing this based on the IVK_Camera_Frame_Buffer_Demo. My biggest concern right now is that some brams are utilized for the Spartan6 family and their .mif files are missing,  so I’m not able to rebuild them for the Virtex6 family. So I would like to ask for those .mif files or even the coregen project files to rebuild them correctly.
Are there any other issues to know about or a workflow that I should follow in order to do this?

I’m not interesting in all the functionality of the IVK_Camera_Frame_Buffer_Demo, I just need to capture a video stream and extract some frames.

Thank you in advance,

Antonis
Avnet Employee (Star Contributor)
Posts: 471
Registered: ‎04-16-2009

Re: Camera Frame Buffer Demo migrate to ML 605 board

Antonis,

 

You should not have to manually include MIF files (I didn't).

I think you may be on a false path ...

 

Can you send me your project so that I can look at it.

I may be able to resolve your issue quickly.

 

Regards,

 

Mario.

Regular Visitor
Posts: 7
Registered: ‎11-11-2011

Re: Camera Frame Buffer Demo migrate to ML 605 board

Mario,

 

I attach you the project files

 

I get the following error during map process:

 

NgdBuild:604 - logical block 'sg_i2c_controller_s6_plbw_0/sg_i2c_controller_s6_plbw_0/sysgen_dut/sg_i2c_controller_s6_x0/i2c_controller_e098cd9e07/picoblaze_rom/comp0.core_instance0/BU2/U0/blk_mem_generator/valid.cstr/ramloop[0].ram.r/s6_init.ram/SP.SIMPLE_PRIM18.ram' with type 'RAMB16BWER' could not be resolved. A pin name misspelling can cause this, a missing edif or ngc file, case mismatch between the block name and the edif or ngc file name, or the misspelling of a type name. Symbol 'RAMB16BWER' is not supported in target 'virtex6'.

 

Regards

Antonis

 

Avnet Employee (Star Contributor)
Posts: 471
Registered: ‎04-16-2009

Re: Camera Frame Buffer Demo migrate to ML 605 board

Antonis,

 

The "sg_i2c_controller_s6_plbw_v1_01_a", as well as all the PCOREs with "_s6_" in their name were generated for the Spartan-6 and will not build for the Virtex-6.

 

I have attached the IVK repository with "_v6_" versions of the PCORES.

 

Replace all of the "_s6_" PCOREs with the equivalent "_v6_" version.

 

Regards,

 

Mario.

Regular Visitor
Posts: 7
Registered: ‎11-11-2011

Re: Camera Frame Buffer Demo migrate to ML 605 board

Mario,

 

The EDK project is successfully built for the ML605 board, but I now get a series of errors in SDK (13.1) when I port the software files taken from the EDK 12.2 project. Is there any SDK project for the Camera Frame Buffer Demo available to start with? It would be rather helpful. I attach my current SDK 13.1 project which is failing to compile.

 

Antonis.

Avnet Employee (Star Contributor)
Posts: 471
Registered: ‎04-16-2009

Re: Camera Frame Buffer Demo migrate to ML 605 board

Antonis,

 

There may be several causes of errors:

   - building without the required software libraries

   - code has not been modified for the _V6_ versions of the pcores

 

======================================================

Building with required software libraries

======================================================

 

Let's start with the first probable cause ...

 

I noticed in your system.mss file that there is no software libraries specified.

The IVK applications need to be linked with the following software libraries:

   fmc_iic_sw

   fmc_ipmi_sw

   fmc_imageov_sw

   fmc_dvidp_sw

 

These software libraries are located in the following directory:

  ..\IVK_Repository\IVKProcessorIPLib\sw_services  

 

I noticed that you tried a couple of things:

   - specifying the individual software library directories in the repositories

      => you need to specify the directory above "sw_services", as descrived below

   - copying the software library files to your application directory

      => this is one way of doing it, I would recommend to do it properly as described below

      => first, delete the software library files you copied over ...

  

Here is how you can add these software libraries to your SDK project.

 

SDK menu => Tools => Repositories

   add the following path to the local repositories (visible to this SDK project)

   or to the global repositories (visible to all SDK projects)

        ..\IVK_Repository\IVKProcessorIPLib

 

SDK menu => Tools => Board Support Package Settings

   select the following software libraries

      fmc_iic_sw

      fmc_ipmi_sw

      fmc_imageov_sw

      fmc_dvidp_sw

   click OK, this will re-build the BSP and your application(s)

 

======================================================

Modifying the code for the _V6_ versions of the pcores

======================================================

 

Code such as the following:

  

   #if defined(XPAR_SG_I2C_CONTROLLER_S6_PLBW_NUM_INSTANCES)

   #include "sg_i2c_controller_s6_plbw.h"

   #define SG_I2C_CONTROLLER_PLBW_ConfigTable SG_I2C_CONTROLLER_S6_PLBW_ConfigTable

   #endif

 

Needs to be changed for the _V6_ versions of the pcores, as shown below.

 

   #if defined(XPAR_SG_I2C_CONTROLLER_V6_PLBW_NUM_INSTANCES)

   #include "sg_i2c_controller_v6_plbw.h"

   #define SG_I2C_CONTROLLER_PLBW_ConfigTable SG_I2C_CONTROLLER_V6_PLBW_ConfigTable

   #endif

 

There may be several instances of this kind of code. 

You will notice that I wrote my code so that it only needs to be changed in one place (for each pcore, typically).

 

Regards,

 

Mario.

Contributor
Posts: 12
Registered: ‎02-14-2011

Re: Camera Frame Buffer Demo migrate to ML 605 board

HI,

 

have you got it to work on ML605 without the Net "fmc_imageov_video_clk_pin" CLOCK_DEDICATED_ROUTE = FALSE ? 

and have you manage to get a stable output on the monitor ? 

 

i am getting shaking image on the monitor, and i am not sure why this is happening.

 

 

 

 

 

Regular Visitor
Posts: 7
Registered: ‎11-11-2011

Re: Camera Frame Buffer Demo migrate to ML 605 board

Hi

I have forced to set  "fmc_imageov_video_clk_pin" CLOCK_DEDICATED_ROUTE = FALSE" in order to bypass an error during build in XPS. I haven't finished the SDK project yet to check if I get a proper output on the monitor.

 

Antonis

Contributor
Posts: 12
Registered: ‎02-14-2011

Re: Camera Frame Buffer Demo migrate to ML 605 board

[ Edited ]

Right, after leaving it aside for awhile, I have now come back to this design, 

regarding the shaking images that I am getting, I am now hunting down to find out where is the exact problem.

 

first, i set the omnivision to generate a test pattern using the following : ivk_camera_test_pattern_config(1, 1); this sets the image sensor to generate the colorbars, white, yellow, ...., blue, black 

when I run this, on the LCD, I manage to get the color bars, but not a consistent colorbar, it sort of shakes, example with the white bar having some pinks appearing before the yellow. 

 

then I put in a chipscope on the ivk_video_det debug port, and checking the data in the chipscope I notice the problem now.

on the white section, its suppose to be FE,FE,FE for the respective RGB, but looking at it, I have some rubbish on 1 of the G part, and it turns out to be PINK when converted, which is exactly what I see on the image.

 

i've attached the chipscope image file, have a look.

so what have I done wrong...... ? hm.... trying to get to solve this problem to proceed with my design. 

any help is appreciated. thanks

 

Chee Kin

 

edit : for color conversion : http://drpeterjones.com/colorcalc/

ivk_video_det_chipscope.jpg
Avnet Employee (Star Contributor)
Posts: 471
Registered: ‎04-16-2009

Re: Camera Frame Buffer Demo migrate to ML 605 board

I am not sure what could be causing this shaking ...

 

Would it be possible for you to send me your design ?

I now have the hardware to reproduce your setup.

 

Regards,

 

Mario.