• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 80 subscribers
  • Views 513 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: Issue related to flash programming, after implementing bootloader

Jignesh Patel0
Prodigy 30 points
Part Number: MSP430F5438A


Hi,

I face some issues related to programming of MSP430F5438A using MSP430 USB-Debug-Interface MSP_FET430UIF, after implementing bootloader in My project.

My step is:

1. Bootloader has been customized. I also do read & write information memory in bootloader program as well as in application program.
2. Bootloader and application program has been Programmed successfully MSP430F5438A first time using MSP430 USB-Debug-Interface MSP_FET430UIF.
3. After successfully programming first time, run the program.
4. I am not able to reprogram MSP430F5438A after 1 or 2 try, while the programming of application program using FET-pro430 flash programmer or debugging from IAR. MSP430F5438A's memory might be permanently corrupted.


I have also some question :
1. Can we reprogram application program(after modification) using FET-pro430, if Chip has already a Bootloader?
    OR
    Should we always use bootloader to program application program if chip has already a bootloader?
 
2. Is it possible to debug application program when chip has already a bootloader?

Thanks,
Jignesh Patel

  • 0
    Guru 34773 points

    There is no relation between flashing by FET or BSL, or debugging. SBW / JTAG (and all stuff related to it) should work with or without customized BSL.

    Problem is that you need to take care during custom BSL development, to not write fuse values (017FCh, located inside BSL segment) because this will lock SBW / JTAG access forever. Unfortunately, TI FET's / CCS will not warn you about this. I never worked with UART BSL, but with USB BSL there is protect function, that with wrong returning value can lock device too.

    When I was working on my CDC BSL with AES, during development main flash was used without touching factory BSL. At the end, when I was 100% sure that everything is working OK, it was relocated to BSL area. And my flasher have warning related to overwriting fuse values.  

**Attention** This is a public forum