On 01/12/11 17:16, Peter Bigot wrote: > I think the point is that, if you already know the device, you can find the > address map (from the datasheet, from the msp430mcu package's devices.csv > file provided by TI that's used to generate the linker scripts for the > toolchain, or from information in the debug DLL package). What's missing > is how to figure out what device you have by looking at the MCU boot memory > through JTAG/SpyBiWire or at runtime, or some other automated inspection > method. > > I believe mspdebug has performed the MCU identification task by matching > FET byte sequences against a database collected from known chips. Perhaps > some constants in mspdebug's drivers/fet_db.c are the same as in the 0x0FF0 > region. > > I've wanted to have a routine that could identify the MCU at runtime for a > while myself, but the information isn't readily available. > > Peter Yes, thats exactly what I have been looking for. OK, it's good to know that it doesn't (yet) exist, at least I won't waste time looking further.
Many thanks Peter, Bob Mitnacht, Thomas wrote: MSP430G2231 datasheet page 11 should give you what you need Thomas, I think we talked past each other. I know the flash info is there, I wanted a correlation between identity byte(s) and flash size. As Peter confirms, it doesn't exist. Many thanks anyway, 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
