DSignT Support Database - User contributions [en]

JTAG Target Connection Issue

2017-08-23T08:54:31Z

Adolf:

== Problem ==
No target connection with XDS220 ISO.

The VTRef pin (also called TVRef, TVD or VREF) on the JTAG header is used by most emulators to sense and detect the target's I/O voltage.
Texas Instruments target board emulation design guidelines (http://processors.wiki.ti.com/index.php/XDS_Target_Connection_Guide#TVRef_2) recommends to connect VTRef via a 100 ohms current limiting series resistor to the target IO power supply.

The XDS220 ISO however draws more current from the VTRef pin to supply the target side isolation drivers. A 100 ohms series resistor causes too much voltage drop and the XDS220 ISO will fail to connect to the target.

== Solution ==
Replace the 100 ohms resistor on your target board with a 0 ohms resistor or a ferrite bead with low DC resistance for better noise immunity.

[[category:XDS220 ISO USB/Ethernet JTAG Emulator]]

JTAG Target Connection Issue

2017-08-23T08:47:33Z

Adolf:

== Problem ==
No target connection with XDS220 ISO.

The VTRef pin on the JTAG header is used by most emulators to sense and detect the target's I/O voltage.
Texas Instruments target board emulation design guidelines (document sprab21 and http://processors.wiki.ti.com/index.php/XDS_Target_Connection_Guide) recommend to connect VTRef via a 100 ohms current limiting series resistor to the target IO power supply.

The XDS220 ISO however draws more current from the VTRef pin to supply the target side isolation drivers. A 100 ohms series resistor causes too much voltage drop and the XDS220 ISO will fail to connect to the target.

== Solution ==
Replace the 100 ohms resistor on your target board with a 0 ohms resistor or a ferrite bead with low DC resistance for better noise immunity.

[[category:XDS220 ISO USB/Ethernet JTAG Emulator]]

JTAG Target Connection Issue

2017-08-23T08:45:18Z

Adolf: Created page with "== Problem == No target connection with XDS220 ISO. The VTRef pin on the JTAG header is used by most emulators to sense and detect the target's I/O voltage. Texas Instrument..."

== Problem ==
No target connection with XDS220 ISO.

The VTRef pin on the JTAG header is used by most emulators to sense and detect the target's I/O voltage.
Texas Instruments target board emulation design guidelines (document sprab21 and http://processors.wiki.ti.com/index.php/JTAG_Connectors) recommend to connect VTRef via a 100 ohms current limiting series resistor to the target IO power supply.

The XDS220 ISO however draws more current from the VTRef pin to supply the target side isolation drivers. A 100 ohms series resistor causes too much voltage drop and the XDS220 ISO will fail to connect to the target.

== Solution ==
Replace the 100 ohms resistor on your target board with a 0 ohms resistor or a ferrite bead with low DC resistance for better noise immunity.

[[category:XDS220 ISO USB/Ethernet JTAG Emulator]]

Main Page

2017-08-23T08:19:14Z

Adolf:

Category:XDS220 ISO USB/Ethernet JTAG Emulator

2017-08-23T08:17:25Z

Adolf: Created page with "category:Emulator"

[[category:Emulator]]

Downloads

2014-11-04T13:34:17Z

Adolf:

== Downloads and Manuals ==
=== Data Sheets ===
==== D.Module2 DSP Boards ====
* D.Module2.C6657: [http://{{SERVERNAME}}/files/dsignt/media/datasheets/tdd2c6657.pdf tdd2c6657.pdf]

* D.Module2.C6747: [http://{{SERVERNAME}}/files/dsignt/media/datasheets/tdd2c6747.pdf tdd2c6747.pdf]

* D.Module2.DM642: [http://{{SERVERNAME}}/files/dsignt/media/datasheets/tdd2dm642.pdf tdd2dm642.pdf]

* D.Module2.TS203: [http://{{SERVERNAME}}/files/dsignt/media/datasheets/tdd2ts203.pdf tdd2ts203.pdf]

==== Legacy D.Module DSP Boards ====
* D.Module.C6713: [http://{{SERVERNAME}}/files/dsignt/media/datasheets/tdd6713.pdf tdd6713.pdf]

* D.Module.C6203: [http://{{SERVERNAME}}/files/dsignt/media/datasheets/tdd6203.pdf tdd62013.pdf]

* D.Module.VC33: [http://{{SERVERNAME}}/files/dsignt/media/datasheets/tdd33.pdf tdd33.pdf]

* D.Module.21065: [http://{{SERVERNAME}}/files/dsignt/media/datasheets/tdd21065.pdf tdd21065.pdf]

Downloads

2014-11-04T13:13:08Z

Adolf:

== Downloads and Manuals ==
=== Data Sheets ===
==== D.Module2 DSP Boards ====
* D.Module2.C6657: [http://{{SERVERNAME}}/files/dsignt/media/datasheets/tdd2c6657.pdf tdd2c6657.pdf]

* D.Module2.C6747: [http://{{SERVERNAME}}/files/dsignt/media/datasheets/tdd2c6747.pdf tdd2c6747.pdf]

* D.Module2.DM642: [http://{{SERVERNAME}}/files/dsignt/media/datasheets/tdd2dm642.pdf tdd2dm642.pdf]

* D.Module2.TS203: http://{{SERVERNAME}}/files/dsignt/media/datasheets/tdd2ts203.pdf tdd2ts203.pdf]

==== Legacy D.Module DSP Boards ====
* D.Module.C6713: [http://{{SERVERNAME}}/files/dsignt/media/datasheets/tdd6713.pdf tdd6713.pdf]

* D.Module.C6203: [http://{{SERVERNAME}}/files/dsignt/media/datasheets/tdd6203.pdf tdd62013.pdf]

* D.Module.VC33: [http://{{SERVERNAME}}/files/dsignt/media/datasheets/tdd33.pdf tdd33.pdf]

* D.Module.21065: [http://{{SERVERNAME}}/files/dsignt/media/datasheets/tdd21065.pdf tdd21065.pdf]

Downloads

2014-11-04T13:11:58Z

Adolf:

== Downloads and Manuals ==
=== Data Sheets ===
==== D.Module2 DSP Boards ====
* D.Module2.C6657: [http://{{SERVERNAME}}/files/dsignt/media/datasheets/tdd2c6657.pdf tdd2c6657.pdf]

* D.Module2.C6747: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd2c6747.pdf tdd2c6747.pdf]

* D.Module2.DM642: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd2dm642.pdf tdd2dm642.pdf]

* D.Module2.TS203: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd2ts203.pdf tdd2ts203.pdf]

==== Legacy D.Module DSP Boards ====
* D.Module.C6713: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd6713.pdf tdd6713.pdf]

* D.Module.C6203: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd6203.pdf tdd62013.pdf]

* D.Module.VC33: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd33.pdf tdd33.pdf]

* D.Module.21065: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd21065.pdf tdd21065.pdf]

Downloads

2014-11-04T13:10:34Z

Adolf:

== Downloads and Manuals ==
=== Data Sheets ===
==== D.Module2 DSP Boards ====
* D.Module2.C6657: [http://files/dsignt/media/datasheets/tdd2c6657.pdf tdd2c6657.pdf]

* D.Module2.C6747: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd2c6747.pdf tdd2c6747.pdf]

* D.Module2.DM642: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd2dm642.pdf tdd2dm642.pdf]

* D.Module2.TS203: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd2ts203.pdf tdd2ts203.pdf]

==== Legacy D.Module DSP Boards ====
* D.Module.C6713: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd6713.pdf tdd6713.pdf]

* D.Module.C6203: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd6203.pdf tdd62013.pdf]

* D.Module.VC33: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd33.pdf tdd33.pdf]

* D.Module.21065: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd21065.pdf tdd21065.pdf]

Downloads

2014-11-04T13:01:18Z

Adolf:

== Downloads and Manuals ==
=== Data Sheets ===
==== D.Module2 DSP Boards ====
* D.Module2.C6657: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd2c6657.pdf tdd2c6657.pdf]

* D.Module2.C6747: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd2c6747.pdf tdd2c6747.pdf]

* D.Module2.DM642: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd2dm642.pdf tdd2dm642.pdf]

* D.Module2.TS203: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd2ts203.pdf tdd2ts203.pdf]

==== Legacy D.Module DSP Boards ====
* D.Module.C6713: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd6713.pdf tdd6713.pdf]

* D.Module.C6203: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd6203.pdf tdd62013.pdf]

* D.Module.VC33: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd33.pdf tdd33.pdf]

* D.Module.21065: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd21065.pdf tdd21065.pdf]

Downloads

2014-11-04T12:55:46Z

Adolf:

== Downloads and Manuals ==
=== Data Sheets ===
==== DSP Boards ====
* D.Module2.C6657: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd2c6657.pdf tdd2c6657.pdf]

* D.Module2.C6747: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd2c6747.pdf tdd2c6747.pdf]

* D.Module2.DM642: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd2dm642.pdf tdd2dm642.pdf]

* D.Module2.TS203: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd2ts203.pdf tdd2ts203.pdf]

Downloads

2014-11-04T12:52:55Z

Adolf:

== Downloads and Manuals ==
=== Data Sheets ===
==== DSP Boards ====
D.Module2.C6657: [http://p523118.webspaceconfig.de/files/dsignt/media/datasheets/tdd2c6657.pdf tdd2c6657.pdf]

Downloads

2014-11-04T12:52:03Z

Adolf:

== Downloads and Manuals ==
=== Data Sheets ===
==== DSP Boards ====
D.Module2.C6657: [http://./files/dsignt/media/datasheets/tdd2c6657.pdf tdd2c6657.pdf]

Downloads

2014-11-04T12:50:58Z

Adolf:

== Downloads and Manuals ==
=== Data Sheets ===
==== DSP Boards ====
D.Module2.C6657: [http:///files/dsignt/media/datasheets/tdd2c6657.pdf tdd2c6657.pdf]

Downloads

2014-11-04T12:50:32Z

Adolf:

== Downloads and Manuals ==
=== Data Sheets ===
==== DSP Boards ====
D.Module2.C6657: [http://files/dsignt/media/datasheets/tdd2c6657.pdf tdd2c6657.pdf]

Category:D.Module

2011-07-04T09:12:55Z

Adolf:

== D.Module and D.Module2 related problems ==

*[[:Category:D.Module.C6203|D.Module.C6203]]
*[[:Category:D.Module.C6713|D.Module.C6713]]
*[[:Category:D.Module.C6747|D.Module.C6747]]
*[[:Category:D.Module.VC33|D.Module.VC33]]
*[[:Category:D.Module2.TS203|D.Module2.TS203]]

*[[:Category:D.Module.ADDA16|D.Module.ADDA16]]

[[category:Hardware]]

Category:D.Module.ADDA16

2011-07-04T09:12:20Z

Adolf: Created page with "Category:D.Module"

[[Category:D.Module]]

Cascading two ADDA16 boards

2011-07-04T09:10:29Z

Adolf:

===Problem===
Cascading two ADDA16 boards for an 8-channel data acquisition system

===Solution===
1. Both boards need to be configured to different I/O addresses. Leave the first board in the default factory setting and close jumper JPA4 on the second board.

2. The default header file adda16.h does not provide macros for a dual configuration. Create a new header file adda16_dual.h for use in your project:
<syntaxhighlight lang="c">
#define ADDA16_1_OFFSET 0x000000
#define ADDA16_2_OFFSET 0x000040

#define ADDA16_1_BASE (IOSEL_BASE + ADDA16_1_OFFSET)
#define ADDA16_2_BASE (IOSEL_BASE + ADDA16_2_OFFSET)

typedef struct
{
volatile short rsvd0;
volatile short ch0;
volatile short rsvd1;
volatile short ch1;
volatile short rsvd2;
volatile short ch2;
volatile short rsvd3;
volatile short ch3;
volatile short rsvd4;
volatile unsigned short fs;
volatile short rsvd5;
volatile unsigned short cfg;
} adda16_type;

#define ADDA16_1 ((adda16_type *) ((unsigned int *)ADDA16_1_BASE))
#define ADDA16_2 ((adda16_type *) ((unsigned int *)ADDA16_2_BASE))

/***********************************************************************
Macros to read ADC and write DAC:
***********************************************************************/
#define ADDA16_1_READ_ADC(ch) (*(volatile short*)(ADDA16_1_BASE+2+(ch<<2)))
#define ADDA16_1_WRITE_DAC(ch,val) (*(volatile short*)(ADDA16_1_BASE+2+(ch<<2)) = val)
#define ADDA16_2_READ_ADC(ch) (*(volatile short*)(ADDA16_2_BASE+2+(ch<<2)))
#define ADDA16_2_WRITE_DAC(ch,val) (*(volatile short*)(ADDA16_2_BASE+2+(ch<<2)) = val)

</syntaxhighlight>

the remainder of the header file is identical to adda16.h:

<syntaxhighlight lang="c">
/***********************************************************************

ADDA16 Sampling Frequency Register

***********************************************************************/
/* common sampling frequencies */
#define ADDA16_FS250 0x000F
#define ADDA16_FS200 0x0013
#define ADDA16_FS160 0x0018
#define ADDA16_FS120 0x001F
#define ADDA16_FS100 0x0027
#define ADDA16_FS80 0x0031
#define ADDA16_FS67 0x003B
#define ADDA16_FS50 0x004F
#define ADDA16_FS33 0x0077
#define ADDA16_FS25 0x009F
#define ADDA16_FS20 0x00C7
#define ADDA16_FS16 0x00F9
#define ADDA16_FSEXT 0x0000

/* this macro can be used for any integer sampling frequency from 15625 Hz to 250 kHz */
#define ADDA16_FS(x) ((4000000/(int)x)-1)

/***********************************************************************

ADDA16 Configuration Register

***********************************************************************/
#define ADDA16_DAC_READY 0x0080 /* read : DAC ready for new transfer */
#define ADDA16_EXTCLK_ON 0x0080 /* write: turn on EXTCLK output */

#define ADDA16_INT1DAC 0x0040 /* map DAC to nINT1 */
#define ADDA16_INT1ADC 0x0020 /* map ADC to nINT1 */
#define ADDA16_INT1FS 0x0060 /* map sampling frequency to nINT1 */
#define ADDA16_INT0DAC 0x0010 /* map DAC to nINT0 */
#define ADDA16_INT0ADC 0x0008 /* map ADC to nINT0 */
#define ADDA16_INT0FS 0x0018 /* map sampling frequency to nINT0 */

#define ADDA16_LDAC_ANY 0x0000 /* update DACs after any DAC write */
#define ADDA16_LDAC_2 0x0001 /* update DACs after writing to DAC 2 */
#define ADDA16_LDAC_3 0x0002 /* update DACs after writing to DAC 3 */
#define ADDA16_LDAC_4 0x0003 /* update DACs after writing to DAC 4 */
#define ADDA16_LDAC_FS 0x0004 /* use ADC sampling frequency to update DACs */

</syntaxhighlight>

3. The ADDA16 is shipped with some spare D.Module connectors. Press two of these connector pins into locations C22 and C23 on both ADDA16 boards.

4. To use internal sampling clock configure the first board to generate the sampling clock and enable its EXTCLK_OUT output. The second board is configured to external sampling clock. To feed the clock output from board1 to the input of board2 connects pins C22 to pin C23:

<syntaxhighlight lang="c">
ADDA16_1->fs = ADDA16_FS(125000);
ADDA16_1->cfg = (ADDA16_INT0ADC | ADDA16_EXTCLK_ON | ADDA16_LDAC_FS);
ADDA16_2->fs = ADDA16_FSEXT;
ADDA16_2->cfg = ADDA16_LDAC_FS;
</syntaxhighlight>

5. to use an external sampling clock for both boards, feed this clock to EXTCLK_IN (C22) of both boards. The solftware configuration is:
<syntaxhighlight lang="c">
ADDA16_1->fs = ADDA16_FSEXT;
ADDA16_1->cfg = (ADDA16_INT0ADC | ADDA16_LDAC_FS);
ADDA16_2->fs = ADDA16_FSEXT;
ADDA16_2->cfg = ADDA16_LDAC_FS;
</syntaxhighlight>

[[category:D.Module.ADDA16]]

Main Page

2011-03-02T12:56:58Z

Adolf:

Main Page

2011-03-02T12:53:14Z

Adolf:

Main Page

2011-03-02T12:52:38Z

Adolf:

Category:DSP

2011-03-02T12:51:27Z

Adolf: Created page with "category:software"

[[category:software]]

Install C3x CodeComposer + XDS510USB under Windows 7

2011-02-25T23:53:21Z

Adolf:

=== Problem ===
CC- and emulator setup are incompatible with Windows 7

How to install and setup C3x CodeComposer and XDS510USB under Windows 7

=== Solution ===
:# Login as administrator
:# "run as administrator" ccs\setup.exe (standard setup.exe from root or autostart won't work)
:# ignore known compatibility problems with Visual Studio and Windows 7
:# install program
:# restart computer
:# login as administrator
:# install CC Service Pack 2 ("run as administrator")
:# restart computer
:# login as administrator
:# The following steps are required to install a compatible Windows driver for the XDS510USB emulator. The XDS510USB drivers for Code Composer 3x/4x cannot be installed on Windows-7
:#* load and unpack [http://support.spectrumdigital.com/ccs33/Release-30330/setupCCSPlatinum_v30330.ZIP SetupCCSPlatinum_V30330.zip] from SpectrumDigital homepage
:#* "run as administrator" SetupCCSPlatinum_V30330.exe
:#* choose custom installation
:#* installation path must be the same as the CC 3x installation directory (default c:\tic3x4x )
:#* connect XDS510USB emulator to a USB port on your PC
:#* choose manual driver installation, USB driver is located in c:\tic3x4x\specdig\xds510_win64
:# "run as administrator" c:\tic3x4x\specdig\sdconfig\SdConfig.exe
:# click the red 'R' in the toolbar for emulator reset. The emulator should now be enumerated (small enumeration window on the bottom right corner occurrs) and be resetted
:# Since the C3x/4x driver installation is incompatible with Windows-7, two files must be copied manually from an existing CC C3x/4x installation:
:#* copy sdgovc3xusb.drv to directory c:\tic3x4x\drivers
:#* copy vc33_xds510usb.ccs to directory c:\tic3x4x\drivers\import
:# "run as administrator" c:\tic3x4x\cc\bin\cc_setup.exe
:# import vc33_xds510usb.ccs, quit and save
:# "run as administrator" c:\tic3x4x\cc\bin\cc_app.exe

[[category:C3x4x]]
[[category:D.Module.VC33]]

MediaWiki:Sidebar

2011-02-25T15:49:24Z

Adolf:

* navigation
** mainpage|mainpage-description
** Special:PopularPages|Popular pages
** recentchanges-url|recentchanges
** Special:AllPages|All pages
* SEARCH

Template:DignTSidebar

2011-02-25T15:48:28Z

Adolf: Created page with "* navigation ** mainpage|mainpage-description ** Special:PopularPages|Popular pages ** recentchanges-url|recentchanges ** Special:AllPages|All pages * Usage ** Special:Categories..."

MediaWiki:Sidebar

2011-02-24T13:29:17Z

Adolf:

DSignT Support Database:General disclaimer

2011-02-22T16:08:02Z

Adolf:

D.SignT GmbH & Co. KG will not guarantee the correctness and completeness of the information offered on this website, or any referred external website.

D.SignT is in no case responsible for the content of linked websites.

<hr>

Die D.SignT GmbH & Co. KG übernimmt keine Gewährleistung für die Vollständigkeit und Korrektheit der auf dieser Internetpräsenz bereitgestellten Informationen.

Links zu externen Webseiten wurden einmalig sorgfältig geprüft. D.SignT trägt keinerlei Verantwortung für den Inhalt verlinkter Seiten.

DSignT Support Database:About

2011-02-22T16:05:37Z

Adolf: Created page with "[http://www.dsignt.de/impressum.html Impressum/Imprint]"

[http://www.dsignt.de/impressum.html Impressum/Imprint]

DSignT Support Database:General disclaimer

2011-02-22T16:03:42Z

Adolf: Created page with "D.SignT GmbH & Co. KG will not guarantee the correctness and completeness of the information offered on this website, or any referred external website. D.SignT is in no case res..."

DSignT Support Database:Privacy policy

2011-02-22T16:02:28Z

Adolf: Created page with "D.SignT respects your privacy. No cookies or other technologies are used to track website visitors. Any information left to us, either via forms on this website or by e-mail, i..."

D.SignT respects your privacy. No cookies or other technologies are used to track website visitors.

Any information left to us, either via forms on this website or by e-mail, is treated confidential and is not made available to thirds. We will collect and store this information for internal use only to provide the requested services and information.

Category:C3x4x

2011-02-22T13:56:13Z

Adolf: Created page with "[[category:Code Generation Tools]"

[[category:Code Generation Tools]

Main Page

2011-02-22T13:48:15Z

Adolf:

Main Page

2011-02-22T13:48:01Z

Adolf:

CCS4 open old CCS3 DSP/BIOS project

2011-02-22T13:30:51Z

Adolf:

=== Problem ===
after opening old DSP/BIOS project CCS4 fails to link due to several errors like:<br>
* run placement fails for object ".abc"
* absolute symbol "XYZ" being redefined

=== Solution ===
CCS4 already uses all defined sections from database without generating a linker command file. Old DSP/BIOS projects contain automatically generated linker command files. These *.cmd files are imported by CCS4 to the current project and linked again to the current executable. Exclude these files from build for proper link process.

[[Category:CCS4 Usage]]

CCS4 install checklist

2011-02-22T13:29:11Z

Adolf:

== CCS4 Installation Checklist ==

* only install from admin account, runas is not sufficient: some items will not be installed properly

[[Category:CCS4 Install]]

D6713 HPI Boot

2011-02-22T13:22:00Z

Adolf:

=== Question ===
Is it possible to boot the D.Module over the HPI? The D.Module user guide makes no mention of this. The DSP chip itself supports it, but D.SignT have set it up to boot from the module’s onboard ROM. There is no obvious jumper on the D.Module to change that behaviour. There are some jumpers but they are all unmarked.

=== Solution 1 ===
The board jumper settings are shown in the D.Module.C6713 User's Guide, page 9. To select HPI boot mode:
* JPH1 must be set to position 'b' (HPI)
* JPH2 must be closed (HPI bus enabled)
* JPBOOT must be set to position 'a' (Host Interface)

''Notes for HPI boot mode:''
* The D.Module BIOS functions are not available.
* All initializations (EMIF, PLL etc.) must be done manually
* PRGIO[31:16] cannot be used.
* McASP cannot be used

=== Solution 2 ===
* Leave the module configured to Flash Boot. Write a small program which configures and initializes the D.Module and then branches into a loop which waits for a DSP interrupt (poll the HPIC register). Store this program in Flash Memory.
* The host processor can now load code and data sections to the 6713 module. If finished, the host writes the program entry point address to a dedicated memory address and issues a DSP interrupt by setting the DSPINT bit in HPIC.
* The DSP now exits the "wait for DSPINT" loop, reads the entry point, and executes a branch to the entry point.
* Advantage: the DSP and its peripherals are readily configured, all memory (e.g. SDRAM) is accessible by the host without special initialization. All BIOS functions are available.
* Disadvantage: a small portion of the memory is used for the "wait for DSPINT" program and must not be overwritten by the host.

=== Additional Tags ===
Host Port Bootloader

[[Category:D.Module.C6713]]
[[Category:HPI]]

D2ts203 timer

2011-02-17T23:29:52Z

Adolf:

=== Question ===
I want to trigger an event (data acquisition), using one of the I/O coming from the TS203, at as precise a time interval (maybe 100nS or 1mS) as possible

=== Solution ===
Use the TS203 timer TMR0 to generate periodic pulses or clocks. The timer.c program from the support software can be used as a basis.

The DSP timer output can be routed to one of the GPIO[3:0] pins on the BUS-1 and BUS-2 connectors. The DSP generates only a narrow pulse each time the timer expires. You can select either the direct TMR0E output (pulse), or the output of a toggle-flipflop driven by TMR0E (clock). The toggle-flipflop will divide the timer output by 2 and provide 50% duty cycle.

<syntaxhighlight lang="c">
DM2_gpioMap (DM2_GPIO_TIMERPULSE, 3); // TMR0E -> GPIO3
DM2_gpioMap (DM2_GPIO_TIMERCLK, 3); // TMR0E -> toggle-ff -> GPIO3
</syntaxhighlight>

The timer input clock is SYSCLK. To initialize and start the timer use:
<syntaxhighlight lang="c">
DM2_timerStart (0, DM2_dspGetClock()/output_frequency_in_hz);
</syntaxhighlight>

If the toggle-flipflop output is used:
<syntaxhighlight lang="c">
DM2_timerStart (0, DM2_dspGetClock()/(2*output_frequency_in_hz));
</syntaxhighlight>

A timer interrupt is installed with
<syntaxhighlight lang="c">
int temp;

interruptf(SIGTIMER0LP, timer_int);
temp = __builtin_sysreg_read(__IMASKL);
temp = temp | INT_TIMER0L;
__builtin_sysreg_write(__IMASKL, temp);
temp = __builtin_sysreg_read(__SQCTL);
temp = temp | SQCTL_GIE;
__builtin_sysreg_write(__SQCTL, temp);
</syntaxhighlight>

The interrupt function will be called periodically, but with some jitter: the interrupt code execution is delayed until the current instruction has completed. If this instruction accesses external memory, or if a DRAM refresh cycle is in progress, the interrupt will be delayed. Therefore we do not recommend to toggle an output "manually" in the interrupt service function. For lowest jitter always use the timer output directly.

[[Category:D.Module2.TS203]]
[[Category:Timer]]

Category:Emulator

2011-02-15T11:31:09Z

Adolf:

Emulator issues
[[Category: Installation]]

Category:Emulator

2011-02-15T11:30:10Z

Adolf:

Emulator issues
[[Category: Installation]]
[[Category: SDFlash]]

CCS4 C6713 Debug Target Connection

2011-02-15T11:26:17Z

Adolf:

=== Problem ===
When creating a new Target Connection the TMS320C6713 does not appear in the device list, only a DSK6713 is displayed.

=== Solution ===
The TMS320C6713 must be added manually:

# select "New Target Connection" from menue "Target"
# enter a name and select the destination of the ccxml file
# select your emulator hardware from "General" - "Connection"
# do not select a device in "General" - "Device"
# click the link "Target Configuration" in "Advanced"
# select your emulator in "All Connections"
# click the "Add" Button
# a new window will open, select the "CPU" tab
# select the "C671x" and click "Finish"
# back in "Advanced" select the initialization script (GEL-file)
# Save the configuration

=== Additional Tags ===
migration CCS3 emulation gel

[[category:CCS4 Usage]]
[[category:D.Module.C6713]]

Category:CCS4

2011-02-10T13:44:11Z

Adolf:

== Code Composer Studio 4 related problems ==

*[[:Category:CCS4 Install|Installation]]
*[[:Category:CCS4 Usage|Usage]]
*[[:Category:CCS4 Updates|Updates]]
*[[:Category:CCS4 License|License]]

[[category:Code Generation Tools]]

Category:Custom Designs

2011-02-10T13:43:30Z

Adolf:

== Custom design issues ==

[[category:Hardware]]

Category:D.Module

2011-02-10T13:43:05Z

Adolf:

Template:Solution no

2011-02-10T10:26:41Z

Adolf:

{{no|{{{1}}}}}

Template:Status no

2011-02-10T10:25:34Z

Adolf: Created page with "{{no|{{{1}}}}}"

{{no|{{{1}}}}}

Template:Status yes

2011-02-10T10:23:51Z

Adolf:

{{yes|{{{1}}}}}

Template:Solution yes

2011-02-10T10:23:03Z

Adolf:

{{yes|{{{1}}}}}

Template:Solution yes

2011-02-10T10:21:28Z

Adolf: Created page with "{{yes}}"

Template:Status yes

2011-02-10T10:20:58Z

Adolf: Created page with "{{yes}}"

Category:Timer

2011-02-10T10:13:58Z

Adolf: Replaced content with "Category:D.Module"

[[Category:D.Module]]