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.

MSP430G2553: Any need to have valid field lengths and checksums in INFOA?

Part Number: MSP430G2553

I would like to use the empty parts of INFOA for BSL boot code.  But it's down to the last byte, so while all the calibration data will be preserved where it is, the bytes normally used for data type, field length and checksum will be overwritten by my code.  Would you expect that to cause any problems?  I don't think I've ever seen an application that actually used that information.

  • The calibration data is there for your own applications to use; neither the boot code nor the hardware itself use it. If you remove the TLV structures, you will affect only an application that expects them to be there.

    You could also remove all the calibration data from INFOA and store it directly in your application code. This works as long as you don't use a 'normal' application that tries to uses it.

**Attention** This is a public forum