Mirror of CollapseOS
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Virgil Dupras 6e714875dc zasm: Constants now override labels at all times 4 years ago
..
at28w Rename blockdev's API routines to GetB/PutB 4 years ago
basic Extract str.asm from core.asm and make core included by userspace 4 years ago
ed Extract str.asm from core.asm and make core included by userspace 4 years ago
lib lib/parse: decimal ending with a whitespace are now valid 4 years ago
memt zasm: rename #inc to .inc 4 years ago
sdct Rename blockdev's API routines to GetB/PutB 4 years ago
zasm zasm: Constants now override labels at all times 4 years ago
README.md basic: begin an implementation from sratch 4 years ago

README.md

User applications

This folder contains code designed to be “userspace” application. Unlike the kernel, which always stay in memory. Those apps here will more likely be loaded in RAM from storage, ran, then discarded so that another userspace program can be run.

That doesn't mean that you can't include that code in your kernel though, but you will typically not want to do that.

Userspace convention

We execute a userspace application by calling the address it's loaded into. This means: a userspace application is expected to return.

Whatever calls the userspace app (usually, it will be the shell), should set HL to a pointer to unparsed arguments in string form, null terminated.

The userspace application is expected to set A on return. 0 means success, non-zero means error.

A userspace application can expect the SP pointer to be properly set. If it moves it, it should take care of returning it where it was before returning because otherwise, it will break the kernel.

Apps in Collapse OS are design to be ROM-compatible, that is, they don't write to addresses that are part of the code's address space.