Thanks Adam.
We have purchased Davinci DM3730 Logic PD Zoom kit. After setting up the board as per the manual. I observed that the:
1) DM3730 Torpedo + Wireless SOM is not booting up (No UART logs and LCD display). And also the chip is heating up. Is there anything I can do to confirm the behavior. Do I need to raise a request for replacement?
2) DM3730 Torpedo SOM is booting up and UART logs are seen. But it is not taking the IPAddress. The following error is seen:

"Setting up networking on loopback device:
Setting up networking on eth0:
udhcpc: SIOCGIFINDEX: No such device"

Note:  I have started the product registration process.

Thanks,
Swathi

I should note the RMA for the Torpedo + Wireless should route through the distributor where you purchased the SOM.

adam

If you're going to use the 2.4-4 BSP, you'll want to review the custom board file. On our virtual machine, it's located: ~/logic/Logic_BSPs/Linux_3.0/1027480_LogicPD_Linux_BSP_2.4-4/rpm/BUILD/linux/arch/arm/mach-omap2/board-omap3logic.c

Inside here, there are some structures setup for the camera. Specifically, the

isp_v4l2_subdevs_group omap3logic_camera_subdevs[] = {
     .interface = ISP_INTERFACE_PARALLEL,
     .bus = {
          .parallel = {
          .data_lane_shift = ISPCTRL_SHIFT_0 >> ISPCTRL_SHIFT_SHIFT, //3.3+ISP_LANE_SHIFT_0,
          .clk_pol = 0,
          .hs_pol = 0, // HSYNC not inverted
          .vs_pol = 0, // VSYNC not inverted
          .bridge = ISPCTRL_PAR_BRIDGE_LENDIAN>> ISPCTRL_PAR_BRIDGE_SHIFT //3.3+ISP_BRIDGE_LITTLE_ENDIAN,
//3.3+ .bt656 = 0,
           },
},
 

The .interface references the ISP_INTERFACE_PARALLEL

The bus references parallel, and the various pol entries determine whether or not they are inverted or not (ie active low/high)

There is also the pin-muxing entires that tell the system how to configure the various GPIO pins and route them to the ISP camera interface.

static void dm3730logic_camera_init(void)
{
        omap_mux_init_signal("cam_hs.cam_hs",OMAP_PIN_INPUT);
        omap_mux_init_signal("cam_vs.cam_vs",OMAP_PIN_INPUT);
        omap_mux_init_signal("cam_xclka.cam_xclka", OMAP_PIN_INPUT);
//        omap_mux_init_signal("cam_xclkb.cam_xclkb", OMAP_PIN_INPUT);
        omap_mux_init_signal("cam_pclk.cam_pclk", OMAP_PIN_INPUT);

        omap_mux_init_signal("cam_d0.cam_d0", OMAP_PIN_INPUT);
        omap_mux_init_signal("cam_d1.cam_d1", OMAP_PIN_INPUT);
        omap_mux_init_signal("cam_d2.cam_d2", OMAP_PIN_INPUT);
        omap_mux_init_signal("cam_d3.cam_d3", OMAP_PIN_INPUT);
        omap_mux_init_signal("cam_d4.cam_d4", OMAP_PIN_INPUT);
        omap_mux_init_signal("cam_d5.cam_d5", OMAP_PIN_INPUT);
        omap_mux_init_signal("cam_d6.cam_d6", OMAP_PIN_INPUT);
        omap_mux_init_signal("cam_d7.cam_d7", OMAP_PIN_INPUT);
}

From the kit, you can run
# media-ctl --print-dot

That will dump a bunch of text. If you then copy that text to your host machine and create a text file called pipeline.dot, you can convert the output of that to a graphic which will show the pipeline options.

dot -T png -o pipeline.png pipeline.dot