u boot下自动升级功能设计说明

客户服务电话 客户服务传真 客户服务邮箱 U-bootSD卡U盘自动升级功能的需求、应用场景分析及其升级原理U-bootSD卡U盘升级功能的设计思路和实现细节，为后续工作------目 FAT文件系统支 MMC驱动移 使能USB 手动升级验证移植的USBOHCI驱 AutoUpdate详细设 图1-1U-boot下SD卡/U盘升级简要流程 图3-1函数运行过程

12.SDU3.4.1-1当同时插入SD卡和U盘时，若SD卡中没有有效升级包，则系统自动转入U盘升级，若SD卡中含有有效升级包直接使用SD卡中的升级包升级系统，不再扫描U盘中的内容。具体实现见内部函数实现”Hi3520D/Hi3515A/Hi3535/Hi3536U盘升级，不支持SD−−−−include/configs/−include/configs/−include/configs/−include/configs/−include/configs/−include/configs/hi3516a.h和 −include/configs/hi3536.h和include/configs/hi3536_spinand.h 下面以Hi3516A代码为例，说明各部分的相关作用*sdcard/usbstoragesystem #define1#ifdef#define1#define // #define1#define1**#ifdefCONFIG_AUTO_SD_UPDATE //SD卡驱动编译开关，受总开关#define#defineREG_BASE_MCI #defineCONFIG_HIMCI_V100#define#define #define**11112SDUSBOHCI支持SD卡升级或者U盘升级#define #define Hi3536代码为例，SDHi3516A代码为例，说明升级模块中各个子模Hi3536或Hi3516A的相关代码改为相应平台的代 【编译开关 FAT*sdcard/usbstoragesystem*#define #ifdef#define #define #define #define MMC* #ifdef#define#defineREG_BASE_MCI #defineCONFIG_HIMCI_V100#define#define #define

MMCCONFIG_AUTO_SD_UPDATE Hi3520D、Hi3515A、Hi3535、Hi3536SD卡，故不支持从SD**#define1#define1#define1#define#define1#define2

完成“2.2.1FAT文件系统支持”和“2.2.2MMCU-boot支mmcinfommcSD卡的相关命令。同理完成“2.2.1FAT文件系统支持”和“2.2.3USBOHCIUUSBOHCI驱动是的升级包到内存，烧写到Flash上的相应的位置即可。SD卡自动升级使用手册和移植说明.docfatloadmmc00x82000000kernelkernel0x82000000sfprobe0;sferase100000400000;sfwrite0x82000000100000400000;将内核烧写到SPI【烧写位置可以自行决定】或者直接bootm0x82000000启动新内核hisilicon#mmcinfoDevice:HIMCI_V100ManufacturerID:3OEM:5344Name:SD01GTranSpeed:25000000RdBlockLen:512SDversion2.0HighCapacity:NoCapacity:1015808000BusWidth:4-bithisilicon#fatlsmmchisilicon#fatloadmmc00x82000000readingkernel2902412bytesreadhisilicon#bootm##BootingkernelfromLegacyImageat82000000ImageName:Linux-ImageType:ARMLinuxKernelImage(uncompressed)DataSize: 2902348Bytes=2.8MiBLoadAddress:EntryPoint:80008000LoadingKernelImage...OKStartingkernelSD卡自动升级使用手册和移植说明.docusbstartUSBfatlsusb0Ufatloadmmc00x42000000kernelkernelsfprobe0;sferase100000600000;sfwrite0x42000000100000600000;将内核烧写到SPI（烧写位置可以自行决定）或者直接bootm0x42000000启动新内核hisilicon#usbstart(Re)startUSB... scanningbusfordevices...2USBDevice(s)scanningbusforstoragedevices...usb_stor_get_info-1StorageDevice(s)hisilicon#fatlsusb02902412kernel220236u-39495683file(s),0hisilicon#fatloadusb00x42000000kernelreadingkernel2902412byteshisilicon#bootm##BootingkernelfromLegacyImageat42000000ImageName:Linux-ImageType:ARMLinuxKernelImage(uncompressed)DataSize: 3941184Bytes=3.8MiBLoadAddress:EntryPoint:40008000LoadingKernelImage...OKStartingkernel计见3详细设计。int{#ifdef

#ifdefexternintdo_auto_update(void);#ifdefCFG_MMU_HANDLEOK #ifdefCFG_MMU_HANDLEOK#endif/*CONFIG_AUTO_UPDATE*/return0;}AutoUpdateImage*"StandalonePrograms"aredirectlyrunnableintheprovidedbyU-Boot;itisexpectedthat(iftheywell)youcancontinuetoworkinU-BootafterreturntheStandalone"OSKernelImages"areusuallyimagesofsomeEmbeddedOSwilltakeovercontrolcompletely.Usuallythesewillinstalltheirownsetofexceptionhandlers,drivers,setuptheMMU,etc.-thismeans,thatyouexpecttore-enterU-Bootexceptbyresettingthe"RAMDiskImages"aremoreorlessjustdatablocks,andparameters(address,size)arepassedtoanOSkernelthatbeing"Multi-FileImages"containseveralimages,typicallyan(Linux)kernelimageandoneormoredataimagesRAMDisks.ThisconstructisusefulforinstancewhenyoutobootoverthenetworkusingBOOTPetc.,wheretheserverprovidesjustasingleimagefile,butyouwanttoforinstanceanOSkernelandaRAMDisk"Multi-FileImages"startwithalistofimagesizes,imagesize(inbytes)specifiedbyan"uint32_t"inbyteorder.ThislististerminatedbyanImmediatelyaftertheterminating0followtheimages,oneone,allalignedon"uint32_t"boundaries(sizeroundedupamultipleof4bytes-exceptforthelast"FirmwareImages"arebinaryimagescontainingfirmwareU-BootorFPGAimages)whichusuallywillbeprogrammedflash"Scriptfiles"arecommandsequencesthatwillbeexecutedU-Boot'scommandinterpreter;thisfeatureisusefulwhenyouconfigureU-Boottousearealshellascommandinterpreter(=>Shell#define /*Invalid #defineIH_TYPE_STANDALONE1 /*StandaloneProgram #defineIH_TYPE_KERNEL2 /*OSKernelImage #defineIH_TYPE_RAMDISK3 /*RAMDiskImage #defineIH_TYPE_MULTI4 /*Multi-FileImage*/#defineIH_TYPE_FIRMWARE /*FirmwareImage*/#defineIH_TYPE_SCRIPT6 /*Scriptfile*/#defineIH_TYPE_FILESYSTEM7 /*FilesystemImage(anytype)*/#defineIH_TYPE_FLATDT8 /*BinaryFlatDeviceTreeBlob*/–/*indexofeachfileinthefollowingarrays*/#defineIDX_FIRMWARE0#defineIDX_KERNEL#defineIDX_ROOTFS/*max.numberoffileswhichcouldinterestus*/#defineAU_MAXFILES3#defineAU_FIRMWARE"u-boot"#defineAU_KERNEL #define /*pointerstofilenames*/char*aufile[AU_MAXFILES]={AU_FIRMWARE,autoupdatestruct{longstart;longend;/*layoutoftheFLASH.ST=startaddress,ND=endaddress.*/#defineAU_FL_FIRMWARE_ST0x0#defineAU_FL_FIRMWARE_ND0x7FFFF#defineAU_FL_KERNEL_ST0x100000#defineAU_FL_KERNEL_ND0x5FFFFF#defineAU_FL_ROOTFS_ST0x600000#defineAU_FL_ROOTFS_ND0xbFFFFF/*sizesofflashareasforeachfile*/longausize[AU_MAXFILES]={(AU_FL_FIRMWARE_ND+1)-AU_FL_FIRMWARE_ST,(AU_FL_KERNEL_ND+1)-AU_FL_KERNEL_ST,(AU_FL_ROOTFS_ND+1)-/*arrayofflashareasstartandendaddresses*/structflash_layoutaufl_layout[AU_MAXFILES]={{ {AU_FL_KERNEL_ST,AU_FL_KERNEL_ND,{AU_FL_ROOTFS_ST,AU_FL_ROOTFS_ND,/*wheretoloadfilesintomemory#defineLOAD_ADDR((unsignedchar/*theappisthelargestimage#defineMAX_LOADSZUflash上的步骤：1.SD卡/Uload到内存上。步骤2.从内存写到SPIflash上。每个升级所用的镜像的开头几个字节，都必须包含如下信息：（包括魔术字、crc校#defineIH_MAGIC 0x27051956/*ImageMagicNumber*/#defineIH_NMLEN 32/*ImageNameLength*/typedefstructimage_header{ ih_magic;/*ImageHeaderMagicNumber /*ImageHeaderCRCChecksum /*ImageCreationTimestamp*/ /*ImageDataSize /*DataLoadAddress /*EntryPointAddress /*ImageDataCRCChecksum*/uint8_tih_os;/*