Memory

Parent Previous Next

Memory.inc


Memory.inc file and the memory-type IC-specific *.inc driver files include the following user-oriented procedures:


- TftBmpMemSet()

- TftBmpMemFormat()

- TftBmpFlashSectorErase()

- TftBmpSdToMem()

- TftBmpMemFileName()

- TftBmpFromMemName()

- TftBmpFromMemIndex()

- TftBmpFlashPageWrite()

- TftBmpFlashByteRead()

- TftBmpFlashWordRead()

- TftBmpFlashDwordRead()


Why might we want to include Flash memory in our design?


Flash memory can be used to store BMP image files that the system may need to display. For example, if the user wants a visually appealing screen menu with shadowed, rounded, or transparent buttons, these elements can be created as separate BMP files and rendered at the appropriate positions, for example this demo video and code: DEMO TOUCH MENU FROM FLASH MEMORY


Flash memory can also be used to save screen captures for later display. This is useful when dealing with dynamic content, such as real-time temperature, speed, or other changing data, where the user may want to save a full or partial screenshot.


Compared to SD cards, Flash memory offers faster read speeds and greater reliability. Users can transfer BMP files from an SD card into Flash memory for later use. Once stored, the files remain in Flash memory until it is explicitly formatted. Details on how this works are provided in the memory-related commands.


Including Flash memory in the design is optional, and if used, it can come in various sizes depending on the application requirements.


Note: Currently, only SPI Flash memory is supported, as EEPROMs typically have small capacities and varying architectures, especially when dealing with larger capacities (1, 2, 4 MB). However, I plan to include support for SPI EEPROMs in the future, time permitting.






Created with the Personal Edition of HelpNDoc: Simplify Your Help Documentation Process with a Help Authoring Tool