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 utilty issue

Other Parts Discussed in Thread: MSP430F2616, MSP430FG4616, MSP430F4783, MSP430F447

Hello All,

One of our client is using BSL uitility to upgrade code of MSP430F2616.

It was working fine till code size was less.

Now it gives error at address 0x1000e8 verification failed.

With small code it works perfectly but it fails with higher code size

The utility they are using is 10 kpBSL_USBEXE.

Kindly suggest any solution for the same.

Awaiting for reply.

Please help

Regards,

Nilesh N. Kulkarni

  • Which "BSL utility"?

  • they are using BSLDEMO2 utility

    please advise for the same

    regards,

    nilesh

  • Nilesh Kulkarni2 said:

    ... One of our client is using BSL uitility to upgrade code of MSP430F2616.

    It was working fine till code size was less.

    Now it gives error at address 0x1000e8 verification failed.

    With small code it works perfectly but it fails with higher code size...

    I do not work for TI. The following are based on my own opinion.

    BSLDEMO2 is capable of programing F2616 Flash beyond address 0xFFFF. However, 0x1000e8 is way way beyond. Is that a typo? Did you type an extra 0?

    I think there is bug in BSLDEMO2. If you try to load this:

    @FFC0
    00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
    20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F
    FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
    FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
    @10000
    00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
    20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F
    30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F
    40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F
    q

    It would give you an error. But it works with the equivalent:

    @FFC0
    00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
    20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F
    FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
    FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
    00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
    20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F
    30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F
    40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F
    q

    That is, you do not specifically give an address beyond FFFF (with an @....), but let the address automatically advances beyond the 64KB boundary.


    TI probably will tell you to use BSL-Scriptor instead of BSLDEMO2. It is my opinion that for F1xx and F2xx, BSL-Scriptor is much worse. On the other hand, BSLDEMO2 dose not work for F5xx and F6xx

  • Thank you so much for timely reply for the same.....

    I will forward the reply to client and let you know if there are any other queries.

  • You are right the address they wrote with extra zero, there was a typo ,please read it as 0x100e8.

     Please guide which exe should I use to update the code through BSL mode. Please send me that exe file if possible.

    They are using MSP430F2616, MSP430FG4616, MSP430F447 and MSP430F4783 device

  • Sorry, I cannot send you the exe file you requested.

    The BSLDEMO2.exe program in my PC is slightly different from TI’s BSLDEMO2.exe because my BSL hardware interface is different from that of TI’s. Aside of this, the one in my PC is identical to one of the versions from TI. I do not remember nor have any record which TI version mine is based on.

    I searched TI web-site and found that TI has “deprecated” BSLDEMO2.

    As I told you before, I am not a TI employee.

  • I have some update about this issue.

    (1) Earlier versions of BSLDEMO2 do not support this feature. Version 2.00 and 2.01 do. But one has to use the -x option to do so.

    (2) Atul Bhakay posted more detail about his problem. He was using Version 2.00 but he did not use the -x option. I think that is why it did not work for him. All he needs to do to make it work for him is to turn on the -x option.

  • Hey thanks a lotttt.....

    Issue has been reslved by including the -x parameter...

    Thanks for your timely support...

**Attention** This is a public forum