M-system
http://www.m-systems.com/site/th-TH/Products/DiskOnChip/
在嵌入式系統或是X86系統中
多半使用NOR flash 作為儲存bootloader 或BIOS的地方
因為其有特殊XIP的特性
M-system DOC 也可作為開機區
其設計方式為 SRAM+NAND Flash
而H3這個系列的設計 已經可以達到1GB(128MB)-16GB(2GB)的大小
enhanced by msystems' proprietary TrueFFS(Ture Flash File System) embedded flash management software running as firmware on the flash controllor.
The major memory window.
Booting from mDOC H3
http://www.m-systems.com/site/th-TH/Products/DiskOnChip/
在嵌入式系統或是X86系統中
多半使用NOR flash 作為儲存bootloader 或BIOS的地方
因為其有特殊XIP的特性
M-system DOC 也可作為開機區
其設計方式為 SRAM+NAND Flash
而H3這個系列的設計 已經可以達到1GB(128MB)-16GB(2GB)的大小
enhanced by msystems' proprietary TrueFFS(Ture Flash File System) embedded flash management software running as firmware on the flash controllor.
- All mDOC H3 devices are ball to ball compatible. The replacement of one mDOC H3 device with another of a newer generation requires virtually no changes to the host.
- mDOC H3 has a 32KB Programmable Boot Block. This block provides eXecute In Place (XIP)functionality, enabling mDOC H3 to replace the boot device and to function as the onlynon-volatile memory device on-board.
- Boot Block(XIP):The Programmable Boot Block is 32KB in size.
- Boot Agent:Upon power-up or when the RSTIN# signal is de-asserted, the Boot Agent automatically downloads the Initial Program Loader (IPL) to the Programmable Boot Block.The IPL contains the code for starting the Host boot process.Once Embedded TrueFFS is loaded, executed and completed its media mount process, mDOC H3
is ready to be used as a fully functional storage device.
The major memory window.
Booting from mDOC H3- need
- Formatting mDOC H3
- Creating multiple partitions for different storage needs (IPL, Boot loader, OS images files,
and FAT partitions) - Programming the OS image file
Comments