Hello all,

I'm having trouble with the bootstrap loader (BSL); judging from the
message archives, this is everyone's favorite topic.

I've been able to get the msp430 f149 to go into the bootstrap loader.
I send a SYNC (0x80) and read an ACK (0x90).

I then try to send the "TX BSL VERSION" command; the exact bytes I
transmit are:
0x80 0x1e 0x04 0x04 0x00 0x00 0x00 0x00 0x7b 0xe5

The strange thing is, even though app note SLAA089D says that the "TX
BSL VERSION" doesn't give an ACK, I am recieving a NAK (0xA0) right
after I send the command. I've double-checked my checksum, and it
looks perfect. I can't figure out what I'm doing wrong.
Has anyone else had this problem? Or, can anyone provide for me a
known-to-work sequence of bytes that represent the "TX BSL VERSION"
command?

Thank you,
Nick Johnson Start a New Thread

be careful with BSL, there are multiple versions, and some useful-looking
commands only exist in very late version.

I think you can / should start by fetching the BSL version and looking up
what is supported.

David
> *Subject:* [msp430] The BSL gives a NAK in response to a "TX BSL
> VERSION" message
> *From:* "xxsdfsdfsdfsdfsdfsdfsdfsdfsdfxx"
> *To:* m...
> *Date:* Fri, 13 Jul 2007 23:53:08 -0000
>
> Hello all,
>
> I'm having trouble with the bootstrap loader (BSL); judging from the
> message archives, this is everyone's favorite topic.
>
> I've been able to get the msp430 f149 to go into the bootstrap
> loader.
> I send a SYNC (0x80) and read an ACK (0x90).
>
> I then try to send the "TX BSL VERSION" command; the exact bytes I
> transmit are:
> 0x80 0x1e 0x04 0x04 0x00 0x00 0x00 0x00 0x7b 0xe5
>
> The strange thing is, even though app note SLAA089D says that the
> "TX
> BSL VERSION" doesn't give an ACK, I am recieving a NAK (0xA0) right
> after I send the command. I've double-checked my checksum, and it
> looks perfect. I can't figure out what I'm doing wrong.
> Has anyone else had this problem? Or, can anyone provide for me a
> known-to-work sequence of bytes that represent the "TX BSL VERSION"
> command?
>
> Thank you,
> Nick Johnson
> --
> *Included Files:*
> am2file:001-HTML_Message.html Start a New Thread

David is correct. But this is funny.

"Fatch the BSL version" itself is one of the commands that is not
supported by all versions of BSL.

Thus before you "fetch the BSL version", you should first "fetch the
BSL version" and look up if it supports "fetch the BSL version".

Here is how to do this:

int BSL_version(void)
{
if (BSL_verion() >= VER_1P6 ) return ( BSL_version() );
else return ( ERROR );
}

--- In m..., "David Collier"
wrote:
> be careful with BSL, there are multiple versions, and some
useful-looking
> commands only exist in very late version.
>
> I think you can / should start by fetching the BSL version and
looking up
> what is supported.
>
> David
> > *Subject:* [msp430] The BSL gives a NAK in response to a "TX BSL
> > VERSION" message
> > *From:* "xxsdfsdfsdfsdfsdfsdfsdfsdfsdfxx"
> > *To:* m...
> > *Date:* Fri, 13 Jul 2007 23:53:08 -0000
> >
> > Hello all,
> >
> > I'm having trouble with the bootstrap loader (BSL); judging from the
> > message archives, this is everyone's favorite topic.
> >
> > I've been able to get the msp430 f149 to go into the bootstrap
> > loader.
> > I send a SYNC (0x80) and read an ACK (0x90).
> >
> > I then try to send the "TX BSL VERSION" command; the exact bytes I
> > transmit are:
> >
> >
> > 0x80 0x1e 0x04 0x04 0x00 0x00 0x00 0x00 0x7b 0xe5
> >
> > The strange thing is, even though app note SLAA089D says that the
> > "TX
> > BSL VERSION" doesn't give an ACK, I am recieving a NAK (0xA0) right
> > after I send the command. I've double-checked my checksum, and it
> > looks perfect. I can't figure out what I'm doing wrong.
> >
> >
> > Has anyone else had this problem? Or, can anyone provide for me a
> > known-to-work sequence of bytes that represent the "TX BSL VERSION"
> > command?
> >
> > Thank you,
> > Nick Johnson
> >
> >
> >
> >
> > --
> > *Included Files:*
> > am2file:001-HTML_Message.html
> Start a New Thread

I tried what you did and got 0xA0 back from F149.

But when I do the same to F1232, I got: (hex)
80 00 10 00 12 32 00 40 00 00 00 00 00 00 01 60 01 00 12 12 6F EF

--- In m..., "xxsdfsdfsdfsdfsdfsdfsdfsdfsdfxx"
wrote:
>
> Hello all,
>
> I'm having trouble with the bootstrap loader (BSL); judging from the
> message archives, this is everyone's favorite topic.
>
> I've been able to get the msp430 f149 to go into the bootstrap loader.
> I send a SYNC (0x80) and read an ACK (0x90).
>
> I then try to send the "TX BSL VERSION" command; the exact bytes I
> transmit are:
> 0x80 0x1e 0x04 0x04 0x00 0x00 0x00 0x00 0x7b 0xe5
>
> The strange thing is, even though app note SLAA089D says that the "TX
> BSL VERSION" doesn't give an ACK, I am recieving a NAK (0xA0) right
> after I send the command. I've double-checked my checksum, and it
> looks perfect. I can't figure out what I'm doing wrong.
> Has anyone else had this problem? Or, can anyone provide for me a
> known-to-work sequence of bytes that represent the "TX BSL VERSION"
> command?
>
> Thank you,
> Nick Johnson
> Start a New Thread