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.

InfoMemory of MSP430F6xxx

Expert 2355 points
Other Parts Discussed in Thread: MSP430F6745

Hi,

All MSP430 has infomation memory.

F2xx has calibration data of clk and adc on Info memory.

Does F6xx has same deta ,or not?

http://www.ti.com/lit/ds/symlink/msp430f6745.pdf

I seem that TLV descripter has calibration , ID and so on.

So there is no data in Info area.

best regards,

  • The 5x/6x family has even more data, including the wafer ID and the chip position on the wafer. This information is no longer stored in info memory, but in a separate (read-only) TLV structure. See the datasheet and users guide for details. (search for TLV).

    Clock information is no longer stored because these devices have an FLL that adjusts the DCO based on a reference clock - and they have a suitable reference clock (REFO) built-in. SO no need for clock calibration values.

  • Hi kyt,

    You are correct - the F6xx family does have calibration data, but it is no longer stored in INFOA. The F5xx/6xx devices use the device TLV structure at the addresses mentioned in the datasheet. This is an improvement over F2xx in that on F2xx with INFOA you could erase and lose this calibration data. With the configuration on F5xx/6xx, it is not possible to accidentally erase the data - it is in an area where you do not have this kind of erase/write access. So you can use INFO A for whatever you want on F6xx.

    Hope this helps clear things up.

    Regards,

    Katie

    EDIT: Looks like Jens-Michael beat me to it :-)

  • Katie Pier said:
    EDIT: Looks like Jens-Michael beat me to it :-)

    Plain coincidence :)

     Well, not being able to erase the calibration data is a drawback in the (rare) cases where the calibration data is incorrect :)
    In my project, I copy the data from TLV to INFO memory on first initialization. The code then uses the copy, which I can replace if required (e.g. to take tolerances of external components into account, including external reference or offset or gain errors due to external resistor dividers or amplifiers)