• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 78 subscribers
  • Views 247 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.

Original question:

MSP430FR2355: i2c bsl tool failure when load new firmware

MSP430FR2355: MSP430FR2355

David Cohen
Prodigy 20 points
Part Number: MSP430FR2355

Hi,

The articles you attached does not help to me.

Do you have another idea?

Regards,

  • 0
    TI__Guru 62301 points

    Hi David,

    Do you have a logic probe you can use capture the commands on the I2C where it fails for you?  Maybe verify the commands are correct?

  • 0 in reply to Dennis Lehman
    Prodigy 20 points

    Hi Dennis,


    We noticed something interesting, when we manually deleted the addresses 0xffe0-0xffff (password / vector interrupts) from the TI-TXT-HEX file we noticed that our application did not load but TI's software loaded (BSL) and when we tried to programmed new firmware we saw that a mass erase was being performed and the programming was successful.

    If we hadn't deleted the addresses 0xffeo-0xffff our program would have started.

    Then we would have jumped to the BSL program but for some reason the programming is not successful and the mass erase also failed...

    Our commands are correct and your app msp430-i2c-bsl-tool works.

    We think the problem is in the way the firmware file is created.

    Is it possible to create a file without a password?

    Is it possible to delete the password from our software? Maybe even the problem with the settings we put in our environment code composer?

    Do you maybe have an idea what could be the problem?

    Thank you very much for your help.

  • 0 in reply to David Cohen
    TI__Guru 62301 points

    Hi David,

    Regarding not generating a password, no, you have to provide some PW to the BSL, whether it be vector data or just 0xFFFF_FFFF to force a mass erase.  

    So let me make sure I understand ... if you send 0xFFFFFFFF you can communicate with the BSL and, for example, read back the BSL version, correct?

    But when you attempt to write your application image, you see one form or another of a failure message, correct?

    I assume you are generating .txt style image outputs, so can you share here? Or if confidential you can send me a "Friend" request and our conversation is private.

  • 0 in reply to Dennis Lehman
    Prodigy 20 points

    Hi Dennis,

    This is our TXT-TI-HEX file:

    @8000 

    Data of our application

    @ff80

    FF FF FF FF FF FF FF FF 5A 69 02 5A

    @ffa0 

    48 FF 

    @ffce 

    84 9B 84 9B 84 9B 84 9B 84 9B 84 9B 84 9B 84 9B

    46 9A 68 98 84 9B 84 9B 84 9B 84 9B 84 9B 84 9B

    84 9B 84 9B 84 9B 84 9B 84 9B 84 9B 84 9B 84 9B

    64 9B

    q

    Yes, we can communicate with the bsl but when we try to programm new firmware it is not working for us.

    The failure is 0x1 (crc checksum)

     

  • 0 in reply to David Cohen
    TI__Guru 62301 points

    Hi David,

    I apologize for the delay in getting back to you on this issue.  

    David Cohen said:
    If we hadn't deleted the addresses 0xffeo-0xffff our program would have started

    This is correct.  Address 0xFFFE-0xFFFF is the reset vector to the start of your application so this would explain why your application did not start.

    Do you delay (say 100ms) after a MASS ERASE command, or when sending PW = all 0xFFFF before attempting to program the application?  And in between commands add a 10ms delay.

**Attention** This is a public forum