Step 3: Don’t Scrutinize the Electrical Specifications The bottom line here is to think about all of the processor-related details that you do not need to worry about when you’re writing code in C/C++, and then try to identify the corresponding sections of the datasheet so that you can skip them. In many applications, all of this information will be unnecessary.įortunately, this sort of information (from the MSP430FR59xx user guide) is typically important only for the compiler, not for the person who is writing the code. This means that the compiler will automatically manage numerous details related to the internal functionality of your microcontroller, and consequently you can safely ignore the vast majority of these details (at least initially).įor example, the MSP430FR59xx user guide dedicates about 40 pages to the CPU. Though I stubbornly insist upon the value of assembly language, I recognize that in general it is no longer a practical approach to firmware development, and I have no doubt that almost every person who reads this article will write MCU code in C/C++. Thus, the reference manual is relevant primarily to firmware development, though it certainly does include information that must be incorporated into the schematic. The peripheral sections have register descriptions that provide all the information that I need to configure and implement a peripheral’s functionality. The reference manual, on the other hand, has detailed information about internal memory, interrupts, clock sources, the processor core, and all the peripherals.ĭetailed descriptions of peripheral functionality (such as this diagram for an I2C transaction) are provided only in the EFM8 reference manual, not the datasheet. Thus, I would use the datasheet when I’m investigating the device, checking a few performance specifications (current consumption, oscillator precision, ADC nonlinearity, etc.), creating the CAD component, and designing the schematic. The datasheet has a list of features, electrical specifications, some basic hardware-implementation examples, pin definitions, and footprint dimensions.Ĭonnection diagrams such as this one are provided in the EFM8 datasheet. Step 1: Assess the Nature of the Documentsĭespite the (oversimplified) title of this article, many microcontrollers do not have “a datasheet.” Various types of information may be distributed among multiple documents, and you need to briefly examine these documents in order to determine which ones have the specifications, descriptions, and recommendations that you really need during a particular phase of the development process.Īs an example, the EFM8 devices from Silicon Labs have both a datasheet and a reference manual.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |