• State Resolved
  • Locked Locked
  • Replies 19 replies
  • Subscribers 101 subscribers
  • Views 2812 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.

saLoopBack works saLoopBackFbdev Doesn't

A Marchini
Intellectual 630 points

I used a solution from another thread to copy in the startup script for V4L2 so that the proper binaries were loaded and such. Disable the matrix-gui as well. This is the 5.3.1.15 version of the SDK.

Downloaded and fixed up the rules to compile the saLoopBack.c and saLoopBackFbdev.c examples.

I am feeding the OMX loopback output from one EVM8168 to get a properly framed input for the development EVM8168 with the latest SDK build.

If I execute saLoopBack, I see the video properly on the screen (the second time, there is inevitable failure the first time the program is run).

If I then execute saLoopBackFbdev , I get the following :

Driver Name: ti81xxvin                                                          
Driver bus info: TI81xx Platform                                                
Driver is capable of doing capture                                              
saLoopBackFbdev:                                                                
 Mode set is 1080P60                                                            
Timing Info:                                                                    
  pixel_clk = 148500                                                            
  x_res  = 1920                                                                 
  y_res  = 1080                                                                 
  hfp      = 88                                                                 
  hsw      = 44                                                                 
  hbp      = 148                                                                
  vfp      = 4                                                                  
  vsw      = 5                                                                  
  vbp      = 36                                                                 
=============================================================                   
Capture Format:                                                                 
=============================================================                   
fmt.type                 = 1                                                    
fmt.width                = 1920                                                 
fmt.height               = 1080                                                 
fmt.pixelformat  = 859981650                                                    
fmt.bytesperline         = 5760                                                 
fmt.sizeimage    = 6220800                                                      
=============================================================                   
                                                                                
Fix Screen Info:                                                                
----------------                                                                
Line Length - 3840                                                              
Physical Address = 8ce00000                                                     
Buffer Length = 41943040                                                        
                                                                                
Var Screen Info:                                                                
----------------                                                                
Xres - 1920                                                                     
Yres - 1080                                                                     
Xres Virtual - 1920                                                             
Yres Virtual - 8640                                                             
nonstd       - 0                                                                
Bits Per Pixel - 16                                                             
blue lenth 5 msb 0 offset 0                                                     
red lenth 5 msb 0 offset 11                                                     
green lenth 6 msb 0 offset 5                                                    
trans lenth 0 msb 0 offset 0                                                    
                                                                                
Var Screen Info:                                                                
----------------                                                                
Xres - 1920                                                                     
Yres - 1080                                                                     
Xres Virtual - 1920                                                             
Yres Virtual - 4320                                                             
nonstd       - 0                                                                
Bits Per Pixel - 24                                                             
blue lenth 8 msb 0 offset 0                                                     
red lenth 8 msb 0 offset 16                                                     
green lenth 8 msb 0 offset 8                                                    
trans lenth 0 msb 0 offset 0                                                    
                                                                                
Fix Screen Info:                                                                
----------------                                                                
Line Length - 5760                                                              
Physical Address = 8ce00000                                                     
Buffer Length = 41943040                                                        
C: 0                                                                            
 TS: 59730 index 0                                                              
wait vsync failed.                                                              
: Connection timed out                                                          
Result Time:    0 734002                                                        
Floating point exception                                                        

Any quick ideas on why waiting for vsync fails??

Tony M.

  • 0
    TI__Mastermind 20245 points

    Hi,

    Can you please tell which binary are you loading on VPSS-M3.  It seems you are loading wrong binary. Can you also point out the release you are using.

    Regards,

    Hardik Shah

  • 0 in reply to HardikShah
    Intellectual 630 points

    That is probably the case here. 

    I just copied in the scripts is /usr/share/ti/ti-media-controller-utils , from the EZSDK 5.03.01.15 release product. 
    I figured since saLoopBack was working I was close, but I guess I should just follow the steps in the
     http://processors.wiki.ti.com/index.php/TI81XX_Video_Capture_Driver_User_Guide  .

    I have some confusion though because this document is calling out TI81XX PSP 04.04.00.01  and the latest PSP for the 8168 appears to be 
    http://software-dl.ti.com/dsps/dsps_public_sw/psp/LinuxPSP/DM814x_04_01/04_01_00_07/index_FDS.html 

    I am not sure how to reconcile this or am I just looking in the wrong place.

    I imagine , to do the steps as detailed in the User Guide it will be necessary to cut down any startup for the drivers currently in the SDK kernel image.

    Is there a way to examine the files directly and get a version for them? Is it embedded in a string and readable in a binary dump of the file?

    Tony M.

     

  • 0 in reply to A Marchini
    TI__Mastermind 20245 points

    Hi,

    Userguide is also included as a part of PSP release, you can refer to that userguide. In your case what could be happening is that you are loading ti81xxfb.ko with wrong arguments. You have to load ti81xxfb.ko with following arguments as suggested in Video capture driver userguide. insmod ti81xxfb.ko vram=0:40M,1:1M,2:1M

    Regards,

    Hardik Shah

  • 0 in reply to HardikShah
    Intellectual 630 points

    Let me start with a basic set of questions , I have made assumptions and I want to just dispel my confusion once and for all. 

    I have the EZSDK 5.03.01.15 so

    1. This according to the http://processors.wiki.ti.com/index.php/EZSDK_Feature_List this has support for the V4L2 examples. Correct?
    2. Can I use this kernel image , or do I need to reconfigure and recompile this kernel OR does this package have a pre-compiled image I missed? 
    3. I used the script setup.sh to configure the uboot environment. This is not the correct configuration for  V4L2 , correct?  
      This is where I need to add notifyk.vpssm3_vga=0xA0000000 and the like? 
    4. Other threads have mentioned using the load-hd-v4l2-firmware.sh file in /usr/share/ti/ti-media-controller-utils . It appears I should be able to put it in the /etc/init.d to replace the load-hd-firmware.sh file there .
      Are there pieces from the SDK that I need to disable (boot script wise) in order to use this script?? Obviously while testing I don't want the matrix-gui loading up. 
    5. The load-hd-firmware.sh scripts use firmware_loader , which is not the slaveloader mentioned in the document. 

    Ok, just writing these questions has helped some because I am focusing my attention on the necessary details of getting this to work. In question 3 , for example, I am realizing the address necessary to be set has been set in the SDK, so the version in the setup.sh script perhaps is the proper one. I need to search for the proper address that supports the dm816x_hdvpss_v4l2.xem3 I guess.

    Am I making a mistake starting with the EZSDK 

    Tony


     

  • 0 in reply to A Marchini
    TI__Guru 66170 points

    Please see my comment inline.

    Regards,

    yihe

    A Marchini said:

    Let me start with a basic set of questions , I have made assumptions and I want to just dispel my confusion once and for all. 

    I have the EZSDK 5.03.01.15 so

    1. This according to the http://processors.wiki.ti.com/index.php/EZSDK_Feature_List this has support for the V4L2 examples. Correct?

    [yihe]Yes, 5.03.01.15 support V4l2 capture

    1. Can I use this kernel image , or do I need to reconfigure and recompile this kernel OR does this package have a pre-compiled image I missed? 

    [yihe] if you are running over TI EVM + catalog daughter card, there is no need to reconfigure or recompile, the prebuilt image should be fine

     

    1. I used the script setup.sh to configure the uboot environment. This is not the correct configuration for  V4L2 , correct?  
      This is where I need to add notifyk.vpssm3_vga=0xA0000000 and the like? 

    [yihe]0xA0000000 should not be used for the EZSDK, please follow the EZSDK useguide to setup proper address.

     

    1. Other threads have mentioned using the load-hd-v4l2-firmware.sh file in /usr/share/ti/ti-media-controller-utils . It appears I should be able to put it in the /etc/init.d to replace the load-hd-firmware.sh file there .
      Are there pieces from the SDK that I need to disable (boot script wise) in order to use this script?? Obviously while testing I don't want the matrix-gui loading up. 
    2. The load-hd-firmware.sh scripts use firmware_loader , which is not the slaveloader mentioned in the document. 

    [yihe] you should use load_hd_firmware_v4l2.sh. the document you mentioned is for PSP only, which may not be appliable on EZSDK.

     

    Ok, just writing these questions has helped some because I am focusing my attention on the necessary details of getting this to work. In question 3 , for example, I am realizing the address necessary to be set has been set in the SDK, so the version in the setup.sh script perhaps is the proper one. I need to search for the proper address that supports the dm816x_hdvpss_v4l2.xem3 I guess.

    Am I making a mistake starting with the EZSDK 

    Tony


     

  • 0 in reply to yihe
    Intellectual 630 points

    I did the following and once again I have saLoopBack working, but nothing else. 

    • starting from a clean install of the EZSDK 5.03.01.15 - created the targetfs for nfs boot of the EVM Rev G board
    • copied to flash the u-boot.noxip.bin from the /board-support/prebuilt-images
    • removed all references to matrix-gui-e in the rcX.d directories
    • ALSO REMOVE references to pvr-init in the rcX.d directories
    • copy load-hd-v4l2-firmware.sh to /etc/init.d/load-hd-firmware.sh
    • echo 0 > /sys/devices/platform/vpss/graphics0/enabled
    I still can't get saLoopBackFbdev to work. 
    Fix Screen Info:                                                                
    ----------------                                                                
    Line Length - 5760                                                              
    Physical Address = 8ce00000                                                     
    Buffer Length = 41943040                                                        
    C: 0                                                                            
     TS: 59730 index 0                                                              
    wait vsync failed.                                                              
    : Connection timed out                                                          
    Result Time:    0 734002                                                        
    Floating point exception             
    I am assuming that modprobe ti81xxfb vram=0:40M,1:1M,2:1M is the proper initialization in the load-hd-firmware.sh script.
    I have not loaded in any binary pieces from any other place, this is all from the downloaded EZSDK.
    Do the bootargs in u-boot need to be modified as well? 
    P.S. Do I need copy in all the drivers files from TI816x-HDVPSS-01.00.01.33 to make this all work?? I just saw something that says that in the readme document.

  • 0 in reply to A Marchini
    Intellectual 630 points

    I skipped a detail that I didn't realize applied to these examples, but I guess it does. SO at least I can say I can use all of the examples now.

    I changed my uboot bootargs to the following :

    bootargs=console=ttyO2,115200n8 rootwait rw mem=169M earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M ti816xfb.vram=0:40M,1:1M,2:2M root=/dev/nfs nfsroot=10.1.1.95:/home/user/targetfs ip=dhcp

    So now my saLoopBackFbdev example functions too.
    Obviously , for someone else to use this, they will need to change the NFS stuff to their parameters

    This is EZSDK_dm816x-evm_5_03_01_15 on a Rev G EVM , TI 8168 Board with the expansion I/O and DDR3 

    Thanks for all the support 

  • 0 in reply to A Marchini
    Intellectual 630 points

    This other thread titled "v4l2 capture example (saLoopBack) question" was helpful in making me think I should change the u-boot. Its discussion is valuable. 

  • 0 in reply to A Marchini
    TI__Mastermind 20245 points

    Hi,

    I am not able to make it out from thread that saLoopBack worked or not. Can you please let me know whether you are able to make it work or not.

    Regards,

    Hardik shah

  • 0 in reply to HardikShah
    Intellectual 630 points

    The saLoopBack program always seemed to work (except for the first execution, as you mentioned a known issue in the V4L2 driver).  After my changes saLoopBackFbdev is functional as well. 
    It seems I can execute saLoopBackFbdev multiple times, but if I execute saLoopBack and then execute saLoopBackFbdev , then saLoopBackFbdev will fail.
     

    Tony Marchini

  • 0 in reply to A Marchini
    TI__Mastermind 20245 points

    Hi,

    saLoopBack will work for first execution as well. Only thing is you see a kernel dump on console for the first time. saLoopBackFbdev also works after saLoopBack. What changes have you done to saLoopBackFbdev. It may be because of those changes it may not be working. Can you please send me the console output for working and non working case.

    Regards,

    Hardik Shah

  • 0 in reply to HardikShah
    Intellectual 630 points

    I just want to make this for clear for you.

    HardikShah said:

    Hi,

    saLoopBack will work for first execution as well.

    saLoopBack will "function" for me on the first execution. The program will begin, capture samples, throw a bunch of errors and output information all the way to a standard completion. In my case the program output looks "wrong". There is motion but all the colors look out of synch, like a "solarize" option on a digital camera. After this first run the program looks fine.

    Only thing is you see a kernel dump on console for the first time. saLoopBackFbdev also works after saLoopBack. What changes have you done to saLoopBackFbdev. It may be because of those changes it may not be working. Can you please send me the console output for working and non working case.

    I was actually satisfied with the behavior, but your persistence that these programs work 100% led me to examine this more closely. I didn't really  pay attention to the messages at the beginning of saLoopBackFbdev , like "VPSS_GRPX : please stop grpx0 before continue.".  The program appeared to function so I didn't bother to care about it.
    I then did '/etc/init.d/pvr-init stop' and the errors went away and the operation cleared up.
    I have now removed the pvr-init links in the rcX.d directories.
    All the programs behave MUCH better now. In fact the first run behavior of saLoopBack I described a paragraph ago IS GONE!

    I believe we can say these programs now work to my AND your satisfaction.

    Also , to answer  your other question , I didn't make any changes to saLoopBackFbdev, I was referring to the changes I made to the boot up process listed earlier in the thread to get these programs to operate.

    Regards,

    Hardik Shah

    Thanks a lot for your effort on this , now on to my next question, in a new thread.

    Tony Marchini

  • 0 in reply to A Marchini
    TI__Mastermind 20245 points

    Hi,

    Thanks a lot for getting to the root cause of this.

    Regards,

    Hardik shah

  • 0 in reply to HardikShah
    Expert 1015 points
    Hello all:
            I encounter the same problem about how to update the M3 firmware which in  EZSDK packages to the version TI81xx-HDVPSS-01.00.01.37 which in PSP packages(TI81XX-LINUX-PSP-04.04.00.01) on Dm8148EVM.
           According to the above discussion,I found that if I use the latest M3 firmware (TI81xx-HDVPSS-01.00.01.37 )，I must abide the key rules as belows :
    1、use "notifyk.vpssm3_sva=0xA0000000" not "0xBF9000000(EZSDK offerd)"
    2、use "./slaveloader startup VPSS-M3 ti814x_hdvpss_1G.xem3" not " firmware_loader  dm814x_hdvpss.xem3 start(EZSDK methord)"
    3、use “ insmod vpss.ko sbufaddr=0xA0200000” not "insmod vpss.ko sbufaddr=0xBFB00000(EZSDK methord)"
    execept that ,I also
    1、 update the syslink and ipc and xdc to the version which fit TI81xx-HDVPSS-01.00.01.37 and TI81XX-LINUX-PSP-04.04.00.01.
    2、Change the Rules.mak which in the ezsdk,and compile syslink and omx and gstomx.
        But,When  I use gstomx (gstreamer)、omx(which in the EZSDK packages) to Play Mpeg2 video. If I do as above and use TI81xx-HDVPSS-01.00.01.37 will result the followings errors:
     Assertion at Line no: 445 in /home/anuo/Sdb1/Dm81xx/ezsdk5_0301_15/Myfiles/sysli
    nk_2_10_03_20/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/sysl
    ink/ipc/hlos/knl/Linux/SharedRegionDrv.c: (heapHandle != NULL) : failed
    Assertion at Line no: 1354 in /home/anuo/Sdb1/Dm81xx/ezsdk5_0301_15/Myfiles/sysl
    ink_2_10_03_20/packages/ti/syslink/ipc/hlos/usr/HeapMemMP.c: (hpHandle != NULL)
    : failed
    According to http://processors.wiki.ti.com/index.php/EZSDK_Memory_Map document,I found only the following file may be need to change:
    omx_05_02_00_30_1/src/ti/omx/build/MemSegmentDefinition.xs:
    In this file ,I change the followings section:
    memory[11] = ["HDVPSS_NOTIFY_MEM",
      {
              name: "HDVPSS_NOTIFY_MEM",
              base: 0xBF900000,--------change to 0xA0000000
              len: 0x00200000,
              space: "data"
      }];
     
      memory[12] = ["HDVPSS_V4L2_FBDEF_MEM",
      {
              name: "HDVPSS_V4L2_FBDEF_MEM",
              base: 0xBFB00000,----------change to 0xA0200000
              len: 0x00200000,
              space: "data"
      }];
    If I do this ,errors still exist.Any other things I lost?
     
    So:
    1、Anyone ever test omx or gstomx(which in EZSDK ) when use the newer M3 firmware which from PSP packages( use "notifyk.vpssm3_sva=0xA0000000" methord)? If not,
           then how to use the omx/gstomx with firmware (HDVPSS-01.00.01.37 )  from PSP(PSP-04.04.00.01) ?
    2、Which files in  EZSDK  need to change if I use the M3 firmware (HDVPSS-01.00.01.37 )  from PSP(PSP-04.04.00.01),or  I must change  M3 firmware map(I only have the bin file ,not NDK)? or waitting for the next ezsdk release?
  • 0 in reply to HardikShah
    Expert 1015 points
    Hello all:
            I encounter the same problem about how to update the M3 firmware which in  EZSDK packages to the version TI81xx-HDVPSS-01.00.01.37 which in PSP packages(TI81XX-LINUX-PSP-04.04.00.01) on Dm8148EVM.
           According to the above discussion,I found that if I use the latest M3 firmware (TI81xx-HDVPSS-01.00.01.37 )，I must abide the key rules as belows :
    1、use "notifyk.vpssm3_sva=0xA0000000" not "0xBF9000000(EZSDK offerd)"
    2、use "./slaveloader startup VPSS-M3 ti814x_hdvpss_1G.xem3" not " firmware_loader  dm814x_hdvpss.xem3 start(EZSDK methord)"
    3、use “ insmod vpss.ko sbufaddr=0xA0200000” not "insmod vpss.ko sbufaddr=0xBFB00000(EZSDK methord)"
    execept that ,I also
    1、 update the syslink and ipc and xdc to the version which fit TI81xx-HDVPSS-01.00.01.37 and TI81XX-LINUX-PSP-04.04.00.01.
    2、Change the Rules.mak which in the ezsdk,and compile syslink and omx and gstomx.
        But,When  I use gstomx (gstreamer)、omx(which in the EZSDK packages) to Play Mpeg2 video. If I do as above and use TI81xx-HDVPSS-01.00.01.37 will result the followings errors:
     Assertion at Line no: 445 in /home/anuo/Sdb1/Dm81xx/ezsdk5_0301_15/Myfiles/sysli
    nk_2_10_03_20/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/sysl
    ink/ipc/hlos/knl/Linux/SharedRegionDrv.c: (heapHandle != NULL) : failed
    Assertion at Line no: 1354 in /home/anuo/Sdb1/Dm81xx/ezsdk5_0301_15/Myfiles/sysl
    ink_2_10_03_20/packages/ti/syslink/ipc/hlos/usr/HeapMemMP.c: (hpHandle != NULL)
    : failed
    According to http://processors.wiki.ti.com/index.php/EZSDK_Memory_Map document,I found only the following file may be need to change:
    omx_05_02_00_30_1/src/ti/omx/build/MemSegmentDefinition.xs:
    In this file ,I change the followings section:
    memory[11] = ["HDVPSS_NOTIFY_MEM",
      {
              name: "HDVPSS_NOTIFY_MEM",
              base: 0xBF900000,--------change to 0xA0000000
              len: 0x00200000,
              space: "data"
      }];
     
      memory[12] = ["HDVPSS_V4L2_FBDEF_MEM",
      {
              name: "HDVPSS_V4L2_FBDEF_MEM",
              base: 0xBFB00000,----------change to 0xA0200000
              len: 0x00200000,
              space: "data"
      }];
    If I do this ,errors still exist.Any other things I lost?
     
    So:
    1、Anyone ever test omx or gstomx(which in EZSDK ) when use the newer M3 firmware which from PSP packages( use "notifyk.vpssm3_sva=0xA0000000" methord)? If not,
           then how to use the omx/gstomx with firmware (HDVPSS-01.00.01.37 )  from PSP(PSP-04.04.00.01) ?
    2、Which files in  EZSDK  need to change if I use the M3 firmware (HDVPSS-01.00.01.37 )  from PSP(PSP-04.04.00.01),or  I must change  M3 firmware map(I only have the bin file ,not NDK)? or waitting for the next ezsdk release?
  • 0 in reply to HardikShah
    Expert 1015 points
    Hello all:
            I encounter the same problem about how to update the M3 firmware which in  EZSDK packages to the version TI81xx-HDVPSS-01.00.01.37 which in PSP packages(TI81XX-LINUX-PSP-04.04.00.01) on Dm8148EVM.
           According to the above discussion,I found that if I use the latest M3 firmware (TI81xx-HDVPSS-01.00.01.37 )，I must abide the key rules as belows :
    1、use "notifyk.vpssm3_sva=0xA0000000" not "0xBF9000000(EZSDK offerd)"
    2、use "./slaveloader startup VPSS-M3 ti814x_hdvpss_1G.xem3" not " firmware_loader  dm814x_hdvpss.xem3 start(EZSDK methord)"
    3、use “ insmod vpss.ko sbufaddr=0xA0200000” not "insmod vpss.ko sbufaddr=0xBFB00000(EZSDK methord)"
    execept that ,I also
    1、 update the syslink and ipc and xdc to the version which fit TI81xx-HDVPSS-01.00.01.37 and TI81XX-LINUX-PSP-04.04.00.01.
    2、Change the Rules.mak which in the ezsdk,and compile syslink and omx and gstomx.
        But,When  I use gstomx (gstreamer)、omx(which in the EZSDK packages) to Play Mpeg2 video. If I do as above and use TI81xx-HDVPSS-01.00.01.37 will result the followings errors:
     Assertion at Line no: 445 in /home/anuo/Sdb1/Dm81xx/ezsdk5_0301_15/Myfiles/sysli
    nk_2_10_03_20/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/sysl
    ink/ipc/hlos/knl/Linux/SharedRegionDrv.c: (heapHandle != NULL) : failed
    Assertion at Line no: 1354 in /home/anuo/Sdb1/Dm81xx/ezsdk5_0301_15/Myfiles/sysl
    ink_2_10_03_20/packages/ti/syslink/ipc/hlos/usr/HeapMemMP.c: (hpHandle != NULL)
    : failed
    According to http://processors.wiki.ti.com/index.php/EZSDK_Memory_Map document,I found only the following file may be need to change:
    omx_05_02_00_30_1/src/ti/omx/build/MemSegmentDefinition.xs:
    In this file ,I change the followings section:
    memory[11] = ["HDVPSS_NOTIFY_MEM",
      {
              name: "HDVPSS_NOTIFY_MEM",
              base: 0xBF900000,--------change to 0xA0000000
              len: 0x00200000,
              space: "data"
      }];
     
      memory[12] = ["HDVPSS_V4L2_FBDEF_MEM",
      {
              name: "HDVPSS_V4L2_FBDEF_MEM",
              base: 0xBFB00000,----------change to 0xA0200000
              len: 0x00200000,
              space: "data"
      }];
    If I do this ,errors still exist.Any other things I lost?
     
    So:
    1、Anyone ever test omx or gstomx(which in EZSDK ) when use the newer M3 firmware which from PSP packages( use "notifyk.vpssm3_sva=0xA0000000" methord)? If not,
           then how to use the omx/gstomx with firmware (HDVPSS-01.00.01.37 )  from PSP(PSP-04.04.00.01) ?
    2、Which files in  EZSDK  need to change if I use the M3 firmware (HDVPSS-01.00.01.37 )  from PSP(PSP-04.04.00.01),or  I must change  M3 firmware map(I only have the bin file ,not NDK)? or waitting for the next ezsdk release?
  • 0 in reply to HardikShah
    Expert 1015 points
    Hello all:
            I encounter the same problem about how to update the M3 firmware which in  EZSDK packages to the version TI81xx-HDVPSS-01.00.01.37 which in PSP packages(TI81XX-LINUX-PSP-04.04.00.01) on Dm8148EVM.
           According to the above discussion,I found that if I use the latest M3 firmware (TI81xx-HDVPSS-01.00.01.37 )，I must abide the key rules as belows :
    1、use "notifyk.vpssm3_sva=0xA0000000" not "0xBF9000000(EZSDK offerd)"
    2、use "./slaveloader startup VPSS-M3 ti814x_hdvpss_1G.xem3" not " firmware_loader  dm814x_hdvpss.xem3 start(EZSDK methord)"
    3、use “ insmod vpss.ko sbufaddr=0xA0200000” not "insmod vpss.ko sbufaddr=0xBFB00000(EZSDK methord)"
    execept that ,I also
    1、 update the syslink and ipc and xdc to the version which fit TI81xx-HDVPSS-01.00.01.37 and TI81XX-LINUX-PSP-04.04.00.01.
    2、Change the Rules.mak which in the ezsdk,and compile syslink and omx and gstomx.
        But,When  I use gstomx (gstreamer)、omx(which in the EZSDK packages) to Play Mpeg2 video. If I do as above and use TI81xx-HDVPSS-01.00.01.37 will result the followings errors:
     Assertion at Line no: 445 in /home/anuo/Sdb1/Dm81xx/ezsdk5_0301_15/Myfiles/sysli
    nk_2_10_03_20/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/sysl
    ink/ipc/hlos/knl/Linux/SharedRegionDrv.c: (heapHandle != NULL) : failed
    Assertion at Line no: 1354 in /home/anuo/Sdb1/Dm81xx/ezsdk5_0301_15/Myfiles/sysl
    ink_2_10_03_20/packages/ti/syslink/ipc/hlos/usr/HeapMemMP.c: (hpHandle != NULL)
    : failed
    According to http://processors.wiki.ti.com/index.php/EZSDK_Memory_Map document,I found only the following file may be need to change:
    omx_05_02_00_30_1/src/ti/omx/build/MemSegmentDefinition.xs:
    In this file ,I change the followings section:
    memory[11] = ["HDVPSS_NOTIFY_MEM",
      {
              name: "HDVPSS_NOTIFY_MEM",
              base: 0xBF900000,--------change to 0xA0000000
              len: 0x00200000,
              space: "data"
      }];
     
      memory[12] = ["HDVPSS_V4L2_FBDEF_MEM",
      {
              name: "HDVPSS_V4L2_FBDEF_MEM",
              base: 0xBFB00000,----------change to 0xA0200000
              len: 0x00200000,
              space: "data"
      }];
    If I do this ,errors still exist.Any other things I lost?
     
    So:
    1、Anyone ever test omx or gstomx(which in EZSDK ) when use the newer M3 firmware which from PSP packages( use "notifyk.vpssm3_sva=0xA0000000" methord)? If not,
           then how to use the omx/gstomx with firmware (HDVPSS-01.00.01.37 )  from PSP(PSP-04.04.00.01) ?
    2、Which files in  EZSDK  need to change if I use the M3 firmware (HDVPSS-01.00.01.37 )  from PSP(PSP-04.04.00.01),or  I must change  M3 firmware map(I only have the bin file ,not NDK)? or waitting for the next ezsdk release?
  • 0 in reply to zhichao tan60372
    TI__Mastermind 20245 points

    Hi,

    Old EZSDK will not work directly with new PSP and HDVPSS because of interface changes. Our team is in process of updating EZSDK with all new pacakages.

    Regards,

    Hardik Shah

  • 0 in reply to A Marchini
    Guru 10685 points

    Hi Tony, just wanted to say thanks for your post as I had exactly the same error as you, that is:

    # ./saLoopBackFbdev
    Capturing on VIP0.
    Opening capture device /dev/video0.
    Driver Name: ti81xxvin
    Driver bus info: TI81xx Platform
    Driver is capableRalph: looks like a HDMI signal.
     of doing capture
    saLoopBackFbdev:
     Mode set is 0
    Ralph: TV HDMI not supported.
    Interface is 0 [0:DVI, 1:HDMI]
    =============================================================
    Capture Format:
    =============================================================
    fmt.type                 = 1
    fmt.width                = 1920
    fmt.height               = 1080
    fmt.pixelformat  = 859981650
    fmt.bytesperline         = 5760
    fmt.sizeimage    = 6220800
    =============================================================

    Fix Screen Info:
    ----------------
    Line Length - 7680
    Physical Address = b0b00000
    Buffer Length = 41943040

    Var Screen Info:
    ----------------
    Xres - 1920
    Yres - 1080
    Xres Virtual - 1920
    Yres Virtual - 1080
    nonstd       - 0
    Bits Per Pixel - 32
    blue length 8 msb 0 offset 0
    red length 8 msb 0 offset 16
    green length 8 msb 0 offset 8
    trans length 8 msb 0 offset 24

    Var Screen Info:
    ----------------
    Xres - 1920
    Yres - 1080
    Xres Virtual - 1920
    Yres Virtual - 4320
    nonstd       - 0
    Bits Per Pixel - 24
    blue length 8 msb 0 offset 0
    red length 8 msb 0 offset 16
    green length 8 msb 0 offset 8
    trans length 0 msb 0 offset 0

    Fix Screen Info:
    ----------------
    Line Length - 5760
    Physical Address = b0b00000
    Buffer Length = 41943040
    wait vsync failed.
    : Connection timed out
    Result Time:    0 540870
    Floating point exception

    I solved this by doing just one thing and that was ensuring that no PowerVR modules loaded. i.e. make sure these things don't run at start up:

    modprobe pvrsrvkm
    pvrsrvinit
    modprobe omaplfb

    Ralph