• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 420 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Using DM356 Resizer without a capture thread.

Mario Raffin
Expert 2405 points
Other Parts Discussed in Thread: TVP5158

Hello All,

    I am trying to enable the resizer using the DM365 and dvsdk 2.10,01.18. In may app. I am receiving a stream of jpg images from the network, I decode them, and I would resize them before putting them to the display output. I think the main issue which make my application different from the examples is that the resizer should work in tha absence of a capture thread.  I have some question regarding the resizer configuration:

1) Since my application does not exploit the capture device, I suppose I have to set it to work in one shot mode (not continuos);

2) DMAI documentation states "Resizer functions are not supported in DM365" but I see in the forum that many DM365 users seem to manage the resizer through DMAI. On the contrary I should directly use the resizer driver?

3) Trying to use the resizer in one-shot mode however, I get following message:

davinci_resizer davinci_resizer.2: RSZ_G_CONFIG:1:0:176
Display thread Rdavinci_resizer davinci_resizer.2: RSZ_G_CONFIG:1:0:176
Video CapIRQ handler type mismatch for IRQ 2

Maybe the driver attempts to configure an IRQ channel to sync the capture with the resizer and I don't have a capture thread (really I am using the mcvip driver to capture form a camera but I don't want to resize the images coming from the camera but the images coming from the network). How can I overcome this issue?

At the moment I am trying the one shot mode, I set the dm365__imp.oper_mode=1 in my bootargs and  captureChainMode = FALSE; but I think this last setting has not effect since I am not using the capture.

Thak you.

 

 

 

 

 

  • 0
    Expert 2405 points

    The driver seems to be installed correctly and all is right (resize open, resize configure) until I execute the resize.

    Video CapIRQ handler type mismatch for IRQ 2   means I can not resize images which are not originated from the video capture?

    Below my /proc/interrupts:

      0:          0       AINTC  csl                                               
      1:          0       AINTC  csl                                               
      2:          0       AINTC  csl                                               
      3:          0       AINTC  csl                                               
      4:          0       AINTC  csl                                               
      5:          0       AINTC  csl                                               
      8:     179138       AINTC  davinci_osd                                       
     16:          0       AINTC  EDMA Completion                                   
     17:          0       AINTC  EDMA CC Error                                     
     18:          0       AINTC  EDMA TC0 Error                                    
     19:          0       AINTC  EDMA TC1 Error                                    
     26:       5980       AINTC  davinci-mmc                                       
     32:     299237       AINTC  clockevent                                        
     33:         16       AINTC  free-run counter                                  
     39:          5       AINTC  i2c_davinci                                       
     40:        364       AINTC  serial                                            
     42:          0       AINTC  dm_spi                                            
     52:          0       AINTC  mac_rx_threshold                                  
     53:       9666       AINTC  mac_rx                                            
     54:         43       AINTC  mac_tx                                            
     55:          0       AINTC  mac_misc                                          
     61:          0       AINTC  EDMA TC2 Error                                    
     62:          0       AINTC  EDMA TC3 Error    

  • 0 in reply to Mario Raffin
    TI__Mastermind 19985 points

    Hi,

    I would suggest you to refer to do_resize_42x.c example in the LSP/PSP package. It shows how you can use the resizer in standalone mode. Please ensure that you are not opening capture driver or resizer driver anywhere else inside the DMAI application code.

    Hope this helps.

    Regards,

    Anshuman

    PS: Please mark this post as verified, if you think it has answered your question. Thanks.

  • 0 in reply to Anshuman Saxena
    Expert 2405 points

    Thank you Anshuman.

    After I found that do_resize_42x.c did not fix the problem I discovered the resize driver was already open by the TVP5158 driver (udworks).

    Now I am able to make the resizer work. Some trouble due to frame tearing but I think it can be solved. 

  • 0 in reply to Mario Raffin
    TI__Mastermind 19985 points

    Hi,

    Good that you could move further on your problem. BTW, i just want to clarify that if you are using TVP5158 driver in the "mcvip" framework that is provided by UDWorks, then it uses a different way of handling the resizer driver. It does not use LSP resizer drivers and has its own set of VPFE drivers in the "framework/drv" folder.

    Let me know if you want some details on how the LSP driver is to be used or how the TVP5158 and resizer driver in the DVR reference design framework has to be used. They are a little different and generally do not co-exist.

    Regards,

    Anshuman

    PS: Please mark this post as verified, if you think it has answered your question. Thanks.

  • 0 in reply to Anshuman Saxena
    Expert 2405 points

    Hi Anshuman.

      thank you for your answer.  The resizer of the mcvip frameworks seems to work fine. The only problem I am try to fix is the frame tearing but I am not sure it depends on the resizer.

    I would ask a thing: I am using the TVP5158 driver but the resize hardware is the one of the DM365 not the TV5158. I mean, there are different resizer driver but the HW is the same, right?

    Thank you.