• State Answer Suggested
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 78 subscribers
  • Views 477 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSP430F5438A and BSL version

jezule
Prodigy 140 points

Other Parts Discussed in Thread: MSP430F5438A

Hi all,

My question is basically a duplicate of this one but I seek a different answer:

http://e2e.ti.com/support/microcontrollers/msp430/f/166/t/267787.aspx

We have been using the BSL to program our boards based on an MSP430F5438A Rev. E, with BSL version 05.04.03. We added some dedicated hardware to deal with SYS10 and handle the timing issues. Our boards have been recently upgraded and were shipped with revision F MCUs, with BSL version 07.05.04.

For programming we use mspdebug but with the newer boards we have found some trouble because of that extra 0x00 mentioned in the post above or as can be seen in the next partial frames:

Rev. E: {00}{80}{02}{00}{3B}{00}{60}{C4}{00}...

Rev. F: {00}{00}{80}{02}{00}{3B}{00}{60}{C4}{00}...

I have patched the mspdebug code to deal with it but I would like that someone confirmed to me that this extra 0x00 produced when the BSL is invoked is intentional and a new feature of the newer BSL version? This would create some incompatibilities with previous softwares.

I have verified that that extra 0x00 (which is an ACK?) is sent upon entry in the BSL. I have connected a FTDI cable to BSL TX and I have done a very simple program for the F5438A to invoke the BSL:

__disable_interrupt();
((void (*)())0x1000)();

Using a serial port monitor I can see a 0x00 popping up every time that the BSL is invoked.

I have downloaded SLAA450 and had a look at the source code and I do not see anything that sends an ACK upon entry on the BSL but I do not know either if that source code corresponds to the BSL loaded in the MCU.

Thanks.

Best regards

  • 0
    Prodigy 140 points
    Well, I had completely forgotten about this but I will reply myself in case anybody finds it useful :-)
    Downgrading the BSL for revision F MCUs to BSL 05.04.03 removed this extra zero. So yes, it is BSL related but after checking in the oscilloscope it does not seem that this 0x00 prefix is sent intentionally it looks more like a transient on the data line upon intialization. Anyway it messes up with existing software packages such as mspdebug that do not expect this leading byte.
    Regards

**Attention** This is a public forum