MSP430 Ultra-Low Power Microcontrollers

Re: Get Started with the New Code Composer Essentials Version 3!

Kai — Thu, 01 Oct 2009 02:21:07 GMT

CCS is out, what is going to happen to all those CCE Pro user?

Re: Get Started with the New Code Composer Essentials Version 3!

Bernard Mentink — Fri, 25 Sep 2009 01:24:12 GMT

That syntax specified in that document to init the .bss segment to zero does not work with Code Composer Essential V3.2 linker script.

I have reverted manually providing a pre-Startup function to zero out bss ram prior to main(), that works.

Cheers,

Bernie

Re: Get Started with the New Code Composer Essentials Version 3!

Aarti — Fri, 25 Sep 2009 01:05:31 GMT

The MSP430 Compiler Users Guide, http://www-s.ti.com/sc/techlit/slau132, section on "Initializing Static and Global Variables" shows the linker syntax to do this.

Re: Get Started with the New Code Composer Essentials Version 3!

Bernard Mentink — Thu, 24 Sep 2009 22:58:01 GMT

Hi, on a similar issue.

I have just ported some code that was running on the mspgcc compiler to CCE and I am having some issues. The main problem is with variable initialization. It seems that CCE does not initialize the .bss segment to zeros like

other compilers do. Is there anyway to modify the linker script to do this?

The relevent section is:

SECTIONS

{

.bss : {} > RAM /* GLOBAL & STATIC VARS */

.sysmem : {} > RAM /* DYNAMIC MEMORY ALLOCATION AREA */

.stack : {} > RAM (HIGH) /* SOFTWARE SYSTEM STACK */

.text : {} > FLASH /* CODE */

.cinit : {} > FLASH /* INITIALIZATION TABLES */

.const : {} > FLASH /* CONSTANT DATA */

.cio : {} > RAM /* C I/O BUFFER */

etc etc

I need to know the syntax to change the .bss line to zero out that segment.

Thanks,

Bernie

Re: Get Started with the New Code Composer Essentials Version 3!

Jared — Fri, 21 Aug 2009 00:27:12 GMT

If you are using a processor with a lot of RAM to initialize, then you may run afoul of the watchdog timeout (it happened to me). Add a watchdog reset to each time through the loop and everything will be fine.

#define RAMSTARTADDR 0x0200
#define RAMSIZE      0x0400
#define RAMINITEND   (RAMSIZE - 6)

int _system_pre_init(void)
{
   int i ;
   char *ptr = (char *)RAMSTARTADDR;

   for (i=0; i<RAMINITEND; i++)
   {
       *ptr = 0x00;
       *ptr++;
       *** reset watchdog here ****

}
return 1;
}

Re: Get Started with the New Code Composer Essentials Version 3!

Bobby Pastia — Fri, 10 Jul 2009 16:54:54 GMT

Hi Brandon:

I used CCE Pro V3.1 for quite some time now. I do not recall the version, but I think it was one of the last available. I received a CC430-based board so I updated my tool applying CCE v3.1 SR1 (Rev F - ZIP 113800kB 28 April 2009). I also installed "SimpliciTI-CC430-1.1.0-Demo". When I try to rebuild an old project I get this: "Errors during build. Errors running builder "Generated Makefile Builder" on project ... This project was created using a version of Code Generation tools that is currently not installed: 3.1.0 [null]. Please install the Code Generation tools of this version, or migrate the project to one of the supported versions."

I tried to create a new project. I get no device variant choices and "No Code Generation tools installed......" message.

I would un-install my CCE v3.1 Build: 3.2.4.3.8 and install MSP-CCE430PRO alias "CCE Pro v3.1 SR1" but I cannot download that version. I also do not know how to transfer license. Thanks.

Re: Get Started with the New Code Composer Essentials Version 3!

Gregory — Mon, 29 Jun 2009 06:06:48 GMT

Great Tutorial Brandon. Could I trouble you to guide me how to implement SimpliciTI in CCE. I've tried importing the simpliciTI 1.1.0 folder into my project but I keep getting errors eg. could not open source file"bsp.h" or error failed to match a default include file.

Re: Get Started with the New Code Composer Essentials Version 3!

johnw — Fri, 19 Jun 2009 00:50:44 GMT

Aarti,

Zipped workspace is ~ 70MB which is too large for me to e-mail - so I am going to post on my ftp site and send you the details - did you get my e-mails?

Thanks,
johnw

Re: Get Started with the New Code Composer Essentials Version 3!

johnw — Wed, 17 Jun 2009 23:18:53 GMT

Aarti,

I responded to your e-mail before I read this post - I will send the rest when I am back on my development machine.

Can you glean anything from the list file?

Thanks,
johnw

Re: Get Started with the New Code Composer Essentials Version 3!

Aarti — Wed, 17 Jun 2009 20:41:05 GMT

Yes please send the C source file, generated assembly and listing file, as well as the assembly source file which calls this C function. Also cut and paste the full compile and link command options as they appear in CCE, under Project Properties->C/C++ Build->MSP430 Compiler v3.1 and MSP430 Linker v3.1.

Re: Get Started with the New Code Composer Essentials Version 3!

johnw — Wed, 17 Jun 2009 20:13:53 GMT

Aarti,

I need to correct myself on the previous post on one point - plus, yes, I did too build an example project but it worked... I don't know right now if it has anything to do with the assembly function in my 'real' project being an ISR or not --- but here is the real crux of the issue:

No matter what I did - the compiler would never put the .global myCfunc in the listing file (and thus in the obj). I had to manually add that.

When I turned all optimizations off the function was obviously not inlined anymore and thus I was able to put in the .global statement.

I can send you the c file, generated assembly file, and list file if you think that will help - and I can point out what function this is happening with - will you be able to glean what is going on?

I find it kindof strange that no matter what I did - even declaring the function

extern void myCfunc(void); // at the top of the file - it never was declared to be a global by the compiler.

Thanks,
johnw

Re: Get Started with the New Code Composer Essentials Version 3!

Aarti — Wed, 17 Jun 2009 15:32:47 GMT

John,

I created a test case to duplicate this using the template you provided, and can recreate the "undefined symbol" linker error if the project is compiled with optimization level 3 (which is the level at which automatic inlining is enabled). At lower optimization levels, the function is not inlined, hence the "undefined symbol" error does not appear.

I assume you are using opt level 3, is that correct?

If I add the --auto_inline=0 option, it prevents it from getting inlined and resolves the symbol correctly. Are you saying you tried this and did not work?

As per the Compiler Users Guide, using --no_inlining along with --opt_level 3 will still inline small functions. But the --auto_inline=0 option will disable it. Please let us know if this helps resolve the issue. If it does not, we may need to look at your project.

Re: Get Started with the New Code Composer Essentials Version 3!

johnw — Wed, 17 Jun 2009 10:12:08 GMT

I have something to report with the latest CCE v3.1 SR1 -

In my project I have a C file in which several assembly functions call functions that are in the C file (and vice-versa). One particular function in the C file was inlined, no matter what, by the compiler.

Note this function was declared at the global level but was only called by other c funcs in that file - plus was called by the assembly function.

I did the following:

In the tools dialogs:
set --auto_inline=0 and --no-inlining options.

In the C source file (and put in the header file too - just in case - before the function proto was defined):

#pragma FUNC_CANNOT_INLINE ( myCfunc );
#pragma FUNC_EXT_CALLED ( myCfunc ); /* did this when all else failed - didn't work */
// I was trying to 'force' the compiler to make that .global declaration - but it never did...

I reviewed the list files but the .global declaration that I needed was never there.

So, I had two choices - one, to make the assembly func a C func with some in line assembly or to make the c file into an assembly file.

I chose the latter - let the compiler generate the assembly file and I inserted the following:

.global myCfunc

That solved the unresolved external issue and the project is currently working.

It'll be somewhat counter productive I think to post the project files since the project is fairly large - but I think it will be somewhat easy to recreate this scenario. It is more of a nuisance than anything and hard to believe it isn't affecting others.

Something like this:

unsigned long some_counter = 0;

c();
b();

}

a();
c();

}

c{ // this is inlined, no matter what you do

some_counter++;

}

assembly file:

.global c ; reference c func from c source file

.def myAssemblyFunc

myAssemblyFunc:
                              calla c
                                          ...
                                          ret

func c will always be an unresolved external because the compiler will inline it no matter what.

Thanks And Regards,
johnw

Re: Get Started with the New Code Composer Essentials Version 3!

Kai — Fri, 12 Jun 2009 07:33:43 GMT

As suggested to me, I too suggest do an uninstallation and reinstall your CCE PRO again, then update with only the latest patch.

Re: Get Started with the New Code Composer Essentials Version 3!

lshanguo — Fri, 12 Jun 2009 06:24:35 GMT

Having same problem here; and not able to resolve so far.

I upgraded to CCE PRO SR1 (slac135f.zip) and

- CCE PRO CD ver 3.2.0.24.2

- Updated with slac135d for MSP430x54x support

- Updated with slac135e earlier, and works fine

- Updated with slac135f, and it does not works.

Running on Windows XP, NTFS.

Anyone facing similar problem here? What's the best installation sequence? Any instruction for upgrade?

Looking forward for a resolution.

Thanks