Code Composer

CCS 3.xx How to avoid unwanted casts?

Vitaliy — Thu, 19 Nov 2009 10:43:52 GMT

CCS 3.3.81.6, Code generation tools 4.1.0 DSP 320C5416

unsigned long Sum32(short a,short b)
{
register unsigned long z;
z=(unsigned long)(a*b);
return (z);
}

Get asm:

_Sum32:
FRAME #-2
NOP
STL A,*SP(0)
LD *SP(4),T
SSBX SXM
MPY *SP(0),A ; |114|
LD *(AL),A ; |114| WHAT is THIS ???? i'm need a 32 bit result!
FRAME #2 ; |116|
NOP
NOP
FRET ; |116|

unsigned long SSum32(short a,short b)
{
register unsigned long z;
z=(unsigned long)(a*a);
z+=(unsigned long)(b*b);
return (z);
}

get asm code:

_SSum32:
FRAME #-2
NOP
STL A,*SP(0)
SSBX SXM
SQUR *SP(0),A ; |113|
SQUR *SP(4),B ; |114|
LD *(AL),A ; |113| WHAT is THIS ???? i'm need a 32 bit result!
LD *(BL),B ; |114| WHAT is THIS ???? i'm need a 32 bit result!
ADD B,A ; |114|
FRAME #2 ; |115|
.dwcfa 0x0e, 2
NOP
NOP
FRET ; |115|

How to avoid unwanted casts?

C6416T - Jtag IR length

HR — Sun, 22 Nov 2009 15:47:33 GMT

Hi,

I'm trying to connect to a board with 4 C6416T and I'm getting the error 0x80000240/-1135, the IR length for the four DSP's is 32 which I think should be 152 (4*38) as each DSP length is 38, is this correct? we changed the Jtag chain to connect to one DSP but still we are getting the same error and the IR length is 8, what could be the issue?

Many Thanks,

CCS Studio error message

Arye Lerner — Thu, 19 Nov 2009 16:12:46 GMT

Hello,

I am running the software I've wrote, and keep getting an error message even when running step by step, after every step:

AET Error: Bad jobID passed to GetTimerValue.
AET Error: Bad jobID passed to GetTimerValue.
AET Error: Bad jobID passed to GetTimerValue.
AET Error: Bad jobID passed to GetTimerValue.
AET Error: Bad jobID passed to GetTimerValue.

I dont see any real disfunctionality in program, but still this message worries me. What can cause this?

Regards

Arye

XDS100 USB JTAG Emulator

Sinoj B S — Tue, 10 Nov 2009 03:43:24 GMT

Hi, I'm trying to implement an XDS100 of my own. I've looked at the schematic downloaded from TI web, XDS100 V1.0 USB (TSM320_USB_JTAG_ti_RevC2). I didn't see anywhere in the schematic 5V<->3V3 or 5V<->1V8 conversion is taking place on the JTAG and EMU0/1 lines that are commected to the target. Is the JTAG lines within the target is capable of handling this? Does anyone implemented a working XDS100 USB JTAG Emulator of their own? Am I missing something? -Regards -Sinoj

adding *.dll library file

Jarosław Wojtuń — Thu, 19 Nov 2009 23:03:02 GMT

Hi,

How can I add a *.dll library file to my project i CCSv3.1

Thanks,
Jarek

F280x flash lock during erase

Douglas Carter — Fri, 20 Nov 2009 04:24:30 GMT

Hi,

I am having problems with the flash being locked during flash operations, without the password protection being deliberately activated by me.

I am using CCS4.0.2 (upgraded once), Blackhawk USB2000 emulator and F2808 ControlCARD in an experimenter's dock. I recently bought this hardware, but have many previous years experience with CCS3.x, Spectrum Digital 510usb emulator and F281x.

The first time it happened, I tried to write a simple project to flash. I made sure that the password protection was not set - password bits all ones in CSMPasswords.asm. The programming sequence stalled, and after starting the IDE again the flash was locked. After that I had to order more ControlCARDs and did development work for a couple of weeks using RAM only with no problems.

The second time it happened (now), I wanted to program to flash because the code size was getting close to the RAM size limit. I tried to play it safe. I opened a debug session, and opened the On-Chip Flash tool. I tried using this tool to erase flash bank A only, but it reported that there was an error erasing the flash. The flash was still unlocked. I tried two more times, after which it reported that the flash was locked or the device not connected.

I'm not sure if this is a software or hardware problem. Any thoughts would be appreciated.

Thanks in advance,

Douglas

ps - I'm just wondering whether the flash circuitry draws an impulse of current when a flash erase operation starts, and whether this might cause a catastrophic supply voltage dip if the external supply is weak? I'm down to my last ControlCARD and am loathe to sacrifice it to find out!!

CCSv4: Debugging Linux on OMAP3430 (ARM Cortex A8)

Christina_ — Thu, 19 Nov 2009 23:14:10 GMT

Hi, I was trying to debug Linux using CCSv4 on the Zoom2. I was able to use CCS v3.3 to load the x-loader and the u-boot and step through the code. Unfortunately, when the u-boot passes control to the kernel, CCS doesn't know what's going on.

From what I understand after reading this article: http://tiexpressdsp.com/index.php?title=Linux_Aware_Debug is that CCS v4 is Linux aware.

Has anyone been able to successfully use CCS v4 to load the boatloader and the kernel using CCS and debug?

~Christina.

CCSv4 Command Line Build

Andreas Zoufal — Thu, 19 Nov 2009 17:11:43 GMT

Hello,

I have a strange behaviour on command line builds with CCSv4. Following the instructions from wiki I invoke the following command(s):

set CCS4_INSTALL_DIR=C:\Programme\Texas Instruments
set CCS4_WORKSPACE_DIR=D:\WorkingFolder\wks40

"%CCS4_INSTALL_DIR%\ccsv4\eclipse\jre\bin\java" -jar "%CCS4_INSTALL_DIR%\ccsv4\eclipse\startup.jar" -data "%CCS4_WORKSPACE_DIR%" -application com.ti.ccstudio.apps.projectBuild -ccs.projects MSG_AVC4_CCS40_TEST -css.configuration Release

The build runs, but there are 2 effects I don't understand:

1.) The build uses the current conigurations from the workspace, ignoring my option "-css.configuration Release". I checked, changing the workspace configurations the buld changes for the same command. Is something wrong with my command line?

2.) There is always a preceeding "Clean" step. Why?

I'm pretty sure the configuration names are correct (as default - "Debug" and "Release").

Any Ideas?

Kind regards,
Andi

--- console output ---

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
CCS headless build starting... [Thu Nov 19 17:59:15 CET 2009]
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

================================================================================
Pre processing...

================================================================================
Building...

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

**** Clean-only build of configuration Debug for project MSG_C64P_CCS40 ****

C:\Programme\Texas Instruments\ccsv4\utils\gmake\gmake -k clean
"C:/Programme/Texas Instruments/ccsv4/utils/Cygwin/rm" -rf ./MSG_destroy.obj ./MSG_init.obj ./MSG_levelGet.obj ./MSG_levelSet.obj ./MSG_readFirst.obj ./MSG_readLast.obj ./MSG_readNext.obj ./MSG_readPrev.obj ./MSG_write.obj ./src/MSG_destroy.pp ./src/MSG_init.pp ./src/MSG_levelGet.pp ./src/MSG_levelSet.pp ./src/MSG_readFirst.pp ./src/MSG_readLast.pp ./src/MSG_readNext.pp ./src/MSG_readPrev.pp ./src/MSG_write.pp "MSG_CCS40.l64p"
' '
Build complete for project MSG_C64P_CCS40

**** Build of configuration Debug for project MSG_C64P_CCS40 ****

C:\Programme\Texas Instruments\ccsv4\utils\gmake\gmake -k all
'Building file: D:/WorkingFolder/TMS320C6000/Modules/MSG/src/MSG_destroy.c'
'Invoking: C6000 Compiler'
"C:/Programme/Texas Instruments/ccsv4/tools/compiler/c6000/bin/cl6x" -mv6400+ -g --fp_mode=strict --define="_DEBUG" --include_path="C:/Programme/Texas Instruments/ccsv4/tools/compiler/c6000/include" --include_path="D:/WorkingFolder/TMS320C6000/Modules/MSG/C64P_CCS40/Debug" --include_path="C:/Programme/Texas Instruments/bios_5_41_00_06/packages/ti/bios/include" --include_path="C:/Programme/Texas Instruments/bios_5_41_00_06/packages/ti/rtdx/include/c6000" --include_path="C:/Programme/Texas Instruments/xdais_6_23/packages/ti/xdais" --include_path="C:/CCStudio/C6000/csl/include" --diag_warning=225 --sat_reassoc=off --fp_reassoc=on --mem_model:const=data --mem_model:data=far_aggregates --preproc_with_compile --preproc_dependency="src/MSG_destroy.pp" "D:/WorkingFolder/TMS320C6000/Modules/MSG/src/MSG_destroy.c"
'Finished building: D:/WorkingFolder/TMS320C6000/Modules/MSG/src/MSG_destroy.c'
' '

... and so on ....

HOW TO OPEN A PROJECT?(CCSV4)

chanbw — Wed, 18 Nov 2009 10:14:31 GMT

I am a new user of ccs4,could any body help me about how to open an existing project? I have downloaded some examples composed of *.c ,*.cdtbuld , *.cdtproject , *.project and macros.ini files. Thank you!

CCS4 hangs up at switching of lay-out of keyboard

Alexander Mazalov — Thu, 19 Nov 2009 12:05:48 GMT

Hello,

I have a problem with CCS v4.0. I use Windows XP SP3, pre-SP4 and Code Composer Studio ver 4.02.01003. I have 1.3Gb RAM.

At any switching of keyboard layout with English on Russian and back there is a permanent stop (hang up) of operation of editor CCS. Or at any switching language in Language Bar CCS editor hang up too.

Is there any problem solving at present moment?

Thanks.

CCS4 hangs up at switching of lay-out of keyboard

Eduard Sokolov — Wed, 02 Sep 2009 08:00:57 GMT

At the change of lay-out of keyboard (Ctrl-Shift or Alt-Shift) there is a stop of work of editor for a time to 40 seconds.

Multiple Post-Build commands in CCS V4 ?

Vasanth Nayak — Wed, 18 Nov 2009 17:01:36 GMT

Hi,

Is it possible to have multiple Post build commands in CCS V4 ? I see that there are post build commands for converting to TI-TXT or INTEL-HEX format. I wanted to add another post-build command (invoking a VC++ command application to add checksum) . Is that possible ?

CCSV4 - GUI problem with project options on Vista64

Tomasz — Wed, 18 Nov 2009 19:12:28 GMT

This problem has been reported in the past (http://e2e.ti.com/forums/p/7471/30223.aspx#30223 by Edward) but probably hasn't been addressed by TI (possibly it was difficult to replicate).

When openiing Project->Properties->C/C++ Build: all the tabs for Configuration Settings (Tool Settings, Build Settings etc.) are completely missing. Left pane of the dialog box has to be resized to have all missing elements appear on the screen. In my case (as in Edward's case - see thread mentioned above) this problem demonstrates itself only on Vista64. Similar problem exists with dialog box for setting up target configuration. The problem is seemingly minor because solution is simple (resize every time left pane), but it can be quite time consuming if one doesn't know about it. Nothing about it is mentioned in FAQ and there is no separate thread for GUI problems on this forum. Not knowing what's going on I unistalled CCS and reinstalled it again, which takes time for full version and then I installed it again on XP to find out that everything works OK there. I'm running CCS Version: 4.0.2.01003 on Vista Businees 64 SP2.

String literals with "character codes" > 0xff

johannes — Mon, 16 Nov 2009 10:50:10 GMT

I'd like to initialize string constants such that the high byte of each character can be nonzero.

The string constants are pointed to by members of a struct as in the following code:

struct foo_struct {
char *s;
};

const struct foo_struct foo = { "\x2021\x2223" };

When compiling this code I get the warning:

"test.c", line 182: warning #27-D: character value is out of range
const struct foo_struct foo = { "\x2021\x2223" };

And the corresponding location in memory is initialized with 0x21, 0x23, 0x00.

I could achieve what I want by doing something like this:

struct bar_struct {
const unsigned *u;
};

const unsigned u_ar[] = {0x2021, 0x2223, 0};

const struct bar_struct bar = { u_ar };

What I don't like with this approach is the requirement of the intermediate array u_ar. I don't need that, since I only access the data using the pointers in the structures.

I'd appreciate any hints on how to initialize string constants such that both bytes of a character can be used (I want to save some memory).

BTW, is there a more recent User's Guide to the compiler than spru514c.pdf? spru514c.pdf is marked preliminary and for version 5.0.0 of the compiler. I'm using version 5.2.3 now.

Thanks in advance

Johannes

Migrating from CCS2.20.03 to CCS3.3.38.2

Shiras Pallikkara — Fri, 06 Nov 2009 11:05:25 GMT

I have a project which was created in CCS Ver.2.20.03. I was using DSP/BIOS Ver.4.82.50 and CG tools Ver.4.32 and the binary generated from this build environment is working fine on my target(C6415).

Now i have to migrate the same project to higher versions of CCS. I am now trying to migrate to CCS Ver.3.3.38.2 (Integrated Development Ver. 5.98.0.219,BIOS Ver 5.31.02 and CG Tools v6.0.8).

When i open the project in CCS Ver.3.3.38.2, a Project Update (--version ID:5.1.8) POP-UP window comes and It will ask the following:

"IMPORTANT!

The project you are opening is based upon an older CDB configuration file. It must be converted to the new TConf Script (TCF) format if you want to edit the configuration and build the project.

Do you want to convert the project now?"

On clicking "Yes", a DOS window comes up and It will tell:

"Running "D:\MyProjects\PJTCCS3.3\cdb2tcf.bat"

Please wait...

cdb2tcf command SUCCESSFULL.

Press any Key to continue..."

On pressing any key, The Project Update POP Window again comes and it will now tell that:

"Conversion of the CDB Configuration file to TCF format successful.

The project has been updated, and a backup copy of the original project created.

Note: a generated CSL file has been added to your project.

You will need to add a call to clsCfgInit() manually to your main() function."

I have called CSL_init() followed by cslCfgInit() from my application's main() function after including the generated csl header file( contains the extern declaration to EMIFA and EMIFB config Structures) to this source file. I have also added csl6415.lib to the project.

The project, on building does not give any errors. But the generated binary is fails to load on the target. What could be the problem?

Is there something else i have to take care while migrating a project from CCS2.20 environment to CCS3.3 (the versions of cg tools,DSPBIOS are mentioned above)?

Blackhawk OMAP-L137,OMAP-L138 XDS510 Import Update

Andrew Ferrari — Wed, 18 Nov 2009 18:11:54 GMT

Support for the OMAP-L1x family requires an XML file for the ETB11 device not included with the original CCS v4. driver installation. This will be added to the installer for CCS v4.1 and also available as an update. For now, just download and extract the file, bhemu510etb11.xml, from the ZIP to folder: C:\Program Files\Texas Instruments\ccsv4\common\targetdb\drivers.

Populating CCS v4 with this file will display the OMAP-L1x imports for Blackhawk XDS510 Emulators (USB510, USB510L, etc.).

- Andrew

.net framework error when I try to see the registers

James Thorton — Tue, 17 Nov 2009 15:26:03 GMT

Hi,

I am having an issue with CCS when I try to go to view tab -> Register -> Core registers or whatever internar register that I tried to see. I attach the snapshot of the error. I have tried to uninstall and make a clean install all the .net framework, but no luck. Has anyone any idea about how to fix this? I have tried to to reinstall CCS, no luck either.

Thanks in advance

CCS V4.0.2 & MSP430x5xx: Cannot access upper flash banks

gifford scott — Tue, 03 Nov 2009 15:36:22 GMT

Hey all,

Tell me if you've heard this one before...

I'm running CCS v4.0.2 Platinum, using the 'msp430x5xx C Example' project with the MSP430F5438 Experimenter Board (with a '5419 replacing the '5438). I can compile, load and exec the project output, but cannot access any memory above 0xFFFF. The memory window returns all X's and the tool tip states:

' Address 0x20000

Error code 0x5: Memory access not attempted by the driver (Check memory map) '

Any ideas as to why I cannot see the upper banks of flash (banks 1 & 2) under CCS v4.0?

regards,

gifford scott

DST

CCSv4 Administrative Questions

Andreas Zoufal — Wed, 18 Nov 2009 15:03:03 GMT

Hello,

I have a few questions about CCSv4 administration:

1.) Is it possible to get updates for CCSv4 as install files instead online update, like CCS 3.3 and below? It would be nice to have alle updates on CD/DVD for archiving projects/tools or installations on computers without internet connectivity.

2.) Is it possible to install CCSv4 in parallel to CCS 3.3 and CCS 3.0 without problems? I would need this because different projects are frozen at different CCS versions. And debugging using SD XDS510USB or SD XDS560R is still possible, without driver clashes?

3.) Consequently for the future: will it be possible to install eclipse-based CCS versions in parallel, for example CCSv4 and CCSv5 (in future).

4.) Whats about workspaces for different eclipse installations? I have currently Eclipse 3.5 for java development, CCSv4 and MontaVista DevRocket. I guess I must select different folders for each workspace?

5.) is it possible to run general eclipse add-ins in CCSv4? I tried Splint for Eclipse very short, but it looks like not working. Other desired add-ins would be for example AnyEdit, Subclipse, CopyrightWizard, etc.

Thanx
Andi

CCSv4 Import Dependend Projects With Convenience

Andreas Zoufal — Wed, 18 Nov 2009 15:38:56 GMT

Hello,

During my tests about importing CCS3.3 projects to CCSv4 I struggled with projects using other library projects by project dependencies. This feature is very nice and is available for all CCS version I used in the past. The dependent projects (libraries) are automatically compiled, with the right target (debug/release) AND automatically linked to the executable.

The import tool within CCSv4 fails on this. Is it possible to handle dependent projects with similar convenience?

Kind regards,
Andi

CCSv4 Minor Issue

André Hodder — Mon, 16 Nov 2009 15:56:52 GMT

I'm using F28335 experimenter kit (with XDS100) and working with real time mode debug.

It happens quite often that CCSv4 crashed (terminates). When I relaunch it the Emulator is unable to connect to the target.

Error connecting to the target:
Error 0x80000200/-1142
Fatal Error during: OCS,
Processor blocked debug accesses.

Even if I try to un-power and re-power the DSP board, still the same error.

I launch CCSv3.3 and I can connect to the target and reset the CPU.

However If I re-lauch CCSv4, I still have the same error message. Only solution is to restart computer.

As I can connect with CCSv3.3 it is a pure CCSv4 issue. How can I send the infos to TI to help them debug/improve CCSv4 ?

One more point. As I said I am able to connect and do things with CCSv3.3 and not in CCSv4. Even though it says "Processor blocked debug accesses" it is a CCSv4 issue. I've found that using Scripts "Full_Halt_With_Reset" removes the error. This sounds weird to me as the CPU is already halted and reset using CCSv3.3.

Perhaps it's a minor issue problem, but I thought it was important to tell other user, because as I spend quite a lot of time finding the solution as I thought it was a problem with the DSP and not with CCSv4

Word alignment issues

Bhaskar Reddy — Sat, 14 Nov 2009 13:27:39 GMT

We are using TMS320F28335 and CCS 3.3 with latest code genration tools.

I just wanted to work around this word alignment issue.

I have a structure say

typedef struct _x_x

{

unsigned char a;

unsigned char b;

unsigned short c;

unsigned short d;

}

The size of this structure returns 4. I think this is due to word alignment on this controller. But is it possible to set some compiler options to behave as a byte aligned and return a size of 6 and do the back ground operations to work as if its a byte aligned controller.

I could not able to port code which is written and work on byte alignment.

for example, lets say i'm receiving data on a parellel port (8bit), i would like to typecast the structure pointer to a char pointer and stream in the data and then back typecast to structure and use it. This is not working out as the otherside device streams in data on byte aligned format.

Any suggestioins pls.

CCSv4 & MSP430F54xx family: Upper flash memory bank (bank 2) access problem

gifford scott — Fri, 30 Oct 2009 18:19:19 GMT

Hey all,

I've downloaded the core version (16K limited) of CCS v.4.0.1, and I cannot load and debug code in bank 2 of a MSP430F5419 device. This sounds like a very fundamental flaw, having the debugger fail to access all the memory in the device, so I'm wondering if I'm missing something obvious...

To reproduce the problem: W/CCS v.4.0.1, modify lnkxxx.cmd file to allocate the .text section into flash memory starting @ 0x20000:

MEMORY
{
    SFR                     : origin = 0x0000, length = 0x0010
    PERIPHERALS_8BIT        : origin = 0x0010, length = 0x00F0
    PERIPHERALS_16BIT       : origin = 0x0100, length = 0x0100
    RAM                     : origin = 0x1C00, length = 0x4000
    INFOA                   : origin = 0x1980, length = 0x0080
    INFOB                   : origin = 0x1900, length = 0x0080
    INFOC                   : origin = 0x1880, length = 0x0080
    INFOD                   : origin = 0x1800, length = 0x0080
    FLASH0                  : origin = 0x05C00,length = 0x0A380
    FLASH1                  : origin = 0x10000,length = 0x10000
    FLASH2                  : origin = 0x20000,length = 0x05C00
    INT00                   : origin = 0xFF80, length = 0x0002
    INT01                  ....

SECTIONS
{
    .bss       : {} > RAM                /* GLOBAL & STATIC VARS              */
    .sysmem    : {} > RAM                /* DYNAMIC MEMORY ALLOCATION AREA    */
    .stack     : {} > RAM (HIGH)         /* SOFTWARE SYSTEM STACK             */

    .text      : {} > FLASH2             /* CODE                              */
    .text:_isr : {} > FLASH0             /* ISR CODE SPACE                    */
    .cinit     : {} > FLASH1             /* INITIALIZATION TABLES             */
    .const     : {} > FLASH1             /* CONSTANT DATA                     */
    .cio       : {} > RAM                /* C I/O BUFFER                      */

    .pinit     : {} > FLASH1             /* C++ CONSTRUCTOR TABLES            */

    .infoA     : {} > INFOA              /* MSP430 INFO FLASH MEMORY SEGMENTS */
    .infoB     : {} > INFOB
    .infoC     : {} > INFOC
    .infoD     : {} > INFOD

    .int00   : {} > INT00 ...

Initiating 'Debug Active Project' fails w/the following err message:

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

MSP430: File Loader: Data verification failed at address 0x00020000 Please verify target memory and memory map.
Error found during data verification. Ensure the linker command file matches the memory map.

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

Any insight would be appreciated.

regards,

gifford scott

DST

DSP/BIOS - error: declaration is incompatible with "TSK_Obj

HR — Tue, 17 Nov 2009 15:14:18 GMT

Hi All,

When I added a new Task to the DSP_BIOS I'm getting the error "....error: declaration is incompatible with "TSK_Obj xxx" (declared at line 24 of "xxxx.h") but as I checked the name is identical, what could be incompatible?

Many Thanks,

C6416 DSK emulator Erros

HR — Sun, 15 Nov 2009 16:24:34 GMT

Hi all,

I'm using the C6416 DSK (720MHz) with CCS3.3, I have installed the USB driver and run the SD test on the board which passed, when I'm trying to connect to the board I'm getting the Error -

"Error initializing emulator

I/O Port = 540

Board Name: C6416 Revision 1.1 DSK
Cpu Name: CPU_1"

What can be the issue?

Many Thanks,