MSP-EXP430G2 LaunchPad FAQs
1. Does the MSP-EXP430G2 support fuse blow? The MSP-EXP430G2 LaunchPad experimenter board onboard debugging interface lacks the JTAG security fuse-blow capability. To ensure firmware security on devices going to production, the USB Flash Emulation Tool or the Gang Production Programmer, which support the fuse-blow feature, are recommended. 2. Can other programming tools like the MSP-FET430UIF interface the MSP-EXP430G2 LaunchPad socket device? The LaunchPad experimenter board works with any programming tool supporting the 2-wire Spy-Bi-Wire interface. Both the MSP430 USB FET (MSP-FET430UIF) and the Gang Programmer (MSP-GANG430) support these devices, but the connection must be made directly to the dedicated Spy-Bi-Wire ports. See MSP-FET430 Flash Emulation Tool User's Guide (SLAU138) for details on using MSP430 USB FET and the Gang Programmer for a 2-wire Spy-Bi-Wire interface. Don't try to connect the standard JTAG connector to theMSP-EXP430G2 pinheads, as this could result in damage to the attached hardware. 3. What versions of IAR Embedded Workbench and Code Composer Studio are supported? The MSP-EXP430 LaunchPad hardware is supported by IAR Embedded Workbench KickStart Version 6.00 and Code Composer Studio v4 or higher. To download the software and for more information on the supported software visit the LaunchPad Wiki page. 4. What are the part numbers for the connectors between the LaunchPad emulator board and the other eZ430 target boards? Header: Mill-Max 850-10-006-20-001000 Socket: Mill-Max 851-93-006-20-001000 5. I am not able to select the MSP430 Application UART and cannot receive data. Ensure that the Application UART driver is correctly installed. This is done by installing either IAR Embedded Workbench or Code Composer Studio v4. To determine if the driver is correctly installed: a. Plug in the MSP-EXP430G2 LaunchPad with the included Mini USB cable. b. Right click My Computer and select Properties. c. Select the Hardware tab and click on Device Manager. d. Under Ports (COM & LPT) should be an entry for "MSP430 Application UART (COM xx)". If the entry is there, but no characters are received, reconnect the LaunchPad to the PC and restart the application to reload the drivers. If the Application UART is not listed, install the driver by following the instructions in Section 2.2 of the User's Guide. 6. The device is not answering to any communication, JTAG or UART. If you are experiencing difficulties in communicating to the attached MSP430 target device, even though all the communication drivers for the MSP-EXP430G2 are loaded correctly, the emulator is probably set to a wrong communication state. This can be fixed by reconnecting the LaunchPad Experimenter Board and restarting the communicating application.
FRAM FAQS
1.What is FRAM?
FRAM, an acronym for ferroelectric random access memory, is a non-volatile memory that can hold data even after it is powered off. In spite of the name, FRAM is a ferroelectric memory and is not affected by magnetic fields as there is no ferrous material (iron) in the chip. Ferroelectric materials switch polarity in an electric field, but are not affected by magnetic fields.
2.What are FRAM's key advantages over Flash/EEPROM?
1) Speed. FRAM has fast write times. Beyond all the other operations, the actual write time to an FRAM memory cell is less than 50ns. That is approximately 1000x faster than EEPROM. Additionally, unlike EEPROM where you must have two steps to write data: a write command, followed by a read/verify command; FRAM's write memory function happens in the same process as read memory. There is only one memory access command, one step for either reading or writing. So in effect, all the time associated with an EEPROM write transaction is effectively eliminated in an FRAM-based smart IC.
2) Low Power. Writes to the FRAM cell occur at low voltage and very little current is needed to change the data. With EEPROM high voltages are needed. FRAM uses very low power – 1.5v compared to 10-14v for EEPROM. FRAM's low voltage translates into low power usage and enables more functionality at faster transactions speeds.
3) Data Reliability. Because only a small amount of energy is required, all the necessary power for FRAM is front-loaded at the beginning of data write. This avoids "data-tearing," a partial write of the data which occurs when EEPROM based smart ICs are removed from the RF field power source during a write cycle. Further, FRAM experiences 100 Trillion read/write cycles or greater – far exceeding EEPROM write cycles.
3.How does FRAM perform at high temperatures?
FRAM is a very robust and reliable memory technology, even at high temperatures. FRAM retains its data for more than 10 years at 85 degrees C. This far exceeds the requirements for credentials in the government ID market and represents the robust data retention of FRAM. FRAM is used in several automotive applications and has been qualified to withstand the extremely harsh conditions.
4.Does FRAM have the same problem with scalability as Flash/EEPROM?
Unlike FRAM, Flash/EEPROM employs a floating gate charge storage design which necessitates high voltage and costly, power-hungry and space-hogging circuits, such as transistors and charge pumps. A restriction of all this high-voltage legacy circuitry is that it does not easily scale to smaller and smaller IC process node manufacturing. Also, TI's advanced 130 nanometer (nm) FRAM manufacturing process results in chips that are much smaller than the 180 – 220 nm node sizes used by in most Flash and EEPROM-based embedded microcontrollers, giving FRAM products a significant advantage in size, performance, and power efficiency. Further, the FRAM manufacturing process is fully compatible with digital CMOS processes making the technology easy to scale to smaller technology nodes in the future.
5.Does FRAM lose data after a read?
No. FRAM is a nonvolatile storage memory that retains its data even after the power is turned off. Similar to commonly used DRAM (Dynamic Random Access Memory) found in large (main) memories in personal computers, workstations, and non-handheld game-consoles (such as PlayStation and Xbox), FRAM requires a memory restore after each read. A memory restore is done because like DRAM, FRAM memory cells require each bit accessed to be re-written in a refresh function. Because FRAM has an inexhaustible write endurance (100 trillion write/read cycles), this is not a practical concern.
6.Does new embedded FRAM memory technology raise security concerns?
FRAM is already used in financial smartcard applications in transit and in set-top boxes. Compared to existing EEPROM technologies, FRAM is more resistant to data corruption via electric fields, radiation, etc. The extremely fast write times and the small 130 nanometer (nm) process node make it difficult for attackers. Furthermore, FRAM's lower power consumption (and the fact that its read and write power consumption is identical) arguably make it a more difficult target to attack using differential power analysis techniques.
7.Are FRAM devices affected by magnetic fields?
A common misconception is that ferroelectric crystals contain iron or are ferromagnetic or have similar properties. The term "ferroelectric" refers to similarity of the graph of charge plotted as a function of voltage (Figure below) to the hysteresis loop (BH curve) of ferromagnetic materials. Ferroelectric materials are not affected by magnetic fields.
8.How large of an electric field can a FRAM device withstand?
The FRAM memory cell operates by applying a switched voltage to sense and restore the data state. The ferroelectric film PZT is about 70nm thick. If the device is placed in a 50 kV field at 1 cm, it is not possible to produce more than 1V across the ferroelectric film. As a practical matter, FRAM devices are impervious to external electric fields.
9.Is FRAM affected by radiation or soft errors?
Volatile memories, DRAM and SRAM, use a capacitor to store charge or a simple latch to store state. These cells can be easily upset by a alpha particles, cosmic rays, heavy ions, gamma, x-rays, etc. which cause bits to flip to an opposite state. This is called a soft error, since a subsequent write will be retained. The rate at which this occurs is called the Soft Error Rate (SER) of the device. Because the FRAM cell stores the state as a PZT film polarization, an alpha hit is very unlikely to cause the polarization to change a given cell's state and the FRAM terrestrial SER is not even measurable.
This 'radiation resistant' characteristic of FRAM makes it attractive for use in several emerging medical applications
10.What is TI's focus in FRAM?
While TI is currently producing standalone FRAM memory devices for Ramtron, our internal focus is on
· Embedded FRAM (as a 2 mask adder to digital process flow). We have successfully designed arrays up to 32Mb. <
· FRAM as a true NVRAM technology to replace cache SRAM, DRAM, Flash / EEPROM
· Supporting 1.5V operation for low power applications
While FRAM does provide unparalleled flexibility and benefits to customers, initial implementations and designs are optimized for targeted areas of operation. It is important to emphasize that FRAM technology can support both high performance and low power applications; however, our current FRAM array designs are optimized for low power operation. Some items to consider with our initial FRAM designs are:
· They are best suited for devices operating below 25 MHz. However, as with all technology evolutions, we expect to design higher performance FRAM memory arrays in the future that support devices operating at much higher clock speeds.
· As stated above, we expect that several of our initial FRAM memory devices will use 2T-2C configuration (2 cells are used for each bit of data). This 'redundant' methodology results in the crossover point where FRAM arrays are smaller than equivalent Flash memory in memories lower than 64KB – 128KB (depending on design requirements). Again we expect that this crossover point will increase in 1T-1C operation and in future process technology shrinks.
· TI is also currently not targeting its embedded FRAM products for automotive applications.
11.Is F-RAM and FeRAM the same as FRAM?
Yes. F-RAM, FeRAM and FRAM are synonymous. Texas Instruments has chosen to use the acronym "FRAM" while Ramtron has chosen "F-RAM".
12.Are there commercially available FRAM products in the market?
FRAM is commercially proven in the semiconductor market with more than 150 million units sold by Ramtron alone. Ramtron's F-RAM memory products have become a very popular choice in high quality industries such as automotive. Manufacturers such as Mercedes, GM, BMW, Ford, Porsche, and others, are now using FRAM in their automobiles.
TI is currently producing Ramtron's 4-Mb and 2-Mb FRAM memory on its advanced 130-nanometer (nm) FRAM manufacturing process (http://www.ramtron.com/products/nonvolatile-memory/parallel.aspx). Ramtron's 4-Mb FRAM memory product was named 2008 Product of the Year by Electronic Products China (EPC) Magazine.
13.Can I solder FRAM microcontrollers under the same conditions used for Flash memory based device?
No. Data retention on FRAM memory can not be guaranteed when exceeding the specified maximum storage temperature (Ts).
For soldering during board manufacturing it is required to follow the current JEDEC J-STD-020 specification with peak reflow temperatures not higher than classified on the device label on the shipping boxes or reels.
If hand soldering is required for application prototyping, peak temperature must not exceed 250°C for a total of 5 minutes on any single device.
Programming of devices with user application code should only be performed post reflow/hand soldering.
Factory programmed information such as calibration values are designed to withstand the temperatures normally reached in the current JEDEC J-STD-020 specification.
14.Will code that's been written on other MSP430 devices be compatible with the new MSP430FR57xx devices with FRAM?
Yes! While there are some considerations that need to be taken, code written on flash-based MSP430 devices can absolutely be used with the MSP430FR57xx devices with FRAM. Since FRAM uses many of the same peripherals found on other MSP430 devices, the transition is very simple.
15.Is developing on FRAM completely different from working with a Flash-based MCU?
Not at all. The FRAM technology is completely transparent when it comes to writing code. The development environment is consistent and familiar. While programming and code development is identical to developing on a flash-based MSP430, the performance benefits are staggering.
MSP430 Q&.pdf
(188.5 KB, 下载次数: 3)
|