下载文档原格式
STANDARDUniversal Flash Storage (UFS) Card ExtensionVersion 1.0JESD220-2MARCH 2016JEDEC SOLID STATE TECHNOLOGY ASSOCIATIONNOTICEJEDEC standards and publications contain material that has been prepared, reviewed, and approved through the JEDEC Board of Directors level and subsequently reviewed and approved by the JEDEClegal counsel.JEDEC standards and publications are designed to serve the public interest through eliminatingmisunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for use by those other than JEDEC members, whether the standard is to be used eitherdomestically or internationally.JEDEC standards and publications are adopted without regard to whether or not their adoption may involve patents or articles, materials, or processes. By such action JEDEC does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the JEDEC standards orpublications.The information included in JEDEC standards and publications represents a sound approach to product specification and application, principally from the solid state device manufacturer viewpoint. Within the JEDEC organization there are procedures whereby a JEDEC standard or publication may be further processed and ultimately become an ANSI standard. No claims to be in conformance with this standardmay be made unless all requirements stated inthe standard are met.Special Legal Disclaimer: JEDEC has received information that certain patents or patent applications may be essential to this standard. However, as of the publication date of this standard, no statements regarding an assurance to license such patents or patent applications have been provided. JEDEC does not make any determination as to the validity or relevancy of such patents or patent applications. Anyone making use of the standard assumes all liability resulting from such use. JEDEC and its members disclaim any representation or warranty, express or implied, relating to the standard and its use. Inquiries, comments, and suggestions relative to the content of this JEDEC standard or publication should be addressed to JEDEC at the address below, or refer to under Standards and Documentsfor alternative contact information.Published by©JEDEC Solid State Technology Association 20163103 North 10th StreetSuite 240 SouthArlington, VA 22201-2107This document may be downloaded free of charge; however JEDEC retains the copyright on this material.By downloading this file the individual agrees not to charge for or resell the resulting material.PRICE: Contact JEDECPrinted in the U.S.A.All rights reservedPLEASE!DON’T VIOLATETHELAW!This document is copyrighted by JEDEC and may not bereproduced without permission.For information, contact:JEDEC Solid State Technology Association3103 North 10th StreetSuite 240 SouthArlington, VA 22201-2107or refer to under Standards-Documents/Copyright Information.JEDEC Standard No. 220-2 UNIVERSAL FLASH STORAGE (UFS) CARD EXTENSION, VERSION 1.0ContentsPage Foreword i Introduction i 1Scope 1 2Normative Reference 1 3Terms, and definitions 1 3.1Acronyms 1 3.2Terms and definitions 2 3.3Keywords 2 3.4Abbreviations 3 3.5Conventions 3 4Introduction 4 4.1Overview 4 4.2Functional Features 4 5UFS Card System Architecture 5 5.1Overview 5 5.2UFS Card Signals 5 6UFS Card Design 6 7Feature comParison of embedded UFS and UFS card 9 8UFS Card initialization 10 8.1Initialization Sequence 11 9Power Consumption 12 Annex A (informative) Host Guideline for UFS Card Detection 13 FiguresFigure 5.1 — UFS Card Block Diagram 5 Figure 6.1 — UFS Card Top View 6 Figure 6.2 — UFS Card Bottom View 7 Figure 6.3 — UFS Card Side View 8 Figure 8.1 — UFS Card Initialization 10 Figure 8.2 — UFS Card Initialization Sequence 11 TablesTable 5.1 — Signal Name and Definitions 5 Table 7.1 — Comparison of embedded UFS and UFS Card 9JEDEC Standard No. 220-2UNIVERSAL FLASH STORAGE (UFS) CARD EXTENSION, VERSION 1.0ForewordThis standard has been prepared by JEDEC. The purpose of this standard is to define a UFS card specification. This document will be extension of the UFS Standard, JESD220.IntroductionThe UFS device (embedded/removable) is a universal data storage and communication media. It is designed to cover a wide area of applications as smart phones, cameras, organizers, PDAs, digital recorders, MP3 players, internet tablets, electronic toys, etc.JEDEC Standard No. 220-2Page 1 UNIVERSAL FLASH STORAGE (UFS) CARD EXTENSION, VERSION 1.0 (From JEDEC Board Ballot JCB-16-12, formulated under the cognizance of the JC-64.1 Subcommittee on Electrical Specifications and Command Protocols (Item 133.69).)1ScopeThis standard specifies the characteristics of the UFS card electrical interface and the memory device. This document defines the added/modified features in UFS card compared to embedded UFS device. For other common features JESD220, UFS, Version 2.0, will be referenced.2Normative ReferenceThe following normative documents contain provisions that, through reference in this text, constitute provisions of this standard. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. However, parties to agreements based on this standard are encouraged to investigate the possibility of applying the most recent editions of the normative documents listed. For undated references, the latest edition of the normative document referred to applies.[MIPI-M-PHY], MIPI Alliance Specification for M-PHY SM Specification, Version 3.0[MIPI-UniPro], MIPI Alliance Specification for Unified Protocol (UniPro SM), Version 1.6[MIPI-DDB], MIPI Alliance Specification for Device Descriptor Block (DDB), Version[SAM], SCSI Architecture Model – 5 (SAM–5), Revision 05, 19 May 2010[SPC], T10 Specification: SCSI Primary Commands – 4 (SPC-4), Revision 27, 11 October 2010 [SBC], T10 Specification: SCSI Block Commands – 3 (SBC–3), Revision 24, 05 August 2010 [UFS], JEDEC JESD220B, Universal Flash Storage (UFS), Version 2.0[UFS], JEDEC JEP95, MO-320, UFS Card Form Factor3Terms, and definitionsFor the purpose of this standard, the terms and definitions given in the documents included in section 2“Normative Reference” and the following apply.3.1JEDEC Standard No. 220-2Page 23 Terms, and definitions (cont’d)3.2Terms and definitionsByte: An 8‐bit data value with most significant bit labeled as bit 7 and least significant bit as bit 0. Device: An addressable device on the UFS bus usually a target that contains at least one LUNHost: An addressable device on the UFS bus which is usually the main CPU that hosts the UFS bus3.3KeywordsSeveral keywords are used to differentiate levels of requirements and options, as follow:Can: A keyword used for statements of possibility and capability, whether material, physical, or causal (can equals is able to).Expected: A keyword used to describe the behavior of the hardware or software in the design models assumed by this standard. Other hardware and software design models may also be implemented. Ignored: A keyword that describes bits, bytes, quadlets, or fields whose values are not checked by the recipient.Mandatory: A keyword that indicates items required to be implemented as defined by this standard. May: A keyword that indicates a course of action permissible within the limits of the standard (may equals is permitted).Must: The use of the word must is deprecated and shall not be used when stating mandatory requirements; must is used only to describe unavoidable situations.Optional: A keyword that describes features which are not required to be implemented by this standard. However, if any optional feature defined by the standard is implemented, it shall be implemented as defined by the standard.Reserved: A keyword used to describe objects—bits, bytes, and fields—or the code values assigned to these objects in cases where either the object or the code value is set aside for future standardization. Usage and interpretation may be specified by future extensions to this or other standards. A reserved object shall be zeroed or, upon development of a future standard, set to a value specified by such a standard. The recipient of a reserved object shall not check its value. The recipient of a defined object shall check its value and reject reserved code values.Shall: A keyword that indicates a mandatory requirement strictly to be followed in order to conform to the standard and from which no deviation is permitted (shall equals is required to). Designers are required to implement all such mandatory requirements to assure interoperability with other products conforming to this standard.Should: A keyword used to indicate that among several possibilities one is recommended as particularly suitable, without mentioning or excluding others; or that a certain course of action is preferred but not necessarily required; or that (in the negative form) a certain course of action is deprecated but not prohibited (should equals is recommended that).Will: The use of the word will is deprecated and shall not be used when stating mandatory requirements; will is only used in statements of fact.JEDEC Standard No. 220-2Page 3 3 Terms, and definitions (cont’d)3.4Abbreviationsetc. - And so forth (Latin: et cetera)e.g. - For example (Latin: exempli gratia)i.e. - That is (Latin: id est)3.5ConventionsUFS specification follows some conventions used in SCSI documents since it adopts several SCSI standards.A binary number is represented in this standard by any sequence of digits consisting of only the Western-Arabic numerals 0 and 1 immediately followed by a lower-case b (e.g., 0101b). Spaces may be included in binary number representations to increase readability or delineate field boundaries (e.g., 0 0101 1010b).A hexadecimal number is represented in this standard by any sequence of digits consisting of only the Western-Arabic numerals 0 through 9 and/or the upper-case English letters A through F immediately followed by a lower-case h (e.g., FA23h). Spaces may be included in hexadecimal number representations to increase readability or delineate field boundaries (e.g.,B FD8C FA23h).A decimal number is represented in this standard by any sequence of digits consisting of only the Western-Arabic numerals 0 through 9 not immediately followed by a lower-case b or lower-case h (e.g.,25).A range of numeric values is represented in this standard in the form "a to z", where a is the first value included in the range, all values between a and z are included in the range, and z is the last value included in the range (e.g., the representation "0h to 3h" includes the values 0h, 1h, 2h, and 3h).When the value of the bit or field is not relevant, x or xx appears in place of a specific value.The first letter of the name of a Flag is a lower-case f (e.g., fMyFlag).The first letter of the name of a parameter included a Descriptor or the first letter of the name of an Attribute is:∙ a lower-case b if the parameter or the Attribute size is one byte (e.g., bMyParameter),∙ a lower-case w if the parameter or the Attribute size is two bytes (e.g., wMyParameter),∙ a lower-case d if the parameter or the Attribute size is four bytes (e.g., dMyParameter),∙ a lower-case q if the parameter or the Attribute size is eight bytes (e.g., qMyParameter).JEDEC Standard No. 220-2Page 44Introduction4.1OverviewThe JESD220 standard already defined some features for UFS card (removable). The UFS card uses same protocol as embedded UFS device, but it has few card specific requirements like power consumption.4.2Functional FeaturesUFS card functional features are similar to UFS embedded device. These include:∙Support for MIPI M-PHY PWM-Gear1. HS-Gear2 (optional) and HS-Gear3∙Supports Multiple partitions (LUNs) with partition Management∙Supports Multiple User Data Partition with Enhanced User Data Area options∙Reliable write operation∙Background operations∙Secure operations, Purge and Erase to enhance data security∙Write Protection options, including Permanent and Power-On Write Protection∙Task management operations∙Power management operations5UFS Card System Architecture5.1OverviewThe UFS card will use same protocol as embedded UFS device. There will not be any change in the overall system architecture of removable UFS card compared to embedded card.5.2UFS Card SignalsFigure 5.1 shows the conceptual drawing of UFS card.C/DFigure 5.1 — UFS Card Block Diagram6 UFS Card DesignThe UFS card will follow the shark design and a simplified pictorial representation is shown in Figure 6.1. Refer to JEP95, MO-320, for more detailed mechanical dimensions of Figure 6.1, Figure 6.2 and Figure 6.3.Figure 6.1 — UFS Card Top View6 UFS Card Design (cont’d)Figure 6.2 — UFS Card Bottom ViewPin 16 UFS Card Design (cont’d)Figure 6.3 — UFS Card Side View7Feature comparison of embedded UFS and UFS cardThe embedded UFS and UFS card follow the same protocol. But they will be used in different environment, the use cases will differ. So the UFS card shall have differences in supporting few features compared to embedded UFS. Table 7.1 shows the difference between embedded UFS and UFS card.The UFS card is supposed to be lite version of embedded UFS. So support for unnecessary gears shall be removed and UFS card shall supports only PWM-Gear1, HS-Gear2 (optional), and HS-Gear3. Similarly the UFS card shall support up to 1 lane compared to embedded UFS supports 2 lanes.VCCQ : The VCCQ pin is removed from UFS card to reduce the pin count. The UFS card vendors can use embed LDO to get the lower voltage which is aligned to their low voltage core from 3.3 V or 1.8 V source. Also as a power supply, 3.3 V and 1.8 V are mandatory considering the NAND controller, I/O logic. But 1.2 V can be generated wisely from 3.3 V or 1.8 V. So VCCQ pin (1.2 V) is not supported in UFS card.HW Reset : In case of embedded UFS the chip cannot be detached from the system PCB, so the HW reset pin is required.But in UFS card, card removal is possible, therefore the HW reset pin can be avoided. The minimizing of UFS card pin count can reduce the development and testing cost.Attributes : In embedded UFS the bRefClkFreq, bMaxNumOfRTT, and bMaxDataInSize, bMaxDataOutSize, bOutOfOrderDataEn and bActiveICCLevel attribute values are persistent. As the embedded UFS chip can’t be removed from the host, making these attributes value as persistent avoids re-initialization of these attributes. But in case of UFS card, it can be inserted in to different host which may want to use different values for these parameters. So in UFS card these attributes value shall reset to default value after every reset.8 UFS Card initializationThe UFS cad initialization follows same sequence as of eUFS. But as this is a removable device,VCC(3.3 V) and VCCQ2(1.8 V) may be provided after the UFS card is fully inserted into the card slot. The C/D pin may be used to support card insertion detection (refer to Annex A).Figure 8.1 — UFS Card InitializationCard Insertion UFS Link Start -up Process WaitNot Inserted Supply VCCQ2(1.8 V), VCC(3.3 V) Detect Card insertion in VoltageInserted8.1Initialization SequenceOnce the reset is done, the host will set the attributes to make the card compatible with the particular host.Figure 8.2 — UFS Card Initialization SequenceThe UFS card initialization is same as of embedded UFS, except the bRefClkFreq, bMaxNumOfRTT, bMaxDataInSize, bMaxDataOutSize,bOutOfOrderDataEn and bActiveICClevel attributes value will be set by the host. In embedded UFS these attributes will retain the value after the reset. But since the UFS card can be inserted into different host, these attribute values will be reset to their default value. The host has to set appropriate value before changing the mode to high speed mode.9Power ConsumptionThe UFS card shall be able to work in any host. Therefore power level which any UFS card can work shall be defined for host to provide required amount of power. So considering the removable card industry, the 1.6 watt would be needed for power consumption of the UFS card . The UFS card shall consume maximum 300 mA from VCC(3.3 V) and maximum 300 mA from VCCQ2(1.8 V).Annex A (informative) Host Guideline for UFS Card DetectionThe card detection (C/D) pin may be utilized to detect card insertion, by adding pull-up resistor to the C/D pin in the host-side C/D pin. When the UFS card is not inserted, host-side C/D pin shows non-zero voltage value. When the UFS card is inserted, host-side C/D pin shows zero voltage value because C/D pin of device is tied to ground.Figure A.1 — Host guideline for UFS Card DetectionUFS Card UFS HostStandard Improvement Form JEDECThe purpose of this form is to provide the Technical Committees of JEDEC with input from the industry regarding usage of the subject standard. Individuals or companies are invited to submit comments to JEDEC. All comments will be collected and dispersed to the appropriate committee(s).If you can provide input, please complete this form and return to:JEDECAttn: Publications Department3103 North 10th StreetSuite 240 SouthArlington, VA 22201-2107Fax: 703.907.7583Requirement, clause numberTest method number Clause numberUnclear Too RigidIn ErrorOther2. Recommendations for correction:3. Other suggestions for document improvement:Submitted byName: Phone: Company: E-mail: Address:City/State/Zip: Date:。
CSNP1GCR01-BOWVersion：V1.1JAN20, 2021Revision HistoryVersion Date DescriptionV1.0 16/03/2020 Origin DraftV1.1 20/01/2021 Updated operating temperatureContentsREVISION HISTORY (I)1. INTRODUCTION (1)1.1O VERVIEW (1)1.2F EATURES (1)1.3B LOCK D IAGRAM (1)2. PRODUCT SPECIFICATIONS (2)2.1P IN A SSIGNMENTS (T OP V IEW) (2)2.2P ACKAGE D IMENSIONS (2)3. PERFORMANCE (4)4. DC CHARACTERISTICS (5)5. AC CHARACTERISTICS (6)5.1B US T IMING (D EFAULT M ODE) (6)5.2B US T IMING (H IGH-SPEED M ODE) (6)6. REFERENCE DESIGN (8)1. Introduction1.1 OverviewCSNP1GCR01-BOW is an 1Gb density of embedded storage based on NAND Flash and SD controller. This product has many advantages comparing to raw NAND, it has embedded bad block management, and stronger embedded ECC.CSNP1GCR01-BOW is LGA-8 package. The size is 8mm x 6mm x0.75mm.1.2 Featuresl Interface: Standard SD Specification Version 2.0 with 1-I/O and 4-I/O.l Power supply: Vcc = 2.7V - 3.6Vl Default mode: Variable clock rate 0 - 25 MHz, up to 12.5 MB/sec interface speed (using 4 parallel data lines)l High-Speed mode: Variable clock rate 0 - 50 MHz, up to 25 MB/sec interface speed (using 4 parallel data lines)l Operating Temperature: -30°C to +85°Cl Storage Temperature: -40°C to +85°Cl Standby Current：< 200uA1.3 Block Diagram2. Product Specifications2.1 Pin Assignments (Top View)PIN# SD MODE SPI MODE NAME TYPE1DESCRIPTION NAME TYPE DESCRIPTION1 SDD2 I/O/PP Data Line [Bit2] RSV Reserved2 CD/SDD32I/O/PP3SDNAND Detect/CS I3Chip Select (Neg True)Data Line [Bit3]3 SCLK I Clock SCLK I Clock4 VSS S Supply V oltage Ground VSS S Supply V oltage Ground5 CMD PP Command/Response DI I Data In6 SDD0 I/O/PP Data Line [Bit0] DO O/PP Data Out7 SDD1 I/O/PP Data Line [Bit1] RSV Reserved8 VCC S Supply V oltage VCC S Supply V oltage1) S: power supply; I: input; O: output using push-pull drivers; PP: I/O using push-pull drivers;2) The extended SDD lines (SDD1-SDD3) are input on power up. They start to operate as SDD lines afterSET_BUS_WIDTH command. The Host shall keep its own SDD1-SDD3 lines in input mode, as well,while they are not used. It is defined so, in order to keep compatibility to SDNAND.2.2 Package DimensionsTOP VIEWSIDE VIEWCommon DimensionsSymbol Min Nom Max NoteA 0.65 0.75 0.85B 1.17 1.27 1.37C 6.90 7 7.10D 7.90 8 8.10E 5.90 6 6.10F 10.90 11 11.1H 0.75 0.85 0.95SDNAND Package Dimensions (unit: mm)3. PerformanceParameter RangeWork Model -30°~ 85℃TemperatureStorage Model - 40°~ 85℃Work Model 8% to 95%, Non-condensing HumidityStorage Model 8% to 95%, Non-condensing4. DC CharacteristicsSymbol PARAMETER CONDITIONS MIN TYP MAX UNITS V IL Input low voltage VSS-0.3 0.25VCC V V IH Input high voltage 0.625VCC VCC+0.3 VV OL Output low voltage IOL=100μA@VCC_min0.125VCC VV OH Output high voltage IOH=100μA@VCC_min0.75VCC VI IN Input leakage current VIN=VCC or 0 -10 +/-1 10 μAI OUT Tri-state output leakagecurrent-10 +/-1 10 μAI STBY Standby current 3.3V@clockstop150 200 μAI OP Operation current 3.3v@50MHz(Write)15 25 mA 3.3v@50MHz(Read)15 25 mA5. AC Characteristics5.1 Bus Timing (Default Mode)SYMBOL PARAMETER MIN MAX UNIT NOTEF SD SD clock frequency 0 25 MHzT WL Clock low time 10 nsT WH Clock high time 10 nsT TLH Clock rise time 10 nsT THL Clock fall time 10 nsT ISU Input setup time 5 nsT IH Input hold time 5 nsT ODLY Output delay time 0 14 ns5.2 Bus Timing (High-speed Mode)SYMBOL PARAMETER MIN MAX UNIT NOTEF SD SD clock frequency 0 25 MHzT WL Clock low time 10 nsT WH Clock high time 10 nsT TLH Clock rise time 10 nsT THL Clock fall time 10 nsT ISU Input setup time 5 nsT IH Input hold time 5 nsT ODLY Output delay time 0 14 nsT OH Output hold time 2.5 nsCSNP1GCR01-BOW8 6. Reference DesignNote ：R DAT and R CMD (10K~100 kΩ) are pull-up resistors protecting the CMD and the DAT lines against bus floating when SDNAND is in a high-impedance mode.The host shall pull-up all DAT0-3 lines by R DAT , even if the host uses the SDNAND as 1-bit mode only in SD mode. It is recommended to have 2.2uF capacitance on VCC.R CLKreference 0~120 Ω.。
嵌入式linux常见评估指标介绍在嵌入式项目预研前期阶段，我们常常需要对某个平台进行资源和性能方面的评估，以下是最常见的一些评估指标：1、内存评估系统内存空间通过free、cat /proc/meminfo或者top，查看内存情况。
一般有这样一个经验公式：应用程序可用内存/系统物理内存>70%时，表示系统内存资源非常充足，不影响系统性能；20%<应用程序可用内存/系统物理内存<70%时，表示系统内存资源基本能满足应用需求，暂时不影响系统性能；应用程序可用内存/系统物理内存<20%时，表示系统内存资源紧缺，需要增加系统内存；$ freetotal used free shared buff/c ac heav ai lableMem: 123496 21512 75132 1132 26852 63416Swap: 0 0 0$ cat /proc/meminfoMemTotal: 123496 kB //所有可用的内存大小，物理内存减去预留位和内核使用。
系统从加电开始到引导完成，firmware/B IOS要预留一些内存，内核本身要占用一些内存，最后剩下可供内核支配的内存就是MemTotal。
这个值在系统运行期间一般是固定不变的，重启会改变。
MemFree: 75132 kB //表示系统尚未使用的内存。
MemAvailable: 63400 kB //真正的系统可用内存，系统中有些内存虽然已被使用但是可以回收的，比如cache/buffer、slab都有一部分可以回收，所以这部分可回收的内存加上MemFree才是系统可用的内存Buffe rs: 5644 kB //用来给块设备做缓存的内存，(文件系统的met ad ata、pages)Cached: 19040 kB //分配给文件缓冲区的内存,例如vi一个文件，就会将未保存的内容写到该缓冲区SwapCached: 0 kB //被高速缓冲存储用的交换空间（硬盘的swap）的大小Active: 20356 kB //经常使用的高速缓冲存储器页面文件大小Inactive: 12628 kB //不经常使用的高速缓冲存储器文件大小Active(anon): 9412 kB //活跃的匿名内存Inactive(anon): 20 kB //不活跃的匿名内存Active(file): 10944 kB //活跃的文件使用内存Inactive(file): 12608 kB //不活跃的文件使用内存Unevictable: 0 kB //不能被释放的内存页Mlocked: 0 kB //系统调用 mlockSwapTotal: 0 kB //交换空间总内存SwapFree: 0 kB //交换空间空闲内存Dirty: 0 kB //等待被写回到磁盘的Wri te back: 0 kB //正在被写回的AnonPages: 8300 kB //未映射页的内存/映射到用户空间的非文件页表大小Mapped: 11480 kB //映射文件内存Shmem: 1132 kB //已经被分配的共享内存KReclaimable: 2132 kB //内核内存，内存压力时内核尝试回收Slab: 8240 kB //内核数据结构缓存SReclaimable: 2132 kB //可收回slab内存SUnreclaim: 6108 kB //不可收回slab内存KernelStack: 568 kB //内核消耗的内存PageTables: 516 kB //管理内存分页的索引表的大小NFS_Unstable: 0 kB //不稳定页表的大小Bounce: 0 kB //在低端内存中分配一个临时buffer作为跳转，把位于高端内存的缓存数据复制到此处消耗的内存WritebackTmp: 0 kB //FUSE用于临时写回缓冲区的内存CommitLimit: 61748 kB //系统实际可分配内存Committed_AS: 58568 kB //系统当前已分配的内存VmallocTotal: 1048372 kB //预留的虚拟内存总量VmallocUsed: 1288 kB //已经被使用的虚拟内存VmallocChunk: 0 kB //可分配的最大的逻辑连续的虚拟内存Per cpu: 32 kB //percpu机制使用的内存2、磁盘评估获取磁盘空间$ df -hFilesystem Size Used Available Use% Mounted on /dev/root 6.0M 6.0M 0 100% /romtmpfs 60.3M 1.1M 59.2M 2% /tmp/dev/mtdblock6 23.8M 9.0M 14.8M 38% /overlay overlayfs:/overlay 23.8M 9.0M 14.8M 38% /tmpfs 512.0K 0 512.0K 0% /dev Filesystem：代表该文件系统时哪个分区，所以列出的是设备名称。
摘要SD卡（Secure Digital Memory Card）中文翻译为安全数码卡，是一种基于半导体快闪记忆器的新一代记忆设备，它被广泛地于便携式装置上使用，例如数码相机、个人数码助理(PDA)和多媒体播放器等。
本实训的作品是利用基于ARM Cotex-M3内核的嵌入式处理器STM32自带的SDIO硬件接口来驱动SD卡，并结合文件系统 FATFS R0.07C来完成一个基于嵌入式ARM的SD卡读写的作品，现实向SD 卡写入一个txt文件，并读取SD卡的文件目标并通过串口打印到PC机显示。
关键词：嵌入式；ARM；STM32；SD卡；文件系统AbstractSD Card (Secure Digital Memory Card) Chinese translation for Secure Digital Card, it is a kind of based on semiconductor flash Memory of a new generation of Memory device, it is widely used in portable devices, such as Digital cameras, personal Digital assistant (PDA) and multimedia player, etc. This training work is based on ARM Cotex - M3 kernel embedded processor STM32 own SDIO hardware interface to drive the SD card, and combined with the file system FATFS R0.07 C to complete a based on embedded ARM of the SD card, speaking, reading and writing work, reality to SD card to a TXT file, and read SD card file goals and through the serial port print to PC display.Key words：embedded;ARM;STM32; SD Card; File system目录1 前言 (1)1.1ARM应用背景 (1)1.2研究内容 (2)1.3研究成果 (3)2 STM32处理器概述 (3)2.1STM32简介 (3)2.1.1 STM32F103VET6的参数 (4)2.2内部资源 (6)2.3C ORTEX-M3内核简介 (6)2.4STM32SDIO简介 (7)2.4.1 SDIO简介 (7)2.4.2 SDIO功能特性 (8)3 SDIO的原理及实现方法 (8)3.1原理 (9)3.2SDIO适配器 (10)3.3SDIO卡识别过程 (11)3.4SDIO写数据块 (12)3.5SDIO读数据块 (13)4 FATFS文件系统 (13)4.1F A T FS文件系统简介 (13)4.2F A T FS文件系统移植 (14)4.2.1移植前工作 (14)4.2.2开始移植 (14)5 测试及结果 (15)5.1JTAG仿真器介绍 (16)5.2现象及结果 (16)6 结论 (18)致谢 (19)参考文献 (20)1 前言1.1 ARM应用背景如今，学习一种处理器的就有许多ARM内核的处理器可供使用，现在社会已步入嵌入式学习阶段。
嵌入式系统存储标准与规范测试（答案见尾页）一、选择题1. 嵌入式系统常用的存储标准有哪些？A. SPIB. I2CC. NAND FlashD. NOR FlashE. RAM2. 下列哪个不是嵌入式系统常用的存储类型？A. 随机存取存储器 (RAM)B. 只读存储器 (ROM)C. 硬盘驱动器 (HDD)D. 固态硬盘驱动器 (SSD)E. 闪存卡3. 嵌入式系统中，哪种存储技术具有最快的读写速度？A. SDRAMB. DDR SDRAMC. SRAMD. NAND FlashE. NOR Flash4. 在嵌入式系统中，哪种存储设备通常用于存储固件和引导程序？A. RAMB. ROMC. SSDD. HDDE. 闪存卡5. 嵌入式系统的存储容量通常以什么为单位衡量？B. GBC. TBD. PBE. EB6. 嵌入式系统在读取数据时，哪种存储设备的访问速度最快？A. RAMB. ROMC. 硬盘驱动器 (HDD)D. 固态硬盘驱动器 (SSD)E. 闪存卡7. 在嵌入式系统中，哪种存储技术支持随机访问且无需刷写？A. SDRAMB. DDR SDRAMC. SRAMD. NAND FlashE. NOR Flash8. 嵌入式系统在写入数据时，哪种存储设备需要经过刷写才能保存数据？A. RAMB. ROMC. 硬盘驱动器 (HDD)D. 固态硬盘驱动器 (SSD)E. 闪存卡9. 嵌入式系统在存储大量数据时，哪种存储设备成本最低？A. RAMB. ROMC. 硬盘驱动器 (HDD)D. 固态硬盘驱动器 (SSD)E. 闪存卡10. 在嵌入式系统中，哪种存储设备最适合存储大量数据和程序，并且无需外部电源？B. ROMC. 硬盘驱动器 (HDD)D. 固态硬盘驱动器 (SSD)E. 闪存卡11. 在嵌入式系统存储测试中，通常关注哪些性能指标？A. 读写速度B. 容量C. 抗干扰能力D. 功耗E. 所有上述指标12. 存储器类型中，SRAM和DRAM的主要区别是什么？A. 生命周期B. 价格C. 可靠性D. 频率响应E. 所有上述选项13. 在嵌入式系统中，哪种存储器通常用于存储固件和引导代码？A. FlashB. ROMC. RAMD. Flash Memory14. 嵌入式系统中的存储设备通常遵循哪些规范？A. NAND Flash SpecificationB. Serial Peripheral Interface (SPI) SpecificationC. Intelligent Platform Management Interface (IPMI) SpecificationD. All of the above15. 在进行存储测试时，常用的测试工具有哪些？A. 文件传输工具（如FTP、SFTP）B. 硬件分析仪C. 性能测试软件D. 所有上述工具16. 嵌入式系统存储器的测试通常包括哪些方面？A. 电气性能测试B. 功能测试C. 环境应力测试D. 所有上述方面17. 在嵌入式系统存储测试中，如何验证存储器的可靠性？A. 使用高低温测试箱模拟极端环境B. 进行长时间连续读写测试C. 模拟实际工作条件进行测试D. 使用高频率扫描测试18. 嵌入式系统存储器的测试需要考虑哪些因素？A. 性能参数B. 环境因素C. 使用寿命D. 兼容性E. 所有上述因素19. 在进行嵌入式系统存储器的测试时，如何确保测试结果的准确性？A. 使用高精度的测试设备B. 严格按照测试流程进行操作C. 对测试数据进行多次重复测试D. 使用自动化测试工具20. 嵌入式系统的存储设备通常包括以下哪种类型？A. RAMB. ROMC. NAND FlashD. All of the above21. 在嵌入式系统中，哪种存储技术具有最快的读写速度？A. SRAMB. DRAMC. NAND FlashD. ROM22. 嵌入式系统中常用的数据存储格式是什么？A. FAT32B. NTFSC. exFATD. All of the above23. 关于SD卡，以下哪个说法是正确的？A. SD卡是一种只读存储器B. SD卡的最大容量可以达到512GBC. SD卡的标准格式是SDXCD. SD卡的物理尺寸是11mm x 6.7mm x 1mm24. 在嵌入式系统中，用于存储固件的通常是哪种类型的存储器？A. RAMB. ROMC. Flash MemoryD. HDD25. 嵌入式系统中的闪存通常分为哪两种类型？A. NVRAM和SRAMB. ROM和Flash MemoryC. DRAM和SRAMD. NAND Flash和NOR Flash26. 下列关于eMMC（嵌入式多媒体卡）的说法中，错误的是？A. eMMC是一种闪存技术B. eMMC可以用于存储操作系统C. eMMC的读写速度比SD卡快D. eMMC支持热插拔27. 在嵌入式系统中，用于存储用户数据和应用程序的是哪种存储器？A. 系统存储器B. 随机存储器C. 只读存储器D. 闪存存储器28. 关于固态硬盘（SSD），以下哪个说法是正确的？A. SSD的读写速度比传统硬盘慢B. SSD需要特殊的电源来维持其运行C. SSD支持即插即用功能D. SSD的价格比传统硬盘高很多29. 在嵌入式系统设计中，选择合适的存储解决方案时需要考虑哪些因素？A. 性能需求B. 成本预算C. 功耗限制D. 所需的数据安全性30. 嵌入式系统的存储设备通常用于存储______和______数据。
STANDARDUniversal Flash Storage (UFS) Card ExtensionVersion 1.0JESD220-2MARCH 2016JEDEC SOLID STATE TECHNOLOGY ASSOCIATIONNOTICEJEDEC standards and publications contain material that has been prepared, reviewed, and approved through the JEDEC Board of Directors level and subsequently reviewed and approved by the JEDEClegal counsel.JEDEC standards and publications are designed to serve the public interest through eliminatingmisunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for use by those other than JEDEC members, whether the standard is to be used eitherdomestically or internationally.JEDEC standards and publications are adopted without regard to whether or not their adoption may involve patents or articles, materials, or processes. By such action JEDEC does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the JEDEC standards orpublications.The information included in JEDEC standards and publications represents a sound approach to product specification and application, principally from the solid state device manufacturer viewpoint. Within the JEDEC organization there are procedures whereby a JEDEC standard or publication may be further processed and ultimately become an ANSI standard. No claims to be in conformance with this standardmay be made unless all requirements stated inthe standard are met.Special Legal Disclaimer: JEDEC has received information that certain patents or patent applications may be essential to this standard. However, as of the publication date of this standard, no statements regarding an assurance to license such patents or patent applications have been provided. JEDEC does not make any determination as to the validity or relevancy of such patents or patent applications. Anyone making use of the standard assumes all liability resulting from such use. JEDEC and its members disclaim any representation or warranty, express or implied, relating to the standard and its use. Inquiries, comments, and suggestions relative to the content of this JEDEC standard or publication should be addressed to JEDEC at the address below, or refer to under Standards and Documentsfor alternative contact information.Published by©JEDEC Solid State Technology Association 20163103 North 10th StreetSuite 240 SouthArlington, VA 22201-2107This document may be downloaded free of charge; however JEDEC retains the copyright on this material.By downloading this file the individual agrees not to charge for or resell the resulting material.PRICE: Contact JEDECPrinted in the U.S.A.All rights reservedPLEASE!DON’T VIOLATETHELAW!This document is copyrighted by JEDEC and may not bereproduced without permission.For information, contact:JEDEC Solid State Technology Association3103 North 10th StreetSuite 240 SouthArlington, VA 22201-2107or refer to under Standards-Documents/Copyright Information.JEDEC Standard No. 220-2 UNIVERSAL FLASH STORAGE (UFS) CARD EXTENSION, VERSION 1.0ContentsPage Foreword i Introduction i 1Scope 1 2Normative Reference 1 3Terms, and definitions 1 3.1Acronyms 1 3.2Terms and definitions 2 3.3Keywords 2 3.4Abbreviations 3 3.5Conventions 3 4Introduction 4 4.1Overview 4 4.2Functional Features 4 5UFS Card System Architecture 5 5.1Overview 5 5.2UFS Card Signals 5 6UFS Card Design 6 7Feature comParison of embedded UFS and UFS card 9 8UFS Card initialization 10 8.1Initialization Sequence 11 9Power Consumption 12 Annex A (informative) Host Guideline for UFS Card Detection 13 FiguresFigure 5.1 — UFS Card Block Diagram 5 Figure 6.1 — UFS Card Top View 6 Figure 6.2 — UFS Card Bottom View 7 Figure 6.3 — UFS Card Side View 8 Figure 8.1 — UFS Card Initialization 10 Figure 8.2 — UFS Card Initialization Sequence 11 TablesTable 5.1 — Signal Name and Definitions 5 Table 7.1 — Comparison of embedded UFS and UFS Card 9JEDEC Standard No. 220-2UNIVERSAL FLASH STORAGE (UFS) CARD EXTENSION, VERSION 1.0ForewordThis standard has been prepared by JEDEC. The purpose of this standard is to define a UFS card specification. This document will be extension of the UFS Standard, JESD220.IntroductionThe UFS device (embedded/removable) is a universal data storage and communication media. It is designed to cover a wide area of applications as smart phones, cameras, organizers, PDAs, digital recorders, MP3 players, internet tablets, electronic toys, etc.JEDEC Standard No. 220-2Page 1 UNIVERSAL FLASH STORAGE (UFS) CARD EXTENSION, VERSION 1.0 (From JEDEC Board Ballot JCB-16-12, formulated under the cognizance of the JC-64.1 Subcommittee on Electrical Specifications and Command Protocols (Item 133.69).)1ScopeThis standard specifies the characteristics of the UFS card electrical interface and the memory device. This document defines the added/modified features in UFS card compared to embedded UFS device. For other common features JESD220, UFS, Version 2.0, will be referenced.2Normative ReferenceThe following normative documents contain provisions that, through reference in this text, constitute provisions of this standard. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. However, parties to agreements based on this standard are encouraged to investigate the possibility of applying the most recent editions of the normative documents listed. For undated references, the latest edition of the normative document referred to applies.[MIPI-M-PHY], MIPI Alliance Specification for M-PHY SM Specification, Version 3.0[MIPI-UniPro], MIPI Alliance Specification for Unified Protocol (UniPro SM), Version 1.6[MIPI-DDB], MIPI Alliance Specification for Device Descriptor Block (DDB), Version[SAM], SCSI Architecture Model – 5 (SAM–5), Revision 05, 19 May 2010[SPC], T10 Specification: SCSI Primary Commands – 4 (SPC-4), Revision 27, 11 October 2010 [SBC], T10 Specification: SCSI Block Commands – 3 (SBC–3), Revision 24, 05 August 2010 [UFS], JEDEC JESD220B, Universal Flash Storage (UFS), Version 2.0[UFS], JEDEC JEP95, MO-320, UFS Card Form Factor3Terms, and definitionsFor the purpose of this standard, the terms and definitions given in the documents included in section 2“Normative Reference” and the following apply.3.1JEDEC Standard No. 220-2Page 23 Terms, and definitions (cont’d)3.2Terms and definitionsByte: An 8‐bit data value with most significant bit labeled as bit 7 and least significant bit as bit 0. Device: An addressable device on the UFS bus usually a target that contains at least one LUNHost: An addressable device on the UFS bus which is usually the main CPU that hosts the UFS bus3.3KeywordsSeveral keywords are used to differentiate levels of requirements and options, as follow:Can: A keyword used for statements of possibility and capability, whether material, physical, or causal (can equals is able to).Expected: A keyword used to describe the behavior of the hardware or software in the design models assumed by this standard. Other hardware and software design models may also be implemented. Ignored: A keyword that describes bits, bytes, quadlets, or fields whose values are not checked by the recipient.Mandatory: A keyword that indicates items required to be implemented as defined by this standard. May: A keyword that indicates a course of action permissible within the limits of the standard (may equals is permitted).Must: The use of the word must is deprecated and shall not be used when stating mandatory requirements; must is used only to describe unavoidable situations.Optional: A keyword that describes features which are not required to be implemented by this standard. However, if any optional feature defined by the standard is implemented, it shall be implemented as defined by the standard.Reserved: A keyword used to describe objects—bits, bytes, and fields—or the code values assigned to these objects in cases where either the object or the code value is set aside for future standardization. Usage and interpretation may be specified by future extensions to this or other standards. A reserved object shall be zeroed or, upon development of a future standard, set to a value specified by such a standard. The recipient of a reserved object shall not check its value. The recipient of a defined object shall check its value and reject reserved code values.Shall: A keyword that indicates a mandatory requirement strictly to be followed in order to conform to the standard and from which no deviation is permitted (shall equals is required to). Designers are required to implement all such mandatory requirements to assure interoperability with other products conforming to this standard.Should: A keyword used to indicate that among several possibilities one is recommended as particularly suitable, without mentioning or excluding others; or that a certain course of action is preferred but not necessarily required; or that (in the negative form) a certain course of action is deprecated but not prohibited (should equals is recommended that).Will: The use of the word will is deprecated and shall not be used when stating mandatory requirements; will is only used in statements of fact.JEDEC Standard No. 220-2Page 3 3 Terms, and definitions (cont’d)3.4Abbreviationsetc. - And so forth (Latin: et cetera)e.g. - For example (Latin: exempli gratia)i.e. - That is (Latin: id est)3.5ConventionsUFS specification follows some conventions used in SCSI documents since it adopts several SCSI standards.A binary number is represented in this standard by any sequence of digits consisting of only the Western-Arabic numerals 0 and 1 immediately followed by a lower-case b (e.g., 0101b). Spaces may be included in binary number representations to increase readability or delineate field boundaries (e.g., 0 0101 1010b).A hexadecimal number is represented in this standard by any sequence of digits consisting of only the Western-Arabic numerals 0 through 9 and/or the upper-case English letters A through F immediately followed by a lower-case h (e.g., FA23h). Spaces may be included in hexadecimal number representations to increase readability or delineate field boundaries (e.g.,B FD8C FA23h).A decimal number is represented in this standard by any sequence of digits consisting of only the Western-Arabic numerals 0 through 9 not immediately followed by a lower-case b or lower-case h (e.g.,25).A range of numeric values is represented in this standard in the form "a to z", where a is the first value included in the range, all values between a and z are included in the range, and z is the last value included in the range (e.g., the representation "0h to 3h" includes the values 0h, 1h, 2h, and 3h).When the value of the bit or field is not relevant, x or xx appears in place of a specific value.The first letter of the name of a Flag is a lower-case f (e.g., fMyFlag).The first letter of the name of a parameter included a Descriptor or the first letter of the name of an Attribute is:∙ a lower-case b if the parameter or the Attribute size is one byte (e.g., bMyParameter),∙ a lower-case w if the parameter or the Attribute size is two bytes (e.g., wMyParameter),∙ a lower-case d if the parameter or the Attribute size is four bytes (e.g., dMyParameter),∙ a lower-case q if the parameter or the Attribute size is eight bytes (e.g., qMyParameter).JEDEC Standard No. 220-2Page 44Introduction4.1OverviewThe JESD220 standard already defined some features for UFS card (removable). The UFS card uses same protocol as embedded UFS device, but it has few card specific requirements like power consumption.4.2Functional FeaturesUFS card functional features are similar to UFS embedded device. These include:∙Support for MIPI M-PHY PWM-Gear1. HS-Gear2 (optional) and HS-Gear3∙Supports Multiple partitions (LUNs) with partition Management∙Supports Multiple User Data Partition with Enhanced User Data Area options∙Reliable write operation∙Background operations∙Secure operations, Purge and Erase to enhance data security∙Write Protection options, including Permanent and Power-On Write Protection∙Task management operations∙Power management operations5UFS Card System Architecture5.1OverviewThe UFS card will use same protocol as embedded UFS device. There will not be any change in the overall system architecture of removable UFS card compared to embedded card.5.2UFS Card SignalsFigure 5.1 shows the conceptual drawing of UFS card.C/DFigure 5.1 — UFS Card Block Diagram6 UFS Card DesignThe UFS card will follow the shark design and a simplified pictorial representation is shown in Figure 6.1. Refer to JEP95, MO-320, for more detailed mechanical dimensions of Figure 6.1, Figure 6.2 and Figure 6.3.Figure 6.1 — UFS Card Top View6 UFS Card Design (cont’d)Figure 6.2 — UFS Card Bottom ViewPin 16 UFS Card Design (cont’d)Figure 6.3 — UFS Card Side View7Feature comparison of embedded UFS and UFS cardThe embedded UFS and UFS card follow the same protocol. But they will be used in different environment, the use cases will differ. So the UFS card shall have differences in supporting few features compared to embedded UFS. Table 7.1 shows the difference between embedded UFS and UFS card.The UFS card is supposed to be lite version of embedded UFS. So support for unnecessary gears shall be removed and UFS card shall supports only PWM-Gear1, HS-Gear2 (optional), and HS-Gear3. Similarly the UFS card shall support up to 1 lane compared to embedded UFS supports 2 lanes.VCCQ : The VCCQ pin is removed from UFS card to reduce the pin count. The UFS card vendors can use embed LDO to get the lower voltage which is aligned to their low voltage core from 3.3 V or 1.8 V source. Also as a power supply, 3.3 V and 1.8 V are mandatory considering the NAND controller, I/O logic. But 1.2 V can be generated wisely from 3.3 V or 1.8 V. So VCCQ pin (1.2 V) is not supported in UFS card.HW Reset : In case of embedded UFS the chip cannot be detached from the system PCB, so the HW reset pin is required.But in UFS card, card removal is possible, therefore the HW reset pin can be avoided. The minimizing of UFS card pin count can reduce the development and testing cost.Attributes : In embedded UFS the bRefClkFreq, bMaxNumOfRTT, and bMaxDataInSize, bMaxDataOutSize, bOutOfOrderDataEn and bActiveICCLevel attribute values are persistent. As the embedded UFS chip can’t be removed from the host, making these attributes value as persistent avoids re-initialization of these attributes. But in case of UFS card, it can be inserted in to different host which may want to use different values for these parameters. So in UFS card these attributes value shall reset to default value after every reset.8 UFS Card initializationThe UFS cad initialization follows same sequence as of eUFS. But as this is a removable device,VCC(3.3 V) and VCCQ2(1.8 V) may be provided after the UFS card is fully inserted into the card slot. The C/D pin may be used to support card insertion detection (refer to Annex A).Figure 8.1 — UFS Card InitializationCard Insertion UFS Link Start -up Process WaitNot Inserted Supply VCCQ2(1.8 V), VCC(3.3 V) Detect Card insertion in VoltageInserted8.1Initialization SequenceOnce the reset is done, the host will set the attributes to make the card compatible with the particular host.Figure 8.2 — UFS Card Initialization SequenceThe UFS card initialization is same as of embedded UFS, except the bRefClkFreq, bMaxNumOfRTT, bMaxDataInSize, bMaxDataOutSize,bOutOfOrderDataEn and bActiveICClevel attributes value will be set by the host. In embedded UFS these attributes will retain the value after the reset. But since the UFS card can be inserted into different host, these attribute values will be reset to their default value. The host has to set appropriate value before changing the mode to high speed mode.9Power ConsumptionThe UFS card shall be able to work in any host. Therefore power level which any UFS card can work shall be defined for host to provide required amount of power. So considering the removable card industry, the 1.6 watt would be needed for power consumption of the UFS card . The UFS card shall consume maximum 300 mA from VCC(3.3 V) and maximum 300 mA from VCCQ2(1.8 V).Annex A (informative) Host Guideline for UFS Card DetectionThe card detection (C/D) pin may be utilized to detect card insertion, by adding pull-up resistor to the C/D pin in the host-side C/D pin. When the UFS card is not inserted, host-side C/D pin shows non-zero voltage value. When the UFS card is inserted, host-side C/D pin shows zero voltage value because C/D pin of device is tied to ground.Figure A.1 — Host guideline for UFS Card DetectionUFS Card UFS HostStandard Improvement Form JEDECThe purpose of this form is to provide the Technical Committees of JEDEC with input from the industry regarding usage of the subject standard. Individuals or companies are invited to submit comments to JEDEC. All comments will be collected and dispersed to the appropriate committee(s).If you can provide input, please complete this form and return to:JEDECAttn: Publications Department3103 North 10th StreetSuite 240 SouthArlington, VA 22201-2107Fax: 703.907.7583Requirement, clause numberTest method number Clause numberUnclear Too RigidIn ErrorOther2. Recommendations for correction:3. Other suggestions for document improvement:Submitted byName: Phone: Company: E-mail: Address:City/State/Zip: Date:。
CNCA/CTS XXXX-200X中国电子技术标准化研究所认证技术规范移动存储设备认证技术规范Definition certification technical specificationsfor mobile storage device（备案稿）中国电子技术标准化研究所目录前言 (1)1 范围 (2)2 规范性引用文件 (2)3 术语和定义 (2)4 技术要求 (3)4.1 外观及结构 (3)4.2 文档和标识 (4)4.3 存取功能 (4)4.4 存储容量 (4)4.5数据存取速度 (4)4.6连续存取 (4)4.7中文要求 (5)5 测试方法 (5)5.1测试环境 (5)5.2 外观及结构检查 (5)5.3 文档和标识检查 (5)5.4 产品性能检测 (5)5.5中文要求 (6)前言本技术规范作为移动存储设备存储相关指标的认证依据。
本技术规范由中国电子技术标准化研究所提出。
本技术规范主要起草单位：中国电子技术标准化研究所、信息产业部移动存储器标准工作组。
本技术规范主要起草人：陈庆芳、高健、张宇宏、秦振山、翁跃峰、范迎生。
移动存储设备认证技术规范1 范围本技术规范规定了移动存储设备(下简称：产品)相关指标及其试验方法。
本技术规范适用于闪存卡、闪存盘、移动硬盘、便携式数字音频播放器、便携式数字音视频播放器等移动存储设备。
2 规范性引用文件下列文件中的条款通过本规范的引用而成为本规范的条款。
凡是注日期的引用文件，其随后所有的修改单（不包括勘误的内容）或修订版均不适用于本规范，然而，鼓励根据本规范达成协议的各方研究是否可使用这些文件的最新版本。
凡是不注日期的引用文件，其最新版本适用于本规范。
GB 2312-1980 信息交换用汉字编码字符集基本集GB 9969.1-1998 工业产品使用说明书总则GB 13000.1-1993 信息技术通用多八位编码字符集(UCS) 第一部分:体系结构与基本多文种平面GB 18030-2005 信息技术中文编码字符集GB/T 191-2000 包装储运图示标志(IDT ISO 780:1997)GB/T 14436-1993 工业产品保证文件总则SJ 11240-2001 信息技术汉字编码字符集(基本集)12点阵字型SJ 11297-2004 信息技术通用多八位编码字符集（基本多文种平面）汉字20点阵字型3 术语和定义3.1移动存储设备Mobile Storage Device能够提供数据存储功能的可携带式设备，可配合宿主一起使用。
《嵌入式技术应用》课程标准编制：审核：单位：日期：2020年3月智能交通技术运用专业教学资源库一、课程性质本课程作为智能交通技术运用专业的一门专业技术核心课程，主要培养学生对嵌入式Cortex-M4系列微控制器的开发应用能力、嵌入式系统设计能力、软件程序设计能力以及工程实践能力。
这些能力是构成本专业职业岗位技能的重要组成部分，是现代嵌入式系统、智能交通等行业的核心技术。
通过本课程的学习，着力培养学生的创新思维能力、独立地分析问题、解决问题的能力和工程实践能力，为以后学习和工作打下良好的专业基础，培养具有良好素质和基本技能、适应能力强、符合社会发展需求的专业技术人才。
二、课程设计思路本课程的内容设计上，采用理论与实践相结合，从行业实际应用出发，注重项目式、任务式教学。
以项目需求为教学目标，以任务功能为教学内容，真正达到“学中做、做中学”的教学理念。
课程主要对嵌入式系统软硬件设计开发展开，包含环境搭建、片上外设应用、串行总线、硬件接口、文件系统、网络协议栈应用、系统程序框架设计、硬件电路设计、分析等内容。
课程设计中注重学生实践能力的培养，强调在智能交通中的实际应用是本课程的归宿。
由于本课程是一门实践性很强的专业课程，所以更强调实践能力培养的重要性，将实践能力培养划分为课程实验、课程设计和综合性实验，综合性实验可为学生参加国家、省、校级电子设计竞赛和大学生课外科技竞赛等活动创造有利条件。
三、课程培养目标（一）总目标通过本课程的学习和实践让学生掌握嵌入式系统设计开发的相关知识。
培养学生对嵌入式技术在智能交通行业中的项目设计、开发、应用技术技能。
使学生能够进一步应用嵌入式相关技术解决工程系统中的具体问题。
具备以嵌入式技术为核心的智能交通产品的开发、设计与调试能力。
（二）具体目标1、能力目标《嵌入式技术应用》课程标准●能够根据项目任务要求快速完成开发环境配置和工程文件搭建。
●能够熟练掌握嵌入式微控制器STM32F407系列片上外设的配置和使用方法，并在项目任务中运用片上外设完成特定功能；●能够利用微控制器各类通信接口，完成项目任务所需的数据通信功能；●能够熟练应用GUI库、掌握嵌入式人机交互界面开发技术技能；●能够掌握嵌入式系统接入云服务典型应用；●能根据项目要求完成功能、框架及流程图设计；●能根据项目要求，完成软件程序代码编写，调试。
