dm8168 command for running demos

Sajad Rather4

Other Parts Discussed in Thread: TVP7002

Dear sir,

I am new to this board,we have purchased dm8168 it,i am booting from sd card.I know it is having some standard demos in ROOTFS partition.

What all the programs it is having,is it having image processing program and audio processing demos?

do we need to do any changes in program part of those demo programs?

*what is the linux command to run those demos in minicom?

I think we have to navigate to the location of that program /root/usr/local/ezsdk/.............through minicom,then we have to put some command (like GCC <FILENAME>.C)with the file name..........am i right..?..if so which command we need to use to run the demos and what i said the path for standard demos "/root/usr/local/ezsdk/." is this right?

thank you.

over 9 years ago

0 Margarita Gashova over 9 years ago

TI__Guru* 80190 points

Hello,

Which demos you are searching for in EZSDK?
You could check DM816x_EZ_Software_Developers_Guide.pdf.

BR
Margarita

0 MOHAMMAD NASEER M N over 9 years ago in reply to Margarita Gashova

Genius 5755 points

HI Margarita,
I wanted to run just demo examples nothing apart from that,i wanna do audio/video loop back and audio processing.
I got to know that from Mr.Pavel that,there is are standard examples availbale for this.
so am asking you to help me in this regards.I followed, DM816x_EZ_Software_Developers_Guide.pdf.
but am so much confusion and steps are little bit difficult am unable to get it.

please suggest me how can i run demos example which is there in sd card what we got from kit.

thank you

0 Margarita Gashova over 9 years ago in reply to MOHAMMAD NASEER M N

TI__Guru* 80190 points

Hello,

Yes, there is.

For OMX demos you could refer to OMX_05_02_00_48_UserGuide.pdf page:63.
There you could find how to run video encode, decode, decode_display, display, capture_encode, audio decode.

These demos could be find in /usr/share/ti/ti-omx folder in your rootfs.

Before to run these demos the graphics should be stop.

Here is exmaple:
/etc/init.d/matrix-gui-e stop
/etc/init.d/pvr-init stop

./decode_display_a8host_debug.xv5T -i ./sample.h264 -w 1920 -h 1080 -f 60 –d 0 -g 0

For OMX demos this load-hd-firmware.sh should be load(it is loading by default) .More information you could find in DM816x_EZ_Software_Developers_Guide.pdf. guide about OMX and v4l2.

If you are planning to run gsreamer demo let me know about use case so I will be able to provide you an example pipeline.

If you are planning to run RPE demos refer to Running the RPE examples in DM816x_EZ_Software_Developers_Guide.pdf.

If you are planning to run video demos which are using v4l2 driver, you could find the sources in ezsdk/example-applications/linux-driver-examples-psp04.04.00.01/video.

You should build them:
cd ezsdk
make all

The demo's binaries could be find in ezsdk/example-applications/linux-driver-examples-psp04.04.00.01/video/bin folder.

You should cp them to the SD card.

Keep in mind that load-hd-v4l2-firmware.sh should be loaded in v4l2 capture/display. Refer to DM816x_EZ_Software_Developers_Guide.pdf.

It would be better to point me which demos you are trying to execute or what you are trying to archive (decode-display, capture?).

BR
Margarita

0 MOHAMMAD NASEER M N over 9 years ago in reply to Margarita Gashova

Genius 5755 points

Hi Margarita,

It would be better to point me which demos you are trying to execute or what you are trying to archive (decode-display, capture?).

--->>>we want to do just loop back of video capture,what we get in camera,simply it has to display on TV.is there standard demos for this type of program. in the given SD CARD ,if so please tell me the path and name the demo,requesting to tell the procedure how to get the output.we did "make all",and what to do next to run this demo only.because after seeing the pdf ,we are in confusion about the procedure.

Another thing is we got a kit which comes with daughter card,in daughter card i think we need to connect the camera,as i dont find any input on the board itself to give input but i found output on the board.if so what kind of camera is suitable for doing this.

thank you.

0 Margarita Gashova over 9 years ago in reply to MOHAMMAD NASEER M N

TI__Guru* 80190 points

Hello,

The is saLoopBack demo but you shall build it.

1.You could allocate the source code in ezsdk/example-applications/linux-driver-examples-psp04.04.00.01/video, after building the binary will be in ezsdk/example-applications/linux-driver-examples-psp04.04.00.01/video/bin folder. You could copy it to sd card.

This demo is using v4l2 capture display driver.

More information about the demo you could find here:

2. Capture source must be connected to the component input of IO EXPANSION board before run the sample application, otherwise the sample application reports error. Output should be HDMI.

3. When you boot up the board you should load vpss v4l2 firmware.

You could archive this by two ways:

First way:

target #/etc/init.d/matrix-gui-e stop

target #/etc/init.d/pvr-init stop

target # cd /usr/share/ti/ti-media-controller-utils
target # cp load-hd-v4l2-firmware.sh /etc/init.d/load-hd-firmware.sh
target # sync

Second way :

target #/etc/init.d/matrix-gui-e stop

target #/etc/init.d/pvr-init stop

target#cd /usr/share/ti/ti-media-controller-utils

target# ./load-hd-firmware.sh stop

target#./load-hd-v4l2-firmware.sh start.

Please let me know if you need further details.

BR
Margarita

0 MOHAMMAD NASEER M N over 9 years ago in reply to Margarita Gashova

Genius 5755 points

Hi Margarita,

I did gcc of saLoopBack ,i did that error...and v4l2 capture display driver i got error shown in attachment

please sort it out.

thank you

0 Margarita Gashova over 9 years ago in reply to MOHAMMAD NASEER M N

TI__Guru* 80190 points

Hello,

cd ezsdk main folder
make all

This will build everything including saLoopBack demo.

BR
Margarita

0 MOHAMMAD NASEER M N over 9 years ago in reply to Margarita Gashova

Genius 5755 points

Hi Margarita,
U did Make all,but at the end i got" 2 errors in making",then i did gcc to that video loopaback example,"gcc example.c...i got same errors wat i posted attachment in early conversation...

why this is happening,how to over come with this...

thank you.

0 Margarita Gashova over 9 years ago in reply to MOHAMMAD NASEER M N

TI__Guru* 80190 points

Hello,

What errors you are seeing with make all command?
Are you using the default ezsdk?

BR
Margarita

0 MOHAMMAD NASEER M N over 9 years ago in reply to Margarita Gashova

Genius 5755 points

Hi Margarita,

What errors you are seeing with make all command?

--->>>please see the attachment "sreenshot".

Are you using the default ezsdk?

--->>>yes.

After doing "make all",i got error,but still i did CD and in VIDEO path,i did "GCC saFlopback.c",i got error...please see the "screenshot1".

I only installed EZ by installing codesourcery,nothing apart from this.

thank you

0 Margarita Gashova over 9 years ago in reply to MOHAMMAD NASEER M N

TI__Guru* 80190 points

Hello,

In the EZSDK for dm8168 we have ti-ezsdk_dm816x-evm_5_05_02_00/example-applications/linux-driver-examples-psp04.04.00.01/pcie folder(which contains pcie example demo) could you check are you have it ?

1.I have attach this folder (8272.pcie.tar.gz) extract it here /linux-driver-examples-psp04.04.00.01

2. or you could remove it from the makefile in the EZSDk install folder.

    $(MAKE) -C $(PSP_EXAMPLES_INSTALL_DIR)/pcie \
       CC=$(CSTOOL_PREFIX)gcc \
       KERNEL_DIR=$(LINUXKERNEL_INSTALL_DIR)

After some of this steps try again make all command.

BR
Margarita

0 MOHAMMAD NASEER M N over 9 years ago in reply to Margarita Gashova

Genius 5755 points

Hi,

which is the component input in the board...?

thank you.

0 MOHAMMAD NASEER M N over 9 years ago in reply to Margarita Gashova

Genius 5755 points

Hi,
I overcame the errors of "make all",but if i do "gcc saLoopback.c",i got the errors.the same
e2e.ti.com/.../Screenshot_2D00_1.png,what to do with this.

thank you.

0 Margarita Gashova over 9 years ago in reply to MOHAMMAD NASEER M N

TI__Guru* 80190 points

Hello,

Are you able to allocate in ezsdk/example-applications/linux-driver-examples-psp04.04.00.01/video/bin folder build saLoopBack demo with make all command?

Capture source must be connected to the component input of IO EXPANSION board(J5,J6,J7).

Margarita

0 Margarita Gashova over 9 years ago in reply to Margarita Gashova

TI__Guru* 80190 points

There is a DM816x_C6A816x_AM389x_EVM_Quick_start_guide.pdf in ezsdk/doc folder.

BR
Margarita

0 MOHAMMAD NASEER M N over 9 years ago in reply to Margarita Gashova

Genius 5755 points

Hi Margarita,

Yes i have bin folder in video folder there i can see saLoopback project file,what to with that....how to run that program....as i dont have any debugger...is there any procedre to run without debugger..?

shall i copy it to rootfs partition of sd card and run the demo..?if so what is the command to run.....is it works with "gcc saLoopback" or "./saLoopback" or something else...

thank you.

0 Margarita Gashova over 9 years ago in reply to Margarita Gashova

TI__Guru* 80190 points

Hello,

You could check my previous posts in this thread.

Margarita Gashova said:

1.You could allocate the source code in ezsdk/example-applications/linux-driver-examples-psp04.04.00.01/video, after building the binary will be in ezsdk/example-applications/linux-driver-examples-psp04.04.00.01/video/bin folder.

You should copy it to sd card.

Margarita Gashova said:

3. When you boot up the board you should load vpss v4l2 firmware.

You could archive this by two ways:

First way:

target #/etc/init.d/matrix-gui-e stop

target #/etc/init.d/pvr-init stop

target # cd /usr/share/ti/ti-media-controller-utils
target # cp load-hd-v4l2-firmware.sh /etc/init.d/load-hd-firmware.sh
target # sync

Second way :

target #/etc/init.d/matrix-gui-e stop

target #/etc/init.d/pvr-init stop

target#cd /usr/share/ti/ti-media-controller-utils

target# ./load-hd-firmware.sh stop

target#./load-hd-v4l2-firmware.sh start.

target#./saLoopBack

BR
Margarita

0 MOHAMMAD NASEER M N over 9 years ago in reply to Margarita Gashova

Genius 5755 points

Hello,
But you didnt mention which part of sd card either boot or rootfs..
thank you.

0 MOHAMMAD NASEER M N over 9 years ago in reply to MOHAMMAD NASEER M N

Genius 5755 points

Hi,

when i boot up the device from sd card,the the Matrix application launcher is launched automatically.we have to stop the matrix app before running any code.

But when we do, remove and connect the sd card again for next booting ,will the the Matrix application launcher is launched automatically(will we get the icons on display)?or we need to give the command to start again during next booting?

thank you.

0 Margarita Gashova over 9 years ago in reply to MOHAMMAD NASEER M N

TI__Guru* 80190 points

Hello,

You should cp the demo on ROOTFS.

When you stop the Graphics plane this way:
target # /etc/init.d/pvr-init stop
target # /etc/init.d/matrix-gui-e stop

When you reboot the board the graphics will start again.
If you do not reboot the board you could start it by:
target # /etc/init.d/pvr-init start
target # /etc/init.d/matrix-gui-e start

BR
Margarita

0 MOHAMMAD NASEER M N over 9 years ago in reply to Margarita Gashova

Genius 5755 points

Hi,
we have lot of folders in Rootfs.can i place it by creating the new folder for that in Rootfs.
thank you.

0 Margarita Gashova over 9 years ago in reply to MOHAMMAD NASEER M N

TI__Guru* 80190 points

Hello,

You could create your folder or cp in existed folder.

BR
Margarita

0 Margarita Gashova over 9 years ago in reply to Margarita Gashova

TI__Guru* 80190 points

Hello,

You should execute these commands to run the saLoopBack demo:

/etc/init.d/matrix-gui-e stop

/etc/init.d/pvr-init stop

cd /usr/share/ti/ti-media-controller-utils/
./load-hd-firmware.sh stop

./load-hd-v4l2-firmware.sh start

cd /folder where the demo is

./saLoopBack

BR
Margarita

0 MOHAMMAD NASEER M N over 9 years ago in reply to Margarita Gashova

Genius 5755 points

HI,

I tried the above steps,but i got error when i run ./saLoopBack

"failed to open capture device

Error in opening capture device for channel 0"

please help me sort it out.

thank you.

Fullscreen 3568.error.txt Download

EXT3-fs: barriers not enabled                             
kjournald starting.  Commit interval 5 seconds                                              
EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is rec                                                                                
ommended        
EXT3-fs (mmcblk0p2): using internal journal                                           
EXT3-fs (mmcblk0p2): recovery complete                                      
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode                                                                
VFS: Mounted root (ext3 filesystem) on device 179:2.                                                    
devtmpfs: mounted                 
Freeing init memory: 204K                         
INIT: version 2.86 booting                          
Please wait: booting...                       
Error opening /dev/fb0: No such file or directory                                                 
Starting udev             
udevd (77): /proc/77/oom_adj is deprecated, please use /proc/77/oom_score_adj in                                                                                
stead.      
EXT3-fs: barriers not enabled                             
kjournald starting.  Commit interval 5 seconds                                              
EXT3-fs (mmcblk0p3): warning: maximal mount count reached, running e2fsck is rec                                                                                
ommended        
EXT3-fs (mmcblk0p3): using internal journal                                           
EXT3-fs (mmcblk0p3): recovery complete                                      
EXT3-fs (mmcblk0p3): mounted filesystem with writeback data mode                                                                
Remounting root file system...                              
Caching udev devnodes                     
NET: Registered protocol family 10                                  
ALSA: Restoring mixer settings...                                 
Configuring network interfaces... davinci_mdio davinci_mdio.0: resetting idled c                                                                                
ontroller         
net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, id=282f014)                                                                               
ADDRCONF(NETDEV_UP): eth0: link is not ready                                            
udhcpc (v1.13.2) started                        
Sending discover...                   
Sending discover...                   
Sending discover...                   
No lease, forking to background                               
done.     
Setting up IP spoofing protection: rp_filter.                                             
Sun Apr 29 23:02:00 UTC 2012                            
INIT: Entering runlevel: 5                          
Loading HDVICP2 Firmware                        
DM816X prcm_config_app version: 2.0.0.1                                       
Doing PRCM settings...                      
        PRCM for IVHD0 is in Progress, Please wait.....                                                       
                        BW Phy Addr : 0x48180600 Data : 0x00000002                                                                  
                        AW Phy Addr : 0x48180600 Data : 0x00000002                                                                  
                        Phy Addr : 0x48180c04 Data : 0x00000037                                                               
                        BW Phy Addr : 0x48180620 Data : 0x00070000                                                                  
                        AW Phy Addr : 0x48180620 Data : 0x00070002                                                                  
                        BW Phy Addr : 0x48180624 Data : 0x0003000                                                                
                        AW Phy Addr : 0x48180624 Data : 0x00010002                                                                  
                        Phy Addr : 0x48180600 Data : 0x00000102                                                               
                        BW Phy Addr : 0x48180c10 Data : 0x00000007                                                                  
                        AW Phy Addr : 0x48180c10 Data : 0x00000003                                                                  
                        Phy Addr : 0x48180c14 Data : 0x00000004                                                               
                        BW Phy Addr : 0x58088000 Data : 0x03ebba61                                                                  
                        AW Phy Addr : 0x58088000 Data : 0xeafffffe                                                                  
                        BW Phy Addr : 0x58098000 Data                                                   
                        AW Phy Addr : 0x58098000 Data : 0xeafffffe                                                                  
                        BW Phy Addr : 0x48180c10 Data : 0x00000003                                                                  
                        AW Phy Addr : 0x48180c10 Data : 0x00000000                                                                  
                        Phy Addr : 0x48180c14 Data : 0x00000007                                                               
        PRCM for IVHD0 is Done Successfully                                           
        PRCM for IVHD1 is in Progress, Please wait.....                                                       
                        BW Phy Addr : 0x48180700 Data : 0x00000002                                                                  
                        AW Phy Addr : 0x48180700 Data : 0x00000002                                                                  
                        Phy Addr : 0x48180d04 Data : 0x00000037                                                               
                        BW Phy Addr : 0x48180720 Data : 0x00070000                                                                  
                        AW Phy Addr : 0x48180720 Data : 0x00050002                                                                  
                        BW Phy Addr : 0x48180724 Data : 0x00030000                                                                  
                        AW Phy Addr : 0x48180724 Data : 0x00010002                                                                  
                        Phy Addr : 0x48180700 Data : 0x00000102                                                               
                        BW Phy Addr : 0x48180d10 Data : 0x00000007                                                                  
                        AW Phy Addr : 0x48180d10 Data                                                   
                        Phy Addr : 0x48180d14 Data : 0x00000004                                                               
                        BW Phy Addr : 0x5a088000 Data : 0x93e374e6                                                                  
                        AW Phy Addr : 0x5a088000 Data : 0xeafffffe                                                                  
                        BW Phy Addr : 0x5a098000 Data : 0x0a7710ba                                                                  
                        AW Phy Addr : 0x5a098000 Data : 0xeafffffe                                                                  
                        BW Phy Addr : 0x48180d10 Data : 0x00000003                                                                  
                        AW Phy Addr : 0x48180d10 Data : 0x00000000                                                                  
                        Phy Addr : 0x48180d14 Data                                                
        PRCM for IVHD1 is Done Successfully                                           
        PRCM for IVHD2 is in Progress, Please wait.....                                                       
                        BW Phy Addr : 0x48180800 Data : 0x00000002                                                                  
                        AW Phy Addr : 0x48180800 Data : 0x00000002                                                                  
                        Phy Addr : 0x48180e04 Data : 0x00000037                                                               
                        BW Phy Addr : 0x48180820 Data : 0x00070000                                                                  
                        AW Phy Addr : 0x48180820 Data : 0x00050002                                                                  
                        BW Phy Addr : 0x48180824 Data : 0x00030000                                                                  
                        AW Phy Addr : 0x48180824 Data : 0x00010002              

DRAM:  2 GiB            
MMC:   OMAP SD/MMC: 0    
                        Phy Addr : 0x48180800 Data : 0x00000102    

Hit any key to stop autoboot:  0                         
                        BW Phy Addr : 0x48180e10 Data : 0x00000007boot.bin                  

210312 bytes read                 
## 
                        AW Phy Addr : 0x48180e10 Data : 0x00000003            


U-Boot 2010.06 (Apr 29 2012 - 20:28:20)            
                        Phy Addr : 0x48180e14 Data : 0x00000004
ARM clk: 987MHz               
DDR clk: 796MHz               

                        BW Phy Addr : 0x53088000 Data : 0x83d88a87H8 Selected                           
NAND device: Manufacturer I
                        AW Phy Addr : 0x53088000 Data : 0xeafffffe                                                                  
                        BW Phy Addr : 0x53098000 Data              
No NAND device foun                 
<start|stop>           to start/stop the firmware2XBM@@A552&&AHA2XiisSS252SSsisSs                 
===Optional arguments===                        
-mmap                  input memory map bin file name@@@2@MA&9&HB##Xris29ABMAAX2ir;rsSi5iss5              
-i2c                   0: i2c init not done by M3, 1(default): i2c init done by399&X99i;;;;;;r#H&293H9X#@@@@@@@B&9GhAH@XrrsrsiXABHB&HG2rr;rrSiSi              
M3  
FIRMWARE: isI2cInitRequiredOnM3: 1                         
        
FIRMWARE: Default memory config                             
FIRMWARE: 1 start Successful                            
Loading HDVPSS Firmware2S5SSi2i53hirsh2srr::,,
FIRMWARE: I2cInit will be done by M3i2,.2r;:SGAr;,:                     
FIRMWARE: Memory map bin file not passed                 
;:;rrrrssiriXGSi::shs;
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mma                                                       
;,r;;;;rsriSSrrrr;;5Xrr;
p <memory_map_file>] [-i2c <0|1>];;r;;;srrrrrr;;:;::::            
===Mandatory arguments===                         
<Processor Id>         0: DSP, 1: Video-M3, 2: Vpss-M3222hXXAAGGGX;:,,,:,:,::;:;::,:,,,,...,,,,             
<Location of Firmware> firmware binary file                      
                    
-i2c                   0: i2c init not done by M3, 1(default): i2c init done byrrr;:.......,.,.,,:::,,...............,,::.,,,,:,::,,:,:,,,:,;:                
M3  
FIRMWARE: isI2cInitRequiredOnM3: 1                       
,.::,:,,,,
FIRMWARE: Default memory configuration is used;:;::::,:::::::,:,:,,,                        
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.2.1,,,,:;rrr;;:;,,,,,,,::,.,.:.,.,;s,:;;;;:;:;;;;;::::,:::,:::,:,:,:    
FIRMWARE: Memory Configuration status : In Progress                       
,.,,,,,,,...,,.,,..........
FIRMWARE: 2 start Successful...........:,,,:,:,,,,,     
HDMI W1 rev 2.0               
Starting system message bus: dbus.        

Net:   <ethaddr> not set
Starting telnet daemon                     

 _____                    _____           _         _ht                        
reading boot.scr          
|  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_from MMC/SD to set the ENV...                          
|     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|                            
reading ti_logo.bmp        
|__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_| uImage              

2563448 bytes read             
              |___|                    |___|80009000 ...                                

Arago Project http://arago-project.org dm816x-evm ttyO24.00.01/dm81                                           

Arago 2011.09 dm816x-evm ttyO2x Kernel Image (uncompressed) 

dm816x-evm login: root                      
root@dm816x-evm:~# ls   2563384 Bytes = 2.
tst.c     
root@dm816x-evm:~# c             
     

Starting kernel ...   
boot        lib         mnt         sbin        usrng the kernel.                                     
dev         linuxrc     opt         srv         var(gcc version 4.3.3 (Sourcery G++ Lite 20           
root@dm816x-evm:/# cd media                           
root@dm816x-evm:/media# ls#1 Sun Apr 29 20:16:23 IST
card       hdd        mmcblk0p1  mmcblk0p3  ram        sda1       union13fc082] revision 2 (ARMv7), cr=10c53c7f                               
cf         mmc1       mmcblk0p2  net        realroot   sdb1cache, VIPT aliasing instruction cache                     
root@dm816x-evm:/media# cd ..              
Machine: ti816
root@dm816x-evm:/# cd usrerved size = 52428800 at 
root@dm816x-evm:/usr# ls         
FB: Reserving 

























root@dm816x-evm:/# cd ..      
Kernel command li
root@dm816x-evm:/# ls00n8 rootwait root=/d
Settings    etc         lost+found  proc        sys                                                
36
bin         home        media       saLoopBack  tmpF900000 ip=off noinitrd                            
boot        lib         mnt         sbin        usrD hash table entries: 2048 (order: 1, 8192 bytes)  
dev         linuxrc     opt         srv         varntry cache hash table entries: 65536 (order: 6, 262
root@dm816x-evm:/# cd home                          
root@dm816x-evm:/home# ls-cache hash table entries
root68 (
root@dm816x-evm:/home# cd root                              
root@dm816x-evm:~# ls  
Memory: 314MB = 31
tst.ctal  
root@dm816x-ev          
  
bin         home        media       saLoopBack  tmp0000   ( 896 kB)                                   
boot        lib         mnt         sbin        usr   (   2 MB)                                       
dev         linuxrc     opt         srv         var 528 MB)                                           
root@dm816x-evm:/# /etc/init.d/pvr-init stop  ( 364 MB)                                 
Stopping PVR   
    pkma
root@dm816x-evm:/# /etc/init.d/matrix-gui-e stop                                         
    mo
Stopping Matrix GUI application. (  14 MB)                      
root@dm816x-evm:/# cd /usr/share/ti/ti-media-controller-utils/00   ( 204 kB)                                                

top   
Unloading HDVICP2 Firmware  
SLUB: Genslabs=11, HWal
FIRMWARE: I2cInit will be done by M3=1, Nodes=1                         
FIRMWARE: Memory map bin file not passed     
NR_IRQS:407           
IRQ: Found 
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mma                                          
Total of 128 interrupts on 1 active c
p <memory_map_file>] [-i2c <0|1>]                     
GPMC revisi
===Mandatory arguments===ying to install interrupt
<Processor Id>         0: DSP, 1: Video-M3, 2: Vpss-M3          
Trying to install interrupt handler for IRQ
<Location of Firmware> firmware binary file     
Trying to install interrupt handler f
<start|stop>           to start/stop the firmware     
Trying to install interrupt handler for IRQ
===Optional arguments===                        
FIRMWARE: Memory Configuration status : In Progress6.31 BogoMIPS (lpj=4931584)                        
FIRMWARE: 1 stop Successful   
pid_max: default: 32768
Unloading HDVPSS Firmware                       
S
FIRMWARE: I2cInit will be done by M3                      
Mount-cache h
FIRMWARE: Memory map bin file not passed                
CPU: Testing write buff
Usage : firmware_loader <Processor Id> <Locat         
devtmpfs: initial                
===Optional arguments===dd_dev: VDD specified do
-mmap                  input memory map bin file name          
OMAP GPIO hardware version 0.1            
-i2c                   0: i2c init not done by M3, 1(default): i2c init done byomap_mux_init: Add partition: #1: core, flags: 0                               
M3  
FIRMWARE: isI2cInitRequiredOnM3: 1 Could not find signal i2c2_scl.i2
FIRMWARE: Default memory configuration is used                     
_omap_mux_get_by_name: C
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1                                  
NOR: Can't requ             

.sh startstered ti
Loading HDVICP2 Firmware                
registe
DM816X prcm_config_app version: 2.0.0.1         
ti81xx_pcie: Invoking PCI BIO
Doing PRCM settings...              
ti81xx_
        PRCM for IVHD0 is in Progress, Please wait.....                     
ti81xx_pcie: Register base mapped
                        BW Phy Addr : 0x48180600 Data : 0x00000102ie: Starting PCI scan...                                 
PCI: bus
                        AW Phy Addr : 0x48180600 Data : 0x00000102                 
bio: create slab <bio-0> at 0                   
                        Phy Addr : 0x45 mV                                 
                        BW Phy Addr : 0x58088000 Data : 0xeafffffe    
musb-hdrc musb-hdrc.0: MUSB HDRC host driver                 
                        AW Phy Addr : 0x58088000 Data : 0xeafffffestered, assigned bus number 1                                     
                        BW Phy Addr : 0x58098000 Data : 0xeafffffeendor=1d6b, idProduct=0002                                        
                        AW Phy Addr : 0x58098000 Data : 0xeafffffeuct=2, SerialNumber=1                                             
                        BW Phy Addr : 0x48180c10 Data : 0x00000003                                   
usb usb1: Manufacturer: Linux 
                        AW Phy Addr : 0x48180c10 Data : 0x00000000b1: SerialNumber: musb-hdrc.0                                   
h
                        Phy Addr : 0x48180c14 Data : 0x00000007 1 port detected                            
musb-hdrc musb-hdr
        PRCM for IVHD0 is Done Successfully                                           
                        Phy Addr : 0x48180d04 Data : 0x00000037=0002                                                          
                        BW Phy Addr : 0x48180720 Data : 0x00000002r=1                                                               
                        AW Phy Addr : 0x48180720 Data : 0x00000002                 
usb usb2: Manufacturer: Linux 2.6.37 musb-hcd   
                        BW Phy Addr : 0x48180724 Data : 0x00000002musb-hdrc.1                                   
hub 2-0:1.0: USB hu
                        AW Phy Addr : 0x48180724 Data : 0x000                            
                              
TCP established hash table entries: 16384 (
                        Phy Addr : 0x48180d14 Data : 0x00000007                         
TCP bind hash table entries: 16384 (o
                        BW Phy Addr : 0x5a088000 Data : 0xeafffffe            
TCP: Hash tables configured (established 16384 bind 1
                        AW Phy Addr : 0x5a088000 Data : 0xeafffffe reno registered                   
UDP hash table entries: 256 (o
                        BW Phy Addr : 0x5a098000 Data : 0xeafffffe   
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)       
                        AW Phy Addr : 0x5a098000 DataRegistered protocol fami                           
        PRCM for IVHD1 is Done Successfully                          
omap-iommu omap-
        PRCM for IVHD2 is in Progress, Please wait.....            
omap-iommu omap-iommu.1: sys registered   
                        BW Phy Addr : 0x48180800 Data : 0x00000102001-2006 Red Hat, Inc.                                            
                        AW Phy Addr : 0x48180800 Data : 0x00000102heduler noop registered                            
io scheduler d
                        Phy Addr : 0x48180e04 Data : 0x00000037cfq registered (default)                                     
 
console [ttyO2] enabled          
                        Phy Addr : 0x48180800 Data : 0x00000102loaded                   
ahci ahci.0: forcing PORTS_IMPL to 0x
                        BW Phy Addr : 0x48180e10 Data : 0x00000000 32 slots 2 ports 3 Gbps 0x3 impl platform mode                   
                        AW Phy Addr : 0x48180e10 Data : 0x00000003: flags: ncq sntf pm led clo only pmp pio slum part ccc           
                        Phy Addr : 0x48180e14 Data    
scsi0 : ahci_platform                     

                        AW Phy Addr : 0x53098000 Data : 0xeafffffe                            
0x000000040000-0x000000042000 : "U-Bo
                        BW Phy Addr : 0x48180e10 Data : 0x000000030x0000002c2000 : "Kernel"                                        

                        AW Phy Addr : 0x48180e10 Data : 0x00000000                       
omap2-nand driver initializing            
PRCM Initialization completedomap2-nand.0":               
FIRMWARE: I2cInit will be done by M30000000-0x000000260000 : "U-Boot"   
FIRMWARE: Memory map bin file not passed00000260000-0x000000280000 : "U-Boot Env
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmarnel"                                        
0x0000006c0000-0x00000cee0000 : "F
p <memory_map_file>] [-i2c <0|1>]                      
0x00000cee
===Mandatory arguments===erved"                   
<Processor Id>         0: DSP, 1: Video-M3, 2: Vpss-M3vinci mdio revision 1.6                               
<Location of Firmware> firmware binary file_mdio.0: detected phy mask fffffff9        
<start|stop>           to start/stop the firmwarevinci_mdio.0: probed                      
      
M3  
FIRMWARE: isI2cInitRequiredOnM3: 1    
usbcore: registered new inter
FIRMWARE: Default memory configuration is used                  
Initializing USB Mass Stora
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.2.1d new interface driver usb-storage                                   
FIRMWARE: Memory Configuration status : In Progressd.                                    
mice: PS/2 m
FIRMWARE: 1 start Successfulce                          
Loading HDVPSS (V4L2) Firmware_rtc: rtc core: registered oma
FIRMWARE: I2cInit will be done by M3                                
i2c
FIRMWARE: Memory map bin file not passed  
Linux video capture interface: v2    
<Location of Firmware> firmware binary filenotify drivercreated  for  remote proc id 2
<start|stop>           to start/stop the firmware                                                 
===Optional arguments===core: registered new int
-mmap                  input memory map bin file name                           
asoc: tlv320aic3x-hifi <-
-i2c                   0: i2c init not done by M3, 1(default): i2c init done by 
ALSA device list:                 
  #0: TI81XX EVM                
TCP cubic
M3gi
FIRMWARE: isI2cInitRequiredOnM3: 1istered protocol family 17        
VPSS_DCTRL: setup 7360 filter failed.
tvp7002 2-005d: tvp7002 found @ 0x5d (OMAP I2C adapter)
omap_i2c omap_i2c.2: controller timed out
omap_i2c omap_i2c.2: controller timed out
omap_i2c omap_i2c.2: controller timed out
omap_i2c omap_i2c.2: controller timed out
omap_i2c omap_i2c.2: controller timed out
tvp7002 2-005d: TVP7002 read error -110
tvp7002: probe of 2-005d failed with error -110
ti81xxvin ti81xxvin: Error registering v4l2 subdevice
HDMI W1 rev 2.0
root@dm816x-evm:/usr/share/ti/ti-media-controller-utils# cd /..
root@dm816x-evm:/# ls
Settings    etc         lost+found  proc        sys
bin         home        media       saLoopBack  tmp
boot        lib         mnt         sbin        usr
dev         linuxrc     opt         srv         var
root@dm816x-evm:/# ./saLoopBack
failed to open capture device
Error in opening capture device for channel 0
root@dm816x-evm:/# ./saLoopBack
failed to open capture device
Error in opening capture device for channel 0
root@dm816x-evm:/#

0 Margarita Gashova over 9 years ago in reply to MOHAMMAD NASEER M N

TI__Guru* 80190 points

Hello,

This log is messed up I am not sure why.

Are you executing this steps?

/etc/init.d/matrix-gui-e stop

/etc/init.d/pvr-init stop

cd /usr/share/ti/ti-media-controller-utils/
./load-hd-firmware.sh stop

./load-hd-v4l2-firmware.sh start

After these steps could you check which modules are load?

Are you using the default ezsdk on our sd card and tvp7002?

BR
Margarita

0 MOHAMMAD NASEER M N over 9 years ago in reply to Margarita Gashova

Genius 5755 points

Hi,
Literally sorry for what is happening....

After these steps could you check which modules are load?
--->>how to see the modules...

Are you using the default ezsdk on our sd card and tvp7002?
--->>>I dont know which version of ezsdk is in sd card,i got it from dm8168kit.but i have installed ezsdk recent one ezsdk5,and i did make all there...then i have taken the project file saLoopBack fron bin folder of video and copied it to sd card what i got with board in rootfs partition,and i did the steps what you told,then i got these errors.

thank you

0 Margarita Gashova over 9 years ago in reply to MOHAMMAD NASEER M N

TI__Guru* 80190 points

Hello,

lsmod is the command.

Could you create a new SD card with the latest ezsdk version?

BR
Margarita

0 MOHAMMAD NASEER M N over 9 years ago in reply to Margarita Gashova

Genius 5755 points

Hi,
I ll do that,do we have any video loop back application by default in sd card,or video related applications so that i can connect my camera and see some output.
thank you.

0 Margarita Gashova over 9 years ago in reply to MOHAMMAD NASEER M N

TI__Guru* 80190 points

Hello,

There are video related demos like omx demos which you could run like:

/etc/init.d/matrix-gui-e stop

/etc/init.d/pvr-init stop

cd /usr/share/ti/ti-omx

./decode_display_a8host_debug.xv5T -i /usr/share/ti/data/videos/dm816x_1080p_demo.264 -w 1920 -h 1080 -f 60 -g 0 –d 0 –c h264

This will decode->display a video stream.

You could check this guide OMX_05_02_00_48_UserGuide.pdf, Chapter 4.
The OMX demos does not use v4l2 capture/display driver.

You could use gtreamer as well.

I recommend you to go trough DM816x_EZ_Software_Developers_Guide.pdf.

BR
Margarita

Processors

Processors forum

dm8168 command for running demos