• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 79 subscribers
  • Views 590 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MSP430F2616 - BSL Utility

Atul Bhakay
Genius 3205 points
Other Parts Discussed in Thread: MSP430F2616

We are using a BSL utility to upgrade code of MSP430F2616 device. Till now this was working very fine.

Since yesterday some how this utility is not working correctly. It is giving error at address 0x1000e8 verification failed.

My observation is that whenever it tries to write address starting with 0x10000 it gives error.

We tried to use this utility with small code it works perfectly but it fails with higher code size.1663.10 kpBSL_USBEXE.rar

For your reference I am attaching the utility which I am using. Also attaching the map and text files used.

Please go through the attachment which has the BSL activity on command prompt.

At the end of those files there is error message for big code file.3568.Problem with BSL.rtf[View:http://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/166/8055.OK-BSL.rtf  

 

 

 

 

  • 0
    TI__Guru 68116 points

    Hi Atul,

    Which revision of the F2616 are you using? I'm asking because Rev. A of that device has the FLASH23 erratum (see www.ti.com/lit/pdf/slaz189 ), which causes mass erase to not erase the entire main memory area but requires areas above and below the 64k boundary to be erased separately. So I could see the BSL software only calling a mass erase, but if this was not erasing the upper memory b/c you had a Rev. A part with this erratum, you could end up with a verification error like you see.

    You may also try calling the BSLDEMO2.exe with the +c parameter - this would enable a blank check to occur after the erase but before programming. That might tell you if the error is occurring earlier with the upper flash not being properly erased, or if it is really an error happening when you start programming that area. You would do this with the demo.bat you included by changing line 19 from:

    %HANDLER% -c%ComPort% -m1 +epvw  %TXT%

    to

    %HANDLER% -c%ComPort% -m1 +ecpvw  %TXT%

    Regards,

    Katie

  • 0
    Guru 58965 points

    Katie,

    There is another very similar thread, http://e2e.ti.com/support/microcontrollers/msp430/f/166/t/331729.aspx

    I tried to help but could not resolve it. Please take a look too.

    Regards,

    -- OCY

  • 0 in reply to old_cow_yellow
    Genius 3205 points

    We are using MSP430F2616 with Rev.F

    regards

    atul bhakay

  • 0 in reply to Katie Pier
    Guru 58965 points

    Atul,

    I think you forgot to include the -x option.

    -- OCY

**Attention** This is a public forum