izaya/collapseos
1
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity
20151a97f8
collapseos/recipes/rc2014/sdcard/glue.asm

115 lines
2.0 KiB
NASM
Raw Normal View History

recipe/rc2014/sdcard: new recipe
2019-05-07 15:26:52 -04:00
; classic RC2014 setup (8K ROM + 32K RAM) and a stock Serial I/O module
; The RAM module is selected on A15, so it has the range 0x8000-0xffff
Use zasm in recipes
2019-05-20 11:00:14 -04:00
.equ RAMSTART 0x8000
.equ RAMEND 0xffff
.equ ACIA_CTL 0x80 ; Control and status. RS off.
.equ ACIA_IO 0x81 ; Transmit. RS on.
recipes/rc2014/sdcard: use BASIC shell
2019-12-11 11:18:32 -05:00
.equ USER_CODE 0xa000
recipe/rc2014/sdcard: new recipe
2019-05-07 15:26:52 -04:00
recipes/rc2014/sdcard: mount filesystem!
2019-05-28 13:13:34 -04:00
jp init ; 3 bytes
; *** Jump Table ***
jp printstr
sdc: add sdcPutC Wriiiiiite!
2019-06-01 19:53:42 -04:00
jp sdcWaitResp
jp sdcCmd
jp sdcCmdR1
jp sdcCmdR7
jp sdcSendRecv
recipe/rc2014/sdcard: new recipe
2019-05-07 15:26:52 -04:00
; interrupt hook
.fill 0x38-$
jp aciaInt
zasm: rename #inc to .inc scas, it's not needed any more.
2019-10-06 14:32:23 -04:00
.inc "err.h"
Move ASCII consts to ascii.h And made them shorter in name. The new ascii.h file allow reuse in userspace code.
2019-11-13 20:38:06 -05:00
.inc "ascii.h"
Make the shell a userspace app That's my mega-commit you've all been waiting for. The code for the shell share more routines with userspace apps than with kernel units, because, well, its behavior is that of a userspace app, not a device driver. This created a weird situation with libraries and jump tables. Some routine belonging to the `kernel/` directory felt weird there. And then comes `apps/basic`, which will likely share even more code with the shell. I was seeing myself creating huge jump tables to reuse code from the shell. It didn't feel right. Moreover, we'll probably want basic-like apps to optionnally replace the shell. So here I am with this huge change in the project structure. I didn't test all recipes on hardware yet, I will do later. I might have broken some... But now, the structure feels better and the line between what belongs to `kernel` and what belongs to `apps` feels clearer.
2019-11-15 15:37:49 -05:00
.inc "blkdev.h"
.inc "fs.h"
zasm: rename #inc to .inc scas, it's not needed any more.
2019-10-06 14:32:23 -04:00
.inc "core.asm"
Extract str.asm from core.asm and make core included by userspace Most of register fiddling routines (which is now the only thing contained in care.asm) are used by almost all userspace apps, often in inner loops. That makes the penalty of using jump tables for those a bit too high. Moreover, it burdens jump tables needlessly. Because this unit is very small (now that string routines are out), it makes sense to always include it in binaries.
2019-11-14 09:55:31 -05:00
.inc "str.asm"
Use zasm in recipes
2019-05-20 11:00:14 -04:00
.equ ACIA_RAMSTART RAMSTART
zasm: rename #inc to .inc scas, it's not needed any more.
2019-10-06 14:32:23 -04:00
.inc "acia.asm"
Use zasm in recipes
2019-05-20 11:00:14 -04:00
.equ BLOCKDEV_RAMSTART ACIA_RAMEND
recipes/rc2014/sdcard: add instructions to write to SD card
2019-06-02 11:53:36 -04:00
.equ BLOCKDEV_COUNT 2
zasm: rename #inc to .inc scas, it's not needed any more.
2019-10-06 14:32:23 -04:00
.inc "blockdev.asm"
parts/z80/sdc: add sdcInitialize Also, adjust SD card recipe. Straightforward initialization and read!
2019-05-08 16:03:54 -04:00
; List of devices
Rename blockdev's API routines to GetB/PutB The goal is to avoid mixing those routines with "character devices" (acia, vpd, kbd) which aren't block devices and have routines that have different expectations. This is a first step to fixing #64.
2019-10-30 16:59:35 -04:00
.dw sdcGetB, sdcPutB
.dw blk2GetB, blk2PutB
parts/z80/sdc: implement blockdev's GetC
2019-05-09 10:47:57 -04:00
parts/z80/sdc: add sdcInitialize Also, adjust SD card recipe. Straightforward initialization and read!
2019-05-08 16:03:54 -04:00
Use zasm in recipes
2019-05-20 11:00:14 -04:00
.equ STDIO_RAMSTART BLOCKDEV_RAMEND
stdio: remove a layer of indirection in GetC/PutC We use zasm's ability to use labels in .equ directive. We didn't do it before because for a while, we were in between scas and zasm (scas was used in automated tests) so we needed to use the lowest common denominator: zasm doesn't have macros and scas can't use labels in .equ directives. This forced us to add this layer of indirection. But now that we are completely cut from scas' dependency, we can use this nice zasm's ability.
2019-11-04 09:55:12 -05:00
.equ STDIO_GETC aciaGetC
.equ STDIO_PUTC aciaPutC
zasm: rename #inc to .inc scas, it's not needed any more.
2019-10-06 14:32:23 -04:00
.inc "stdio.asm"
stdio: de-macro-ize
2019-05-17 08:14:19 -04:00
recipes/rc2014/sdcard: mount filesystem!
2019-05-28 13:13:34 -04:00
.equ FS_RAMSTART STDIO_RAMEND
.equ FS_HANDLE_COUNT 1
zasm: rename #inc to .inc scas, it's not needed any more.
2019-10-06 14:32:23 -04:00
.inc "fs.asm"
recipes/rc2014/sdcard: mount filesystem!
2019-05-28 13:13:34 -04:00
recipes/rc2014/sdcard: use BASIC shell
2019-12-11 11:18:32 -05:00
; *** BASIC ***
; RAM space used in different routines for short term processing.
.equ SCRATCHPAD_SIZE 0x20
.equ SCRATCHPAD FS_RAMEND
Make the shell a userspace app That's my mega-commit you've all been waiting for. The code for the shell share more routines with userspace apps than with kernel units, because, well, its behavior is that of a userspace app, not a device driver. This created a weird situation with libraries and jump tables. Some routine belonging to the `kernel/` directory felt weird there. And then comes `apps/basic`, which will likely share even more code with the shell. I was seeing myself creating huge jump tables to reuse code from the shell. It didn't feel right. Moreover, we'll probably want basic-like apps to optionnally replace the shell. So here I am with this huge change in the project structure. I didn't test all recipes on hardware yet, I will do later. I might have broken some... But now, the structure feels better and the line between what belongs to `kernel` and what belongs to `apps` feels clearer.
2019-11-15 15:37:49 -05:00
.inc "lib/util.asm"
recipes/rc2014/sdcard: use BASIC shell
2019-12-11 11:18:32 -05:00
.inc "lib/ari.asm"
Make the shell a userspace app That's my mega-commit you've all been waiting for. The code for the shell share more routines with userspace apps than with kernel units, because, well, its behavior is that of a userspace app, not a device driver. This created a weird situation with libraries and jump tables. Some routine belonging to the `kernel/` directory felt weird there. And then comes `apps/basic`, which will likely share even more code with the shell. I was seeing myself creating huge jump tables to reuse code from the shell. It didn't feel right. Moreover, we'll probably want basic-like apps to optionnally replace the shell. So here I am with this huge change in the project structure. I didn't test all recipes on hardware yet, I will do later. I might have broken some... But now, the structure feels better and the line between what belongs to `kernel` and what belongs to `apps` feels clearer.
2019-11-15 15:37:49 -05:00
.inc "lib/parse.asm"
recipes/rc2014/sdcard: use BASIC shell
2019-12-11 11:18:32 -05:00
.inc "lib/fmt.asm"
.equ EXPR_PARSE parseLiteralOrVar
.inc "lib/expr.asm"
.inc "basic/util.asm"
.inc "basic/parse.asm"
.inc "basic/tok.asm"
.equ VAR_RAMSTART SCRATCHPAD+SCRATCHPAD_SIZE
.inc "basic/var.asm"
.equ BUF_RAMSTART VAR_RAMEND
.inc "basic/buf.asm"
.inc "basic/blk.asm"
.inc "basic/sdc.asm"
.equ BFS_RAMSTART BUF_RAMEND
.inc "basic/fs.asm"
.equ BAS_RAMSTART BFS_RAMEND
.inc "basic/main.asm"
.equ SDC_RAMSTART BAS_RAMEND
pgm: new kernel module The pgm module implements a shell hook so that when an unknown command is typed, we look into the mounted filesystem and look for a file with the same name as the command. If we find one, we load it in memory and run it.
2019-05-31 14:50:43 -04:00
.equ SDC_PORT_CSHIGH 6
.equ SDC_PORT_CSLOW 5
.equ SDC_PORT_SPI 4
zasm: rename #inc to .inc scas, it's not needed any more.
2019-10-06 14:32:23 -04:00
.inc "sdc.asm"
zasm: use blkdev IDs as input and output This will soon allow use to seek and tell on input, which is necessary for a second pass which is necessary for forward symbol references. This require making `blkSel` a bit more flexible. Rather than having one global selected blkdev, each app can select its own, in its own memory space.
2019-05-10 18:20:43 -04:00
init:
di
recipes/rc2014/sdcard: use BASIC shell
2019-12-11 11:18:32 -05:00
ld sp, RAMEND
recipes/rc2014/sdcard: add instructions to write to SD card
2019-06-02 11:53:36 -04:00
im 1
zasm: use blkdev IDs as input and output This will soon allow use to seek and tell on input, which is necessary for a second pass which is necessary for forward symbol references. This require making `blkSel` a bit more flexible. Rather than having one global selected blkdev, each app can select its own, in its own memory space.
2019-05-10 18:20:43 -04:00
call aciaInit
recipes/rc2014: add missing calls to fsInit Also, tighten RAM addresses. They were unecessarily loose.
2019-06-17 13:44:36 -04:00
call fsInit
recipes/rc2014/sdcard: use BASIC shell
2019-12-11 11:18:32 -05:00
call basInit
ld hl, basFindCmdExtra
ld (BAS_FINDHOOK), hl
zasm: use blkdev IDs as input and output This will soon allow use to seek and tell on input, which is necessary for a second pass which is necessary for forward symbol references. This require making `blkSel` a bit more flexible. Rather than having one global selected blkdev, each app can select its own, in its own memory space.
2019-05-10 18:20:43 -04:00
recipes/rc2014/sdcard: add instructions to write to SD card
2019-06-02 11:53:36 -04:00
xor a
blockdev: make selection structure opaque I'm about to change that structure and I don't want fs to be messed up by this. I'm proceeding step by step...
2019-06-04 09:56:36 -04:00
ld de, BLOCKDEV_SEL
recipes/rc2014/sdcard: add instructions to write to SD card
2019-06-02 11:53:36 -04:00
call blkSel
zasm: use blkdev IDs as input and output This will soon allow use to seek and tell on input, which is necessary for a second pass which is necessary for forward symbol references. This require making `blkSel` a bit more flexible. Rather than having one global selected blkdev, each app can select its own, in its own memory space.
2019-05-10 18:20:43 -04:00
ei
recipes/rc2014/sdcard: use BASIC shell
2019-12-11 11:18:32 -05:00
jp basStart
basFindCmdExtra:
ld hl, basFSCmds
call basFindCmd
ret z
ld hl, basBLKCmds
call basFindCmd
ret z
ld hl, basSDCCmds
jp basFindCmd
zasm: use blkdev IDs as input and output This will soon allow use to seek and tell on input, which is necessary for a second pass which is necessary for forward symbol references. This require making `blkSel` a bit more flexible. Rather than having one global selected blkdev, each app can select its own, in its own memory space.
2019-05-10 18:20:43 -04:00
recipes/rc2014/sdcard: mount filesystem!
2019-05-28 13:13:34 -04:00
; *** blkdev 2: file handle 0 ***
Rename blockdev's API routines to GetB/PutB The goal is to avoid mixing those routines with "character devices" (acia, vpd, kbd) which aren't block devices and have routines that have different expectations. This is a first step to fixing #64.
2019-10-30 16:59:35 -04:00
blk2GetB:
fs: adjust to DE->IX change in recipe/emul glue code
2019-06-02 10:18:03 -04:00
ld ix, FS_HANDLES
Rename blockdev's API routines to GetB/PutB The goal is to avoid mixing those routines with "character devices" (acia, vpd, kbd) which aren't block devices and have routines that have different expectations. This is a first step to fixing #64.
2019-10-30 16:59:35 -04:00
jp fsGetB
recipes/rc2014/sdcard: mount filesystem!
2019-05-28 13:13:34 -04:00
Rename blockdev's API routines to GetB/PutB The goal is to avoid mixing those routines with "character devices" (acia, vpd, kbd) which aren't block devices and have routines that have different expectations. This is a first step to fixing #64.
2019-10-30 16:59:35 -04:00
blk2PutB:
fs: adjust to DE->IX change in recipe/emul glue code
2019-06-02 10:18:03 -04:00
ld ix, FS_HANDLES
Rename blockdev's API routines to GetB/PutB The goal is to avoid mixing those routines with "character devices" (acia, vpd, kbd) which aren't block devices and have routines that have different expectations. This is a first step to fixing #64.
2019-10-30 16:59:35 -04:00
jp fsPutB
Reference in New Issue Copy Permalink