Code Composer Forum - Recent Threads

How to indicate the DSP which files must be processed with the loaded program?

Daniel GLG — Sat, 18 May 2013 23:33:09 GMT

Hi members,

I work with: CCSv5.4, the DM6437 EVM, a Blackhawck emulator and video coding standards. I read the documentation provided by the wiki and searched also information within the forum, but my problem remains unresolved. I would like that someone tells me the procedure or points me the right direction (for example, indicating meaningful examples and documentation). My problem may be extrapolated to other areas different from video coding, it is the following:

The program to load on the DSP (a video decoder) has several arguments, one is for the video sequence to decode. Because this decoder have to be tested again many sequences, I would like to create a script to automate the test. With the documentation about DSS, I was not able to know how to indicate the DSP which video sequences must be tested. In other words, how I could tell the target that the program "decoder.out" must run the batch of sequences? (Of course, in an efficient way, for example in a script; not by coding in the decoder code the path to the sequences).

Thanks in advance.

MSP430WARE update to CCSv5.3 unsuccessful

Michael Jordan — Sat, 18 May 2013 15:38:38 GMT

Files attached

Evaluation Version of CCS5 compatibility with MSP430F5172

Jim Taylor99524 — Sat, 18 May 2013 18:54:40 GMT

I have an application that I used the F5151 for and the free code-linited version of CCS5 worked fine for that. I switched over to the F5172 due to its easy availablity and now CCS5 "coughs" at this saying chip not recognized or authorized. So this maybe due to the F5172's 32K program memory which exceeds the 16K code limit? My application program size is only 8K. My CCS5 version is 5.1.1.00031 and am using the Launchpad and Spy-Bi-Wire to program.

Error installing code composer studio 5.4

rswl88 — Sat, 18 May 2013 07:38:05 GMT

I keep getting the following error while installing code composer studio.

Antivirus is disabled.

I have tried both the offline and online installer several times. Always getting the exact same error. This rules out the fact that the download is corrupted,

Attached is my InstallJammer Registry folder.

(Please visit the site to view this file)

Unable to add discovered products from MCSDK 02_01_02_06 to CCS V5.4

Mehly — Fri, 17 May 2013 13:24:44 GMT

Hi,

i'm unable to add discovered products from mcsdk to new CCS v5.4 version.

- Ubuntu 12.04 (64Bit) - (CCS v5.3 is running without problems)

Who can help ??

CCS 5.3.0, very slow flashing when going into debug mode

Davor — Wed, 09 Jan 2013 14:33:23 GMT

CCS 5.3.0 - clean install, Windows 7, 64bit

Spectrum Digital XDS510LC

F28335 target.

When going into the debug mode the flashing takes very long time in total.

After each section there is a long pause. Additionally, the programming pauses approx every 32kb within each section. While pausing, I see no USB acitvity blinking on the emulator.

Any ideas?

i can't build a new ccs project at v5.4

M.Hamza FADIL — Fri, 17 May 2013 22:44:37 GMT

Hi,

I'm new at code composer studio. my problem is when i click 'file>new>' i see only c++/c project, cant see the css project. And there is no css project option. where do i fail? Did i install it in wrong way? or Did i download the wrong version ? thanks for help.

Regards

Debug CM3 core when emulator is suspended

Yogavanan Mathivanan — Thu, 16 May 2013 06:11:30 GMT

Hi,

In 3.2 TI SDK kernel once MPU is suspended we are not able to connect the emulator to the CM3 core. Is this an expected behavior or we need to change any settings in the CCS debugger ? We would like to debug how CM3 core handles the GPIO0 interrupt and wakes up the MPU.

Incase we cannot connect debugger to CM3 core when MPU is suspended. Can we driver UART0 directly from CM3 core to print debug messages?

Please find the CCS error message mentioned below,

CS_DAP_M3: Error: (Error -275 @ 0xFFFFFEED) The attempt to poll a target device exceeded its timeout limit. The utility or debugger has requested that a target device be repeatedly accessed for a specific data or status value. This has failed because the built-in limit for the maximum number of attempts when polling the JTAG scan-path has been exceeded. (Emulation package 5.0.623.0)

M3_wakeupSS_0: Error: (Error -1045 @ 0xFFFFFEED) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Emulation package 5.0.623.0)
CS_DAP_M3: Error: (Error -5002 @ 0xFFFFEC76) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.0.623.0)
M3_wakeupSS_0: Trouble Halting Target CPU: (Error -1044 @ 0xFFFFEC76) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Emulation package 5.0.623.0)

Regards

Yogavanan M

CCSv5.4 how to move/copy a Terminal from one Perspective to another?

RandyP — Wed, 08 May 2013 22:18:00 GMT

It is very awesome to have the Terminal feature in CCS. So when I recently installed CCSv5.4.0.00091, the first thing I did was open a couple of Terminal Windows on /dev/ttyUSB0 and /dev/ttyUSB1. Perfection! Running under Ubuntu 12.04LTS, native, not a virtual window.

Then I launched my Target Configuration which switched me to the CCS Debug Perspective, and I realized my two Terminal Windows did not come over automatically.

Is there a way to drag those windows from one Perspective to another?

Oddly, I was able to create a new Terminal Window in the CCS Debug Perspective for USB0, but it would not let me create one for USB1 until I closed the Terminal Window in the CCS Edit Perspective.

Regards,
RandyP

Problems connecting BH560USBm emulator with CCS v5.2.1.00018 on custom board with 20 C6678 chips

Aamir Husain — Fri, 17 May 2013 23:05:40 GMT

I have a custom board from a vendor. The board has 20 TI c6678 chips on it and it has 10 of them each accessible through two JTAG pin connections on the board. I am using windows XP and the TI Code composer studio version is 5.2.1.00018. My emulator is a BH 560USBm and I have it connected correctly to the board and have it powered up (checks with troubleshooting guide on Blackhawk webpage). It has also enumerated correctly as I can run device manager on my PC and it shows the correct icons and information. I then managed to go to the ccsv5\cs_base\emulation\Blackhawk\Utility\BHProbe.2\ and run the BHprobe_USB560m dos batch file. Results are below and were successful. I also ran the \Blackhawk\Utility\BHDetect and the output is below – again results seem successful. I then opened up CCS studio and View-Target configuration and created a new connection and selected BH 560USBm. I then added 10 DSP c6678 chips each showing 8 cores. My ccxml file is enclosed. It is very similar to the ccxml file I obtained from the board manufacturer except they were using a 560v2 spectrum digital emulator. I then used the test connection on the CCS studio v5.2.1 View-Target Configuration window and the results are enclosed with errors. I did try to connect to the target but got an error which is to be expected. Can you please provide some insight into what could be wrong. I am unable to attach the ccxml file as e2e does not allow for it to be attached. I can provide it offline if need be.

Thanks, Aamir

Output of BHProbe_USB560m batch file run in DOS

16/05/2013-15:07:40.65

****************************************************************************************************

TEST 1 - RESET

****************************************************************************************************

**************************************************

BHProbe 5.01: Blackhawk USB560m JTAG Emulator

**************************************************

16/05/2013-15:07:40.68

bin\XDSProbe.exe -v -F BH560USBm.out -p0x0 -r -o log\BHprobe_USB560m.log

-----[Print the reset-command software log-file]-----------------------------

This utility has selected an XDS560 class product.

This utility will load the program 'BH560USBm.out'.

This utility will operate on port address '0'.

The controller does use a programmable FPGA.

The old VHDL code has a version number of '1544' (0x0608).

The new VHDL code has a version number of '1544' (0x0608).

The emulator program is named 'BH560USBm.out'.

The emulator program is version '35.24.0.3'.

The controller has a version number of '4' (0x0004).

The controller has an insertion length of '0' (0x0000).

The cable+pod has a version number of '2' (0x0002).

The cable+pod has a capability number of '0' (0x0000).

The local memory has a base address of '0' (0x000000).

The local memory has a word capacity of '32768' (0x008000).

This utility will now attempt to reset the controller.

This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.

The software is configured to use all Nano-TBC VHDL features.

The controller type is the Nano-TBC VHDL.

The connection type is a 560-class revision-B fixed-use old-PLL cable.

The controller will be software reset via its configure register.

The controller will use rising-edge timing on output pins.

The controller may use rising edge timing on input pins.

The controller has a logic ONE on its EMU[0] input pin.

The controller has a logic ONE on its EMU[1] input pin.

The scan-path link-delay has been set to exactly '3' (0x0003).

The support logic has not previously detected a power-loss.

Done.

****************************************************************************************************

TEST 2 - SCAN

****************************************************************************************************

**************************************************

BHProbe 5.01: Blackhawk USB560m JTAG Emulator

**************************************************

16/05/2013-15:07:41.75

bin\XDSProbe.exe -v -F BH560USBm.out -p0x0 -i -o log\BHprobe_USB560m.log

-----[Print the controller-open software log-file]---------------------------

This utility has selected an XDS560 class product.

This utility will load the program 'BH560USBm.out'.

This utility will operate on port address '0'.

The controller does use a programmable FPGA.

The emulator program is named 'BH560USBm.out'.

The emulator program is version '35.24.0.3'.

The controller has a version number of '4' (0x0004).

The controller has an insertion length of '0' (0x0000).

The cable+pod has a version number of '2' (0x0002).

The cable+pod has a capability number of '0' (0x0000).

The local memory has a base address of '0' (0x000000).

The local memory has a word capacity of '32768' (0x008000).

-----[Perform the standard path-length test on the JTAG IR and DR]-----------

This path-length test uses blocks of 512 32-bit words.

The test for the JTAG IR instruction path-length succeeded.

The JTAG IR instruction path-length is 60 bits.

The test for the JTAG DR bypass path-length succeeded.

The JTAG DR bypass path-length is 10 bits.

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 512 32-bit words.

This test will be applied just once.

Do a test using 0xFFFFFFFF.

Scan tests: 1, skipped: 0, failed: 0

Do a test using 0x00000000.

Scan tests: 2, skipped: 0, failed: 0

Do a test using 0xFE03E0E2.

Scan tests: 3, skipped: 0, failed: 0

Do a test using 0x01FC1F1D.

Scan tests: 4, skipped: 0, failed: 0

Do a test using 0x5533CCAA.

Scan tests: 5, skipped: 0, failed: 0

Do a test using 0xAACC3355.

Scan tests: 6, skipped: 0, failed: 0

All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 512 32-bit words.

This test will be applied just once.

Do a test using 0xFFFFFFFF.

Scan tests: 1, skipped: 0, failed: 0

Do a test using 0x00000000.

Scan tests: 2, skipped: 0, failed: 0

Do a test using 0xFE03E0E2.

Scan tests: 3, skipped: 0, failed: 0

Do a test using 0x01FC1F1D.

Scan tests: 4, skipped: 0, failed: 0

Do a test using 0x5533CCAA.

Scan tests: 5, skipped: 0, failed: 0

Do a test using 0xAACC3355.

Scan tests: 6, skipped: 0, failed: 0

All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

Done.

****************************************************************************************************

TEST 3 - SCAN2

****************************************************************************************************

**************************************************

BHProbe 5.01: Blackhawk USB560m JTAG Emulator

**************************************************

16/05/2013-15:07:45.00

bin\XDSProbe.exe -v -f bin\bh-noscantest.cfg -F BH560USBm.out -p0x0 -i -o log\BHprobe_USB560m.log

-----[Print the controller-open software log-file]---------------------------

This utility has selected an XDS560 class product.

This utility will load the program 'BH560USBm.out'.

This utility will operate on port address '0'.

The controller does use a programmable FPGA.

The emulator program is named 'BH560USBm.out'.

The emulator program is version '35.24.0.3'.

The controller has a version number of '4' (0x0004).

The controller has an insertion length of '0' (0x0000).

The cable+pod has a version number of '2' (0x0002).

The cable+pod has a capability number of '0' (0x0000).

The local memory has a base address of '0' (0x000000).

The local memory has a word capacity of '32768' (0x008000).

-----[Perform the standard path-length test on the JTAG IR and DR]-----------

This path-length test uses blocks of 512 32-bit words.

The test for the JTAG IR instruction path-length succeeded.

The JTAG IR instruction path-length is 60 bits.

The test for the JTAG DR bypass path-length succeeded.

The JTAG DR bypass path-length is 10 bits.

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 512 32-bit words.

This test will be applied just once.

Do a test using 0xFFFFFFFF.

Scan tests: 1, skipped: 0, failed: 0

Do a test using 0x00000000.

Scan tests: 2, skipped: 0, failed: 0

Do a test using 0xFE03E0E2.

Scan tests: 3, skipped: 0, failed: 0

Do a test using 0x01FC1F1D.

Scan tests: 4, skipped: 0, failed: 0

Do a test using 0x5533CCAA.

Scan tests: 5, skipped: 0, failed: 0

Do a test using 0xAACC3355.

Scan tests: 6, skipped: 0, failed: 0

All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 512 32-bit words.

This test will be applied just once.

Do a test using 0xFFFFFFFF.

Scan tests: 1, skipped: 0, failed: 0

Do a test using 0x00000000.

Scan tests: 2, skipped: 0, failed: 0

Do a test using 0xFE03E0E2.

Scan tests: 3, skipped: 0, failed: 0

Do a test using 0x01FC1F1D.

Scan tests: 4, skipped: 0, failed: 0

Do a test using 0x5533CCAA.

Scan tests: 5, skipped: 0, failed: 0

Do a test using 0xAACC3355.

Scan tests: 6, skipped: 0, failed: 0

All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

Done.

****************************************************************************************************

TEST 4 - DATA

****************************************************************************************************

**************************************************

BHProbe 5.01: Blackhawk USB560m JTAG Emulator

**************************************************

16/05/2013-15:07:46.96

bin\XDSProbe.exe -v -F BH560USBm.out -p0x0 -g -o log\BHprobe_USB560m.log

-----[Print the controller-open software log-file]---------------------------

This utility has selected an XDS560 class product.

This utility will load the program 'BH560USBm.out'.

This utility will operate on port address '0'.

The controller does use a programmable FPGA.

The emulator program is named 'BH560USBm.out'.

The emulator program is version '35.24.0.3'.

The controller has a version number of '4' (0x0004).

The controller has an insertion length of '0' (0x0000).

The cable+pod has a version number of '2' (0x0002).

The cable+pod has a capability number of '0' (0x0000).

The local memory has a base address of '0' (0x000000).

The local memory has a word capacity of '32768' (0x008000).

-----[Perform the standard path-length test on the JTAG IR and DR]-----------

This path-length test uses blocks of 512 32-bit words.

The test for the JTAG IR instruction path-length succeeded.

The JTAG IR instruction path-length is 60 bits.

The test for the JTAG DR bypass path-length succeeded.

The JTAG DR bypass path-length is 10 bits.

-----[Perform the Given Data scan-test on the JTAG IR]-----------------------

This test will use blocks of 512 32-bit words.

This test will be applied just once.

It uses the first 1 of the 10 different test-cases.

Do a test using 0x5533CCAA.

Scan tests: 1, skipped: 0, failed: 0

All of the values were scanned correctly.

The JTAG IR Given Data scan-test has succeeded.

-----[Perform the Given Data scan-test on the JTAG DR]-----------------------

This test will use blocks of 512 32-bit words.

This test will be applied just once.

It uses the first 1 of the 10 different test-cases.

Do a test using 0x5533CCAA.

Scan tests: 1, skipped: 0, failed: 0

All of the values were scanned correctly.

The JTAG DR Given Data scan-test has succeeded.

Done.

Output of BH Detect

16:14:02: BHDetect - Version 1.0.0.11

16:14:02:

16:14:02: Scan started on Thursday, May 16, 2013 at 04:14:02 PM.

16:14:02:

16:14:02: SYSTEM INFORMATION:

16:14:02: -------------------

16:14:02: Computer Name: BC-DSPDEBUG

16:14:02: User Name: dspuser

16:14:02: OsVersionInfo: Platform=2 (0=WIN32s, 1=WIN32_WINDOWS, 2=WIN32_NT)

16:14:02: Major.Minor=5.1; Build=2600 (if Platform=2: 5.0=W2K, 5.1=XP, 5.2=2003Server, 6.x=Vista or later)

16:14:02: (if Platform=1: 4.0=W95, 4.10=W98, 4.90=WMe)

16:14:02: CSD=[Service Pack 3], SP Major=3, SP Minor=0, Suite=256, Product=1

16:14:02: Processor Architecture=0 (INTEL=0 MIPS=1 ALPHA=2 PPC=3 SHX=4 ARM=5 IA64=6 ALPHA64=7 MSIL=8 AMD64=9 IA32onWIN64=10)

16:14:02: Wow64 Process: OS is Running 32-bit version.

16:14:02: -------------------

16:14:02:

16:14:02: SCANNING OPTIONS SELECTED:

16:14:02: --------------------------

16:14:02: + Scanning for CCS v3.3 and earlier.

16:14:02: + Scanning for CCS v4 or later.

16:14:02: --------------------------

16:14:03:

16:14:03: SCANNING CCS v3.3 and EARLIER:

16:14:03: ------------------------------

16:14:03:

16:14:03: Starting Quick Scan for CCStudio v3.3 and earlier Installations...

16:14:03:

16:14:03: %%ERROR: bhDetect_GetIniFile() opening ComponentManager registry key.

16:14:03: bhDetect_ListCCSInstallations: Error locating CCStudio Component Manager INI file.

16:14:03: bhDetect_ListCCSInstallations: No valid CCS v3.3 and earlier installations found.

16:14:03: ------------------------------

16:14:03:

16:14:04:

16:14:04: SCANNING CCS v4 or LATER:

16:14:04: --------------------------

16:14:04:

16:14:04: Starting Quick Scan for CCStudio v4 (or later) Installations...

16:14:04:

16:14:04: bhDetect_FindCCv4Installations: Program Files path: C:\Program Files\.

16:14:04: bhDetect_ListCCSv4Installations: No valid CCS v4 (or later) installations found.

16:14:04: --------------------------

16:14:04:

16:14:04: Starting scan for installed Blackhawk Driver Files...

16:14:04:

16:14:04: Processing NON-SYS Files...

16:14:04: + Checking in System Folder: C:\WINDOWS\System32.

16:14:04: blackhwk.cpl, v01.01.00.00, 155440 bytes, Wed Feb 08 06:09:15 2012

16:14:04:

16:14:04: Processing SYS Files...

16:14:04: + Checking in System Folder: C:\WINDOWS\system32\drivers.

16:14:05: bh560eth.sys, v01.00.00.09, 97776 bytes, Wed Nov 17 14:05:14 2010

16:14:05: bh560usb.sys, v01.10.00.00, 318640 bytes, Wed Feb 08 06:09:14 2012

16:14:05:

16:14:05: Starting scan for Blackhawk Emulators...

16:14:05:

16:14:05: 1.) Blackhawk USB560M JTAG Emulator (S/N:HC7174)

16:14:05:

16:14:05: Completed scan for Blackhawk Emulators.

16:14:06:

16:14:06: Scan Completed Successfully on Thursday, May 16, 2013 at 04:14:06 PM.

16:14:06:

16:14:06: ******************************************************************************

16:14:06: BHDetect - Version 1.0.0.11 Errors: 1, Warnings: 0

16:14:06: ******************************************************************************

16:14:06: BHDetect has completed a scan of your system. The output generated in the

16:14:06: dialog box window is designed to help debug installation and setup problems.

16:14:06: Any messages that begin with "%ERROR" should be addressed and you can

16:14:06: contact Blackhawk support via email: support@blackhawk-dsp.com and include

16:14:06: the output from this utility for faster response.

16:14:06:

16:14:06: Thank you, The Blackhawk Support Team.

16:14:06: ***************************************************************************EOF.

Output of test connection from CCS studio v5.2.1 View->Target Configuration window

[Start]

Execute the command:

%ccs_base%/common/uscif/dbgjtag.exe -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

C:\DOCUME~1\dspuser\LOCALS~1\APPLIC~1\.TI\

3823558504\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 560/2xx-class product.

This utility will load the program 'bh560usbm.out'.

Interface uscif not exported by C:\ti\ccsv5.2.1\ccsv5\ccs_base\common\uscif\uscif.out

An error occurred while soft opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-250' (0xffffff06).

The title is 'SC_ERR_ECOM_EMUNAME'.

The explanation is:

An attempt to access the named emulator via USCIF ECOM has failed.

[End]

One file across two projects (CCS 5.4)

William Perdikakis — Thu, 16 May 2013 14:33:42 GMT

Hello,

I am developing on the Concerto processor and want to share a few H files between the two projects (one for each core). Is there any way that I can have one file that will be included in both builds? Right now, when I update the file, I have to copy it to the other project.

Ideally, I would like this to not be attached to either of the projects, if that is possible. Like, for example, if I could store it in the workspace itself.

Thank you,

Will

CCS5.3 Acting strange

Silver Diamond — Fri, 03 May 2013 02:52:43 GMT

Any way to reset CCS5.3 to all of default settings? for some reason my debugging does not work right. For example as I step through code, I cannot change values manually as I was able to before. Very strange, hard to explain, but I would like to see if I can reset CCS5 to defult settings?

Help on CCS v3.1 + Win Vista + XDS510USB

S V — Fri, 17 May 2013 15:50:22 GMT

Hi,

Does anyone know of any workaround to get XDS510 USB working on Windows Vista with CCS v3.1? XDS510USB got installed on Windows Vista properly. CCS v3.1 seems to be working on Win Vista as well. But it starts complaining when trying to use the JTAG connector.

This is to make some changes to an existing project and I donot want to convert to the latest CCS version.

Thanks,

CCS5.4.0.00091 Unable to Open Existing Workspace

Timothy Dahlin — Fri, 17 May 2013 15:59:04 GMT

After installing CCS5.4.0.00091 (using the offline installer found here ), I am initially able to open up my previous workspace. However, after I close the CCS IDE and attempt to reopen the workspace, I run into a "An error has occured" dialog box and the CCS IDE never shows up.

Here's the log file I got.

(Please visit the site to view this file)

Fedora 18 floating license server ethernet ports not named eth0

Jeff Stringer — Fri, 17 May 2013 18:38:44 GMT

In the post http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/207940/751289.aspx#751289 it discusses this problem but with Fedora 15. The problem is the license server needs the port to be eth0 but with the new fedora port naming, ports are named em1 for example. However I have Fedora 18 and I couldn't get this solution to work. Is there any work around for Fedora 18?

CCSV5.4.00091-Linux 'config is not defined'

sink — Fri, 17 May 2013 18:10:19 GMT

I began to try CCSV5.3 on Windows with LM4F120 board. Runs example from TI-RTOS 1.01 without issue. However, my company default develop environment is Linux. So I install CCSV5.4. The same example has compilation errors. The message is

xs.js: xdc.Warnings failure: package path: /opt/ti/tirtos_1_01_00_25/packages;/opt/ti/tirtos_1_01_00_25/products/bios_6_34_04_22/packages;/opt/ti/tirtos_1_01_00_25/products/ipc_1_25_02_12/packages;/opt/ti/tirtos_1_01_00_25/products/ndk_2_22_01_14/packages;/opt/ti/tirtos_1_01_00_25/products/uia_1_02_00_07/packages;/opt/ti/tirtos_1_01_00_25/products/xdctools_3_24_06_63/packages;/opt/ti/ccsv5/ccs_base;/opt/ti/xdctools_3_25_00_48/packages;..;
js: "/opt/ti/tirtos_1_01_00_25/products/xdctools_3_24_06_63/packages/xdc/bld/BuildEnvironment.xs", line 146: ReferenceError: "config" is not defined.
gmake: *** No rule to make target `.configuro'. Stop.
js: "/opt/ti/tirtos_1_01_00_25/products/xdctools_3_24_06_63/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
"/opt/ti/tirtos_1_01_00_25/products/xdctools_3_24_06_63/packages/xdc/tools/configuro/Main.xs", line 74
"/opt/ti/tirtos_1_01_00_25/products/xdctools_3_24_06_63/packages/xdc/tools/ICmd.xs", line 50

I reinstall the CCS and it doesn't seems have any effect. Did I miss anything or there are difference between Linux and Windows version.

Thanks

Tony

OMAL-l137 EVM and free licence under CCS5.4

Claus Rimestad — Thu, 16 May 2013 15:29:25 GMT

Hi Ti.

Is there a limitation that prevent me from using the OMAP-l137EVM onboard Jtag onboard Emulator, running a free or 90 days CCS5.4 license?

In the Target Configuration:

If I select the onboard "Spectrum Digital DSK-EVM PLUS onboard USB Emulator" there is only one board type available, the EVMDMR45X, trying to make the "board" myself by selecting a ARM9 and the C674X from the CPU library and add the .gel file from ccsv5\ccs_base\emulation\boards\evmomapl137\gel\evmomapl137_dsp.gel or browsing for a board all ends blind.T

The test under target configuration says :

[Start]

Execute the command:

%ccs_base%/emulation/drivers/sdjtag.exe -f %boarddatafile% -v -X reset -X scantest

[Result]

** BoardFilePath: C:\Users\CLAUSR~1\AppData\Local\.TI\693494126\0\0\BrdDat\testBoard.dat
** Resetting Emulator
-- Emulator is Reset
** Emulator Scan Test
-- Found JTAG IR Length of 6
-- Found 1 device(s) in the scan chain

[End]

Have also tried with a 90 days license with the same problems.

Have also tried on two machines, one win7 and one XP.

Have tried to build Target configuration using "Spectrum Digital SDS510USB with same results.

It looks like some thing is missing in the library, one installation had all option selected in the installation the last only what I expected to need. Same experience!!

CCs5.3 or 5.4 make no difference.

The target board is a OMAP-L137EVM from Spectrum digital rev "I".

Claus.

loadti sometimes works fine, but occasionally hangs

mark richardson1 — Fri, 17 May 2013 08:30:10 GMT

From CCS5.3 I can successfully download and run on my target, but I need to automate this from a batch file and so I am using loadti to download and execute on my target (in this case an RM48L950). Most of the time, the download works fine and the program runs:

set PATH=%PATH%;"c:\ti\ccsv5\ccs_base\scripting\examples\loadti\";
call loadti -v -n -r -c C:\LDRA\LDRA_Demos\TICCS50_Workspace\TICCS50_RM48L950_Dice\target.ccxml -n C:\LDRA\LDRA_Demos\TICCS50_Workspace\TICCS50_RM48L950_Dice\LDRA\TICCS50_RM48L950_Dice.out

But sometimes it just hangs. I switched on the -v option and when it hangs it is doing the following:

...

reset: Target reset
getBoolean: ENTRY
getBoolean: RETURN false
reset: RETURN
testEnv.outFiles: C:\LDRA\LDRA_Demos\TICCS50_Workspace\TICCS50_RM48L950_Dice\LDRA\TICCS50_RM48L950_Dice.out
Loading C:\LDRA\LDRA_Demos\TICCS50_Workspace\TICCS50_RM48L950_Dice\LDRA\TICCS50_RM48L950_Dice.out
loadProgram: ENTRY sFileName: C:\LDRA\LDRA_Demos\TICCS50_Workspace\TICCS50_RM48L950_Dice\LDRA\TICCS50_RM48L950_Dice.out
load: Requesting program load
waitUntil: ENTRY timeout: infinite
setupBeforeRun: ENTRY emuPin: 0
exists: ENTRY sSymbol: _RTDX_JTAGONLY
exists: Getting symbol package
exists: Looking-up symbol
exists: RETURN false
exists: ENTRY sSymbol: _RTDX_HPONLY
exists: Getting symbol package
exists: Looking-up symbol
exists: RETURN false
exists: ENTRY sSymbol: _RTDX_ICEONLY
exists: Getting symbol package
exists: Looking-up symbol
exists: RETURN false
exists: ENTRY sSymbol: RTDX$$MSG
exists: Getting symbol package
exists: Looking-up symbol
exists: RETURN false
getConfigMode: ENTRY
getConfigMode: RETURN 1
getConfigMode: ENTRY
getConfigMode: RETURN 1
exists: ENTRY sSymbol: rtdxCioOutputChannel
exists: Getting symbol package
exists: Looking-up symbol
exists: RETURN false
waitUntil: RETURN
load: Program load successful
getBoolean: ENTRY
getBoolean: RETURN true
waitForHaltIfPropertySet: Waiting for halt
waitUntil: ENTRY timeout: infinite
==> ( just hangs here )

Any idea what I can do to resolve this?

Thanks

Mark

How to exclude runtime support libraries from link?

Steve Witt96188 — Fri, 17 May 2013 18:03:47 GMT

I am using CCSv5.3 and have selected none for runtime library support, yet the linker still includes the runtime libraries. How do I prevent the linking of runtime libraries? I have my own C initialization and want none of the functionality of the CRT libraries.

RSEG1066 target connection error

sviss — Wed, 15 May 2013 18:01:10 GMT

Hi forum,

If configuring target (Sitara SK board) RSE connection I should normally receive a host authenticity warning.

I get an error message RSEG1066 box (connection refused) instead.

Guess, something wrong should be with the target.

I can successfully ping it or establish TCP/Winsock terminal connection and log in, however.

Could somebody please suggest where to look next so that to understand the source of trouble?

Attached are screenshots of 1) CCS5 manual + Eclipse message box; 2) Wireshark capture of respective LAN frames.

Thanks!

CCS 5.3 missing a couple files / tools?

Doug Baker — Sun, 23 Dec 2012 13:28:33 GMT

I was upgrading from Version: 5.1.0.07001 to Version: 5.3.0.00090 and I can't find a couple of files I use for the post build step to create a .bin file. The files I used were ofd470.exe and hex470.exe. My post build step was: "${CCS_INSTALL_ROOT}/utils/tiobj2bin/tiobj2bin.bat" "${BuildArtifactFileName}" "App_GCB_vXX.bxxxxx_.bin" "${CG_TOOL_ROOT}/bin/ofd470.exe" "${CG_TOOL_ROOT}/bin/hex470.exe" "${CCS_INSTALL_ROOT}/utils/tiobj2bin/mkhex4bin.exe"

Did I install 5.3 wrong or is there a different way I should create the .bin file now?

Thnaks,

Doug

Resolved - CCSV5 Re-installation missing install_drivers.sh

Le George — Sat, 26 Jan 2013 01:09:37 GMT

Problem: XSD100 V2 driver not properly installed

1. Un-installing CCSV5.3 (Ubuntu 11.10) via these steps:

$ cd /opt/ti/ccsv5

$ sudo ./uninstall_CCSv5

2. After 30 minutes, the un-installation process seemed to hang so I had to kill it,

3. I've manually removed the remaining folders:

$ cd /opt

$ rm -rfv ti/*

4. I've successfully re-installed CCSV5.

5. Where is the file "install_drivers.sh" as mentioned in the readme.txt file?

I've found another file "ti_xds100_linux_install.sh" in the folder "/opt/ti/ccsv5/ccs_base/common/uscif/install/" - Not sure it's correct.

Regards,

-------------------

Solved:

Re-install "CCSV5.3 + all feature option" using the online-installer option is correctly installing: /opt/ti/ccsv5/install_scripts/install_drivers.sh.

The shell script folder never got created with the Linux-offline installer twice + custom setup - weird (installation bug?)

CCS v5.2.1 Blackhawk Driver Updates.

Taahir Shamsuddin — Fri, 17 May 2013 14:06:57 GMT

Hi,

I currently have CCS v5.2.1 with which I want to use a Blackhawk USB560v2 debugger. Fom the release notes I can see I need to update CCS v5.2.1 with Blackhawk Emulation Drivers v5.2.0.203. However because of company firewall issues, it's not possible for me to update directly from the CCS Update Manager. Do you have a zip file for all the necessary Blackhawk drivers which I can point the Update manager to? This will allow me to install the patch locally

Thanks, Taz

Version Control in CCS 5.4

William Perdikakis — Thu, 16 May 2013 14:17:34 GMT

Is there a nice way to increment software versions within this tool? I am sure it is really obvious but my web searches have failed me. I know that this is probably an easy answer so just an informational link or even and search string would get you a "Verify Answer"!

EDIT: I think I am actually just looking for a simple way to increment a build/version number within the tool itself. Right now, I am incrementing a suffix on the project title, there has to be a better way!

Where to get TMS470_4.11

Simon Wang1 — Thu, 16 May 2013 11:43:11 GMT

Hi,

According to http://processors.wiki.ti.com/index.php/AM335x_SYSBIOS_Industrial_SDK_01.00.00.04_User_Guide , TMS470.11 is required to compile Powerlink_slave demo application. Where could I get the compiler?

Thx