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.

some bugs in DM365_DVR_DVSDK3_00.02.00.00.zip

Other Parts Discussed in Thread: TVP5158, TVP7002

hi,experts

i find DM365_DVR_DVSDK3_00.02.00.00.zip  has some bugs.

1,board-dm365-evm.c in mcvip lsp_file dir,line 139,

'static struct tvp7002_platform_data tvp5158_pdata={ ' should be 'static struct tvp5158_platform_data tvp5158_pdata={ '

2,board-dm365-evm.c  should include tvp5158.h

after rectifying above code,i add

static struct i2c_board_info i2c_info[]={

....

{I2C_BOARD_INFO("tvp5158",0x5B),},

....

};

then i could find tvp5158 in boot infomation:

Linux video capture interface: v2.00                                           
ths7303 1-002c: chip found @ 0x58 (DaVinci I2C adapter)                        
{ tvp5158_probe                                                                
tvp5158 1-005b: chip found @ 0xb6 (DaVinci I2C adapter)                        
tvp5158 1-005b: tvp5158 1-005b decoder driver registered !!                    
tvp5158_initialize}                                                            
tvp5158_probe}                                                                 
I2C: Module install successful, device major num = 251                         
DMA: Module install successful, device major num = 250                         
TVP5158: Module built on Mar  5 2012 18:18:23                                  
vpfe_init                                                                      
vpfe-capture: vpss clock vpss_master enabled                                   
vpfe-capture vpfe-capture: v4l2 device registered                              
vpfe-capture vpfe-capture: video device registered                             
mt9p031 1-0048: No MT9P031 chip detected, register read ffffff87               
vpfe-capture vpfe-capture: v4l2 sub device mt9p031 register fails  

If not,dm365 could not find tvp5158.

However,i run mcvip.out ,i have another error:

if i run mcvip_test.out without slave i2c config,mcvip_test.out begin to run.but it can't find /dev/video0.Could any expert tell me what are /dev/video0 device major number and minor number?

i try "mknod /dev/video0 c 81 0 " and i get error msg :                                         
                                               
 MCVIP: Starting. Please wait !!!                                              
---- CAPTURE_tskMain -----                                                     
port: 0                                                                        
 CAPTURE: Alloc info: numCh=2 numBuf=8, bufSize=847872, allocSize=6782976      
 MCVIP_v4l2Create(TVP5158_1) video0                                            
 ERROR  (mcvip_v4l2.c|MCVIP_v4l2Create|82): Device does not support desired vide
o input!                                                                        
 ERROR  (capture_tsk.c|CAPTURE_tskCreate|96): MCVIP_create()                   
 ERROR  (main.c|UI_sysStart|90): CAPTURE_create()                              
 MCVIP: System Exiting !!!                                                     
 MCVIP: Bye Bye !!!                                                            

any comment,any light,any help would be appreciated greatly!

best regards

  • jonny,

    did you go through the reference docs especially ReleaseNotes_TVP5158_DVSDK3_DM365_DVR.doc, you need to do the following steps given.

    even after doing this you get any issues, get back with it..

    Regards,

    --Prabhakar Lad

  • Hi Prabhakar ,

    thank you for your reply.

    i just follow ReleaseNotes_TVP5158_DVSDK3_DM365_DVR.doc.first,copy lsp files to kernel.second,make new kernel and download to my board.three,run mcvip_test.out in my board.

    my trouble is board could not find tvp5158 chip on board.and my tvp5158 27M crystal is ok,all vcc supply of tvp5158 are ok.

    no vpfe-capture sub device is registered from boot infomation when my board power on.

    if i add

    static struct i2c_board_info i2c_info[]={

    ....

    {I2C_BOARD_INFO("tvp5158",0x5B),},

    ....

    };

    explicitly in my board config c file.similar with board-dm365-evm.c.

    i can find from boot msg:

    Linux video capture interface: v2.00                                           
    ths7303 1-002c: chip found @ 0x58 (DaVinci I2C adapter)                        
    { tvp5158_probe                                                                
    tvp5158 1-005b: chip found @ 0xb6 (DaVinci I2C adapter)                        
    tvp5158 1-005b: tvp5158 1-005b decoder driver registered !!                    
    tvp5158_initialize}                                                            
    tvp5158_probe}                                                                 
    I2C: Module install successful, device major num = 251                         
    DMA: Module install successful, device major num = 250                         
    TVP5158: Module built on Mar  5 2012 18:18:23                                  
    vpfe_init                                                                      
    vpfe-capture: vpss clock vpss_master enabled                                   
    vpfe-capture vpfe-capture: v4l2 device registered                              
    vpfe-capture vpfe-capture: video device registered                             
    mt9p031 1-0048: No MT9P031 chip detected, register read ffffff87               
    vpfe-capture vpfe-capture: v4l2 sub device mt9p031 register fails

    No sub devices registered                                                      
    vpfe-capture: vpfe capture clocks disabled                                     
    vpfe_register_ccdc_device: DM365 ISIF                                          
    dm365_isif: probe of dm365_isif failed with error -22                          
    af major#: 249, minor# 0                                                       
    AF Driver initialized                                                          
    aew major#: 248, minor# 0                                                      
    AEW Driver initialized                              

    But  i also could not find tvp5158 registered as vpfe capture sub device.So my board have no /dev/video0.

    i don't know what is wrong with my board.could you give me any light?

    thanks a lot.

     

  • Hi jonny gates,

    Did you follow the steps given there,

    1: go to the directory , mcvip_tvp5158/build

    2:  run the following command, sh kernel_patch.sh <git_kernel_path>

        Where, <git_kernel_path> is the installed git kernel path in the host PC

    3: To generate the uImage, build the updated kernel by running the following command in the DVSDK 3.x directory:

        $ make linux

    if i add

    static struct i2c_board_info i2c_info[]={

    ....

    {I2C_BOARD_INFO("tvp5158",0x5B),},

    ....

    };

    explicitly in my board config c file.similar with board-dm365-evm.c.

    i can find from boot msg:

    Don't add manually these statements in your board file, the above steps which i mentioned does it for you in the right manner.

    No sub devices registered                                                      
    vpfe-capture: vpfe capture clocks disabled                                     
    vpfe_register_ccdc_device: DM365 ISIF                                          
    dm365_isif: probe of dm365_isif failed with error -22                          
    af major#: 249, minor# 0                                                       
    AF Driver initialized                                                          
    aew major#: 248, minor# 0                                                      
    AEW Driver initialized                              

    But  i also could not find tvp5158 registered as vpfe capture sub device.So my board have no /dev/video0.

    i don't know what is wrong with my board.could you give me any light?

    Since the dm365 isif failed, you are not able to find /dev/video0 node.

    Please read the release document properly, it has all the details.

    Regards,

    --Prabhakar Lad