User Tools

Site Tools


faqs:general |

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
faqs:general [2015/05/04 17:31]
rchen [(25) Do Z3 encoders support Closed GOPs?]
faqs:general [2019/05/20 15:30] (current)
cflintiii [Capturing Packet Stream with Wireshark]
Line 12: Line 12:
 <​code>​ <​code>​
     sudo apt-get install bison flex mtd-utils liblzo2-dev uuid-dev zlib1g-dev libpcre3-dev autoconf \     sudo apt-get install bison flex mtd-utils liblzo2-dev uuid-dev zlib1g-dev libpcre3-dev autoconf \
-         ​autoconf-archive automake automake1.9 ​automake1.9-doc ​libtool libtool-doc+         ​autoconf-archive automake automake1.9 libtool libtool-doc ​lynx xutils-dev
 </​code>​ </​code>​
  
Line 21: Line 21:
 <​code>​ <​code>​
    sudo yum install bison flex mtd-utils mtd-utils-ubi lzo-devel libuuid-devel pcre-devel automake \    sudo yum install bison flex mtd-utils mtd-utils-ubi lzo-devel libuuid-devel pcre-devel automake \
-        automake17 automake14 autoconf libtool+        automake17 automake14 autoconf libtool ​lynx xorg-x11-server-devel
 </​code>​ </​code>​
- 
- 
-\\  
  
 ==== (2) Will the code build in a 64-bit environment?​ ==== ==== (2) Will the code build in a 64-bit environment?​ ====
Line 34: Line 31:
  
 <​code>​ <​code>​
-    ​sudo apt-get ​install ia32-libs+   sudo dpkg --add-architecture i386 
 +   sudo apt-get ​update 
 +   sudo apt-get install libc6:i386 libncurses5:​i386 libstdc++6:​i386 zlib1g:i386
 </​code>​ </​code>​
  
Line 44: Line 43:
     sudo yum install glibc.i686     sudo yum install glibc.i686
 </​code>​ </​code>​
- 
- 
-\\  
  
 ==== (3) What versions of Linux can I use to build the Z3 codebase? ==== ==== (3) What versions of Linux can I use to build the Z3 codebase? ====
Line 1017: Line 1013:
  
 Yes, Z3's encoders all generate Closed GOPs. Yes, Z3's encoders all generate Closed GOPs.
 +
 +\\
 +
 +==== (26) What are the maximum bitrates that can be used for each encoding platform? ====
 +
 +The following are the maximum recommended bitrates for streaming for each platform:
 +
 +^Platform ^ Maximum Streaming Bitrate |
 +|DM368 ​  | 16Mbps |
 +|DM8107 ​ | 35Mbps |
 +|DM8148 ​ | 35Mbps |
 +|DM8168 ​ | 50Mbps |
 +
 +
 +Note that, when encoding to a file, limitations of the media used may apply.
  
 \\ \\
Line 1564: Line 1575:
 \\ \\
  
-==== (17) How do you change ​the timeout value for decode? ==== +==== (17) How do you modify files in the DM368 file system? ====
- +
-The timeout command can be found by running +
- +
-<​code>​ +
-    grep -e 'read -t' ​ /​opt/​dvsdk/​*.sh +
-</​code>​+
  
 To change files on the DM36x filesystem, you need to make it writable first: To change files on the DM36x filesystem, you need to make it writable first:
Line 1585: Line 1590:
 \\ \\
  
-==== (18) What size SD cards are supported? ====+==== (18) How do you change the timeout value for decode? ==== 
 + 
 +The timeout command can be found by running 
 + 
 +<​code>​ 
 +    grep -e 'read -t' ​ /​opt/​dvsdk/​*.sh 
 +</​code>​ 
 + 
 +See question (17) on making the DM368 file system writable so changes can be made. 
 + 
 + 
 +\\ 
 + 
 +==== (19) What size SD cards are supported? ====
  
 Any firmware released in 2012 or later supports up to 32GB. Any firmware released in 2012 or later supports up to 32GB.
Line 1591: Line 1609:
 \\  \\ 
  
-==== (19) Are mini-SD cards (with adapter) supported in the SD card slot? ====+==== (20) Are mini-SD cards (with adapter) supported in the SD card slot? ====
  
 Yes they are. Yes they are.
  
 \\ \\
-==== (19) After updating the firmware and trying to write the configuration we get a "​mounting /​dev/​mtdblock5 on /tmp/config failed"​ message. ​ What can we do? ====+==== (21) After updating the firmware and trying to write the configuration we get a "​mounting /​dev/​mtdblock5 on /tmp/config failed"​ message. ​ What can we do? ====
  
 Somehow mtd5 got in an unknown state in the update process. ​ You can get mtd5 back in a known state by typing: Somehow mtd5 got in an unknown state in the update process. ​ You can get mtd5 back in a known state by typing:
Line 1606: Line 1624:
 \\ \\
  
-==== (20) I have a DM368-SDI-RPS. When switching from encoder to decoder mode, the decoder runs, but it shows a black screen with audio only. ====+==== (22) I have a DM368-SDI-RPS. When switching from encoder to decoder mode, the decoder runs, but it shows a black screen with audio only. ====
  
 The DM368-SDI-RPS and DM368-VI-RPS require a power cycle between changing from encoder to decoder mode.  Note that a power cycle is not needed for the DM368-RPS. The DM368-SDI-RPS and DM368-VI-RPS require a power cycle between changing from encoder to decoder mode.  Note that a power cycle is not needed for the DM368-RPS.
Line 1612: Line 1630:
 \\ \\
  
-==== (21) I am getting a "​failed to encode video buffer"​ message. ​ What could be causing this? ====+==== (23) I am getting a "​failed to encode video buffer"​ message. ​ What could be causing this? ====
  
 This can happen if high bitrates are used for sub-D1 resolutions (for example, > 1Mbps for CIF).  To avoid This can happen if high bitrates are used for sub-D1 resolutions (for example, > 1Mbps for CIF).  To avoid
Line 1624: Line 1642:
 \\  \\ 
  
-==== (22) We are seeing an '​hCapture failed'​ message. ​ What could be causing this? ====+==== (24) We are seeing an '​hCapture failed'​ message. ​ What could be causing this? ====
  
 The full message is: The full message is:
Line 1637: Line 1655:
 \\ \\
  
-==== (23) Is encode of 29.97 / 59.94Hz content supported? ====+==== (25) Is encode of 29.97 / 59.94Hz content supported? ====
  
 Yes it is.  The DM368-based products will automatically detect 29.97 and 59.94 Hz and encode at that rate. Yes it is.  The DM368-based products will automatically detect 29.97 and 59.94 Hz and encode at that rate.
Line 1643: Line 1661:
 \\ \\
  
-==== (24) How do I reconfigure startup behavior? ====+==== (26) How do I reconfigure startup behavior? ====
  
 Behavior at startup is controlled in /​root/​.profile on the board filesystem. Behavior at startup is controlled in /​root/​.profile on the board filesystem.
Line 1649: Line 1667:
 \\ \\
  
-==== (25) What are the specifications of the audio RCA inputs on the DM368 APP board? ====+==== (27) What are the specifications of the audio RCA inputs on the DM368 APP board? ====
  
 The specifications are: The specifications are:
Line 1661: Line 1679:
 \\ \\
  
-==== (26) We are using our own hardware with its own Ethernet chip.  It appears that the Ethernet packets are being corrupted somehow when we send RTP.  What should we look at? ====+==== (28) We are using our own hardware with its own Ethernet chip.  It appears that the Ethernet packets are being corrupted somehow when we send RTP.  What should we look at? ====
  
 This points to the Ethernet switch getting overloaded. ​ You can try adjusting the delay between packets with the parameter "​--interpacketgap"​. ​ The default value is 150 microseconds.  ​ This points to the Ethernet switch getting overloaded. ​ You can try adjusting the delay between packets with the parameter "​--interpacketgap"​. ​ The default value is 150 microseconds.  ​
Line 1669: Line 1687:
 \\ \\
  
-==== (27) When decoding DVB-ASI, how do you select which program to decode? ====+==== (29) When decoding DVB-ASI, how do you select which program to decode? ====
  
 Use the "​port"​ value to select. ​ "​1"​ is the first program, "​2"​ is the second program etc. Use the "​port"​ value to select. ​ "​1"​ is the first program, "​2"​ is the second program etc.
Line 1675: Line 1693:
 \\ \\
  
-==== (28) On the DME-01, what inputs/​outputs are used for DVB-ASI decode / HD-SDI output? ====+==== (30) On the DME-01, what inputs/​outputs are used for DVB-ASI decode / HD-SDI output? ====
  
 The middle BNC connector is used for ASI In (same as "SDI In"​). ​ The left BNC connector is used for SDI Out (same as "ASI Out"). The middle BNC connector is used for ASI In (same as "SDI In"​). ​ The left BNC connector is used for SDI Out (same as "ASI Out").
Line 1681: Line 1699:
 \\ \\
  
-==== (29) There are 3 different ubl.bin files generated. ​ How do I know which one to use? ====+==== (31) There are 3 different ubl.bin files generated. ​ How do I know which one to use? ====
  
 ubl_DM36x_nand_270_243.bin is for nominal timing for the DM365. ubl_DM36x_nand_270_243.bin is for nominal timing for the DM365.
Line 1691: Line 1709:
 \\ \\
  
-==== (30) Is HDMI display supported on the DM365/​DM368?​ ====+==== (32) Is HDMI display supported on the DM365/​DM368?​ ====
  
 Yes.  RTPRX supports HDMI output. ​ Select the "​component"​ option to cause video data to go to the HDMI.  It may also be necessary to run the HDMI driver. ​ This can be done by typing the following before running RTPRX: Yes.  RTPRX supports HDMI output. ​ Select the "​component"​ option to cause video data to go to the HDMI.  It may also be necessary to run the HDMI driver. ​ This can be done by typing the following before running RTPRX:
Line 1701: Line 1719:
 \\ \\
  
-==== (31) How do I change the MAC address on my DM365/DM368 unit? ====+==== (33) How do I change the MAC address on my DM365/DM368 unit? ====
  
 The MAC address can be changed in u-boot by doing the following steps: The MAC address can be changed in u-boot by doing the following steps:
Line 1715: Line 1733:
 \\ \\
  
-==== (32) What file systems are supported on the DM365/​DM368?​ ====+==== (34) What file systems are supported on the DM365/​DM368?​ ====
  
 VFAT and EXT3 are supported. VFAT and EXT3 are supported.
Line 1721: Line 1739:
 \\ \\
  
-==== (33) What is the maximum sizes of flash drives connected to DM365/​DM368?​ ====+==== (35) What is the maximum sizes of flash drives connected to DM365/​DM368?​ ====
  
 For VFAT, the limit is 32GB.  For EXT3, the limit is 2TB. For VFAT, the limit is 32GB.  For EXT3, the limit is 2TB.
Line 1727: Line 1745:
 \\ \\
  
-==== (34) Is it possible to configure the DM368 system so that it autostarts after reset? ====+==== (36) Is it possible to configure the DM368 system so that it autostarts after reset? ====
  
 Yes it is.  To do this, save the settings while an encode is running. Yes it is.  To do this, save the settings while an encode is running.
  
 \\ \\
 +
 +
 ===== DM814X/​DM816X-specific questions (EZSDK) ===== ===== DM814X/​DM816X-specific questions (EZSDK) =====
  
Line 2374: Line 2394:
 ==== (32) I see a greenish tint when encoding HDMI with a DM8107 MOD.  What could be the cause? ==== ==== (32) I see a greenish tint when encoding HDMI with a DM8107 MOD.  What could be the cause? ====
  
-This is indicative of the one of the 2 ribbon connectors in the back of the module being lose.  Please double-check those connections.+This is indicative of the one of the 2 ribbon connectors in the back of the module being loose.  Please double-check those connections.
  
 \\ \\
Line 2403: Line 2423:
 The best way to do this is to remove "​S99webserver.sh"​ from /etc/rc5.d on the system. The best way to do this is to remove "​S99webserver.sh"​ from /etc/rc5.d on the system.
  
 +\\
 +
 +==== (36) I want to telnet to the board and run the same menu of options that you see when you run through the serial console. ​ How do I do this? ====
 +
 +After telnet'​ing into the board, you can type the following command (for DM816X products):
 +
 +<​code>  ​
 +   /​opt/​dvr_rdk/​ti816x/​run_mcsenc.sh
 +</​code>​
 +
 +For DM8107 and DM8148 products, the "​ti816x"​ would change to "​ti810x"​ and "​ti814x",​ respectively.
  
 \\ \\
 +
 +
 +==== (37) I want to use serial port 0 for something else besides the console. ​ How do I configure serial port 0 so it no longer outputs the console? ====
 +
 +This can be done by editing the "​console"​ environment variable in u-boot. ​ Currently it is set to:
 +
 +<​code>​
 +   ​console=ttyO0,​115200,​quiet
 +</​code>​
 +
 +You can reroute the console output to the second serial port instead by typing while in the Linux prompt on your target board:
 +
 +<​code>​
 +   ​fw_setenv console=ttyO1,​115200,​quiet
 +</​code>​
 +
 +You also need to edit /​etc/​inittab to keep getty from respawning on ttyO0.
 +
 +\\
 +
 +
 +
 ===== Miscellaneous ===== ===== Miscellaneous =====
  
Line 2492: Line 2545:
 \\ \\
  
-==== (8) We have a DM8169 product and want to add support for Service Description Tables (SDT) and Stream Identifier (SID) to conform to ISO 13818-11 and ETSI EN 300 468 V1.14.1. ​ Is this possible to do? ====+==== (8) We have a DM8169 product and want to add support for Service Description Tables (SDT) and Stream Identifier (SID) to conform to ISO 13818-11 and ETSI EN 300 468 V1.14.1. Is this possible to do? ==== 
 + 
 + 
 +Yes. You can use the function tsmux_add_user_table() to support this. This applies to both the EZSDK and the RDK. 
 + 
 + 
 +===== General Troubleshooting ​ ===== 
 + 
 + 
 +==== Capturing Packet Stream with Wireshark ==== 
 + 
 + 
 +1) Download and install [[http://​www.wireshark.org|Wireshark ]]and associated programs to enable live stream capture on the PC you already use VLC Media Player. A Restart will be required once installation is complete. 
 + 
 + 
 +2) Set encoder for RTP/RTSP transfer and begin encoding as described in your product'​s manual. 
 + 
 + 
 +3) Open Wireshark. Double click the "​Ethernet"​ near the center of the window to automatically begin capture. 
 + 
 + 
 +{{  http://​wiki.z3technology.com//​lib/​plugins/​ckgedit/​fckeditor/​userfiles/​image/​faqs/​media_servers/​wireshark_start.jpg?​nolink&​819x599 ​ }} 
 + 
 + 
 +4) Open VLC Media Player on the Same PC and begin Streaming RTSP as described in your product'​s manual. 
 + 
 + 
 +5) Allow Stream to capture for 1 minute. Click the Red Stop button on the menu bar of Wireshark. 
 + 
 + 
 +{{  http://​wiki.z3technology.com//​lib/​plugins/​ckgedit/​fckeditor/​userfiles/​image/​faqs/​media_servers/​wireshark_running.jpg?​nolink&​819x599 ​ }} 
 + 
 + 
 +6) Hit <​cntrl+S>​ or the Save button at the top of the window to open a save dialog. Give the file a name of your choice that you will remember. 
 + 
 + 
 +\\  
 +{{  http://​wiki.z3technology.com//​lib/​plugins/​ckgedit/​fckeditor/​userfiles/​image/​faqs/​media_servers/​wireshark_stop.jpg?​nolink&​819x601 ​ }} 
 + 
 + 
 +7) Attach the saved file to an email and send it to Z3 Technology. 
 + 
 + 
 +====  ==== 
  
-Yes.  You can use the function tsmux_add_user_table() to support this.  This applies to both the EZSDK and the RDK.+==== Z3 Cam Solutions Forgotten Password ====
  
  
 +To reset a forgotten password you will need physical access to the unit.
  
  
 +Create a file called **z3passreset ** on an empty SD Card or USB flash drive; insert the SD Card or USB flash drive and power cycle the unit to reset the password to nothing.
  
faqs/general.1430760709.txt.gz · Last modified: 2015/05/04 17:31 by rchen