In the interest of saving someone else in the future this problem, here's what I came up with. Your comments and criticism are welcome! 
# Parse a single line of S-record, validate the line, and extract the 
+address
# and data fields. Return a list of three scalars:
#  1. TRUE if extraction was successful, FALSE otherwise (i.e. not a v
+alid data
#     carrying S-record, bad s-record length, bad s-record checksum).
#  2. The address of the line's payload, as a string.
#  3. The data of the line's payload, as a string.
sub ProcessSrecLine
{
    my $line = shift;
    
    # Get rid of all line endings, regardless of which flavor they are
    $line =~ s/(\n|\r)//g;

    # be a pessimist
    my $status = 0;
    my $type;
    my $count;
    my $address;
    my $data;
    my $cs;

    # does this look like a S1, S2, or S3 record? These are the only o
+nes that
    # carry an actual data payload. Other record types do not, so just
+ ignore
    # them.
    if (
        ($line =~ /^s(1)([0-9a-f]{2})([0-9a-f]{4})([0-9a-f]+)([0-9a-f]
+{2})$/i) ||
        ($line =~ /^s(2)([0-9a-f]{2})([0-9a-f]{6})([0-9a-f]+)([0-9a-f]
+{2})$/i) ||
        ($line =~ /^s(3)([0-9a-f]{2})([0-9a-f]{8})([0-9a-f]+)([0-9a-f]
+{2})$/i)
       )
    {
        $type = $1;
        $count = $2;
        $address = $3;
        $data = $4;
        $cs = $5;

        # Make sure the COUNT field makes sense. It should represent t
+he sum of
        # address, data, and checksum fields, in bytes
        if ( hex($count) == ((length($address) + length($data) + lengt
+h($cs)) / 2) )
        {
            # Make sure the checksum makes sense. It is the two's comp
+lement of
            # the sum of count, address, and data fields
            my $compCs = hex($count);
            for (my $i=0; $i<length($address); $i+=2)
            {
                $compCs += hex(substr($address, $i, 2)); 
            }
            for (my $i=0; $i<length($data); $i+=2)
            {
                $compCs += hex(substr($data, $i, 2)); 
            }
            $compCs %= 256;
            $compCs = 255 - $compCs;

            # if the checksum actually matches, then call it a good S-
+record
            if ($compCs == hex($cs))
            {
                $status = 1;
            }
        }

        return ($status, $address, $data);
    }
}

[download]

In reply to Re^2: Parsing Motorola S-Rec file by gri6507
in thread Parsing Motorola S-Rec file by gri6507

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.