• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 80 subscribers
  • Views 916 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.

MSP430 Flash Monitor/BSL

Charles Klibbe
Prodigy 230 points
Other Parts Discussed in Thread: MSP430FG4618

Hi,

 

I am going to be writing a Flash monitor/BSL and would like some comments please.

My requirements are that the client can update the code via the existing communication interface using an application I develop that can tap into the comms interface. Portions of the link will be via RF and some via RS485 so the monitor/BSL will be fairly large to accommodate both.

I have read slaa341, slaa149, slaa089, slaa096 and others.

My questions are as follows:

1. Since I can't directly use the TI BSL serial interface do I still use the TI BSL to do the Flashing (well tested), if so is there an interface spec?

2. Do I use a downloadable monitor, advantage is that if it changes then the latest version is always used.

3. Use a permanent monitor/BSL but should it use direct or indirect interrupts?

Thanks,

Charles

 

  • 0
    TI__Mastermind 24360 points

    Charles,

    Based on your description, it sounds like option 2 is the best scenario for you, especially if you can spare the additional flash. For that SLAA341 is probably the best starting point. Since the BSL is not-modifiable this is likely going to be your best bet.

  • 0 in reply to Brandon08
    Prodigy 230 points

    Thanks Brandon.

     

    I was also staring to go down that path. Yes I do have enough Flash as I am using a 249.

     

    Charles

  • 0 in reply to Charles Klibbe
    TI__Prodigy 30 points

    Hi ,

    Can the SLAA341 program a MSP430FG4618 device? If so, can you help me with the #define CHIP XX settings or mods that may have to be done to the code.

    Thanks,

    Preetham

  • 0 in reply to Preetham Raj
    Prodigy 230 points

    Hi Peetham,

     

    Sorry I can't help as I used slaa103.pdf as a reference and added my own interface.

     

    Charles

  • 0 in reply to Charles Klibbe
    Guru 58965 points

    In order to minimize the Flash footprint, I would put only the essential code in Flash to (a) download data/code from a remote system to local SRAM, (b) authenticate that, and (c) jump to the downloaded code.

    The downloaded code does the erasing, re-writing, and verifying. Usually the SRAM is not big enough to hold all the code and data to do the entire job. I break that job into smaller chunks. Each downloaded chunk would finish part of the job and jump back to my code in Flash to do the next chunk.

    This method leaves the details of BSL to be directed by the remote system, which I assume is easier to develop and update.

    I once did this in MSP430F20xx with 128 bytes of SRAM and 196 bytes of Info Flash. It works. But programming PC under Windows is not what I want to do. Once I verified that the scheme works, I through it out of the window [:6]

  • 0 in reply to old_cow_yellow
    TI__Prodigy 30 points

    Hi ,

    This sounds like a good idea. But i have sufficient flash to spare , an would like to re-use the code in from SLAA341 modify it 20-bit addressing. But modifying the linker file for CCE is what i'm a little wary about, and cause the main app is in C and uses interrupts, and must admit i'm a novice at that [:S]

    Any help here would be very usefull..

    Regards,

    Preetham

**Attention** This is a public forum