Hans

Considered your feedback @JoGei @andrewstevens-infineon! The default case (simple_mem_system.memseg_initelement_ =0) initializes each MemSeg with randomized values Otherwise, a specific uint8_t value is set to all elements in uint8_t* Array (set...

@wysiwyng @JoGei @PhilippvK Thank you for your feedback: I changed the `simple_mem_system.memseg_initelement_XX` element to a `string` type. The default behavior behavior (not specified attr) allocates a randomized `MemSegment`. (Documented with...

> Still missing a case to "not initialize anything" when `simple_mem_system.memseg_initelement_XX` is not present in the config. You can use `etiss::cfg().isSet` to check whether a value is present in the...

Maybe just related: I’ve been thinking about user-level emulation and wondering how to properly set up a working argc/argv stack. My idea was to allocate a custom memory region and...

Thank you both for the input/code snippet. I’ll probably implement a workaround by changing files on a hard-coded relative path to load different argv options. Regarding relative paths — do...

> Do you mean using the Semi-hosting file-I/O API to access a file holding argv? Sounds viable but my preference would be to implement a "pseudo-device file" like "SEMIHOST_CMDLINE:" in...