EmbeddedRelated.com
Forums
Memfault Beyond the Launch

Programming parts in production (IAR trouble)

Started by Dan Miner April 8, 2005
I have (nearly) finished developing the code for our product
using the IAR compiler.  Since I'm the only MSP430 programmer
at our company, I bought the USB dongle with the license so I
can compile from my office, the lab, or home.

Anyway now that the code is done, I am ready to release the 
binary file to production.  The snag is that IAR seems to only
support programming through C-SPY and would require us to buy
another expensive license.  Email to customer support has not 
been helpful.  As I see it, I have a few options:

1) Figure out which file format (coff; elf/dwarf; other) works
correctly with the free downloader from msp-gcc or similar.

2) Port all my code to msp-gcc or other commercial compiler that
is not so brain-dead when it comes to the needs of a production
environment.

3) Re-write enough chunks of my code to assembler so that the 
remaining portion in C can be compiled with the free IAR compiler
and its 4K limit.  (I already know which one Al would choose.  :-)

Can anyone out there help me?  I need to determine which of the
30+ IAR binary formats will work with <which?> download tool.

				- Dan Miner

Beginning Microcontrollers with the MSP430

> 
> 1) Figure out which file format (coff; elf/dwarf; other) works
> correctly with the free downloader from msp-gcc or similar.
> 

Choose the TI-txt file format. It works for TI's program BSLDemo and
pyjtag.




It shouldn't be too bad. If you are talking about the final code, IAR
must 
support some sort of HEX output, likely in the Intel HEX format. In which 
case, almost anyone's downloading tool should be able to handle that. Our 
compiler comes with a command line tool that a licensed user can
"give" to 
production people to use for this purpose and I am almost certain that most 
other compilers do as well. So you don't have to switch compiler unless you

want to.

At 08:57 AM 4/8/2005, Dan Miner wrote:


>I have (nearly) finished developing the code for
our product
>using the IAR compiler.  Since I'm the only MSP430 programmer
>at our company, I bought the USB dongle with the license so I
>can compile from my office, the lab, or home.
>
>Anyway now that the code is done, I am ready to release the
>binary file to production.  The snag is that IAR seems to only
>support programming through C-SPY and would require us to buy
>another expensive license.  Email to customer support has not
>been helpful.  As I see it, I have a few options:
>
>1) Figure out which file format (coff; elf/dwarf; other) works
>correctly with the free downloader from msp-gcc or similar.
>
>2) Port all my code to msp-gcc or other commercial compiler that
>is not so brain-dead when it comes to the needs of a production
>environment.
>
>3) Re-write enough chunks of my code to assembler so that the
>remaining portion in C can be compiled with the free IAR compiler
>and its 4K limit.  (I already know which one Al would choose.  :-)
>
>Can anyone out there help me?  I need to determine which of the
>30+ IAR binary formats will work with <which?> download tool.
>
>                                 - Dan Miner

// richard (This email is for mailing lists. To reach me directly, please 
use richard at imagecraft.com) 


Dan,
	Try the free MSPFET at http://mspfet.hellos.biz/  We use it
regularly for production programming of our MSP430 based VHF transceiver
and aviation intercoms. Works a treat and nothing more than a FET kit
and the hex file is required.


Ken Luxford
Lorien Developments



-----Original Message-----
From: Dan Miner [mailto:miner@mine...] 
Sent: Saturday, 9 April 2005 1:58 AM
To: 'msp430@'msp...'
Subject: [msp430] Programming parts in production (IAR trouble)



I have (nearly) finished developing the code for our product using the
IAR compiler.  Since I'm the only MSP430 programmer at our company, I
bought the USB dongle with the license so I can compile from my office,
the lab, or home.

Anyway now that the code is done, I am ready to release the 
binary file to production.  The snag is that IAR seems to only support
programming through C-SPY and would require us to buy another expensive
license.  Email to customer support has not 
been helpful.  As I see it, I have a few options:

1) Figure out which file format (coff; elf/dwarf; other) works correctly
with the free downloader from msp-gcc or similar.

2) Port all my code to msp-gcc or other commercial compiler that is not
so brain-dead when it comes to the needs of a production environment.

3) Re-write enough chunks of my code to assembler so that the 
remaining portion in C can be compiled with the free IAR compiler and
its 4K limit.  (I already know which one Al would choose.  :-)

Can anyone out there help me?  I need to determine which of the
30+ IAR binary formats will work with <which?> download tool.

				- Dan Miner


.

 
Yahoo! Groups Links



 










We use www.elprotronic.com USB programmer.  We have 2 of them, very fast, 
takes msp430.txt .s19 and .hex (as can be produced by IAR).  Going to buy 
some for our distributors too.


----- Original Message ----- 
From: "Dan Miner" <miner@mine...>
To: <msp430@msp4...>
Sent: Saturday, April 09, 2005 1:57 AM
Subject: [msp430] Programming parts in production (IAR trouble)


>
> I have (nearly) finished developing the code for our product
> using the IAR compiler.  Since I'm the only MSP430 programmer
> at our company, I bought the USB dongle with the license so I
> can compile from my office, the lab, or home.
>
> Anyway now that the code is done, I am ready to release the
> binary file to production.  The snag is that IAR seems to only
> support programming through C-SPY and would require us to buy
> another expensive license.  Email to customer support has not
> been helpful.  As I see it, I have a few options:
>
> 1) Figure out which file format (coff; elf/dwarf; other) works
> correctly with the free downloader from msp-gcc or similar.
>
> 2) Port all my code to msp-gcc or other commercial compiler that
> is not so brain-dead when it comes to the needs of a production
> environment.
>
> 3) Re-write enough chunks of my code to assembler so that the
> remaining portion in C can be compiled with the free IAR compiler
> and its 4K limit.  (I already know which one Al would choose.  :-)
>
> Can anyone out there help me?  I need to determine which of the
> 30+ IAR binary formats will work with <which?> download tool.
>
> - Dan Miner
>
>
> .
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
> =======================================================================>
Spam and Virus filtering by Mail Security      www.mailsecurity.net.au
> Forward undetected SPAM to:                   spam@spam...
> =======================================================================>
> 



======================================================================= Spam and
Virus filtering by Mail Security      www.mailsecurity.net.au
 Forward undetected SPAM to:                   spam@spam...
=======================================================================

Doesn't CSPY works without the dongle?

Stefan


-----Ursprgliche Nachricht-----
Von: Dan Miner [mailto:miner@mine...]
Gesendet am: Freitag, 8. April 2005 17:58
An: 'msp430@'msp...'
Betreff: [msp430] Programming parts in production (IAR trouble)


I have (nearly) finished developing the code for our product
using the IAR compiler.  Since I'm the only MSP430 programmer
at our company, I bought the USB dongle with the license so I
can compile from my office, the lab, or home.

Anyway now that the code is done, I am ready to release the 
binary file to production.  The snag is that IAR seems to only
support programming through C-SPY and would require us to buy
another expensive license.  Email to customer support has not 
been helpful.  As I see it, I have a few options:

1) Figure out which file format (coff; elf/dwarf; other) works
correctly with the free downloader from msp-gcc or similar.

2) Port all my code to msp-gcc or other commercial compiler that
is not so brain-dead when it comes to the needs of a production
environment.

3) Re-write enough chunks of my code to assembler so that the 
remaining portion in C can be compiled with the free IAR compiler
and its 4K limit.  (I already know which one Al would choose.  :-)

Can anyone out there help me?  I need to determine which of the
30+ IAR binary formats will work with <which?> download tool.

				- Dan Miner


.

 
Yahoo! Groups Links



 








Under the "Project Options", Category: XLINK, an output file and
format can be specified.  Personally, I got as far away from IAR as I
could a few years ago.  MSPGCC is really great for an open source
project, but doesn't produce thee tightest code.  Given the pricing of
the parts, it is easy to justify spending more on another compiler
that will squeeze the code into the next smaller part.  This very
group had a brisk discussion of the merits and drawbacks of each
package.  Check out the archives for some drama and info on the topic.

Matt Farley

> Anyway now that the code is done, I am ready to
release the 
> binary file to production.  The snag is that IAR seems to only
> support programming through C-SPY and would require us to buy
> another expensive license.  Email to customer support has not 
> been helpful.  ...
>




Thanks to everyone with suggestions and ideas.  The production
guy I need to work with is away on a business trip this week.
When he gets back, I'll try using the mspgcc download tools
with the proper binary generated by IAR.

				- Dan Miner

>    Date: Tue, 12 Apr 2005 12:23:13 -0000
>    From: "fqrley" <fqrley@fqrl...>
> Subject: Re: Programming parts in production (IAR trouble)
> 
> Under the "Project Options", Category: XLINK, an output file and
> format can be specified.  Personally, I got as far away from IAR as I
> could a few years ago.  MSPGCC is really great for an open source
> project, but doesn't produce thee tightest code.  Given the pricing of
> the parts, it is easy to justify spending more on another compiler
> that will squeeze the code into the next smaller part.  This very
> group had a brisk discussion of the merits and drawbacks of each
> package.  Check out the archives for some drama and info on the topic.
> 
> Matt Farley
> 
> > Anyway now that the code is done, I am ready to release the 
> > binary file to production.  The snag is that IAR seems to only
> > support programming through C-SPY and would require us to buy
> > another expensive license.  Email to customer support has not 
> > been helpful.  ...

On Fri, Apr 08, 2005 at 10:57:57AM -0500, Dan Miner wrote:
> 
> I have (nearly) finished developing the code for our product
> using the IAR compiler.  Since I'm the only MSP430 programmer
> at our company, I bought the USB dongle with the license so I
> can compile from my office, the lab, or home.

The TI gang programmer is great for this, it lets everyone else program
parts without interrupting you. All you have to do it load it with the
production image and it can program up to 8 devices at once with no PC
attached.

It also supports blowing the JTAG fuse.

Brian

-- 
---[Office 70.8F]--[Fridge 34.0F]---[Fozzy 83.3F]--[Coaster 70.6F]---
Linux Software Developer                     http://www.brianlane.com





Hi,

> > I have (nearly) finished developing the code
for our product
> > using the IAR compiler.  Since I'm the only MSP430 programmer
> > at our company, I bought the USB dongle with the license so I
> > can compile from my office, the lab, or home.
> 
> The TI gang programmer is great for this, it lets everyone else program
> parts without interrupting you. All you have to do it load it with the
> production image and it can program up to 8 devices at once with no PC
> attached.
> 
> It also supports blowing the JTAG fuse.

you can use every programmer/FET/BSL Tool ( 
http://www.gessler-electronic.com/msp430/ ,
http://llg.cubic.org/dmx43/bslsh.html )
etc. without a dongle.
I do prefer the free tools msp430-gdbproxy and msp430-gdb + ddd with the parport

FET but there are other free tools.

Regards,

Rolf




Memfault Beyond the Launch