I'm probably missing something very simple, but.. 

I'm running IAR workbench and I keep getting a checksum error during
linking 
with XLink. Here's the error:

Error[e3]: Corrupt file. Checksum failed in module ?getchar ( E:\Program 
Files\IAR Systems\ew23\430\LIB\cl430ks.r43 ). Linker checksum is 0x90b1, 
module checksum is 0x47e1

I'm just running a build-all, and I haven't the foggiest idea of which

direction to go to fix it. Any ideas would be appreciated. 

Thanks!
-Micah 	

Hello,

Are you using IAR workbench evaluation or professional? 

Are you programming in C or Assembly?

What MSP430 chip are you using?

Need to know these....


Thanks

  ----- Original Message ----- 
  From: Micah 
  To: msp430@msp4... 
  Sent: Monday, August 02, 2004 11:47 AM
  Subject: [msp430] newbie question.


  I'm probably missing something very simple, but.. 

  I'm running IAR workbench and I keep getting a checksum error during
linking 
  with XLink. Here's the error:

  Error[e3]: Corrupt file.  Checksum failed in module ?getchar ( E:\Program 
  Files\IAR Systems\ew23\430\LIB\cl430ks.r43 ). Linker checksum is 0x90b1, 
  module checksum is 0x47e1

  I'm just running a build-all, and I haven't the foggiest idea of
which 
  direction to go to fix it. Any ideas would be appreciated. 

  Thanks!
  -Micah       



  .




        
             
       
       


------
  . 

I'm using the professional, and the code is in C. The target chip is a

MSP430F169, the code I'm using is from their audio demo board. 

Thank you,
-Micah 


On Monday 02 August 2004 01:14 pm, IL wrote:
>  Hello,
>
>  Are you using IAR workbench evaluation or professional?
>
>  Are you programming in C or Assembly?
>
>  What MSP430 chip are you using?
>
>  Need to know these....
>
>
>  Thanks
>
>   ----- Original Message -----
>   From: Micah
>   To: msp430@msp4...
>   Sent: Monday, August 02, 2004 11:47 AM
>   Subject: [msp430] newbie question.
>
>
>   I'm probably missing something very simple, but..
>
>   I'm running IAR workbench and I keep getting a checksum error
during
> linking with XLink. Here's the error:
>
>   Error[e3]: Corrupt file. Checksum failed in module ?getchar (
> E:\Program Files\IAR Systems\ew23\430\LIB\cl430ks.r43 ). Linker checksum is
> 0x90b1, module checksum is 0x47e1
>
>   I'm just running a build-all, and I haven't the foggiest idea
of which
>   direction to go to fix it. Any ideas would be appreciated.
>
>   Thanks!
>   -Micah
>
>
>
>   .
>
>
>
>
>   
>  
>  
>  
>
>
> 
> ---
>--- .

Just in case, upon first installation, I compiled the little light flasher 
prog they tell you to try to test things out and successfully uploaded it. 
That all worked fine. I just talked to the TI rep, and he said I may be 
running the evaluation version of the software, and since I didn't pay them

for it, that would actually make sense, so perhaps there's a code size
limit 
or something that I'm running into? 

-Micah 

On Monday 02 August 2004 01:41 pm, Micah wrote:
>  I'm using the professional, and the code is in C. The target chip is
a
>  MSP430F169, the code I'm using is from their audio demo board.
>
>  Thank you,
>  -Micah
>
>  On Monday 02 August 2004 01:14 pm, IL wrote:
>  > Hello,
>  >
>  > Are you using IAR workbench evaluation or professional?
>  >
>  > Are you programming in C or Assembly?
>  >
>  > What MSP430 chip are you using?
>  >
>  > Need to know these....
>  >
>  >
>  > Thanks
>  >
>  >  ----- Original Message -----
>  >  From: Micah
>  >  To: msp430@msp4...
>  >  Sent: Monday, August 02, 2004 11:47 AM
>  >  Subject: [msp430] newbie question.
>  >
>  >
>  >  I'm probably missing something very simple, but..
>  >
>  >  I'm running IAR workbench and I keep getting a checksum error
during
>  > linking with XLink. Here's the error:
>  >
>  >  Error[e3]: Corrupt file. Checksum failed in module ?getchar (
>  > E:\Program Files\IAR Systems\ew23\430\LIB\cl430ks.r43 ). Linker
checksum
>  > is 0x90b1, module checksum is 0x47e1
>  >
>  >  I'm just running a build-all, and I haven't the foggiest
idea of
>  > which direction to go to fix it. Any ideas would be appreciated.
>  >
>  >  Thanks!
>  >  -Micah
>  >
>  >
>  >
>  >  .
>  >
>  >
>  >
>  >
>  >  
>  > 
>  > 
>  > 
>  >
>  >
>  >
>  > 
>  >--- --- .
>
>  .
>
>
>
>
>
>
> 
>
>
>
>
>
>
>
>  .

Okay, thanks for the info. I'll have to measure how big the code is, but
I'll 
assume that's whats wrong. 

Has anyone used the GCC compiler for linux that is out there? I'm used to
GCC 
for PC stuff, so It hough that might be easier..

-Micah 

On Monday 02 August 2004 07:13 pm, IL wrote:
>  Yes, the evaluation edition of IAR workbench has a code size limit, and
> has far less features than the professional edition. The limit is 2 KB for
> C-coded programs only. There is no limit on assembly coded program on
> either edition. But then, you want to use IAR for coding in C, right?
>
>  Since you got the light flashing, it makes sense to assume you know how to
> set the right chip description under project >> options. So, you
should be
> good to go now, and write other C programs.
>
>  I wrote a LCD driver code for my MSP430F449 using the evaluation version
> and it was simply frustrating when I ran out of the 2 KB of evaluation
> space. But still, 2 KB is a fair of code to test the performance of IAR
> workbench, and if you are just beginning out on your '169, it will
take
> some time until you encounter this limit. Enough said, the limited space
> makes it difficult to deploy full-blown programs of greater complexity.
>
>  IL
>
>
>
>   ----- Original Message -----
>   From: Micah
>   To: msp430@msp4...
>   Sent: Monday, August 02, 2004 3:00 PM
>   Subject: Re: [msp430] newbie question.
>
>
>
>   Just in case, upon first installation, I compiled the little light
> flasher prog they tell you to try to test things out and successfully
> uploaded it. That all worked fine. I just talked to the TI rep, and he said
> I may be running the evaluation version of the software, and since I
didn't
> pay them for it, that would actually make sense, so perhaps there's a
code
> size limit or something that I'm running into?
>
>   -Micah
>
>   On Monday 02 August 2004 01:41 pm, Micah wrote:
>   > I'm using the professional, and the code is in C. The target
chip is
> a > MSP430F169, the code I'm using is from their audio demo board.
>
>   > Thank you,
>   > -Micah
>   >
>   > On Monday 02 August 2004 01:14 pm, IL wrote:
>   > > Hello,
>   > >
>   > > Are you using IAR workbench evaluation or professional?
>   > >
>   > > Are you programming in C or Assembly?
>   > >
>   > > What MSP430 chip are you using?
>   > >
>   > > Need to know these....
>   > >
>   > >
>   > > Thanks
>   > >
>   > > ----- Original Message -----
>   > > From: Micah
>   > > To: msp430@msp4...
>   > > Sent: Monday, August 02, 2004 11:47 AM
>   > > Subject: [msp430] newbie question.
>   > >
>   > >
>   > > I'm probably missing something very simple, but..
>   > >
>   > > I'm running IAR workbench and I keep getting a
checksum error
> during > > linking with XLink. Here's the error:
>   > >
>   > > Error[e3]: Corrupt file. Checksum failed in module
?getchar (
>   > > E:\Program Files\IAR Systems\ew23\430\LIB\cl430ks.r43 ).
Linker
> checksum > > is 0x90b1, module checksum is 0x47e1
>   > >
>   > > I'm just running a build-all, and I haven't the
foggiest idea of
>   > > which direction to go to fix it. Any ideas would be
appreciated.
>   > >
>   > > Thanks!
>   > > -Micah
>   > >
>   > >
>   > >
>   > > .
>   > >
>   > >
>   > >
>   > >
>   > > 
>   > >
>   > >
>   > >
>   > >
>   > >
>   > >
>   > >
>  >
> >--- --- .
>
>
>   .
>
>
>
>
>   
>  
>  
>  
>
>
> 
> ---
>--- .

Yes, the evaluation edition of IAR workbench has a code size limit, and has
far less features than the professional edition. The limit is 2 KB for C-coded
programs only. There is no limit on assembly coded program on either edition.
But then, you want to use IAR for coding in C, right?

Since you got the light flashing, it makes sense to assume you know how to set
the right chip description under project >> options. So, you should be
good to go now, and write other C programs.

I wrote a LCD driver code for my MSP430F449 using the evaluation version and it
was simply frustrating when I ran out of the 2 KB of evaluation space. But
still, 2 KB is a fair of code to test the performance of IAR workbench, and if
you are just beginning out on your '169, it will take some time until you
encounter this limit. Enough said, the limited space makes it difficult to
deploy full-blown programs of greater complexity.

IL



  ----- Original Message ----- 
  From: Micah 
  To: msp430@msp4... 
  Sent: Monday, August 02, 2004 3:00 PM
  Subject: Re: [msp430] newbie question.



  Just in case, upon first installation, I compiled the little light flasher 
  prog they tell you to try to test things out and successfully uploaded it. 
  That all worked fine. I just talked to the TI rep, and he said I may be 
  running the evaluation version of the software, and since I didn't pay
them 
  for it, that would actually make sense, so perhaps there's a code size
limit 
  or something that I'm running into? 

  -Micah 

  On Monday 02 August 2004 01:41 pm, Micah wrote:
  >  I'm using the professional, and the code is in C. The target chip
is a
  >  MSP430F169, the code I'm using is from their audio demo board.
  >
  >  Thank you,
  >  -Micah
  >
  >  On Monday 02 August 2004 01:14 pm, IL wrote:
  >  >  Hello,
  >  >
  >  >  Are you using IAR workbench evaluation or professional?
  >  >
  >  >  Are you programming in C or Assembly?
  >  >
  >  >  What MSP430 chip are you using?
  >  >
  >  >  Need to know these....
  >  >
  >  >
  >  >  Thanks
  >  >
  >  >    ----- Original Message -----
  >  >    From: Micah
  >  >    To: msp430@msp4...
  >  >    Sent: Monday, August 02, 2004 11:47 AM
  >  >    Subject: [msp430] newbie question.
  >  >
  >  >
  >  >    I'm probably missing something very simple, but..
  >  >
  >  >    I'm running IAR workbench and I keep getting a checksum
error during
  >  > linking with XLink. Here's the error:
  >  >
  >  >    Error[e3]: Corrupt file.  Checksum failed in module ?getchar (
  >  > E:\Program Files\IAR Systems\ew23\430\LIB\cl430ks.r43 ). Linker
checksum
  >  > is 0x90b1, module checksum is 0x47e1
  >  >
  >  >    I'm just running a build-all, and I haven't the
foggiest idea of
  >  > which direction to go to fix it. Any ideas would be appreciated.
  >  >
  >  >    Thanks!
  >  >    -Micah      
  >  >
  >  >
  >  >
  >  >    .
  >  >
  >  >
  >  >
  >  >
  >  >          
  >  >              
  >  >        
  >  >        
  >  >
  >  >
  >  >
  >  > 
  >  >--- --- .
  >
  >  .
  >
  >
  >
  >
  >
  >
  > 
  >
  >
  >
  >
  >
  >
  >
  >  .


  .




        
             
       
       


------
  . 

Hi,


>Has anyone used the GCC compiler for linux that is
out there? I'm used to GCC 
>for PC stuff, so It hough that might be easier..
>  
>

Yes, works fine.  http://www.mikrocontroller.net/wiki/MSPGCC

Rolf