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.

Unique code of MSP430- exists?

Hello,

my question is: is there an "unique code" that every MSP430 contains somewhere in memory and which I can read in application (something like ROM code in DS18x20 temperature sensors)?

Best regards,

Mikolaj

  • Mikolaj Filar said:
    my question is: is there an "unique code" that every MSP430 contains somewhere in memory and which I can read in application

    Newer 5xx and 6xx series devices have a "Lot/Wafer ID + Die X position + Die Y position" in the device descriptor tag-length-value (TLV) structure which uniquely identifies the die. See Unique chip ID?

    For earlier devices I think you are stuck with allocating your own unique ID in info flash, e.g. as done by the Elprotronic FET-Pro430 programmer.

  • Thank you for you answer. I knew I had seen similar topic in the past but I couldn't fint it :)

    I'd prefer to have something like this in value line devices. I am sad.

    Best regards,

    Mikolaj

  • Mikolaj Filar said:
    I'd prefer to have something like this in value line devices.

    Putting individual information into a device is an additional processing step. You can get it cheap or comfortable, but not both. The value line are the cheap devices.

  • You are absolutely right. I would like to use cheap MSP430 solution as comfortable replacement of DS18B20 that measures temperature, contains unique ROM code and annoying 1-wire interface. Using TI MCU with temperature sensor and own code would additionally increase flexibility of the system but If I use f5 or f6 MCU there is no sense to use the current main controller which is less powerful than any f5 and f6. I have just migrated to bigger MCU of the same family it was developed for and doing it again wasn't make my boss happy (although MSP is my favorite family)  :)

    The 2nd thing: I' ve heard there were problems in the past wih MCUs in SMD packages in low temperatures (probably something related with used soldering technologies). We are using DIP packaged MCUs now.

    Best regards,

    Mikolaj

  • If you use the (commercial) version of the elprotronic flashing software, you can automatically replace a certain memory location by a 'serial number' (or text or whatever) taken from a text file while flashing your devices. It's almost as good as a factory-programmed ID.

    About the temperature thing, I don't have an info. I don't remember hearing of any temperature and SMD  related problem in the past.

    I can imagine that a shrinking (by temperature) plastic body may cause more mechanical stress to the SMD pins than to the DIP pins. It could cause the soldering to rip off. But then I don't know how this could have been solved (maybe different plastic material) or why such a thing should/could have happened at all (except for a bad raw material charge). After all, SMD packages aren't that new.

  • Jens-Michael Gross said:
    If you use the (commercial) version of the elprotronic flashing software, you can automatically replace a certain memory location by a 'serial number' (or text or whatever) taken from a text file while flashing your devices. It's almost as good as a factory-programmed ID.

    It's an interesting idea. I surely will analyze that. How does the serialization process work? When I turn-off the application does it still store a next address to program? I want to don't care that someone will make some parts with the same serials.

    There is a free lite version (unfortunately without serialization). Can I use it with launchpad or I need a special programmer to test it?

    I don't know details of temp issues because I didn't work on this project yet and more experienced engineers decided to replace SMD parts by DIP and as it turns out it works (but most part is still SMD: mosfets, resistors, capacitors etc.) .

    edit. I see version with serialization in download section on an elprotronic website. Maybe it's a try version. I will try to download it.

  • Mikolaj Filar said:
    It's an interesting idea. I surely will analyze that. How does the serialization process work?

    AFAIK (I only use the free version, so I never actually used htis feature) it fetches one line at a time from a text file on every programming cycle and keeps a counter of which line was last. So when you continue flashing later, the serialization continues with the next line.

    Mikolaj Filar said:
    There is a free lite version. Can I use it with launchpad or I need a special programmer to test it?

    Yes, the free verison wotks with all original Ti FETs, including the EZ430 variant on the LaunchPad and of course the Fet-430UIF.
    But 3rd party FETs (e.g. Olimex) are not supported.

  • Jens-Michael Gross said:
    Yes, the free verison wotks with all original Ti FETs, including the EZ430 variant on the LaunchPad and of course the Fet-430UIF.
    But 3rd party FETs (e.g. Olimex) are not supported.

    The free version of FET-Pro430 has the Setup -> Connection / Device Reset screen where a 3rd party FET DLL can be selected. e.g. with the following setup was able to use FET-Pro430 with a MSP430-JTAG-ISO-MK2:

      

  • Chester Gillon said:
    The free version of FET-Pro430 has the Setup -> Connection / Device Reset screen where a 3rd party FET DLL can be selected.

    Hmmm, yes, you're right. I was citing this information from a mail exchange with Elprotronic three years ago. Maybe this has changed in the later versions of the program, or I misinterpreted it. It made some sense to me that the free version cannot be used for a competitors device, so I didn't question my interpretation.

  • I posted code to extract the unique lot/die information to create a MAC address here

    http://e2e.ti.com/support/microcontrollers/msp430/f/166/p/19506/1059511.aspx#1059511

    cheers,

    Mark Lakata

**Attention** This is a public forum