Android Camera (quad): Camera driver GT2005

Camera Main parameters:

1, MCLK 24MHz;

2, PCLK 48~52mhz~;

3, Voltage 1.8V (1.5V), 2.8V;

4, SCL (IIC clock) 100KHz or 400KHz.

Download: Common camera Spec book (individual with Android driver) : bf3703 30W, gc0308 30W, ov7670, gt2005 200W, gt2015 200W, NT99250 200W, S5k5ba 200W, S5k4ba

First, the camera driver

Let's take GT2005 as an example to tell a camera-driven debug process:

The diagram of the camera and the master control is as follows:

Camera driver is relatively simple, three major steps to complete a single step:

The basic condition of the camera's power-up and clock;

IIC guarantees the initialization of the camera;

The camera returns data to the master after working.

Complete these three steps to complete the basic work of the camera debugging.

1, the camera's power-up, clock these basic conditions of implementation

Power supply Section, corresponding to the specification when power on, confirm the power-on timing; MCLK the camera's main clock is available, see below is and the power and specifications in the book

(1), the idea of the camera work to two sets of voltage: 1.8V (1.5V), 2.8V and MCLK

Power control in the program: in the ARCH\ARM\MACH-SMDKV310.C, we complete the above two steps of the code, (this point may be different platform, here is an example, this part of the code is only for the Samsung platform)

[CPP]View Plaincopy

2. #ifdef config_video_gt2005
4. static void Set_cam2005_main_power (int onoff)
8. {
12. unsigned int gpio;
14. int err;
18. if (onoff)
20. {
22. Err = Gpio_request (S5PV210_GPB (2), "GPB");
24. if (err)
26. PRINTK (Kern_err "# # # Failed to request GPB2 for cam\n");
28. S3c_gpio_cfgpin (S5PV210_GPB (2), s3c_gpio_output);
30. S3c_gpio_setpull (S5PV210_GPB (2), s3c_gpio_pull_up);
32. Gpio_direction_output (S5PV210_GPB (2), 1);
34. Gpio_free (S5PV210_GPB (2));
38. //reset
40. Err = Gpio_request (S5pv210_gpe1 (4), "GPE1");
42. if (err)
44. PRINTK (Kern_err "# # # Failed to request gpe1_4 for cam\n");
46. S3c_gpio_setpull (S5pv210_gpe1 (4), s3c_gpio_pull_none);
48. Gpio_direction_output (S5pv210_gpe1 (4), 0);
50. Mdelay (100);
52. Gpio_direction_output (S5pv210_gpe1 (4), 1);
54. Gpio_free (S5pv210_gpe1 (4));
60. //PWDN Cam_back
62. Err = Gpio_request (S5PV210_GPB (4), "GPB");
64. if (err)
66. PRINTK (Kern_err "# # # Failed to request GPB4 for cam\n");
68. S3c_gpio_cfgpin (S5PV210_GPB (4), s3c_gpio_output);
70. S3c_gpio_setpull (S5PV210_GPB (4), s3c_gpio_pull_up);
72. Gpio_direction_output (S5PV210_GPB (4), 0);
74. Mdelay (100);
76. Gpio_direction_output (S5PV210_GPB (4), 1);
78. Gpio_free (S5PV210_GPB (4));
82. }
84. Else
86. {
88. ..................
90. }
92. return;
94. }
96. #endif

Provide the MCLK code as follows:

[CPP]View Plaincopy

2. static int smdkv210_cam_clk_init (void)
4. {
6. unsigned int tempvalue=0;
8. Tempvalue = Readl (S5P_CLK_DIV1);
10. Tempvalue = (Tempvalue &0xffff0fff);
12. Writel (TEMPVALUE,S5P_CLK_DIV1);
14. Tempvalue = Readl (S5P_CLK_SRC1);
16. Tempvalue = (Tempvalue &0xffff0fff) |0x00001000;
18. Writel (TEMPVALUE,S5P_CLK_SRC1);
22. return 0;
24. }

At this time take the oscilloscope caught on the power of the waveform and Mclk24mhz clock, signal that we have completed this step, in fact, in the actual work, we generally have problems when the data will be measured, confirm the problem point.

Power-up sequence:

(1), power-up sequence;

(2), mclk as shown below.

2, IIC and some parameters of the configuration

[CPP]View Plaincopy

2. #ifdef config_video_gt2005
4. Static struct Gt2005_platform_data Gt2005_plat = {
6. . Default_width = 640,
8. . Default_height = 480,
10. . PixelFormat = V4l2_pix_fmt_uyvy, //. Freq = 24000000,
12. . Is_mipi = 0,
14. };
18. Static struct I2c_board_info gt2005_i2c_info = {
20. I2c_board_info ("GT2005", 0x78 >> 1), //1, IIC address
22. . Platform_data = >2005_plat,
24. };
28. Static struct S3c_platform_camera GT2005 = {
30. #ifdef CAM_ITU_CH_A
32. . id = camera_par_a,
34. #else
36. . id = camera_par_b,
38. #endif
40. . Type = Cam_type_itu, //2, Data Interface selection (ITU\MIPI, etc.)
42. . FMT = Itu_601_ycbcr422_8bit,
44. . order422 = Cam_order422_8bit_cbycry, //3, image Data format
48. . I2c_busnum = 1,
50. . info = >2005_i2c_info,
52. . PixelFormat = V4l2_pix_fmt_uyvy,
54. . Srclk_name = "MOUT_MPLL", //4, this part relates to the clock
56. . Clk_name = "sclk_cam1",
58. . clk_rate = 24000000,/ * 24MHz * /
60. . Line_length = 640,/ * 640*480 * /
62. / * Default resol for preview kind of thing * /
64. . width = 640,
66. . Height = 480,
68. . window = {
70. . left = 16,
72. . top = 0,
74. . width = (640-16),
76. . Height = 480,
78. },
82. /* Polarity * //5, signal polarity,. INV_PCLK = 0,
84. . Inv_vsync = 1,
86. . Inv_href = 0,
88. . Inv_hsync = 1,
92. . initialized = 0,
94. . cam_power=set_cam2005_main_power
96. };
98. #endif

Note the following parameters:

(1), IIC address

(2), Data Interface selection (ITU\MIPI, etc.), these data interfaces we mentioned earlier;

(3), image Data format, this is the yvu\uvy we mentioned earlier, such as different data order;

(4), this part relates to the clock;

(5), the polarity of the output signal, is our pclk, VSYNC, hsvnc the polarity of these signals, incorrect when there will be no image and other phenomena, this also should be noted.

Complete this step to confirm that the IIC communication is normal, such as the captured waveform:

3, complete the above two steps, the basic configuration of the camera is completed, we confirm the output end PCLK, VHSN, SVSN, D1-d7

Second, the camera debugging process often encountered problems

1, video in the preview when the normal, playing the recording of the flower screen (The program is interpreted as Samsung s5pv210/s5pv310 Yes, other can refer to, find the corresponding code)

Cause analysis: (1) FIMC2 of recording phase,

int Seccamera::startrecord (void) in Android/device/samsung/proprietary/libcamera/seccamera.cpp

[CPP]View Plaincopy

1. M_cam_fd_rec = open (camera_dev_name2, O_RDWR);
3. Vendor\sec\sec_proprietary\smdkc110\libcamera\seccamera.h
4. #define CAMERA_DEV_NAME2 "/dev/video2"

(2) The video format used in the

In Android/device/samsung/proprietary/libcamera/seccamerahwinterface.cpp

void camerahardwaresec::m_initdefaultparameters (int camera_id)

[CPP]View Plaincopy

2. int default_preview_pixel_format = Mseccamera->getpreviewdefaultpixelformat ();
4. switch (default_preview_pixel_format) {
6. Default:
8. Case V4L2_PIX_FMT_NV21:
10. P.setpreviewformat (cameraparameters::P ixel_format_yuv420sp);
12. Break ;
14. Case v4l2_pix_fmt_nv12t:
16. P.setpreviewformat ("yuv420sp_tiled");
18. Break ;
20. }
24. where Mseccamera->getpreviewdefaultpixelformat () in
26. Implemented in Vendor\sec\sec_proprietary\smdkc110\libcamera\seccamera.cpp,
28. int Seccamera::getpreviewdefaultpixelformat (void)
30. {
32. return Default_preview_pixel_format;
34. }
36. Set the initial value in the Android/device/samsung/proprietary/libcamera/seccamera.h. What we've set up here is
38. #ifdef dual_port_recording
40. #define DEFAULT_PREVIEW_PIXEL_FORMAT (V4L2_PIX_FMT_NV21)
42. #else
44. #define DEFAULT_PREVIEW_PIXEL_FORMAT (V4L2_PIX_FMT_NV12T)
46. #endif

the above results in video format V4l2_pix_fmt_nv21.

2, the image interference problem, as shown in

The reasons may be:

(1), Camera module has a problem, change a camera to try;

(2), the data line drive capacity is insufficient, this can be changed in the camera register, ask the camera module FAE, see Change those places;

(3), two cameras shared data cable, the non-working camera will reduce the working data signal;

(4), PCB traces too long, there will be interference, but I think this possibility is small, debugging good on a such, module factory Fae said, but they have problems in the module itself, two factors are: PCB (line too long), module proofing also have problems.

3, the YUV sequence is not correct:

The following behavior occurs when the YUV sequence is incorrect.

Look at the camera specification book, the corresponding register value can be changed. The following in red box is a different YUV order, find the corresponding.

4, the preview direction is not correct (the camera register can only be changed to 180 degrees for the base, 90 degrees will be in the FIMC change)

To know and more clearly explain the flip angle, the most commonly used is to write an "F", and then see the preview of how to turn.

It has a 90-degree flip, because this is a register in the FIMC, and this part of the value is generally not changed. Either change it in the module register, or it will be on the upper level. The above just shows how to confirm the image rollover.

Look at the GT2005 about the flip register:

5. Miscellaneous Light, Ghost Shadow:

The jargon of the industry is known as flare, which refers to the shadow of a light or a complete object at the edge of a source or a strong light object, and this phenomenon can only be mitigated by the fact that the lens material causes the light not only to exist in refraction but also to reflect, Machine due to lens surface to protect the lens distance is more obvious!

6, common problems related

What are the camera effects evaluations?

Above take gt2005 as an example, said the camera drive, and drive common problems, if the above problem resolution, the camera is lit, indicating that the platform is running is no problem, small problems and details, to find the module Factory fae come to help solve, but you want to study more words, also can, if the project allows, To see more, to debug a driver, all the problems are understood, so that the work experience, accumulation is very important, I hope to be useful to everyone.

Android Camera (quad): Camera driver GT2005