When developing microprocessors, the user writes machine programs as memory dumps in a file, and loads the file into a ROM before starting simulation. If RAM option "Read data on every simulation start" is selected, Antares remembers the path to the user's local file from which the memory dump has been imported, and loads the dump from that file every time the simulation is started.
After a while, the user has several machine programs he wants to execute. It would be nice if these memory dumps could be added as explicit project objects, just like circuits, truth tables, or images. The ROM component could then allow the user to select one of the available memory dumps from where content is loaded. This way, an Antares project with a microprocessor and various added machine programs would be self-contained and easier to distribute to other users.
When developing microprocessors, the user writes machine programs as memory dumps in a file, and loads the file into a ROM before starting simulation. If RAM option "Read data on every simulation start" is selected, Antares remembers the path to the user's local file from which the memory dump has been imported, and loads the dump from that file every time the simulation is started.
After a while, the user has several machine programs he wants to execute. It would be nice if these memory dumps could be added as explicit project objects, just like circuits, truth tables, or images. The ROM component could then allow the user to select one of the available memory dumps from where content is loaded. This way, an Antares project with a microprocessor and various added machine programs would be self-contained and easier to distribute to other users.
Source: #733, comment from May 5. by user fpw.