Spectrum Digital Inc
Web: http://www.spectrumdigital.com/
Support: mailto:support@spectrumdigital.com
Phone: 281-494-4500
Fax: 281-494-5310
Processor Supported:
TMS320C6455 on TMS320C6455 DSK
Operating Systems Supported:
Windows 2000 with service pack 2
Windows XP
USB Connection:
Version 1.10 or 2.0
Code Composer version supported:
Version 3.2
Product Release 3.0
Release Date July
2006
2.0 Installation
See Quick Start guide shipped with product for step by step
install.
3.0 Some Basics on How it Works
When the DSK is powered up the embedded USB controller will
boot up and wait for enumeration from the host.
Once the host has enumerated, Code Composer can be started. When a USB
device is enumerated it will show up under the Windows Hardware Device Manager. When Code Composer is started the emulation
driver will make contact with the DSK (see led DS201 flash). It will then download the emulation firmware
to the DSK. Once that is complete the
firmware will disconnect from the USB bus and reconnect as an emulator. When the LED DS201 is on solid the USB
controller is disconnected from the USB bus. DS201 will normally be on solid
for ~1 second to meet the USB disconnect reconnect timing. Once connected DS201 will flash during
emulation activity. When you exit Code
Composer the DDB will once again disconnect from the USB bus and reconnect in
boot mode, ready for the next debug session.
The C6455DSK icon is used to load the emulation app then start CCS.
The USB controller is not affected by the DSK reset
push-button. When the DSK is powered on
the USB controller gets a power on reset.
The USB controller does NOT pull a hardware reset on the C6455 processor
or hold the C6455 in reset. This allows the DSK to run standalone.
To use the external emulator JTAG port, power off the DSK,
install the JTAG cable and power the DSK. By default the embedded USB
controller will supply JTAG signals to the C6455. When the external JTAG cable is plugged, in
the JTAG signals are switched asynchronously to the external emulator. This can cause glitches on the C6455 JTAG
signals. With the external emulator is
plugged in when power is off, the DSK will startup in external emulator mode
with clean JTAG signals
You have to be logged on as an administrator to install USB
devices on Windows 2000/XP. Under
Windows each time you move your USB cable to a new port on the same machine
this is a new install. This can be annoying if you move your USB cable around
to different ports. During the install
process you can cycle through installing the DSK on all your USB ports. This "preps" your machine to run
the DSK on any of its USB ports.
4.0 Limitations
4.0.1 Single DSK per PC
Multiple DSKs on one host are NOT
supported.
4.027 SDSsq19464 Admin privileges needed
for Code Composer Studio installation
Release Note
CCS requires access to specific registry entries when installing and using the
tool. In certain installations of CCS, while in user mode, you are prevented
from writing to the registry. The following instructions provide details of how
to install CCS with Administrative privileges and allow write access in the
registry as a user.
Windows NT
The Code Composer Studio
product needs to be installed using an account with Administrator privileges:
1. Log in as an
administrator.
2. Install the product
by running <setup.exe>.
3. If the installation
process prompts for a reboot, the administrator must log in again prior to
first use. This will allow the installation process to update registry settings
after a reboot.
Once this procedure is
complete users belonging to the "Users" group may fully utilize the
Code Composer Studio product.
Windows 2000
Similar to the procedure on
Windows NT, the Code Composer Studio product needs to be installed using an
account with Administrator privileges. If the installation process prompts for
a reboot the administrator must log in again prior to first use. This will
allow the installation process to update registry settings after a reboot.
However, the
"Users" account under Windows 2000 is, by default, significantly more
restricted than a "Users" account under Windows NT. One of the new
restrictions is that the "Users" group has read-only access to all
parts of the registry. During its normal course of operation, Code Composer
Studio reads and writes configuration and session information to the registry.
There are two possible actions that may be taken to allow non-administrator
users to use Code Composer Studio:
1. The administrator may
modify registry permissions for the areas of registry that are used by Code
Composer Studio. The procedure to do this is as follows:
a) Log in as an
administrator.
b) Choose
"Start->Run" from the Windows 2000 Start menu.
c) Type
"regedt32" (not "regedit") to
bring up the Registry Editor.
d) From the
"Window" menu, select "HKEY_LOCAL_MACHINE on the Local
Machine".
e) Expand the
"SOFTWARE" key.
f) Locate and select
the sub-key "GODSP".
g) With
"GODSP" selected, choose "Security Permissions..." from the
menu.
h) In the upper half of
the "Permissions for GODSP" window there will be a list of all the
users and groups that access the key.
i) Select the "Users"
group.
j) In the
"Permissions:" box, locate the item "Full Control" and
check the corresponding box under "Allow".
k) Repeat steps
"e" through "i" for
"HKLM\Software\Texas Instruments."
2. The second option is to
allow users that will be using the Code Composer Studio product access via a
"Power User" account. "Power User" accounts on Windows 2000
provide an access level similar to that of a "User" account on WinNT.