How to get more MSP430 microcontroller resources (updated)[Copy link]
This post was last edited by tiankai001 on 2019-2-22 13:39This content is originally created by EEWORLD forum user tiankai001. If you need to reprint or use it for commercial purposes, you must obtain the author's consent and indicate the sourceI once saw a sentence on the Internet: MSP430 microcontroller is the one with the most official resources. This sentence may be a bit exaggerated, but it also shows from the side that TI has provided a lot of technical support for the development and promotion of MSP430. There are abundant resources on MSP430 MCU. Not to mention the learning notes, tutorials and tips on MSP430 MCU released by technicians engaged in MSP430 MCU development on various websites, TI also provides various resources with rich content. Today I saw a book about MSP430 in the EEWORLD download center, "MSP430 Microcontroller Basics", which is an original English book. I glanced over the book and found that it is very good. It contains content about how to obtain more MSP430 resources. I think the summary is very good, so I simply translated it and share and learn with everyone. This part mainly describes how to obtain TI's official MSP430 microcontroller development resources, including many aspects: data sheets, user guides, sample codes, etc. There are 9 parts in total. I will post them one by one and put them in this post. The specific content is scattered on each floor. Please check them as appropriate. Welcome to put forward valuable suggestions, learn together and improve together!
How to get more resources for MSP430 microcontrollers?
Even a small and low-priced microcontroller is a complex system. It also requires a lot of resource information to fully understand and familiarize yourself with this microcontroller. One of the wishes of electronic engineers in their work is to obtain high-quality resources provided by most manufacturers. TI is no exception. Of course, you need to obtain the data sheet and corresponding user guide of the microcontroller you are using. Be sure to get the latest version from the TI official website, which will serve as your preferred reference material. This post mainly contains the following contents: 1. Data Sheet 2. User Guide 3. Simulation Tool (FET) User Guide 4. Application Notes 5. Code Examples 6. Training 8. End with an example The specific content is in each floor.
You will quickly become familiar with the organization of TI's MSP430 microcontroller resources. This section is a brief summary of the datasheet organization. Here we use the MS0430F2013 microcontroller as an example to briefly explain. Like most MSP430 microcontroller data sheets, this data sheet covers the relevant models of this type of microcontroller: MSP430x20x1, MSP430x20x2, and MSP430x20x3. Here are the main parts of the data sheet for this type of microcontroller: Home: Give a brief general description of this type of microcontroller. This section is very useful when you are looking for key features of the chip's peripherals. For example, the analog-to-digital converter ADC and the integrated circuit bus I2C interface. Here, some of the most important functions will be "selected" to show the characteristics of the chip. For example: At a main frequency of 1MHz and a power supply of 2.2V, the operating current is 220uA; then it is mentioned that the CPU main frequency can reach up to 16MHz. Of course, it is impossible for a CPU to run at the highest clock speed and the lowest current at the same time. This may sound a bit like "stealing the bell from the ears", but it is not: it just emphasizes the most important characteristics of the chip. In any case, the data sheet has complete data, and you can find these data in a targeted manner according to your needs. Device output: For the chip package and pin assignment, please refer to the corresponding figure. Functional block diagram: Displays the main functional modules and peripherals inside the chip. For details, please refer to the figures in the relevant chapters. Terminal Function: Shows which pins the peripheral modules are connected to internally and displays the information displayed on the pins. Brief Description: A brief overview of the CPU, instruction set, operating (low power) modes and interrupt vector addresses. Special Function Registers SFR: Mainly used to control internal functions rather than peripherals. Memory Organization: Gives the main features of the memory map. Flash Memory: Gives more information on the Flash memory segmentation, which is very important when you need to erase the Flash memory. Peripherals: A brief overview of most of the peripheral modules. Because this information is fully described in the "User's Guide". Of course, the distinction between the relevant data in the data sheet and the user's guide is not clear-cut. This section is most important for peripherals with general-purpose inputs and outputs, which may have different ways of internal or external connections. For example: Timer_A is a typical example. It can choose 4 clock sources, two of which are general-purpose clocks ACLK and SMCLK, but the other clocks INCLK and TACLK may come from different clock sources. In some chips, INCLK and TACLK are independent, but here, INCLK=TACLK. If necessary, either of them can be connected to P1.0. This also allows the timer to be clocked by either the positive or negative edge of the input clock. Peripheral File Map: Lists the peripheral registers and their standard names, which are automatically recognized by the compiler or assembler. Electrical Characteristics: This section covers a wide range of information. Unless you wish to damage the chip you are using, keep the electrical parameters within the "Absolute Maximum Ratings". For a specific application, you should focus your attention on one or more of the relevant sections. For example, if battery life is the most important performance indicator, then tables and charts on chip current consumption, operating mode, frequency, supply voltage, temperature, etc. must be focused on.
1. Data Sheet (Continued) Application Information: Since this manual covers three types of microcontrollers, this section occupies a large space in the data sheet. The most useful part is the allocation of each chip pin (refer to the memory map section of input and output pins ). For hardware designers, the internal circuit structure of the pin is very useful. For example, Schmitt triggers on the inputs are very useful for reducing noise (see the Analog Characteristics of Digital Inputs section). The details in a good data sheet can seem boring and difficult to read, and it takes practice to select the key information. Ron Mancini has written an excellent article on "How to Read a Semiconductor Data Sheet". It focuses on op amps, but the principles apply to microcontrollers as well. There is one point to be made here. Many values are listed in the table with minimum, typical and maximum values, but usually not all. For example, under certain conditions, the current values in the working mode (relative to the sleep mode) are as follows: Minimum value, uncertain; Typical value, 220uA; Maximum value, 270uA. The typical value is obtained by measuring a large number of chips and taking the average value. If you buy a chip and measure the current under the same conditions, you will generally get a close value , which is described in detail in the corresponding table in the data sheet. Now, suppose this parameter is critical to the current design, which must meet a demanding requirement regarding battery life. Can you rely on the typical value? If it is a product that is to be produced in large quantities, you must not only look at the typical value when designing. You should design based on the worst case, that is, according to the maximum operating current in this case. You also need to read the data sheet carefully to determine whether this parameter has been tested. In other words, does the chip manufacturer provide products that ensure that all chips have an operating current of less than 270uA, or is the current value just an estimate that has not been tested in batches? On the other hand, it is possible that you only produce one product. In this case, you should buy more MCUs, test them separately, and then choose the chip with the lowest current. Designing based on typical values may be safe. Finally, the minimum value is not specified, mainly because the minimum value is useless for design, and the design should usually be based on the worst case. Another point is that the ideal value should be zero. Reputable companies such as TI usually provide conservative data that applies to all specified operating conditions. For example, the port output characteristics are suitable for the full temperature range of allowed operation, -40°C to 85°C. In most applications, the device is unlikely to experience the extremes of this range, and you may feel that you can take the data more optimistically than the worst-case scenario. Of course, if you take your product to Antarctica, you will be in trouble. Always check the data sheet for the latest errata. Some bugs are long-standing and effectively built into the chip, for example, the CPU4 bug affects the (push) instruction, but a workaround is built into the development software and the errata states "there are no plans to fix this bug". Other problems may be chip specific.
2. User Guide The data sheet for a specific chip should be read together with the user guide for that series of chips. For example, the MSP430F2013 requires the MSP430x2xx series user guide. The user guide provides a detailed description of all the functional modules in this series, including the CPU. This approach makes the individual data sheets shorter and is convenient because the modules are implemented in the same way in most chips. For example, all msp430s have the same Timer_A, except for the number of channels. Highly customized modules, such as op amps, vary more between different chips. There is a helpful glossary and register list in the first half of the user guide. The general format is that each module is followed by a description of its function. A list of the relevant registers is at the end. It takes a lot of reading to understand how to configure each peripheral. The value of each bit of the register after reset is also provided to indicate how the chip starts.
This post was last edited by tiankai001 on 2019-2-19 16:573. Emulation Tool (FET) User Guide It may seem a bit strange to list this separately, but the MSP-FET430 Flash Emulation Tool (FET) User Guide is a treasure trove of information, even if you don't use the specific hardware or software it is designed for. The main reason is that this document contains a list of frequently asked questions about hardware, program development, and debugging. These are all very useful, so I recommend that you print them out for reference. This article also describes the hardware built into the MSP430 for debugging and emulation. For a long time, the chip's user guide didn't mention it, but a section called "Embedded Emulation Module (EEM)" was added. This is useful to understand the main features when debugging in emulation, such as how many breakpoints are available when debugging, how big the program is, how much RAM space is used, etc. There is more in the application note Using IAR's MSP430 EEM Debug Features.
Fourth, Application Notes There are a large number of application notes about MSP430 on the TI official website. Some application notes are general, such as "MSP430 microcontroller software coding technology", and most application notes record how to solve specific problems. You can browse the list of these application notes. If someone has already solved your problem, it is very valuable for reference. One application note that must be specially mentioned is Lutz Bierl's application report. Although the content of this note is a bit outdated because it is based on the outdated MSP430x3xx series, the details in it are worth paying attention to. It includes software and hardware, CPU and peripherals. The author of this application note is one of the architects of the msp430 microcontroller.
V. Code Examples These code examples usually include assembly language and C language. You can choose the examples of the corresponding programming language to learn and refer to as needed. These examples basically cover all the main functions of this type of chip. Almost every peripheral module has at least one routine to demonstrate how to use and program control. These processes can help developers quickly become familiar with and use the msp430 microcontroller. The code examples provided by TI are selected from typical representative chips. Not every microcontroller has a reference process. For example, for Timer_A, msp430F2013 provides nearly 20 examples, covering various functions such as timing, counting, PWM, capture, and comparison. (If there is no ACLK in the system, do not try to select ACLK as the clock source for Timer_A unless the chip contains a VLO module.)
TI provides various trainings based on MSP430. MSP430 DAY is an introductory training, and the MSP430 MCU Advanced Technical Conference (ATC) training lasts 2.5 days and provides in-depth training on many aspects of MSP430. This training is not cheap, but there are very good training materials. Although the team is small, it is enough for you to meet many people who are involved in chip design, writing application notes, etc. In addition, some online courses and even video courses are also launched on TI's official website.
TI's official website also lists many other resources, including third-party networks and discussion groups. For example, Yahoo's MSP430 discussion group (I don't know if it still exists). Domestic websites, such as EEWORLD, have TI's official cooperation columns, where more designers working on MSP430 microcontrollers can communicate with each other. 8. End with an example Suppose that an MSP430F2013 microcontroller is to perform a series of tasks that require a specific number of clock cycles. How should the system be designed to minimize power consumption? Should the maximum clock frequency (MCLK=16MHz) be used to keep the CPU running for the shortest time? If the frequency of MCLK is reduced, the current will also decrease, but will this measure compensate for the longer time required to perform the task? Remember that the maximum frequency of MCLK depends on VCC. Looking at the current curves in the operating mode in the data sheet, you can choose from the following: a) low frequency 1MHz; b) maximum frequency allowed under the current VCC value; c) maximum frequency allowed by the microcontroller 16MHz. Or, if you have stronger analytical skills, you can use a current as a function of MCLK and VCC for analysis.
Only by being familiar with and understanding the functional configuration of the microcontroller can you do a good job in the project.
Details
Published on 2019-2-20 11:56
提升卡
变色卡
千斤顶
京公网安备 11010802033920号
