Re: Asm source code page?

"[email protected] [msp430]" <[email protected]> Mon, 11 Jan 2016 19:13:53 -0500
Newsgroups gmane.comp.hardware.texas-instruments.msp430.discuss
Message-ID <[email protected]>
------=_Part_12372_1561705512.1452557633590
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

sorry for my jumping in
i had a crash and in 2 computers a very big storm with lightnings so everyt=
hing is lost
but i have some programmed chips that i uploaded from them an  image as TI-=
txt  files
can i disassemble them with kickstart
i thank you for your consideration
Ezra

=20

=20

=20

-----Original Message-----
From: Onestone [email protected] [msp430] <[email protected]>
To: msp430 <[email protected]>
Sent: Tue, Jan 12, 2016 1:47 am
Subject: Re: [msp430] Asm source code page?



=20=20
=20=20=20=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
        Hi Jon, the strange stuff I talk about was a      tendency to crash=
 if you disconnected power from the target unit      accidentally. Or to lo=
se lose contact and have to be reset or      restarted if the USB lost cont=
act. I even had one version that      would crash my computer regularly. I =
tested all of these across at      least 2 machines and a laptop, but that =
was a long time ago. It      has been solid for quite a few years now. In t=
he very early days      of the flash parts you actually had to match the Ki=
ckstart version      to the batch number, but that was mostly cured when Ti=
 moved from      the clunky old serial port JTAG to the USB one.
=20=20=20=20=20=20
      I too am extremely grateful to IAR for fielding such a well      roun=
ded tool for free for all these years. I have written hundreds      of prog=
rams using it, and mostly it has been a very enjoyable      process for me.
=20=20=20=20=20=20
      Al
=20=20=20=20
=20=20=20=20
On 12/01/2016 7:59 AM, Jon Kirwan      [email protected] [msp430] wr=
ote:
=20=20=20=20
=20=20=20=20
=20=20=20=20=20=20
On Mon, 11 Jan 2016 19:33:47 +1030, Al wrote:


=20=20=20=20=20=20
=20=20=20=20=20=20=20=20
I Totally agree with Jon.

=20=20=20=20=20=20
=20=20=20=20=20=20
  :)


=20=20=20=20=20=20
=20=20=20=20=20=20=20=20
IAR's assembler is excellent, does everything=20
I want, is unlimited, is free, and since I don't use any libraries from=20
third parties there are no royalty issues.

=20=20=20=20=20=20
=20=20=20=20=20=20
That assembler and linker tool-pair is good. I've used a LOT
of assemblers in my life and have written a few, as well.
This one from IAR is about as good as assemblers for micros
usually get. The abstract segmentation model is great. The
macro facility could be better, but I consider it "good
enough for most things." (I can also use M4 or some other
tool on the source where I feel there are some limitations.
Such tools won't be fluent with the semantics but they may be
fruitfully used. I just haven't felt enough of a need yet,
since IAR's capabilities are good enough for now.)


=20=20=20=20=20=20
=20=20=20=20=20=20=20=20
The IDE is straightforward, and quite good.

=20=20=20=20=20=20
=20=20=20=20=20=20
It's remarkably easy to get started using and remains very
capable as you advance further over time. It just wears well
over time. They've done a very good job on its design. And,
fortunately for some of us, have decided to offer a fully
functional toolset for assembler programmers at no charge.
I'm in debt to them for this fact.

(I'm also in debt for another reason -- I've never needed
more than an additional 4k of C generated code for an MSP430
project, so the KickStart has been "good enough" for all my
project uses so far.)


=20=20=20=20=20=20
=20=20=20=20=20=20=20=20
It used to do some strange things, but they seem to have=20
been cleaned up over the years, either that or I subconsciously avoid=20
them!

=20=20=20=20=20=20
=20=20=20=20=20=20
I haven't found anything that was "strange." I have found
things that took a moment to consider before I fully
understood them. But once I gathered up the conceptual model
they made good sense to me.

The only "strange" things are things I've done myself with
their toolset. For example, I needed a way to find the
largest common divisor for a pair of configuration parameters
to help me set up a clocking system that would serve two
purposes at once with only integer multiplier differences in
their operation. I hacked up a MACRO tool to do exactly that,
too. Worked perfectly. Now, someone looking at it would see
"strange" there, I suppose. But that's my fault, not IARs!


=20=20=20=20=20=20
=20=20=20=20=20=20=20=20
I find the syntax is more in line with the vast majority of=20
assemblers I've used over the last too many years, no strange things.

=20=20=20=20=20=20
=20=20=20=20=20=20
That's pretty much my feeling, too.


=20=20=20=20=20=20
=20=20=20=20=20=20=20=20
Their header files for each processor are also quite good, but large=20
because they are general use for C, c++ and assembler, so I personally=20
always clean out all the stuff I am unlikely to use, add some stuff that=20
I personally like to use, and rename the file, so I have an original=20
version incase I ever decide to mix assembly and C for example.

=20=20=20=20=20=20
=20=20=20=20=20=20
Hmm. So far, I've not bothered with that. In part, perhaps,
because I haven't done as much as you have and haven't
reached a situation where the trouble would have been worth
it. In part, perhaps, because I tend not to change standard
facilities unless I can clearly justify the change. I'd
rather use an additional file I create and add it to the
inclusion list. But again, you probably have a wider array of
usages than I do and I may very well have made similar
choices if I had faced similar situations, too.

Jon


=20=20=20=20=20=20
=20=20=20=20=20=20=20=20
Cheers

Al

On 11/01/2016 6:15 AM, Jon Kirwan [email protected] [msp430] wrote:

=20=20=20=20=20=20=20=20
=20=20=20=20=20=20=20=20=20=20
On Sat, 9 Jan 2016 22:47:23 -0800, Craig Carmichael wrote:


=20=20=20=20=20=20=20=20=20=20
=20=20=20=20=20=20=20=20=20=20=20=20
... ideas for web pages of sample code in Asm?

=20=20=20=20=20=20=20=20=20=20
=20=20=20=20=20=20=20=20=20=20
Just as an additional note...

If you are interested in writing assembly-only projects for
the MSP430 and MSP430X families, I'd recommend using IAR's
Kickstart tools. Their assembler is quite general-purpose and
does NOT have any code size limitations at all. See:

http://supp.iar.com/FilesPublic/UPDINFO/004578/infocenter/product_packages.=
html

where the 2nd bullet under the Kickstart heading says, "The
IAR Assembler delivered is the full version without any
restrictions" and the 3rd bullet expands, "The IAR XLINK
Linker will link ... an unlimited amount of code originating
from assembly code." (The 4th bullet adds, "The IAR KickStart
C-SPY Simulator ... is unlimited in the amount of assembly
code read.") This pretty much means you get an excellent
assembler/linker toolset, plus a very nice IDE and debugger
for coding purposes and ZERO cost to you. I've used IAR for
assembly coding development and I really like the tools a
lot, as they present a very clean, orthogonal design with all
the features you need. Other assembler tools I've used, off
and on, tend to have odd "limitations" which are frustrating
at times. IAR's tools "just work well." Never wished for a
feature that I couldn't already find in IAR's assembler +
linker toolset.

You can also explore C/C++ with IAR's tools, but the free
Kickstart version does limit your final application size.
IAR asks a "fairly high price" for unlimited C/C++ code
sizes. If you do plan on mixing C and assembly and plan on
developing larger applications then you should consider other
tools for a cost/benefit analysis. A starting point might be
TI's page here:

http://www.ti.com/lsds/ti/microcontrollers_16-bit_32-bit/msp/tools_software=
.page

However, be aware that this page in no way provides all your
options. Rowley and ImageCraft are just two such examples
that you don't see there:

http://www.rowley.co.uk/msp430/
https://www.imagecraft.com/devtools_MSP430.html

I'm sure there are others, as well, that aren't included in
the TI page.

If you are doing this all as a hobby, then you are free to
make your own choices about assembly-only or mixed coding
styles. Whatever makes you happy works just fine.

If you have your own product/product-line in mind, then you
need to be aware of licensing issues (libraries used, as well
as compiler generated output) for the tools you apply. I
believe you can use the IAR assembler/linker toolchain for
commercial products without paying them a fee, so long as you
are careful about library use (not using any library other
than public domain would be safer.) It sounds like you might
be in this frame of mind, but it is hard to tell.

For professional contract work, you will want to be able to
support mixed assembly and C/C++. Clients deserve to have the
widest range of options available for their project
development so that the overall development process can be
optimized for them, weighing all conditions appropriate to
their circumstances. You should then carefully study the
various commercial options. But you should ALSO contact the
vendors, too, and speak or write to a human there and get a
feel for what contact and support will be like after you buy
their tools. Most MSP430 vendors should be pretty good, I
think. But it helps to make contact and see how things play
out before making a final decision and spending your money.

As an employee in an organization with more than one
programmer, which does NOT sound like your situation, you do
what has been established by careful consideration of your
team members. If you are a sole employee, then I suppose you
get to make your own choices but you need to make them well
for those depending on you.

Jon

=20=20=20=20=20=20=20=20
=20=20=20=20=20=20
=20=20=20=20=20=20
------------------------------------
Posted by: Jon Kirwan <[email protected]>
------------------------------------

To unsubscribe from the msp430 group, send an email to:
[email protected]


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

Yahoo Groups Links





=20=20=20=20
=20=20=20=20
=20=20
=20=20=20=20
=20=20=20=20=20=20=20=20=20=20=20=20=20

=20=20


------=_Part_12372_1561705512.1452557633590
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit





<head>

<style type="text/css">
<!--

/* start of attachment style */
       .ygrp-photo-title{
         clear: both;
         font-size: smaller;
         height: 15px;
         overflow: hidden;
         text-align: center;
         width: 75px;
       }
       div.ygrp-photo{
         background-position: center;
         background-repeat: no-repeat;
         background-color: white;
         border: 1px solid black;
         height: 62px;
         width: 62px;
       }

       div.photo-title 
         a,
         div.photo-title a:active,
         div.photo-title a:hover,
         div.photo-title a:visited {
           text-decoration: none; 
       }

       div.attach-table div.attach-row {
         clear: both;
       }

       div.attach-table div.attach-row div {
         float: left;
         /* margin: 2px;*/
       }

       p {
         clear: both;
         padding: 15px 0 3px 0;
	 overflow: hidden;
       }

       div.ygrp-file {
         width: 30px;
         valign: middle;
       }
       div.attach-table div.attach-row div div a {
         text-decoration: none;
       }

       div.attach-table div.attach-row div div span {
         font-weight: normal;
       }

       div.ygrp-file-title {
         font-weight: bold;
       }
 /* end of attachment style */
        -->
        </style>
        </head>
<html>
<head>
<style type="text/css">
<!--
#ygrp-mkp {
  border: 1px solid #d8d8d8;
  font-family: Arial;
  margin: 10px 0;
  padding: 0 10px;
}

#ygrp-mkp hr {
  border: 1px solid #d8d8d8;
}

#ygrp-mkp #hd {
  color: #628c2a;
  font-size: 85%;
  font-weight: 700;
  line-height: 122%;
  margin: 10px 0;
}

#ygrp-mkp #ads {
  margin-bottom: 10px;
}

#ygrp-mkp .ad {
  padding: 0 0;
}

#ygrp-mkp .ad p {
  margin: 0;
}

#ygrp-mkp .ad a {
  color: #0000ff;
  text-decoration: none;
}
-->
</style>
</head>
<body>



<!-- |**|begin egp html banner|**| -->

<br><br>

<!-- |**|end egp html banner|**| -->


<font color='black' size='2' face='arial'>so<font size="2">rry for my jumping in<br>
i had a crash and in 2 computers a very big storm with lightnings so everything is lost<br>
but i have some programmed chips that i uploaded from them an&nbsp; image as TI-txt&nbsp; files<br>
can i disassemble them with kickstart<br>
i thank you for your consideration<br>
Ezra<br>
</font>

<div> <br>

</div>



<div> <br>

</div>



<div> <br>

</div>



<div style="font-family:arial,helvetica;font-size:10pt;color:black">-----Original Message-----<br>

From: Onestone [email protected] [msp430] &lt;[email protected]&gt;<br>

To: msp430 &lt;[email protected]&gt;<br>

Sent: Tue, Jan 12, 2016 1:47 am<br>

Subject: Re: [msp430] Asm source code page?<br>

<br>






<div id="AOLMsgPart_2_ccb1c373-29c1-43e1-b3ba-773293e71bc2">


<div style="background-color: #fff;" class="aolReplacedBody">
<span style="display:none">&nbsp;</span>




<div id="ygrp-mlmsg" style="position:relative;">
  

<div id="ygrp-msg" style="z-index: 1;">


    

<div id="ygrp-text">
      
      
      

<div>
  
  
    <font size="-1">Hi Jon, the strange stuff I talk about was a
      tendency to crash if you disconnected power from the target unit
      accidentally. Or to lose lose contact and have to be reset or
      restarted if the USB lost contact. I even had one version that
      would crash my computer regularly. I tested all of these across at
      least 2 machines and a laptop, but that was a long time ago. It
      has been solid for quite a few years now. In the very early days
      of the flash parts you actually had to match the Kickstart version
      to the batch number, but that was mostly cured when Ti moved from
      the clunky old serial port JTAG to the USB one.<br>


      <br>


      I too am extremely grateful to IAR for fielding such a well
      rounded tool for free for all these years. I have written hundreds
      of programs using it, and mostly it has been a very enjoyable
      process for me.<br>


      <br>


      Al<br>


    </font><br>


    </div>



<div class="moz-cite-prefix">On 12/01/2016 7:59 AM, Jon Kirwan
      <a class="moz-txt-link-abbreviated" target="_blank" href="mailto:[email protected]">[email protected]</a> [msp430] wrote:<br>


    </div>


    <blockquote cite="about:blank">
      <pre>On Mon, 11 Jan 2016 19:33:47 +1030, Al wrote:

</pre>
      <blockquote>
        <pre>I Totally agree with Jon.
</pre>
      </blockquote>
      <pre>  :)

</pre>
      <blockquote>
        <pre>IAR's assembler is excellent, does everything 
I want, is unlimited, is free, and since I don't use any libraries from 
third parties there are no royalty issues.
</pre>
      </blockquote>
      <pre>That assembler and linker tool-pair is good. I've used a LOT
of assemblers in my life and have written a few, as well.
This one from IAR is about as good as assemblers for micros
usually get. The abstract segmentation model is great. The
macro facility could be better, but I consider it "good
enough for most things." (I can also use M4 or some other
tool on the source where I feel there are some limitations.
Such tools won't be fluent with the semantics but they may be
fruitfully used. I just haven't felt enough of a need yet,
since IAR's capabilities are good enough for now.)

</pre>
      <blockquote>
        <pre>The IDE is straightforward, and quite good.
</pre>
      </blockquote>
      <pre>It's remarkably easy to get started using and remains very
capable as you advance further over time. It just wears well
over time. They've done a very good job on its design. And,
fortunately for some of us, have decided to offer a fully
functional toolset for assembler programmers at no charge.
I'm in debt to them for this fact.

(I'm also in debt for another reason -- I've never needed
more than an additional 4k of C generated code for an MSP430
project, so the KickStart has been "good enough" for all my
project uses so far.)

</pre>
      <blockquote>
        <pre>It used to do some strange things, but they seem to have 
been cleaned up over the years, either that or I subconsciously avoid 
them!
</pre>
      </blockquote>
      <pre>I haven't found anything that was "strange." I have found
things that took a moment to consider before I fully
understood them. But once I gathered up the conceptual model
they made good sense to me.

The only "strange" things are things I've done myself with
their toolset. For example, I needed a way to find the
largest common divisor for a pair of configuration parameters
to help me set up a clocking system that would serve two
purposes at once with only integer multiplier differences in
their operation. I hacked up a MACRO tool to do exactly that,
too. Worked perfectly. Now, someone looking at it would see
"strange" there, I suppose. But that's my fault, not IARs!

</pre>
      <blockquote>
        <pre>I find the syntax is more in line with the vast majority of 
assemblers I've used over the last too many years, no strange things.
</pre>
      </blockquote>
      <pre>That's pretty much my feeling, too.

</pre>
      <blockquote>
        <pre>Their header files for each processor are also quite good, but large 
because they are general use for C, c++ and assembler, so I personally 
always clean out all the stuff I am unlikely to use, add some stuff that 
I personally like to use, and rename the file, so I have an original 
version incase I ever decide to mix assembly and C for example.
</pre>
      </blockquote>
      <pre>Hmm. So far, I've not bothered with that. In part, perhaps,
because I haven't done as much as you have and haven't
reached a situation where the trouble would have been worth
it. In part, perhaps, because I tend not to change standard
facilities unless I can clearly justify the change. I'd
rather use an additional file I create and add it to the
inclusion list. But again, you probably have a wider array of
usages than I do and I may very well have made similar
choices if I had faced similar situations, too.

Jon

</pre>
      <blockquote>
        <pre>Cheers

Al

On 11/01/2016 6:15 AM, Jon Kirwan <a class="moz-txt-link-abbreviated" target="_blank" href="mailto:[email protected]">[email protected]</a> [msp430] wrote:
</pre>
        <blockquote>
          <pre>On Sat, 9 Jan 2016 22:47:23 -0800, Craig Carmichael wrote:

</pre>
          <blockquote>
            <pre>... ideas for web pages of sample code in Asm?
</pre>
          </blockquote>
          <pre>Just as an additional note...

If you are interested in writing assembly-only projects for
the MSP430 and MSP430X families, I'd recommend using IAR's
Kickstart tools. Their assembler is quite general-purpose and
does NOT have any code size limitations at all. See:

<a class="moz-txt-link-freetext" target="_blank" href="http://supp.iar.com/FilesPublic/UPDINFO/004578/infocenter/product_packages.html">http://supp.iar.com/FilesPublic/UPDINFO/004578/infocenter/product_packages.html</a>

where the 2nd bullet under the Kickstart heading says, "The
IAR Assembler delivered is the full version without any
restrictions" and the 3rd bullet expands, "The IAR XLINK
Linker will link ... an unlimited amount of code originating
from assembly code." (The 4th bullet adds, "The IAR KickStart
C-SPY Simulator ... is unlimited in the amount of assembly
code read.") This pretty much means you get an excellent
assembler/linker toolset, plus a very nice IDE and debugger
for coding purposes and ZERO cost to you. I've used IAR for
assembly coding development and I really like the tools a
lot, as they present a very clean, orthogonal design with all
the features you need. Other assembler tools I've used, off
and on, tend to have odd "limitations" which are frustrating
at times. IAR's tools "just work well." Never wished for a
feature that I couldn't already find in IAR's assembler +
linker toolset.

You can also explore C/C++ with IAR's tools, but the free
Kickstart version does limit your final application size.
IAR asks a "fairly high price" for unlimited C/C++ code
sizes. If you do plan on mixing C and assembly and plan on
developing larger applications then you should consider other
tools for a cost/benefit analysis. A starting point might be
TI's page here:

<a class="moz-txt-link-freetext" target="_blank" href="http://www.ti.com/lsds/ti/microcontrollers_16-bit_32-bit/msp/tools_software.page">http://www.ti.com/lsds/ti/microcontrollers_16-bit_32-bit/msp/tools_software.page</a>

However, be aware that this page in no way provides all your
options. Rowley and ImageCraft are just two such examples
that you don't see there:

<a class="moz-txt-link-freetext" target="_blank" href="http://www.rowley.co.uk/msp430/">http://www.rowley.co.uk/msp430/</a>
<a class="moz-txt-link-freetext" target="_blank" href="https://www.imagecraft.com/devtools_MSP430.html">https://www.imagecraft.com/devtools_MSP430.html</a>

I'm sure there are others, as well, that aren't included in
the TI page.

If you are doing this all as a hobby, then you are free to
make your own choices about assembly-only or mixed coding
styles. Whatever makes you happy works just fine.

If you have your own product/product-line in mind, then you
need to be aware of licensing issues (libraries used, as well
as compiler generated output) for the tools you apply. I
believe you can use the IAR assembler/linker toolchain for
commercial products without paying them a fee, so long as you
are careful about library use (not using any library other
than public domain would be safer.) It sounds like you might
be in this frame of mind, but it is hard to tell.

For professional contract work, you will want to be able to
support mixed assembly and C/C++. Clients deserve to have the
widest range of options available for their project
development so that the overall development process can be
optimized for them, weighing all conditions appropriate to
their circumstances. You should then carefully study the
various commercial options. But you should ALSO contact the
vendors, too, and speak or write to a human there and get a
feel for what contact and support will be like after you buy
their tools. Most MSP430 vendors should be pretty good, I
think. But it helps to make contact and see how things play
out before making a final decision and spending your money.

As an employee in an organization with more than one
programmer, which does NOT sound like your situation, you do
what has been established by careful consideration of your
team members. If you are a sole employee, then I suppose you
get to make your own choices but you need to make them well
for those depending on you.

Jon
</pre>
        </blockquote>
      </blockquote>
      <pre>------------------------------------
Posted by: Jon Kirwan <a class="moz-txt-link-rfc2396E" target="_blank" href="mailto:[email protected]">&lt;[email protected]&gt;</a>
------------------------------------

To unsubscribe from the msp430 group, send an email to:
<a class="moz-txt-link-abbreviated" target="_blank" href="mailto:[email protected]">[email protected]</a>


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

Yahoo Groups Links

&lt;*&gt; To visit your group on the web, go to:
    <a class="moz-txt-link-freetext" target="_blank" href="http://groups.yahoo.com/group/msp430/">http://groups.yahoo.com/group/msp430/</a>

&lt;*&gt; Your email settings:
    Individual Email | Traditional

&lt;*&gt; To change settings online go to:
    <a class="moz-txt-link-freetext" target="_blank" href="http://groups.yahoo.com/group/msp430/join">http://groups.yahoo.com/group/msp430/join</a>
    (Yahoo! ID required)

&lt;*&gt; To change settings via email:
    <a class="moz-txt-link-abbreviated" target="_blank" href="mailto:[email protected]">[email protected]</a> 
    <a class="moz-txt-link-abbreviated" target="_blank" href="mailto:[email protected]">[email protected]</a>

&lt;*&gt; To unsubscribe from this group, send an email to:
    <a class="moz-txt-link-abbreviated" target="_blank" href="mailto:[email protected]">[email protected]</a>

&lt;*&gt; Your use of Yahoo Groups is subject to:
    <a class="moz-txt-link-freetext" target="_blank" href="https://info.yahoo.com/legal/us/yahoo/utos/terms/">https://info.yahoo.com/legal/us/yahoo/utos/terms/</a>


</pre>
    </blockquote>
    <br>


  



<div></div>



    </div>


     

    
    

<div style="color: #fff; height: 0;"></div>








  <style type="text/css">#AOLMsgPart_2_ccb1c373-29c1-43e1-b3ba-773293e71bc2 td{color: black;}       .aolReplacedBody #ygrp-mkp {   border: 1px solid #d8d8d8;   font-family: Arial;   margin: 10px 0;   padding: 0 10px; }  .aolReplacedBody #ygrp-mkp hr {   border: 1px solid #d8d8d8; }  .aolReplacedBody #ygrp-mkp #hd {   color: #628c2a;   font-size: 85%;   font-weight: 700;   line-height: 122%;   margin: 10px 0; }  .aolReplacedBody #ygrp-mkp #ads {   margin-bottom: 10px; }  .aolReplacedBody #ygrp-mkp .ad {   padding: 0 0; }  .aolReplacedBody #ygrp-mkp .ad p {   margin: 0; }  .aolReplacedBody #ygrp-mkp .ad a {   color: #0000ff;   text-decoration: none; }   .aolReplacedBody #ygrp-sponsor #ygrp-lc {   font-family: Arial; }  .aolReplacedBody #ygrp-sponsor #ygrp-lc #hd {   margin: 10px 0px;   font-
 weight: 700;   font-size: 78%;   line-height: 122%; }  .aolReplacedBody #ygrp-sponsor #ygrp-lc .ad {   margin-bottom: 10px;   padding: 0 0; }    .aolReplacedBody #actions {     font-family: Verdana;     font-size: 11px;     padding: 10px 0;   }    .aolReplacedBody #activity {     background-color: #e0ecee;     float: left;     font-family: Verdana;     font-size: 10px;     padding: 10px;   }    .aolReplacedBody #activity span {     font-weight: 700;   }    .aolReplacedBody #activity span:first-child {     text-transform: uppercase;   }    .aolReplacedBody #activity span a {     color: #5085b6;     text-decoration: none;   }    .aolReplacedBody #activity span span {     color: #ff7900;   }    .aolReplacedBody #activity span .underline {     text-decoration: underline;   }    .aolReplacedB
 ody .attach {     clear: both;     display: table;     font-family: Arial;     font-size: 12px;     padding: 10px 0;     width: 400px;   }    .aolReplacedBody .attach div a {     text-decoration: none;   }    .aolReplacedBody .attach img {     border: none;     padding-right: 5px;   }    .aolReplacedBody .attach label {     display: block;     margin-bottom: 5px;   }    .aolReplacedBody .attach label a {     text-decoration: none;   }      .aolReplacedBody blockquote {     margin: 0 0 0 4px;   }    .aolReplacedBody .bold {     font-family: Arial;     font-size: 13px;     font-weight: 700;   }    .aolReplacedBody .bold a {     text-decoration: none;   }    .aolReplacedBody dd.last p a {     font-family: Verdana;     font-weight: 700;   }    .aolReplacedBody dd.last p span {     margin-rig
 ht: 10px;     font-family: Verdana;     font-weight: 700;   }    .aolReplacedBody dd.last p span.yshortcuts {     margin-right: 0;   }    .aolReplacedBody div.attach-table div div a {     text-decoration: none;   }    .aolReplacedBody div.attach-table {     width: 400px;   }    .aolReplacedBody div.file-title a,.aolReplacedBody  div.file-title a:active,.aolReplacedBody  div.file-title a:hover,.aolReplacedBody  div.file-title a:visited {     text-decoration: none;   }    .aolReplacedBody div.photo-title a,.aolReplacedBody  div.photo-title a:active,.aolReplacedBody  div.photo-title a:hover,.aolReplacedBody  div.photo-title a:visited {     text-decoration: none;   }    .aolReplacedBody div#ygrp-mlmsg #ygrp-msg p a span.yshortcuts {     font-family: Verdana;     font-size: 10px;     font-wei
 ght: normal;   }    .aolReplacedBody .green {     color: #628c2a;   }    .aolReplacedBody .MsoNormal {     margin: 0 0 0 0;   }    .aolReplacedBody o {     font-size: 0;   }    .aolReplacedBody #photos div {     float: left;     width: 72px;   }    .aolReplacedBody #photos div div {     border: 1px solid #666666;     height: 62px;     overflow: hidden;     width: 62px;   }    .aolReplacedBody #photos div label {     color: #666666;     font-size: 10px;     overflow: hidden;     text-align: center;     white-space: nowrap;     width: 64px;   }    .aolReplacedBody #reco-category {     font-size: 77%;   }    .aolReplacedBody #reco-desc {     font-size: 77%;   }    .aolReplacedBody .replbq {     margin: 4px;   }    .aolReplacedBody #ygrp-actbar div a:first-child {         margin-right: 2px; 
     padding-right: 5px;   }    .aolReplacedBody #ygrp-mlmsg {     font-size: 13px;     font-family: Arial, helvetica,clean, sans-serif;     *font-size: small;     *font: x-small;   }    .aolReplacedBody #ygrp-mlmsg table {     font-size: inherit;     font: 100%;   }    .aolReplacedBody #ygrp-mlmsg select,.aolReplacedBody  input,.aolReplacedBody  textarea {     font: 99% Arial, Helvetica, clean, sans-serif;   }    .aolReplacedBody #ygrp-mlmsg pre,.aolReplacedBody  code {     font:115% monospace;     *font-size:100%;   }    .aolReplacedBody #ygrp-mlmsg * {     line-height: 1.22em;   }    .aolReplacedBody #ygrp-mlmsg #logo {     padding-bottom: 10px;   }     .aolReplacedBody #ygrp-msg p a {     font-family: Verdana;   }    .aolReplacedBody #ygrp-msg p#attach-count span {     color: #1E66AE;
      font-weight: 700;   }    .aolReplacedBody #ygrp-reco #reco-head {     color: #ff7900;     font-weight: 700;   }    .aolReplacedBody #ygrp-reco {     margin-bottom: 20px;     padding: 0px;   }    .aolReplacedBody #ygrp-sponsor #ov li a {     font-size: 130%;     text-decoration: none;   }    .aolReplacedBody #ygrp-sponsor #ov li {     font-size: 77%;     list-style-type: square;     padding: 6px 0;   }     .aolReplacedBody #ygrp-sponsor #ov ul {     margin: 0;     padding: 0 0 0 8px;   }    .aolReplacedBody #ygrp-text {     font-family: Georgia;   }    .aolReplacedBody #ygrp-text p {     margin: 0 0 1em 0;   }    .aolReplacedBody #ygrp-text tt {     font-size: 120%;   }    .aolReplacedBody #ygrp-vital ul li:last-child {     border-right: none !important;    }    </style>






</div>


</div>





</div>

</font>



<!-- |**|begin egp html banner|**| -->

<br>


<br>

<!-- |**|end egp html banner|**| -->


<div width="1" style="color: white; clear: both;"/>__._,_.___</div>

      
  

    
    <div id="fromDMARC" style="clear:both; margin-top: 10px;">
         <hr style="height:2px ; border-width:0; color:#E3E3E3; background-color:#E3E3E3;">
         Posted by: [email protected]         <hr style="height:2px ; border-width:0; color:#E3E3E3; background-color:#E3E3E3;">
    </div>
<!-- Start Recommendations -->
<!-- End Recommendations -->


<!-- |**|begin egp html banner|**| -->

<br><br>
<tt>
To unsubscribe from the msp430 group, send an email to:<BR>
[email protected]<BR>
<BR>
</tt>
<br><br>

<!-- |**|end egp html banner|**| -->



<!-- |**|begin egp html banner|**| -->

  <img src="http://geo.yahoo.com/serv?s=97476590/grpId=2342629/grpspId=1705005378/msgId=52480/stime=1452557636" width="1" height="1"> <br>

<!-- |**|end egp html banner|**| -->

  
<!-- |**|begin egp html banner|**| -->

<br>



   
     
 
        <!-- |**|begin egp html banner|**| -->
        <div id="ygrp-vital" style="background-color: #f2f2f2; font-family: Verdana; font-size: 10px; margin-bottom: 10px; padding: 10px;">

        <span id="vithd" style="font-weight: bold; color: #333; text-transform: uppercase; "><a href="https://groups.yahoo.com/neo/groups/msp430/info;_ylc=X3oDMTJlN3BmaDlpBF9TAzk3MzU5NzE0BGdycElkAzIzNDI2MjkEZ3Jwc3BJZAMxNzA1MDA1Mzc4BHNlYwN2dGwEc2xrA3ZnaHAEc3RpbWUDMTQ1MjU1NzYzNg--" style="text-decoration: none;">Visit Your Group</a></span>

     <ul style="list-style-type: none; margin: 0; padding: 0; display: inline;">
            <li style="border-right: 1px solid #000; font-weight: 700; display: inline; padding: 0 5px; margin-left: 0;">
      <span class="cat"><a href="https://groups.yahoo.com/neo/groups/msp430/members/all;_ylc=X3oDMTJmZWRmMWkzBF9TAzk3MzU5NzE0BGdycElkAzIzNDI2MjkEZ3Jwc3BJZAMxNzA1MDA1Mzc4BHNlYwN2dGwEc2xrA3ZtYnJzBHN0aW1lAzE0NTI1NTc2MzY-" style="text-decoration: none;">New Members</a></span>
      <span class="ct" style="color: #ff7900;">1</span>
    </li>
                                              </ul>
  </div>


<div id="ft" style="font-family: Arial; font-size: 11px; margin-top: 5px; padding: 0 2px 0 0; clear: both;">
  <a href="https://groups.yahoo.com/neo;_ylc=X3oDMTJkY2FjZjBtBF9TAzk3NDc2NTkwBGdycElkAzIzNDI2MjkEZ3Jwc3BJZAMxNzA1MDA1Mzc4BHNlYwNmdHIEc2xrA2dmcARzdGltZQMxNDUyNTU3NjM2" style="float: left;"><img src="http://l.yimg.com/ru/static/images/yg/img/email/new_logo/logo-groups-137x15.png" height="15" width="137" alt="Yahoo! Groups" style="border: 0;"/></a>
  <div style="color: #747575; float: right;"> &bull; <a href="https://info.yahoo.com/privacy/us/yahoo/groups/details.html" style="text-decoration: none;">Privacy</a> &bull; <a href="mailto:[email protected]?subject=Unsubscribe" style="text-decoration: none;">Unsubscribe</a> &bull; <a href="https://info.yahoo.com/legal/us/yahoo/utos/terms/" style="text-decoration: none;">Terms of Use</a> </div>
</div>

<!-- |**|end egp html banner|**| -->

  </div> <!-- ygrp-msg -->

   


  <br>

<!-- |**|end egp html banner|**| -->


<div style="color: white; clear: both;"/>__,_._,___</div>
</body>

</html>

------=_Part_12372_1561705512.1452557633590--