Skip to content

Flash Storage Persistence

Jump to bottom
vintagepc edited this page Apr 22, 2023 · 3 revisions

For Releases/commits AFTER v0.9.6

If not specified, the machine(s) will automatically create and use default .bin files on disk for storage of EEPROM contents. To reset or clear these files, simply delete them. Typically:

  • [Machine]_xflash.bin
  • [Machine]_eeprom.bin
  • [Machine]_eeprom_sys.bin

You can manually specify alternate images or filenames. The legacy mtdblock and pflash methods described in the second section will continue to work, however, the preferred method is now with -drive arguments specifying a label - for example, -drive file=[filename],id=mini404-xflash,format=raw. Recognized IDs are:

  • mini404-xflash
  • mini404-eeprom
  • mini404-eeprom-sys
  • loveboard-eeprom (Mk4 only)

You can also use the Command Line Configurator to help generate the arguments you want to use.

For Releases/commits BEFORE v0.9.6

The onboard flash storage devices are persisted across reboots in memory, but not across machine shutdowns.

To back these files with a real file on disk, you will need to create the file and provide additional command line arguments.

The external SPI flash chip is 64 MBit (8 MByte). To create a file of this size, use truncate -s 8M [filename]. Then, pass in this filename with the mtdblock command: qemu-system-buddy [options] -mtdblock [filename].

The internal st25dv64k has two 64k blocks. These can be created using the above command with -s 8K instead. These are provided with two pflash arguments, e.g. qemu-system-buddy [options] -pflash file1.bin -pflash file2.bin

Clone this wiki locally