- 积分
- 18
- 实力分
- 点
- 金钱数
- 两
- 技术分
- 分
- 贡献分
- 分
|
马上注册,结交更多好友,享用更多功能,让你轻松玩转社区。
您需要 登录 才可以下载或查看,没有帐号?注册会员
x
4.3 RAM
16Mbytes of 70ns SRAM are integrated in Siemens SX1. This RAM is used by the application CPU and as a result is also shared by the applications and the Symbian OS.
RAM is visible for applications in the form of stack and heap spaces. The maximum stack and heap size is limited for each new process: around 2MB heap and 8K stack. This maximum is independent of the number of threads used. While a stack is allocated statically during initialization, the heap space is managed dynamically and starts with a minimum value. It is very important to keep in mind that the maximum heap size is only reached in very few cases. Applications are informed if memory resources are low. However, the system can close any application if it does not react to low memory warnings and continue to allocate memory.
There is no backup power supply for the RAM and the content will be lost if the device is switched off.
4.4 Flash ROM
Siemens SX1 uses flash ROM to store the system operating software and the user data, which should be retained in power-off states.
Flash ROM is divided into several areas and mapped to logical drives. Some of these are read-only; some have write permission. Symbian OS, Series 60 as well as most of the embedded applications reside on the "Z" drive. The flash ROM area of the "Z" drive supports the "execute-in-place" (XIP) feature. This allows system applications to be executed directly from the ROM address space. Other drives currently do not support XIP. All applications installed on any of these drives have to be loaded into RAM first and then executed. This fact should be considered by developers when designing the application runtime.
4.5 File system
The sections below provide information about the drives and files systems in the Siemens SX1, which can be used by 3rd-party applications. The data on any other drives should not be used or manipulated by 3rd-party applications. The content and the structure of this data can be changed without notice.
4.5.1 C drive
The C drive is read/write and located in flash ROM. This drive contains all user data as well as system and application data files. The content of the drive is retained if the device is switched off, though it can be re-initiated by the user via the "restore factory defaults" option in the system setup.
The total size of the drive is 4 Mbytes. Some 1.5 Mbytes are usually allocated by system applications, user PIM data as well as by a small number of sound and picture files.
Applications should not use or manipulate system data files, which are not documented in the SDK. The content and the structure of this data can be changed without notice. A good way to avoid this type of problem is to use documented APIs and avoid accessing the files directly.
The C drive is mapped to a directory in the PC file system in the emulator.
4.5.2 D drive
The D drive is a read/write virtual RAM drive. This drive contains temporary application and system data. The drive is re-initialized each time the device is powered on. The content of the drive is lost each time the device powers off.
The drive is allocated dynamically depending on current allocation requests. This is why the size of the allocated space is always about the same as the total size of the drive. Nevertheless, the maximum size of the drive is also limited by the size of the free RAM.
Siemens SX1 Technical Note for Application Developers Copyright ? 2003 Siemens AGAll rights reserved-10-
Information and Communication Mobile Hardware details for application developers Since the D drive resides in RAM, file read and write operations have a maximum speed in comparison to other drives. Applications should always use this drive for intensive file and caching operations. In some cases it may even make sense to create and write to a file on the D drive and, as soon as it is ready, to copy it to the C drive for permanent storage.
The D drive is mapped to a directory in the PC file system in the emulator.
4.5.3 E drive
The E drive is mapped to the MMC card and can contain arbitrary user data as well as installed applications and midlets.
The total and allocated sizes of the E drive correspond to the allocation of the MMC card being used. Application developers should be aware that their applications could be installed on the MMC card, which can be removed and may be replaced at any later time.
The E drive is mapped to a directory in the PC file system in the emulator. |
|