文件名称:S3C2440A_Nand_Bootloader
- 所属分类：
- 其他嵌入式/单片机内容
- 资源属性：
- [C/C++] [源码]
- 上传时间：
- 2012-11-26
- 文件大小：
- 93kb
- 下载次数：
- 0次
- 提 供 者：
- 詩*
- 相关连接：
- 无
- 下载说明：
- 别用迅雷下载，失败请重下，重下不扣分！
介绍说明－－下载内容均来自于网络，请自行研究使用
由于Nand Flash不能直接线性的访问，所以对于烧到Nand的上的程序，处理器无法直接执行，为了解决这个问题，S3C2440A在内部设置了地位于0x0000_0000容量为4Kbytes的SRAM，在处理器上电时会通过内部电路自动把Nand里头4k的程序（bootloader）装载到SRAM执行，这里称其为小程序，小程序执行后
再装载Nand里位于4K以后的大程序到SDRAM执行。-As Nand Flash can not directly access a linear, so for the burn process on the Nand of the processor can not be directly implemented, in order to solve this problem, S3C2440A set up in-house capacity for 4Kbytes located 0x0000_0000 the SRAM, the processor power through the internal circuitry will automatically Nand inside 4k program (bootloader) loaded into the SRAM implementation, here called applets, small program execution after the load Nand Village is located in a large 4K after the implementation of programs to SDRAM.
再装载Nand里位于4K以后的大程序到SDRAM执行。-As Nand Flash can not directly access a linear, so for the burn process on the Nand of the processor can not be directly implemented, in order to solve this problem, S3C2440A set up in-house capacity for 4Kbytes located 0x0000_0000 the SRAM, the processor power through the internal circuitry will automatically Nand inside 4k program (bootloader) loaded into the SRAM implementation, here called applets, small program execution after the load Nand Village is located in a large 4K after the implementation of programs to SDRAM.
(系统自动生成,下载前可以参看下载内容)
下载文件列表
MicroBoot\memcfg.s
.........\microboot.c
.........\MicroBoot_Data\DebugRel\ImageList.lst
.........\..............\........\MicroBoot.axf
.........\..............\........\MicroBoot.bin
.........\..............\........\ObjectCode\microboot.o
.........\..............\........\..........\runkernel.o
.........\..............\........\..........\startup.o
.........\..............\Release\ImageList.lst
.........\..............\.......\MicroBoot.axf
.........\..............\.......\MicroBoot.bin
.........\..............\.......\ObjectCode\microboot.o
.........\..............\.......\..........\runkernel.o
.........\..............\.......\..........\startup.o
.........\option.h
.........\option.s
.........\runkernel.s
.........\s3c2440.h
.........\s3c2440.s
.........\startup.s
.........\MicroBoot_Data\DebugRel\ObjectCode
.........\..............\Release\ObjectCode
.........\..............\Debug
.........\..............\DebugRel
.........\..............\Release
.........\MicroBoot_Data
MicroBoot
.........\MicroBoot.mcp
.........\........._Data\CWSettingsWindows.stg
.........\..............\Debug\TargetDataWindows.tdt
.........\..............\.....Rel\TargetDataWindows.tdt
.........\..............\Release\TargetDataWindows.tdt
.........\microboot.c
.........\MicroBoot_Data\DebugRel\ImageList.lst
.........\..............\........\MicroBoot.axf
.........\..............\........\MicroBoot.bin
.........\..............\........\ObjectCode\microboot.o
.........\..............\........\..........\runkernel.o
.........\..............\........\..........\startup.o
.........\..............\Release\ImageList.lst
.........\..............\.......\MicroBoot.axf
.........\..............\.......\MicroBoot.bin
.........\..............\.......\ObjectCode\microboot.o
.........\..............\.......\..........\runkernel.o
.........\..............\.......\..........\startup.o
.........\option.h
.........\option.s
.........\runkernel.s
.........\s3c2440.h
.........\s3c2440.s
.........\startup.s
.........\MicroBoot_Data\DebugRel\ObjectCode
.........\..............\Release\ObjectCode
.........\..............\Debug
.........\..............\DebugRel
.........\..............\Release
.........\MicroBoot_Data
MicroBoot
.........\MicroBoot.mcp
.........\........._Data\CWSettingsWindows.stg
.........\..............\Debug\TargetDataWindows.tdt
.........\..............\.....Rel\TargetDataWindows.tdt
.........\..............\Release\TargetDataWindows.tdt