• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 422 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.

DMVA2 Appro IPNC kit not working with TVP150AM1 decoder chip

Charvi Mehta
Intellectual 450 points
Other Parts Discussed in Thread: TVP5150AM1

Hi,

We have Appro IPNC kit with DMVA2. The original kit came with MT9P031 sensor which we have replaced with custom TVP5150AM1 deocder board. We have done the following configurations:

DECODER :- The decoder has been configured to give BT.656 output. The C0 to C7 lines of the decoder are connected to the CIN0 to CIN7 pins in ISIF. We configure the decoder through i2c.

Next we followed the YUV_sensor_integration_Guide.pdf (Collaterals) to confiure the RDK for TVP514X. The only changes we made than default are : we set the ycInSwap to FALSE so that the Y-Signal and C-Signal are not swapped on the ISIF input. After compiling the RDK for IPNC platform (NOT EVM, as we have IPNC kit) when we run the av_server.out binary with the following arguments :-

# ./av_server.out D1 H264 3000000 VBR AUTO MENUOFF &

the application hangs after IPNC AUTO_IRIS = 0.... Then we run the moduletest application for testing the "drv_isif"as follows:

# ./moduletest.out drv_isif

this application hangs where it waits for the VDINT0 interrupt. The register dump of the entire VPSS subsystem registers is attached herewith. It seems all the registers are configured appropriately still we get no interrupt.

NOTE:- We probed the data and PCLK lines from the decoder and we can see the data coming.

  • 0
    TI__Genius 11000 points

    Which version of IPNC RDK are you using ? 

    can you try to run with only capture and check if it works fine?

    for ex: ./av_server.out D1 with some default options.

    Try not to use H264 insitally, so that we can isolate the issue

    For AUtoiris, there is a GIO read that is done in the capure part, can you check his and try to mask this?

    Please let us know the details

    Regards,

    Raghu

  • 0 in reply to Raghu Kudva
    Intellectual 450 points

    Hi Raghu,

    For update, yesterday we got some new ribbon cable attached between the main board and the decoder board and after that we were able to capture some images when we run the moduletest binary for ISIF as mentioned above. But the images are not clear. We still have no luck with the binary we have prepared by following the YUV integration guide.

    Will follow your suggestions and update you on them shortly.

    Thanks ,

    Charvi

  • 0 in reply to Charvi Mehta
    Intellectual 450 points

    Hi Raghu,

    Presently we are able to run the ./moduletest drv_isif and capture frames (although the frames are not perfect but we are going to take that part up later) but we are getting the frame dump. Then when we go a step forward and try to run

    # ./av_server.out D1 H264 300000 VBR AUTO MENUOFF &

    But this ends with error :

     ./av_server.out D1 H264 300000 VBR AUTO MENUOFF &
    root@10:/opt/ipnc#
     DM365MM Init Successful
    AVSERVER UI: Initializing.

     CLK Hz,
     ARM   Hz =  432000000
     DDR   Hz =  340000000
     VPSS  Hz =  340000000
     IMCOP Hz =  340000000

     [OSA_FILE ] Reading file [/mnt/nand/IMG_Paramset.bin] ... ERROR
    IMAGE TUNE: Paramset File is not available..... Setting DEFAULT parameter

     DM365MM Init SuccessfulSYSTEM.MSTPRI0 value changed to 00440011

    CONFIGURING AVSERVER FOR DM368 .....
    queue id:65538

    CMEM Error: allocHeap: Failed to mmap buffer at physical address 0x838fd000; fd = 14; size = 0 error: Invalid argument
    CMEM Error:     Freeing phys buffer 0x838fd000

    The cmem error seems to arise when "VIDENC1_create" is being called. We have printed the fd, size and strerror(erno) for better understanding. As he size is "0" the mmap fails with error. Do you have any idea why this would happen ?

    Also I tried to run ./av_server.out D1 as per your suggestio but it hangs after :

    CONFIGURING AVSERVER FOR DM368 .....

    Have made the GPIO read of Auto Iris change, thanks for heads up.

    NOTE: We are using IPNC RDK version 5.1.0

    Thanks and Regards,

    Charvi

  • 0 in reply to Charvi Mehta
    TI__Genius 11000 points

    Hello,

    Looks like there is some memory allocation issue here, have you burnt the uIMAGE with cmem built as part of it?

    Also, in bootargs, please include the cmem intialization commnds which specify the region of the start and end address for this

    Regards,

    Raghu