Bob, You are right, SLAU320 already talks about how to identify a derivative. The related memory configuration needs to read from the device datasheet. We are working on a machine readable database as part of our debug stack, but this will not be available until m/o next year.
Thanks, Thomas Mitnacht -----Original Message----- From: Bob von Knobloch [mailto:b...@vknobloch.de] Sent: Thursday, December 01, 2011 3:38 PM To: mspgcc-users@lists.sourceforge.net Subject: Re: [Mspgcc-users] MSP430 Device ID Bytes On 01/12/11 15:27, Mitnacht, Thomas wrote: > Hi Bob, > What details are you missing? > > Thanks, > Thomas Mitnacht I was hoping to be able to identify the part (or, at least, the flash start address which I need for programming). The SLAU320c doc only maps 3 bytes (0xff0, 0xff1 & 0xffd) to several families of parts (F20x2 & G3x2x Parts) and not distinct models. I expect I must do it myself with a small list. Thanks for helping, Bob ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
