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.

DM368 - AR0330 problem

Hello,

I want to build my own IP Camera. I want to stream video from a LI-CAM-AR0330 via a DM368. I up-lad the firmware and everything correctly. But the system boots without finishing. Please look bellow the final Time Out :

CONFIGURING AVSERVER FOR DM368 .....

queue id:65538

SENSOR FPS VALUE = 30

 i2c16_transfer(0x10, 0x30)

   pci

Read AR0330 Sensor ID:0x   0

 ERROR  (drv_imgs_AR0330_3.1MP.c|DRV_imgsCheckId|358): DRV_i2cRead16()

 i2c16_transfer(0x10, 0x30)

 i2c16_transfer(0x10, 0x30)

Read AR0330 Sensor ID:0x   0

 ERROR  (drv_imgs_AR0330_3.1MP.c|DRV_imgsCheckId|358): DRV_i2cRead16()

   pci      [success]

Read AR0330 Sensor  i2c16_transfer(0x10, 0x30)

ID:0x   0

 ERROR  (drv_imgs_AR0330_3.1MP.c|DRV_imgsCheckId|358): DRV_i2cRead16()

Read AR0330 Sensor ID:0x   0

 ERROR  (drv_imgs_AR0330_3.1MP. i2c16_transfer(0x10, 0x30)

c|DRV_imgsCheckId|358): DRV_i2cRead16()

Read AR0330 Sensor ID:0x   0

 ERROR  (drv_imgs_AR0330_3.1MP.c|DRV_imgsCheckId|358): DRV_i2cRead16()

 i2c16_transfer(0x10, 0x30)

 i2c16_transfer(0x10, 0x30)

Read AR0330 Sensor ID:0x   0

 ERROR  (drv_imgs_AR0330_3.1MP.c|DRV_imgsCheckId|358): DRV_i2cRead16()

   usb

 i2c16_transfer(0x10, 0x30)0

 

 ERROR  (drv_imgs_AR0330_3.1MP.c|DRV_imgsCheckId|358): DRV_i2cRead16()

Read AR0330 Sensor ID:0x   0

 ERROR  (drv_imgs_AR0330_3.1MP.c|DRV_imgs i2c16_transfer(0x10, 0x30)

CheckId|358): DRV_i2cRead16()

Read AR0330 Sensor ID:0x   0

 ERROR  (drv_imgs_AR0330_3.1MP.c|DRV_imgsCheckId|358): DRV_i2cRead16()

 i2c16_transfer(0x10, 0x30)

 i2c16_transfer(0x10, 0x30)

Read AR0330 Sensor ID:0x   0

 ERROR  (drv_imgs_AR0330_3.1MP.c|DRV_imgsCheckId|358): DRV_i2cRead16()

Read AR0330 Sensor ID:0x   0

 ERROR  (drv_imgs_AR0330_3.1MP.c|DRV_imgsCheckId|358): DRV_i2cRead16()

 ERROR  (drv_imgs_AR0330_3.1MP.c|DRV_imgsOpen|62): DRV_imgsCheckId()

 ERROR  (drv_capture.c|DRV_captureOpen|63): Open failed

 ERROR  (videoCaptureThr.c|VIDEO_captureTskCreate|82): DRV_captureOpen()

 ERROR  (videoCaptureThr.c|VIDEO_captureTskMain|741): VIDEO_captureTskCreate() ERROR  (avServerMainThr.c|AVSERVER_tskStart|24):

   usb      [success]

   isapnp

   isapnp   [success]

   ide

   ide      [success]

   input

   input    [success]

   scsi

   scsi     [success]

done.

Starting portmap daemon: portmap.

Starting internet superserver: inetd.

io scheduler deadline registered

io scheduler cfq registered

 sbulla: unknown partition table

Installing knfsd (copyright (C) 1996 okir@monad.swb.de).

loop: loaded (max 8 devices)

tun: Universal TUN/TAP device driver, 1.6

tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>

CSLIP: code copyright 1989 Regents of the University of California

netconsole: not configured, aborting

PPP generic driver version 2.4.2

PPP Deflate Compression module registered

davinci-mmc davinci-mmc.0: Supporting 4-bit mode

davinci-mmc davinci-mmc.0: Using DMA mode

usbcore: registered new driver usbfs

usbcore: registered new driver hub

musb_hdrc: version 6.0, cppi-dma, peripheral, debug=0

musb_hdrc musb_hdrc: No DMA interrupt line

musb_hdrc: USB Peripheral mode controller at c40fa000 using DMA, IRQ 12

Loading iSCSI transport class v1.1-646.<5>iscsi: registered transport (tcp)

 sbulla: unknown partition table

mkdosfs 3.0.6 (04 Oct 2009)

unable to get drive geometry, using default 255/63

/dev/sbulla has 255 heads and 63 sectors per track,

logical sector size is 512,

using 0xf8 media descriptor, with 1024 sectors;

file system has 2 12-bit FATs and 4 sectors per cluster.

FAT size is 1 sector, and provides 247 clusters.

Root directory contains 512 slots.

Volume ID is 35c47aa1, no volume label.

queue id:0

TimeOut occure in boot_proc.

Program exit.

ApproDrvInit: 3

queue id:131076

INIT: Entering runlevel: 3

Please tell me if you could help. 

Best

  • hi 

            its looks like you have a problem with i2c ....its not able to read it properly , i suggest you to check your device nod, whether it is registered to correct major number , then try to test i2c peripheral by reading and writing through test application. it might help you.