This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
faqs:general [2015/05/11 20:08] rchen |
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 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 dpkg –-add-architecture i386 | + | sudo dpkg --add-architecture i386 |
sudo apt-get update | sudo apt-get update | ||
sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386 zlib1g:i386 | sudo apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386 zlib1g:i386 | ||
Line 46: | 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 2400: | 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 2437: | Line 2431: | ||
<code> | <code> | ||
/opt/dvr_rdk/ti816x/run_mcsenc.sh | /opt/dvr_rdk/ti816x/run_mcsenc.sh | ||
- | <\code> | + | </code> |
For DM8107 and DM8148 products, the "ti816x" would change to "ti810x" and "ti814x", respectively. | 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 2530: | 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. | ||