1. Manuals
  2. Brands
  3. Signalogic Manuals
  4. PCI Card
  5. SigC667x
  6. User manual

Signalogic SigC667x User Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
SigC667x / SigC641x
Includes Installation and Test for:
• • • • SigC6xxx Hardware
• • • • DirectCore® Software
• • • • CIM® Software
1
Includes SigC667x 32-core and 64-core PCIe cards, and SigC641x PCI/PCIe
cards and PTMC modules
2
Includes Texas Instruments code gen tools installation
1
2
Copyright © © © © 2012-2014 Signalogic, Inc.
Signalogic, Inc.
9617 Wendell @ Skillman
Dallas, TX 75243
Tel: 214-349-5551
Fax: 214-343-0163
http://www.signalogic.com
tech_support@signalogic.com
User Guide
Revision B8
January 2015

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the SigC667x and is the answer not in the manual?

Questions and answers

Summary of Contents for Signalogic SigC667x

  • Page 1 Revision B8 January 2015 Signalogic, Inc. 9617 Wendell @ Skillman Dallas, TX 75243 Tel: 214-349-5551 Fax: 214-343-0163 http://www.signalogic.com tech_support@signalogic.com Includes SigC667x 32-core and 64-core PCIe cards, and SigC641x PCI/PCIe cards and PTMC modules Includes Texas Instruments code gen tools installation...

  • Page 2: Table Of Contents

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 TABLE OF CONTENTS 1 SigC667x Hardware Installation SigC667x Card Overview ....................5 Installing SigC667x Cards ....................6 SigC667x Card and Firmware Revisions ................ 9 2 SigC641x Hardware Installation SigC641x Module Overview ..................
  • Page 3 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 4.5.2 RTAF Peripheral Support ..................88 4.5.3 RTAF Development and Host Platform Notes ............. 88 4.5.3.1 Linux Platform Builds CIM Software Installation..................... 92 4.6.1 Running User Programs with CIM ............... 92 4.6.2...

  • Page 4: Revision History

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Revision History Created Rev A Jul 2012 Modified Rev B Nov 2012 – Jan 2013, merged SigC677x documentation Modified Rev B2 Feb 2013, updated with software changes Modified...

  • Page 5: Sigc667X Hardware Installation

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 1 SigC667x Hardware Installation The sections below cover installation of specific SigC66x and SigC64x card types. Note that section 3, Server Installations, covers a few different types of popular servers and may have some additional hardware installation information that could prove useful, depending on your type of server.

  • Page 6: Installing Sigc667X Cards

    PCIe connector is not touching components on the motherboard, for instance heat sinks or tall capacitors. The SigC667x cards support two boot modes: emulation boot mode and I2C boot mode. Boot mode is selected by Switch 1 (labeled “SW1” on the card), as shown in Figure 1-3 below. I2C boot mode is the default setting and should be used for normal SigC667x card operation.

  • Page 7: Sigc667X / Sigc641X User Guide, Rev B7 Copyright © Signalogic

    BIOS scan of the PCIe device tree (which includes PCIe slots). There are four (4) PCIe LEDs on the SigC667x card that will flash to indicate valid PCIe initialization after boot. The placement of these LEDs is shown in Figures 1-4 and 1-5, as shown below.
  • Page 8 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 1-4, PCIe boot LEDs, top side Figure 1-5, PCIe boot LEDs, bottom side If after boot all PCIe LEDs are not flashing, then a system reset, either through software (for example ‘shutdown –r now’...

  • Page 9: Sigc667X Card And Firmware Revisions

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 1.3 SigC667x Card and Firmware Revisions For SigC6678-32, card and firmware revision is printed on the back side of the card, near the inner edge of the PCIe connector, as shown in Figure 1-6 below:...
  • Page 10 Copyright © Signalogic 2012-2014 Hardware Version Table Card Type, Revision Silkscreen labeling on back of card SigC6678-32 SigC6678-64 9692868100E A101 9692868100 9692868101E A102 9692868102E A103 19C2868200 A101 19C2868201-01 A102 Table 1-1, SigC667x card and firmware revision information 10 / 109...

  • Page 11: Sigc641X Hardware Installation

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 2 SigC641x Hardware Installation 2.1 SigC641x Module Overview The SigC6415T PMC module has eight C6415T single-core devices and a PCI interface. From the top of the card, two C6415T devices can be seen as shown in Figure 2-1 below.

  • Page 12: Installing Sigc641X Modules

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 2.2 Installing SigC641x Modules In order to use a SigC641x PMC module, it must first be inserted onto a PMC-to-PCIe adapter card. The module has been tested with a Dynamic Engineering PMC to PCIe adapter (PCIeBPMCX1), shown in Figure 2-3, and an Integrative Innovation PMC to PCIe adapter, shown in Figure 2-4.
  • Page 13 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 After inserting the module into an adapter, the adapter card can now be placed in a PCIe slot (or PCI slot if a PMC to PCI adapter is used instead). Ensure that the card is inserted into the PCIe slot with the proper orientation.

  • Page 14: Sigc641X Loopback Connections

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 2.3 SigC641x Loopback Connections In order for test software to operate correctly, loopback connections on the correct PN4 and backplate connector pins should be established (see Figures 6-1 and 6-2 for PN4-to-backplate connector mapping diagrams).

  • Page 15: Sigc641X Module And Logic Revisions

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 2.4 SigC641x Module and Logic Revisions The module revision number is printed on the silkscreen along the left edge (with the bezel plate towards you) of both sides of the module as shown in Figure 2-8. The logic revision number is affixed to the Xilinx boot PROM (U39) as shown in Figure 2-9.

  • Page 16: Sigc641X Processor And Sdram Clock Rates

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 2.5 SigC641x Processor and SDRAM Clock Rates The processor clock rate for the particular module used is affixed to the flash memory chip (marked U8 on the module silkscreen) which is located next to the module status LEDs (marked D1-D16 on the module silkscreen) and is shown in Figure 2-10 below.

  • Page 17: Server Installations

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 3 Server Installations The Server Installations section contains information on specific types of servers. This information does not cover all servers, but some of the physical and configuration procedures and requirements documented here may also apply to other server enclosures.

  • Page 18: Supermicro 1U

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 The additional power cable is required when the card has a PEG (PCI Express Graphics) type of connector, which has become a de facto industry standard due to the proliferation of PCIe GPU boards.
  • Page 19 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 the picture) has two (2) PCIe slots, which would allow two (2) SigC6678-64 cards to be installed. Figure 3-3, SigC6678-64 card installed in a 1U server, top view, with 6-pin external power connection highlighted (red square) Note that it's also possible to “mix and match”...

  • Page 20: Desktop And Other Pc Enclosures

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 3.3 Desktop and Other PC Enclosures Installation for non-server PC enclosures, for example desktop, tower and shuttle cases, is very similar to server installation, with the exception of external power cables for SigC6678-64 cards.
  • Page 21 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 drives, DVD players, etc. For the SigC6678-64 card, a minimum of two connectors should be mated, but it's preferable if all 3 connectors are mated (see notes below).
  • Page 22 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 (or other PC enclosure) internal connector, without the SigC6678-4 card installed and with the top panel or lid open on the enclosure, boot the machine, and use a voltmeter (set to DC volts) to measure the pins.

  • Page 23: Software Installation

    RTAF components, and CIM components The host software .rar file should be unzipped to the "/root" directory, creating a main Signalogic software folder, with subfolder hierarchy as shown in Figure 4-1 below: 23 / 109...
  • Page 24 .rar file. For SigC667x cards, all TI code generation and configuration is handled either with make files or using the fully automated CIM build process, and intended to be used with TI's command line build tools.
  • Page 25 For target software, the target .rar file installs in the “mCPU_target” subfolder under the main Signalogic folder on a Linux machine, as shown in Figure 4-1 above and Figure 4-2a below.
  • Page 26 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 4-2b, Target software folder hierarchy for SigC641x modules For SigC641x cards, TI code generation and configuration is not automated and must be performed with TI's Code Composer Studio IDE environment, using project files included in the target software.

  • Page 27: Building The Loadable Kernel Module (Lkm) Driver

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 4.1 Building the Loadable Kernel Module (LKM) Driver Files for the host software DirectCore driver reside on the “driver” subfolder under the “DirectCore” subfolder (see Figure 4-1 above). Key files include: - SigC667x and SigC641x driver source code sig_mc_hw.c...
  • Page 28 This is a rare occurrence, but can happen in some systems and/or depending on which firmware revision is loaded on the SigC641x or SigC667x card. For the latter case, see the notes in section 1.2 above, “Installing SigC667x Cards”.

  • Page 29: Linux Kernel-Devel Installation Requirement

    /dev/sigc641x_n /dev/sigc667x_n Where n is the device number for SigC667x, and card number for SigC641x. Figure 4-4 below is a screen capture showing files on the driver subfolder and the driver unload process: Figure 4-4, SigC641x / SigC667x driver unload process 4.1.1 Linux Kernel-Devel Installation Requirement...
  • Page 30 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Note that the “uname –r” command can be used separately to determine the version of the currently running kernel: [root@host]# uname -r The result will look similar to this (depending on what kernel revision is installed): 2.6.18-400.1.1.el5xen...

  • Page 31: Building Directcore Libraries

    Currently these libraries are only supported by SigC641x hardware. Building and/or running these Tdmlib libraries should not be attempted for SigC667x hardware. Sessionmgr Voplib For each library, after building, either an archive (.a) or shared object (.so) file should be copied to the default system library directory, typically /usr/lib.
  • Page 32 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 4-5, DirectCore library rebuild process After building each library, resulting library filenames should be: 32 / 109...
  • Page 33 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 libenmgr.a (or libenmgr.so) • libhwmgr.a (or libhwmgr.so) • libhwlib.a (or libhwlib.so) • libcimlib.a (or libcimlib.so) • Note: See notes above libfilelib.a (or libfilelib.so) • about whether to build these libraries.

  • Page 34: Test Programs

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 4.3 Test Programs The following test programs are available after default software installation. Test Program Card Connections Required Comments memTest None . No loopback connections Can be used to validate the card and or other hardware connections are driver installation.

  • Page 35: Memtest

    This is not the normal or recommended method of using SigC641x modules and SigC667x cards but serves instead as a diagnostic and measurement tool. The memTest program has several test modes as follows: •...
  • Page 36 To exit from the program, press any key. Note! For SigC667x hardware, “core list” with multiple bits set may span one or more target multicore CPUs. For SigC641x hardware, “core list” has the same meaning as “processor list”, as the C641x series of devices is single-core, and thus any core list value with more than one bit set specifies more than one device (CPU).
  • Page 37 Copyright © Signalogic 2012-2014 Figure 4-6, memTest running diagnostic test for 3 cores on SigC667x or SigC641x hardware Figure 4-7 below is a screen capture of a memTest diagnostic run for 32 cores, using SigC667x hardware, by executing the following command: #./memTest -cSIGC66XX -d -m0xffffffff -B98304 -P...
  • Page 38 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 4-7, memTest running diagnostic test for 32 cores on a SigC667x card Figure 4-8 below is a screen capture of a successful random block memTest run for 3 cores, using SigC641x hardware, by executing the following command: #./memTest –m0xa8 –r–B204 –n20 –cSIGC64XX...
  • Page 39 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 4-8, memTest running random block test for 3 cores on a SigC641x module Note that in the above command, the parameter specifies the test to run for 20 iterations.
  • Page 40 Figure 4-10 below is a screen capture of a successful random block test of onchip shared memory (i.e. MCSM, or multicore shared memory) for 32 cores, using SigC667x hardware, by executing the following command: #./memTest –cSIGC66XX –B0x100000 –pt –P –r –m0xffffffff –Mos –n10...
  • Page 41 Figure 4-10 above by examining the “mask” value printed along with test results. Block Size Parameter Notes 1. For SigC641x, 4 kByte is the maximum block size for all memory areas. For SigC667x, 1 MByte is the maximum block size for external memory and shared memory (MCSM), and 96 kByte is the maximum size for core-specific L2 memory.

  • Page 42: Boardtest

    Currently, the “make” is the standard (default) option, and should be tested first. Before running boardTest, first enter: #./boardTest –h This will bring up the help menu in order to configure SigC667x or SigC641x hardware. Command line option syntax (options with “+” sign are mandatory): -f<num>...
  • Page 43 Output Description Figure 4-11 below is a screen capture of output from the boardTest test program, executed using the following command for a SigC667x PCIe card: # ./boardTest -m1 –f1250 -ebdtest.out -cSIGC66XX for the following command for a SigC641x PCIe card or PTMC module: # ./boardTest -m1 –f1000 -ebdtest.out -cSIGC64XX...
  • Page 44 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 4-11, Example boardTest display To exit from the boardTest program, press the q (Quit) or ESC keys. Note: you can also exit using Ctrl-C, but using the interactive keyboard commands is preferred as that allows the test program to free (de-allocate) the card handle, close its instance of the driver, and perform other clean up operations.

  • Page 45: Ffttest

    #cd ../DirectCore/apps/SigC641x_C677x/fftTest #make Before running fftTest, first enter: #./fftTest –h This will bring up the help menu in order to configure SigC667x hardware. Command line option syntax (options with “+” sign are mandatory): -f<num> Device clock rate in MHz (e.g. -f1000) -m<num>...
  • Page 46 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 fftTest Output Description Figure 4-12 below is a screen capture of output from the fftTest test program, executed using the following command for a SigC667x PCIe card: # ./fftTest -m1 –f1000 -efft.out -cSIGC66XX -n4 The screen capture in Figure 4-12 shows output for a small FFT order using a parallelized method based on Bailey's "Four Step"...
  • Page 47 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 4-12, Example fftTest display output 47 / 109...

  • Page 48: Videotest

    #cd ../DirectCore/apps/SigC641x_C677x/videoTest #make Before running videoTest, first enter: #./videoTest –h This will bring up the help menu in order to configure SigC667x hardware. Command line option syntax (options with “+” sign are mandatory): -f<num> Device clock rate in MHz (e.g. -f1000) -m<num>...
  • Page 49 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 # ./videoTest -m1 –f1000 -evideo.out -cSIGC66XX -itouchdown_pass_1080p_tr.yuv The screen capture in Figure 4-13 shows typical videoTest run-time output, and Figure 4-14 shows the resulting H.264 encoded output file viewed using the Videolan VLC player.
  • Page 50 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 4-14, Example of encoded videoTest output. In the above screen capture, H.264 encoded data has been stored to a file, and then played back for test / comparison purposes...

  • Page 51: Apptest

    Note 2: Currently appTest is only supported by SigC641x hardware. Building and/or running appTest should not be attempted for SigC667x hardware. The appTest program gives an example of communicating with target code as it runs in real- time, demonstrating several DirectCore library API calls.

  • Page 52: Apptest Output Description

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Note that SigC66xx cards do not support a TDM interface. Note also that in the above command-line, the option specifies a executable “-etmsc64xx.out” or “-etmsc66xx.out” code file generated by Texas Instruments CGT (Code Generation Tools), v7.2.x or higher. See “Host Test Programs”...
  • Page 53 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 4-15, Example appTest display appTest program interactive keyboard commands include: Main Level Algorithm Mode Control Show list of currently active call IDs Display diagnostic data (currently shows per-channel state and...

  • Page 54: Rtp Audio Test Program

    -s10.0.0.29 -dsnd -u8 -f 4.3.5.2.1 Installing and Running RTP Audio 1) To install the RTP Audio test program, download “WinXP_01Apr09.rar” or “RtpAudio.zip” or similar compressed file from Signalogic’s website, and extract to a suitable folder on your 54 / 109...
  • Page 55 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 target PC. For full-duplex operation between two PCs, two copies of RtpAudio should be installed, on one each PC. 2) To run the RTP Audio test program, open a console application window (e.g. run “Cmd”...

  • Page 56: Call And Voice Processing Test Procedures

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 4.3.5.3 Call and Voice Processing Test Procedures Note: This section only applies if a TDM interface is being used. If not, ignore this section and skip to section 4.3.6, Interactive Command Summary.
  • Page 57 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 In Figure 4-16 above, “Phone 1” and “Phone 2” refer to standard handsets with RJ-11 connectors. The handsets are used for verbal and aural confirmations in the test procedures below.
  • Page 58 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Note: TECT3 framer and T8110 chip setup contained in the DS3cfg script is progressively being replaced by test program code. Running the script beforehand is always a safe step, even if the test program Resets these chips and rewrites chip registers.

  • Page 59: Interactive Command Summary

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 4) Run the appTest program, using the following command line: cd /root/Signalogic_2012v4/DirectCore/apps/SigC641x_C667x/appTest #./appTest -m1 -f720 -etmsc64xx.out -cSIGC64XX –t The current version of the test program will initially show a substantial amount of debug information related to hardware and driver initialization, and pause three (3) times for keyboard prompt.
  • Page 60 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Load media Show list of currently active media IDs Operating Mode Control |____ O Exit operating mode control |____ D Enable target voice processing (default = enabled) |____ I...

  • Page 61: Basic Call, Media, And Dtmf Test Procedures

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 4.3.5.5 Basic Call, Media, and DTMF Test Procedures Note: This section includes references to a TDM interface (e.g. CTBus). If no TDM interface is installed or configured, those references may be ignored. References to IP calls, DTMF events, and Media playouts, and interactive command interface remain valid.
  • Page 62 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Channel format can be: where N is a channel number from 0 to 127 and ‘i’ specifies an IP channel (default with no prefix specified is a TDM channel). For an IP channel, no endpoint or T1 stream information should be entered.
  • Page 63 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 The above sequence will set up six (6) calls. In the first call, endpoints are not specified so endpoints 1 and 2 are allocated. In calls 2 and 3, channels are not specified, so channels 2-5 are allocated.
  • Page 64 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 4) A call type of ‘p’ can be used to set up a PTT call. The following entry: p.10.11 will set up a PTT call on channels 10 and 11 (using available endpoints 7 and 11), with the PTT “talker”...
  • Page 65 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 p6.12.e13 will add a third leg to PTT call with Call Id value of 6 (note that the value of 6 was assigned in the ‘p.10.11’ call setup entry in step 4 above, as 6 was the next available Call Id). This call leg will become the second PTT “listener”...
  • Page 66 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 p.14.15 would first establish a PTT call on channels 14 and 15 (using next available endpoints of 15 and 16), with channel 14 (endpoint 15) acting as the talker leg and channel 15 (endpoint 16) the listener leg.
  • Page 67 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 4-21, Setting up an IP call 10) Next press ‘s’ to set up an IP call using the following command line: c.i9.13 After setting up the call, press ‘Enter’, you should see the following screen.
  • Page 68 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 4-22, After setting up a TDM-to-IP call 11) Set up three (3) more IP calls as shown below: c.16.i17 c.18.i19 c.i22.23 12) Now press 'c' key to verify the current call list. The test program should display all currently active calls, as shown in Figure 4-23 below.
  • Page 69 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 4-23, Call display including IP calls 13) Run “RTP Audio” test program on a separate WinXP machine to verify IP calls, using handsets (for TDM side of call) and headsets connected to the WinXP PC sound card (for IP side of call).
  • Page 70 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 3) Only one IP call can be connected to a WinXP machine at one time. This is a limitation of the RTP Audio test program. To test multiple IP calls, use more than one WinXP machine.
  • Page 71 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 4-25, Display after entering Algorithm Mode and toggling AGC Active If a digital scope is connected as shown in “Notes and Equipment” section above, note that effects of AGC are visible on the scope. If AGC is not active, then the output trace (green) will show a flat line (zero pattern) for any unused channels.
  • Page 72 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 4-26, Diagnostic data display The diagnostic data display includes target code “probes” (used for monitoring certain sections of target code), IP call transmit (send) packet values (RTP payload only), and a target channel table, which shows a 32-bit encoded “channel information”...
  • Page 73 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Field Description Encoded Values VAD Score Current VAD score for 0-15, with increasing score indicating higher confidence the channel that voice has been detected DTMF Detect Most recent DTMF tone...
  • Page 74 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Channel Source Voice / data source for None the channel TDM (CTBus, McBSP0) H.110 (McBSP1) Inter-DSP (McBSP1) Notes If handset has a fourth (4 column of keys. A TDM channel connects to one of 28 T1 streams on the DS3/T3 module.
  • Page 75 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 16) Press keypad keys on a connected handset and verify that you see DTMF event display as shown in Figure 4-27 below. Figure 4-27, DTMF event display Note that DTMF events are detected only on channels currently allocated for calls; i.e. if a channel is not connected to a phone, then no DTMF events are detected or displayed.
  • Page 76 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 17) Press the ‘L’ key to load one or more medias. For example load in_begin_low.wav as first media, test.wav as second media, test2_mu.wav as third media, etc. The following waveform file formats are supported: .wav, PCM (16-bit linear)
  • Page 77 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Where id is Media Id, rc is Repeat Count, and ch is Channel on which to play the media. For example, to play Media Id 1 on channel 0, enter at the playout prompt:...
  • Page 78 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 4-29, Media playout event display 21) When media playout is finished, use the handsets to verify calls continue to function correctly. 22) Measuring CPU usage, open another terminal window (use putty again) and connect to the HW400c/2 board.
  • Page 79 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 4-30, Example of running Linux Top process 23) Use ‘t’ key to tear down calls 1-7 and call 10. Note effects on scope if connected. Verify using handsets that no calls are active (per-Channel loopback state is restored).
  • Page 80 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 4-31, Call list after call tear down 80 / 109...
  • Page 81 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 25) Optional Lab equipment Verification. If a digital scope is connected to the CTBus between the DS3 module and SigC641x modules, then the scope should show a display similar to Figure 4-32 below.

  • Page 82: Texas Instruments Tools Installation

    Note 1 This section covers installation of TI Linux command-line tools, which are required for SigC667x systems. For SigC641x systems, TI Code Composer Studio installation is required on a WinXP or Win7/8 system -- see the SigC5x / SigC6x Hardware Reference Guide for more information.
  • Page 83 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 4-33, TI Code Generation Tools download page 83 / 109...

  • Page 84: Ti Bios-Mcsdk Download

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 4.4.2 TI BIOS-MCSDK Download The second step is to download TI’s BIOS-MCSDK, which will download the following components: SYSBIOS (Real-time operating system for TI multicore CPUs) • IPC (Interprocessor Communication) •...
  • Page 85 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 4-34, TI software folder hierarchy, including Code Gen tools, SYSBIOS, IPC, XDCtools, and PDK 85 / 109...

  • Page 86: Ti Sysbios, Ipc, And Xdctools Download

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 4.4.3 TI SYSBIOS, IPC, and XDCtools Download If needed, SYSBIOS, IPC, and XDCtools can be downloaded separately, for example to upgrade one of the components without downloading all of BIOS-MCSDK. To download components separately, go to the following page: http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/sysbios/index.html...

  • Page 87: Rtaf Software Usage

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 4.5 RTAF Software Usage This section covers use of the Real-Time Algorithm Framework (RTAF) software. RTAF software includes the following components and run-time functionality: for TI targets, SYSBIOS configuration, including run-time initialization and memory •...

  • Page 88: Rtaf Peripheral Support

    If present on the hardware 4.5.3 RTAF Development and Host Platform Notes As noted in section 4 above, Software Installation, for SigC667x cards, RTAF software is installed under the mCPU_target folder on Linux systems as shown in Figure 4-35a below.
  • Page 89 RTAF software is not generated or rebuilt on a Linux system. Instead, the software must be maintained on a WinXP or Win7/8 system with Texas Instruments CCS software installed. Conversely, SigC667x RTAF software builds may be handled using CCS software or Texas Instruments command-line code generation tools (TI’s Linux version of CGT).

  • Page 90: Linux Platform Builds

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 2. In Linux systems, RTAF software is stored on the “mCPU_target” subfolder. This naming convention refers to run-time software for multicore CPU or other target hardware; e.g. CIM accelerator, DSP card, video or telecom card, network processing card, neural net card, etc.

  • Page 91: Sigc667X / Sigc641X User Guide, Rev B7 Copyright © Signalogic

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 4. LINKER_INCLUDES are the include directories for the linker process. There are 3 targets used in the makefile under the '# All Target' comment. The first one can be edited to change the platform used by changing the -p parameter.

  • Page 92: Cim Software Installation

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 4.6 CIM Software Installation To install CIM software unzip the sig_sw_host_cim_vNN.rar file. You should see the following Figure 4-36, CIM host software folder hierarchy, after installation 4.6.1 Running User Programs with CIM...

  • Page 93: H264_Encode Demo

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 platform with no optimizations. Allowable PlatformType, AccelType, and CardType parameters are listed below: PlatformType Description Support Status none x86 + Linux x86 + Linux ARM + Linux AccelType...
  • Page 94 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 4-37a, h264_encode CIM build process output display 94 / 109...
  • Page 95 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 4-37b, h264_encode CIM build process output display, cont. 95 / 109...
  • Page 96 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 4-37c, h264_encode CIM build process output display, cont. After the CIM build process completes, the h264_encode executable file will be created, and can be run as a typical Linux program: ./h264_encode...
  • Page 97 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 h264_encode$ ./h264_encode DSInitCores: qwCoreList = 0xff SlotIndx = 0 Card_Type 0x8106 Talker not used DSXInitCard SigC66x ds66xInitCard: InitCardT50 success DSXInitCard Successful! Loading input video .yuv data... Clearing output video mem region...

  • Page 98: Pn4Test Host Program

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 5 pn4Test Host Program Note This section only applies to SigC641x DSP systems. The pn4Test host program controls and tests the McBSP1 and GPIO devices on the selected DSPs.
  • Page 99 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 MCBSP – Test only the serial mode sides of McBSP1 in serial mode UART – Test only the serial mode sides of McBSP1 in UART mode GPIO – Test only the GPIO sides of McBSP1 MCBSP_GPIO –...
  • Page 100 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 After entering the mandatory command line options and running pn4Test, the entered options are echoed back to the terminal display. DSP, FPGA and on-chip memory tests are then run and DSPs are reset.
  • Page 101 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Once the SDRAM tests complete, if the details level is set at 2, FPGA logic versions are displayed followed by physical memory addresses (both on-chip and off-chip memory) of the DSP code variables that pn4Test will read from or write to for various settings and data display.
  • Page 102 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 5-3 shows the data display for UART_GPIO test mode with the details level set to 2. Currently, there is a delay of 40 ms for UART mode before the first data word is sent. If DSP code is changed to remove this delay, errors may be seen on the data words during the first 40 ms of operation depending on when the first and subsequent data words are sent.
  • Page 103 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 5-5 shows the data display for MCBSP_GPIO test mode with the details disabled. Figure 5-5, pn4Test –MMCBSP_GPIO –d0 data display Figure 5-6 shows the data display for GPIO test mode with details level set to 1.

  • Page 104: Pn4Test Theory Of Operation

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 6 pn4Test Theory of Operation Note This section only applies to SigC641x systems. The current implementation of pn4Test runs according to the Rev 2.4a spec shown in Figure 6-1 on the next page.
  • Page 105 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 … … … … … … Figure 6-1, Rev 2.4a Specifications 105 / 109...
  • Page 106 1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 Figure 6-2, Rev 2.4b Specifications 106 / 109...

  • Page 107: Mcbsp Test Mode

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 6.1 MCBSP Test Mode In MCBSP test modes, the McBSPs are initialized to transmit and receive 8-bit words at a frequency of 1 MHz. The last step in initialization for the MCBSP test modes is syncing between group A and group B DSPs.

  • Page 108: Gpio Test Mode

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 6.3 GPIO Test Mode In GPIO only mode, the McBSPs are initialized to transmit and receive at a frequency of 1 MHz. In all GPIO modes, GPIO sampling is done via a timer interrupt which occurs at a frequency of 900 KHz.

  • Page 109: Host Operation

    1/27/15 SigC667x / SigC641x User Guide, Rev B7 Copyright © Signalogic 2012-2014 6.4 Host Operation Once the board and enabled DSPs are reset and initialized, a callback function based on the uNotifyMode flag is registered. The uNotifyMode flag takes values 0-2 and can be modified in the pn4Test source code going into effect once the code is rebuilt.

This manual is also suitable for:

Sigc641x

Table of Contents